# Sanity and Shopify: a headless CMS beside your catalog.

> We model editorial content in Sanity alongside Shopify’s catalog, for content-led brands on a headless storefront. Products, prices and stock stay in Shopify; stories, campaigns and pages live in Sanity, with preview and visual editing for marketers. It starts with a fixed-fee Readiness Assessment.

Headless commerce · Sanity and Shopify

- **Starts with:** A fixed-fee Readiness Assessment
- **Typical build:** Content model first, then the storefront, phased
- **You own:** The schema, the Sanity Studio and the code

## When does a Shopify brand need Sanity?
- Campaigns, lookbooks and stories have outgrown product descriptions and a blog.
- Editors wait on developers to publish pages the theme editor cannot build.
- The same content feeds several storefronts, markets, languages or an app.
- Content is copied by hand between Shopify, a CMS and other tools.
- Editors need drafts, review and scheduled releases before anything goes live.

## How do we set up Sanity with Shopify?
1. **Audit the content** — Every page type, field and owner, and where each lives today.
2. **Model it** — Schemas in code, with products referenced from Shopify, not retyped.
3. **Connect the catalog** — Products sync from Shopify for editors to reference; Shopify stays the source.
4. **Build the editing** — Preview and visual editing on the real storefront, before anything publishes.
5. **Migrate and train** — Existing content moved, editors trained, and the model documented.

## A content model your editors can work in.
- A Sanity content model, versioned in your repository
- A Sanity Studio configured for your editors
- Products synced from Shopify, referenced in content
- Preview and visual editing on the real storefront
- Localised content, where you sell in several languages
- Existing content migrated and checked
- An editor guide and a documented schema

## What usually goes wrong
- **Copying product data into the CMS.** — Shopify stays the source for products, prices and stock.
- **Modelling pages instead of content.** — Reusable content types outlast any single page design.
- **Editors locked out of preview.** — Visual editing is built in from the start.
- **Ignoring metaobjects when they would do.** — Some content belongs in Shopify, close to products.

## The studio’s own platform runs on Sanity.

Our website, client portal, admin and concept previews are one Next.js 16 platform with Sanity and Postgres, deployed on Vercel. The studio runs on what it recommends.

## Questions
### Should we use Sanity or Shopify metaobjects?

Metaobjects suit structured content close to products, such as ingredients, size guides or specifications, and they work in a theme. Sanity suits editorial teams, rich pages, drafts and content shared across surfaces. Many headless stores use both, with a clear rule for what lives where.

### How do products get into Sanity?

Products and collections sync from Shopify into Sanity, so editors can reference them in stories and pages. Shopify remains the source of truth for products, prices and stock. Editors add the context around them, not a second catalog.

### Can marketers preview before publishing?

Yes. Editors see drafts on the real storefront before they publish, and can click from the page to the field that renders it. Related changes can be grouped, so a campaign goes live together.

### Does Sanity work with Hydrogen and Next.js?

Yes, with preview and visual editing on both. Hydrogen on Oxygen or Next.js on Vercel depends on the rest of your stack, and Shopify checkout stays native either way. The Readiness Assessment compares them with a two-year cost.

### Who owns the content model?

You do. The schema lives in your repository, the Sanity project sits in your account, and the editor guide explains how to extend it, so another team can pick it up without us.

[Request a Readiness Assessment](https://www.studioantipodes.com/start-a-project)