Go headless on Shopify only when you have a requirement a theme can’t meet and a development team to own the result. For most stores, a customized premium theme or a custom Online Store 2.0 theme delivers the speed and flexibility they need at a fraction of the cost and risk. Headless pays off for brands running multiple storefronts, content-led experiences or app-like interactions, at a scale where a permanent engineering budget makes sense.
Three build options: premium theme, custom theme, headless
Every Shopify build sits on a ladder. Each rung buys flexibility and costs more to build and to run.
- Customized premium theme. You license a theme from the Shopify Theme Store for a one-time fee, configure it in the theme editor and add targeted code changes.
- Custom Online Store 2.0 theme. A developer builds a Liquid theme around your brand, with your own sections, templates and metafield-driven content. It still runs on Shopify and works with the theme editor and app blocks.
- Headless. Shopify keeps running products, inventory, orders and checkout, but the storefront customers see is a separate application that pulls data through the Storefront API and runs on its own hosting.
| Customized premium theme | Custom OS 2.0 theme | Headless | |
|---|---|---|---|
| Front end | Shopify-hosted Liquid | Shopify-hosted Liquid | Separate app (Hydrogen, Next.js or similar) |
| Who edits pages | Marketing, in the theme editor | Marketing, in the theme editor | Developers, plus a headless CMS if you add one |
| App compatibility | Most apps plug in | Most apps plug in | Storefront apps need an API or headless SDK |
| Typical build cost (rough range) | $5,000-$20,000 | $20,000-$75,000 | $75,000-$250,000+ |
| Typical time to launch | Weeks | 2-4 months | 4-9 months |
| Ongoing cost | Low | Moderate | High: dedicated or retained engineers |
Costs and timelines are rough ranges, not quotes; scope moves them a lot. The pattern holds: each rung multiplies both build and upkeep.
When a customized theme stops being enough
Good premium themes are fast and flexible. Move up a rung because of friction you can name, not a wish to look modern.
Signs you’ve outgrown a premium theme
- Every new landing page needs a developer to work around the theme’s section limits.
- Code edits have piled up to the point where you can’t apply theme updates without breaking something.
- Your product data needs displays the theme can’t handle: bundles, configurators, comparison tables, spec sheets driven by metafields.
- You’ve installed several apps just to add layout features a custom section would do better.
Signs you’ve outgrown a custom theme
- You need several storefronts from one catalog with genuinely different experiences, beyond the prices and languages Shopify Markets handles.
- Content and commerce are merged: editorial, lookbooks and interactive guides your content team wants to manage in a real CMS.
- You need app-like interactions, such as complex configurators or account-driven experiences, that fight Liquid’s page-by-page model.
- The same product data must feed a website, a mobile app and in-store screens.
- You’ve already fixed apps, scripts and media, and still hit a measurable performance ceiling.
If speed is the main reason and the basics aren’t fixed, stop there. Most slow Shopify stores are slow because of apps, third-party scripts and heavy media, which follow you to headless. Fix them first with these Shopify speed fixes.
What headless actually changes on Shopify
Going headless replaces one layer of the stack, not the platform.
- Stays on Shopify: products, inventory, pricing, discounts, orders, customers, Markets, the admin and checkout. Your storefront builds the cart through the API, then hands the buyer to Shopify’s checkout.
- Moves into your code: every page template, navigation, search and filtering, cart, account pages, meta tags, structured data, sitemaps, redirects and analytics events.
- Goes away: the theme editor as a page builder, and everything an app used to inject into your Liquid theme.
That last point causes most of the surprises.
Benefits that are real
A higher performance ceiling
A modern front end lets you control exactly what reaches the browser: server rendering, streaming, edge caching and no unused theme code. Note the word ceiling. A disciplined Liquid theme is fast too, and a headless build carrying the same tag manager and widgets won’t be.
Content flexibility
Pairing Shopify with a headless CMS such as Sanity, Contentful or Storyblok gives your content team structured, reusable content that isn’t tied to theme templates, which matters when storytelling sells the product.
Multiple storefronts, one backend
One Shopify backend can feed several front ends: separate brand sites, a campaign microsite, a mobile app. Shared components and one catalog make each new surface cheaper than the last.
Engineering control
Developers get reusable components, automated tests and a preview deployment for every change. With a real engineering team, that’s a gain; without one, it’s a liability.
Costs teams underestimate: apps, checkout and maintenance
Apps
Apps that run in the admin, checkout or back office keep working. Storefront apps that add blocks or scripts to a Liquid theme don’t render on a headless storefront. Reviews, subscriptions, loyalty, upsells, search, back-in-stock alerts: each needs an API or headless SDK, plus a developer to build its interface. Audit every storefront app before you scope; each one without headless support is a rebuild, a replacement or a lost feature.
Checkout
Headless doesn’t free you from Shopify’s checkout. You customize it the same way a theme store does, and the deepest options depend on your plan. If a custom checkout is your reason for going headless, it’s a plan question, not an architecture question; see Shopify vs Shopify Plus.
Tracking, consent and SEO
On headless you rebuild the event layer (page views, add to cart, checkout start, ad pixels), consent handling, canonical tags, structured data, sitemaps and redirects. Mistakes here quietly cost organic traffic or the conversion data your ad platforms bid on.
Dependence on developers
When marketing can’t change a banner or launch a landing page without a ticket, campaigns slow down. A CMS with a visual editor helps, but it’s another license and integration to maintain.
Maintenance
You now own framework and dependency upgrades, hosting, monitoring and Storefront API versions, which Shopify releases regularly and retires over time. A theme store leaves most of this to Shopify, so budget monthly engineering hours for headless, not just the build.
Hydrogen vs other front-end frameworks
Hydrogen is Shopify’s React-based framework for headless storefronts, and Oxygen is Shopify’s hosting for it. The most common alternative is Next.js with the Storefront API; teams also use Nuxt or Astro.
| Hydrogen + Oxygen | Next.js (or similar) + Storefront API | |
|---|---|---|
| Maintained by | Shopify | Framework vendor; the Shopify integration is yours |
| Shopify building blocks | Built in: cart, product, pricing, analytics and SEO utilities | Starter kits and libraries, or built by your team |
| Hosting | Oxygen, included on most paid Shopify plans | Your choice of host; you manage caching and cost |
| Best when | Shopify is your only commerce backend and you want the shortest path | Your team already runs Next.js, or the site blends Shopify with other systems |
| Watch out for | Tighter coupling to Shopify’s way of doing things | More integration work and more pieces to keep in sync |
My rule: pick the framework your team, or the team you’ll retain, already knows. Who maintains the storefront in two years matters more than the framework.
A lower-risk path: hybrid and partial headless
You don’t have to move the whole store at once.
- Headless content, theme commerce. Keep collections, product pages and cart on your Liquid theme, and build the content-heavy area (editorial, guides, lookbooks) as a separate front end on a subdomain or edge-routed paths. Commerce stays app-compatible; content gets flexibility.
- A headless microsite. Launch a campaign site or second brand headless on the same Shopify backend, so your team learns the stack with limited downside.
- Structured content inside the theme. Model content with metaobjects and metafields, then render it in custom Online Store 2.0 sections. You get much of a CMS’s structure without leaving Liquid.
- Theme now, headless later. Build a custom theme on a structured data model today. If you go headless later, the data model carries over and the move is a front-end rebuild, not a replatform.
Hybrid has its own cost: two front ends mean two headers, footers and tracking setups to keep in sync. Run it as a pilot with an end date and set the metrics that would justify going fully headless, such as conversion rate, page speed or content shipped per week.
Decision checklist by revenue, catalog and team
These are my working rules of thumb, not industry benchmarks. Team capacity and specific requirements matter more than revenue.
| Situation | Usually the right build |
|---|---|
| Under roughly $1M online revenue, standard catalog, no in-house developers | Customized premium theme |
| Roughly $1M-$20M, brand-led design or complex product data, agency or freelance developers | Custom Online Store 2.0 theme |
| Above roughly $20M, multiple storefronts or content-led experience, in-house engineers | Headless or hybrid |
Before approving a headless build, check:
- You can name the requirement a custom theme can’t meet, and it’s tied to revenue
- App bloat, third-party scripts and heavy media on the current store are already fixed
- Every app you depend on has an API or headless support, or replacements are budgeted
- You have in-house or retained engineers for ongoing work, not just the build
- Marketing accepts a CMS workflow in place of the theme editor, and the CMS is budgeted
- Tracking, consent and SEO migration are in scope, each with a named owner
- The business case covers the build plus at least two years of maintenance
- You’ve considered a hybrid or microsite pilot first
If the first or fourth box stays unchecked, a custom theme is the better investment. This is the first conversation in most of my Shopify development projects: choose the lowest rung that meets the requirement, and build it so the next rung is easy.
Get it built
Not sure which build your store needs? I’ll review your theme, apps and data model, recommend the right rung, then build it. Shopify builds and migrations start from $6,000. See pricing or get in touch.