Headless commerce on Shopify is having a moment. Hydrogen + Oxygen are mature, the dev experience is genuinely good, and the case studies are out there. We've shipped Hydrogen storefronts and we'll keep shipping them — but most brands considering headless shouldn't go.
Here's the framework we use when a partner asks whether to go headless.
The cost of headless is mostly hidden
The first thing to understand about going headless is that the cost is not mostly upfront. The build is more expensive — call it 50–80% — but the bigger number is over the next three years.
When you go headless, you take ownership of:
- The whole storefront stack. Hydrogen is a Remix app you maintain. Updates, security patches, framework upgrades — all yours.
- Edge caching strategy. What gets cached, for how long, with what invalidation. Liquid handles this for you.
- Image optimization. Built into Liquid. You configure it in Hydrogen.
- A/B testing infrastructure. Liquid integrates trivially with Shopify's native experiments. Hydrogen — you bring your own.
- App ecosystem fit. Most apps drop a script tag into Liquid and it works. Hydrogen requires explicit integration. Your "install Yotpo and call it done" becomes "build the Yotpo integration."
If you've got the team and the budget for that, great. If you don't — and most brands don't — you're going to feel it in year two.
When Hydrogen is genuinely the answer
There are real cases where headless is the right call. We see four common ones:
1. Custom merchandising that Liquid can't express
If your brand requires presenting products in ways that Liquid's section/block model can't do — composable bundles assembled at request time, content-managed PDPs that pull from a separate CMS, dynamic personalization tied to logged-in user state — Hydrogen gives you the flexibility.
A perfumer we work with had a "build your own scent" experience that involved 12 selection steps, dynamic pricing based on combinations, and a recommendation layer that called into a separate ML service. Liquid would have collapsed under the complexity. Hydrogen handled it cleanly.
2. Content + commerce composition
If your storefront is half content, half product, and the content lives somewhere other than Shopify (Sanity, Contentful, custom CMS), Hydrogen's data fetching makes the composition clean. Pulling from two GraphQL endpoints in a single page is the natural Hydrogen pattern.
3. Internationalization beyond Markets
Markets handles a lot. If you've got requirements that exceed it — country-specific catalogs that aren't subsets, region-specific UX flows, content that varies by region beyond translation — Hydrogen gives you the routing and data-fetching to do it.
4. Performance at the bleeding edge
Hydrogen's edge runtime can outperform Liquid for certain shapes of storefront — especially product detail pages with heavy dynamic content. We've seen 200–400ms TTFB improvements on PDP at scale.
That said: if your Liquid TTFB is already under 600ms, you'll save more conversion ditching three marketing tags than going headless.
When Liquid is the right call
For most brands, the right answer is a clean Online Store 2.0 build on Liquid:
- You've got a marketing team that ships campaigns weekly. OS 2.0's section blocks are the difference between "marketing files a ticket" and "marketing ships."
- You're using Shopify-native tooling. Plus Markets, Audiences, Functions, Analytics — these all integrate more cleanly with Liquid than with headless.
- You're using off-the-shelf Shopify apps. Most apps are designed for Liquid first. Headless integrations exist but vary.
- Your dev team is small. Maintaining a Hydrogen app is a real ongoing cost. If you're not staffed for it, the cost shows up as "the storefront feels stale and we don't know how to ship the redesign."
The honest tradeoff for most brands
Most brands doing $5–50M ARR on Shopify Plus don't need headless. They need a clean OS 2.0 theme, a section library their marketers can ship from, a performance budget that's enforced in CI, and the right integration layer.
That's a 6–10 week build for most stores, and the result is a storefront that ships campaigns weekly without dev tickets. Headless gets you a more flexible storefront and a permanent engineering tax. Choose accordingly.
What we tell partners on the call
When a partner asks "should we go headless?" the conversation usually goes:
- What specifically can't you do today that you'd want to? (If they can't name three, the answer is no.)
- Who maintains the storefront in two years? (If the answer is "your agency," fine. If it's "us, but we're not sure how," the answer is no.)
- Is your performance ceiling actually limiting growth, or are you just told it is? (Real numbers, not vibes.)
- Are you using Shopify-native tools you'd lose access to? (Markets, Audiences, native A/B — these have headless paths but they're not zero-cost.)
If we get past those four and headless still looks right, we go headless. If not, the conversation becomes about a clean OS 2.0 build that does 90% of what they wanted at 50% of the cost — and they can always go headless later if the case actually shows up.
What changes this advice
Two trends would push more brands to Hydrogen:
- Shopify continuing to invest in headless tooling. The gap between "I install Yotpo on Liquid" and "I integrate Yotpo on Hydrogen" is closing every quarter.
- AI-driven personalization becoming table stakes. The composition flexibility of headless wins when half your PDP is dynamic.
We watch both. For now, our default is Liquid, and we say yes to Hydrogen when the case is real.