Headless is the most oversold architecture in e-commerce. The pitch — total design freedom, app-like speed, content everywhere — is real. So is the part that doesn’t make the pitch deck: you just volunteered to rebuild, and forever maintain, everything the Shopify theme layer gave you for free. Here’s the honest decision framework we use with brands considering Hydrogen or any Storefront API build.
What headless actually means on Shopify
You keep Shopify as the commerce engine — products, inventory, checkout, admin — and replace the theme storefront with your own frontend (Shopify’s Hydrogen/Remix stack, or Next.js and friends) talking to the Storefront API. Checkout stays on Shopify. Everything else — page rendering, navigation, search UI, cart state, SEO plumbing, analytics wiring — becomes your code.
What you genuinely gain
- Frontend freedom. Interactions, transitions and page architectures no theme can express — if your brand actually needs them.
- Content velocity. Pairing commerce with a real CMS (Sanity, Contentful) is the strongest argument: editorial teams get structured content workflows themes can’t match.
- Multi-surface reuse. One backend feeding web, apps and kiosks.
- Performance ceiling. Note: ceiling, not floor. A well-built headless store can be extremely fast; a badly built one is slower than a good Liquid theme — and we see both in the wild.
What you quietly lose
The theme layer is an enormous amount of free, battle-tested functionality: app integrations that “just work” (most Shopify apps inject into Liquid — headless means rebuilding or replacing each one), theme editor access for marketers (every copy change becomes a developer ticket unless you build CMS controls), automatic platform upgrades, and the ecosystem of themes, sections and snippets. You also acquire a permanent engineering dependency: headless isn’t a project, it’s a staffed capability. Budget the build at 3–6x a premium theme project and the maintenance at a part-time engineer minimum.
Run the two-question test. One: is there a specific, revenue-linked experience you cannot build in Online Store 2.0? Name it precisely — “feels more premium” doesn’t count; a configurator with live 3D preview does. Two: do you have (or will you fund) permanent engineering ownership? Two yeses: headless is a legitimate tool. Anything else: it’s an expensive way to make your marketing team file tickets.
The middle path most brands should take
Online Store 2.0 closed most of the gap that used to justify headless: sections everywhere, metaobjects for structured content, app blocks, and themes that hit excellent Core Web Vitals when built lean. The pattern we recommend for ambitious brands without an engineering org: a custom-built lean theme for the store, a headless content layer (blog, editorial, landing pages) where CMS workflows matter, and checkout extensibility for the conversion-critical customization. You get 80% of the headless upside at 30% of the cost — and your team can still edit the homepage on a Tuesday without a deploy.
If you do go headless, go in properly: Hydrogen on Oxygen hosting keeps you inside Shopify’s support surface, server-side rendering is non-negotiable for SEO, and the analytics/pixel wiring the theme did automatically must be rebuilt deliberately — it’s the most common thing we find broken in headless Shopify development audits.
Frequently asked questions
Is headless Shopify faster than a normal theme?
It has a higher ceiling but no guaranteed floor. Well-engineered headless outperforms themes; mediocre headless is slower than a lean 2.0 theme. Speed comes from engineering quality, not architecture.
How much does a headless Shopify build cost?
Realistically 3–6x a premium theme build upfront, plus permanent engineering maintenance. Most apps also need rebuilding or replacing, since they can’t inject into a custom frontend.
What is Shopify Hydrogen?
Shopify’s official headless framework — a Remix-based React stack with commerce components, hosted on Oxygen, Shopify’s edge runtime. If you go headless, it keeps you closest to platform support.
Can I get a custom design without going headless?
Almost always yes — Online Store 2.0 with a custom-built theme, metaobjects and checkout extensibility covers most brands’ design ambitions at a fraction of the cost, and marketers keep the theme editor.
The takeaway
Headless is a legitimate architecture for brands with a named, revenue-linked experience requirement and permanent engineering ownership — and an expensive mistake for everyone else. Name the thing you can’t build in Online Store 2.0 first. If you can’t, a lean custom theme plus a headless content layer gets you the experience without the standing engineering bill.