Documentation Index
Fetch the complete documentation index at: https://docs.frontic.com/llms.txt
Use this file to discover all available pages before exploring further.
The Shopify connector syncs your Shopify store’s catalog and content into Frontic. Variants are denormalized into separate records with parent links preserved, and the connector covers four resource types — products, blogs, pages, and metaobjects — so you can build product, content, and structured-data experiences off the same backbone.
Auth
Access Token
Update methods
Polling
Resources
Products, Blog, Pages, Metaobjects
What you get
Products
Variants split into separate records, parent links preserved. Per-variant fetch fills in inventory and price detail.
Blog
Blog articles by blog ID — pick which blog feeds the storage when you create the feed.
Pages
Shopify pages — about, contact, custom marketing pages.
Metaobjects
Shopify metaobjects for structured custom data — lookbooks, ingredient lists, store locations.
Connection settings
Your Shopify store domain, e.g.
https://my-shop.myshopify.com.The Shopify app’s API key.
The Shopify app’s API secret key.
The admin API access token granted to your app for the store.
unknown until the first sync runs successfully — at which point it flips to connected. Auth failures surface their reason on the indicator after a sync attempt.
Channels
A Shopify channel in Frontic carries which translations the connector pulls per record.A label for the channel in Frontic.
Locale keys the connector pulls per record.
The translation used when a value is missing in another locale.
Data Feeds
The Shopify connector exposes four feed types:| Feed | What it pulls | Per-feed config |
|---|---|---|
| Products | All products with variants split into separate records, parent-child links preserved. | — |
| Blog | Articles from a specific blog. | Blog ID (required) |
| Pages | Shopify pages. | — |
| Metaobjects | Structured custom data — lookbooks, store locations, etc. | — |
Blog feed config
The Shopify blog ID this feed reads from. Find it in Shopify admin under Online Store → Blog posts — the blog’s ID is in the URL when you open the blog’s settings.
What the data looks like
Variants
Shopify always exposes products and variants as a parent/children pair, so the connector mirrors that: every product becomes a parent record (emptyparentId), and every variant becomes its own record with parentId set to the product. Even single-variant products produce two records — one parent plus one variant — because that’s the structure Shopify itself returns. See Product Models for how this composes at the API layer.
For each variant, the connector issues a dedicated Shopify API call to fetch full variant detail (inventory, pricing, options) and merges it into the variant record on top of the parent’s payload. This makes large catalogs cost more requests against Shopify’s rate limit than a flat product fetch would — keep it in mind when configuring polling schedules on bigger stores.
Schema auto-derivation
Shopify product payloads are rich JSON. As records arrive on the feed, Frontic’s auto-schema fills in the field list for you — no need to declare every Shopify field up front in the wizard’s Schema step. See feed schema in the overview.Good to know
- No companion app. Setup is direct: create a Shopify app or private API client, copy the credentials in. There’s no Frontic-side app you install in Shopify.
- Per-variant fetch. Fetching variant detail issues one request per variant under the hood — large catalogs benefit from polling schedules on the Shopify rate-limit side.
- Custom fields & metafields. Standard product fields come through resolved; metafields land on the raw payload. Map them in your Data Sync.
Related
Product Models
How Shopify’s parent products and variants compose at the API layer.
Shopware
A fully-fledged commerce-platform connector — companion plugin, end-to-end onboarding.