Shopify Sanity integration

Products visible in the CMS. The truth stays in Shopify.For teams that want to tie editorial content closely to the catalog and therefore want to see Shopify products directly in the CMS.

When the combination is worth it

Sanity stands out in one respect: instead of only referencing products, Shopify products can be mirrored into the CMS as documents. Editors see the catalog where they work and can attach content directly to products, without product data being maintained in the CMS.

That closeness is the actual reason for the combination and at the same time the place where discipline is needed. The mirrored products are a copy, not a second version of the truth. Prices, inventory and availability belong to runtime and come from Shopify, not from yesterday's CMS document.

Which objects run in which direction

Unlike most CMS connections, product data flows here as well, but only as a mirror for the editorial team.

Object	Direction	Leading system	Note
Products	Shopify →	Shopify	Shopify products are mirrored into the CMS as documents, not maintained there.
Content	→ Shopify	Sanity	Editorial content and blocks for the storefront.
Media	→ Shopify	Sanity	Images and videos from the media library of the CMS.
Prices	no sync	-	At runtime from Shopify, never from the mirrored document.
Inventory	no sync	-	Inventory is not a content topic.
Orders	no sync	-	Orders bypass the CMS.

Which integration pattern holds up

Product mirroring plus a storefront of your own
The route the combination was built for: products are mirrored into the CMS, content is attached to them, and the storefront renders both. Price and availability are fetched by the frontend from Shopify at runtime.
Content blocks in the Shopify theme
Shopify stays the storefront and loads individual content areas from Sanity. Less elegant than a storefront of your own, but considerably cheaper when only individual page types are affected.
Publishing instead of live requests
Write content into Shopify at approval time. That keeps the storefront fast and independent, which makes sense wherever content changes rarely but generates a lot of views.

Common pitfalls

Treating mirrored data as the truth
Rendering price and availability from the mirrored document leads to incorrect information on the page sooner or later. Those values belong to runtime and come from Shopify, however convenient the copy is.
Editorial product copy
If descriptions are written in the CMS while Shopify carries texts of its own, there are two versions of the same product. For customers, for search engines and for AI assistants, that is the worst of all states.
Underestimating your own storefront
A frontend of your own means your own deployment, your own responsibility for performance and your own SEO duties including redirects. That is doable, but it is a product, not a leftover task at the end of a project.

Frequently asked questions

Are products maintained in Sanity?

No. They are mirrored from Shopify so that editors can see them in the CMS and attach content to them. Product data is still maintained in Shopify or in a PIM. The mirror is a copy, not a source of truth.

Where do price and availability on the page come from?

From Shopify at runtime, through the storefront interface. The mirrored document in the CMS always reflects an earlier state. Anyone rendering prices from it will show wrong figures at some point, and risk complaints when the checkout shows a different number.

Do I need my own storefront for this?

Not necessarily, but that is where the combination shows its strength. For individual page types, Shopify can stay the storefront and pull content from Sanity. The full interlocking of content and catalog only pays off with a frontend of your own.

Who is responsible for SEO?

The system that serves the page. With a storefront of your own, that storefront takes on the whole set: titles, descriptions, structured data, redirects and hreflang. If Shopify stays the storefront, those fields belong there and are filled from the CMS during publishing.

How much work is involved?

The product mirroring itself is manageable. The effort sits in the frontend and in the content model: which blocks exist, how they relate to product pages and who maintains what. Clarifying that takes longer than the technical connection itself usually does.

Shopify Contentful integrationFor brands with their own content team that wants to maintain landing pages and campaigns without working in the store back end.View integration Shopify Storyblok integrationFor teams that want to build landing pages themselves and see how the page looks while doing it, without development work for every campaign.View integration Shopify Pimcore integrationFor companies that model their product data in Pimcore and put Shopify in front as the sales channel instead of running their own store.View integration

System integration: patterns and data ownershipThe overarching view of ERP, PIM, WMS and middleware.