Every quarter we talk to brands considering headless commerce. And every quarter, about half of them shouldn't do it — at least not yet. Hydrogen is Shopify's official React-based headless framework, and it's genuinely excellent. But headless comes with real costs that aren't always apparent until you're six months into a build.
This is the decision framework we use internally with every enterprise client who asks us whether to go headless.
What Is Hydrogen and Why Does It Exist?
Hydrogen is Shopify's official framework for building headless storefronts using React, Remix, and the Storefront API. Instead of rendering pages on Shopify's servers using Liquid templates, Hydrogen decouples the frontend entirely — you build the UI yourself using modern React, query Shopify's backend via API, and deploy to Oxygen (Shopify's global edge hosting) or any other hosting provider.
Shopify built Hydrogen because large, sophisticated brands needed frontend freedom that Liquid couldn't provide: custom performance optimisations, deeply custom checkout flows, integration with content platforms like Contentful or Sanity, and the ability to run their storefront as part of a broader digital experience — not just a shop page on a generic template.
The Real Costs of Going Headless
Before we get to when headless makes sense, it's worth being honest about what it costs:
- Engineering cost: A Hydrogen build costs 2–4x more than an equivalent Liquid build. You need React engineers, not just Liquid/Shopify developers.
- Ongoing maintenance: Every Shopify feature (new checkout components, Shopify Markets, Shop Pay updates) requires engineering work to integrate in headless. In Liquid, many of these just work.
- App compatibility: Most Shopify apps don't support headless out of the box. You'll spend significant time either building custom integrations or avoiding entire app categories.
- Time to launch: A Hydrogen storefront typically takes 3–4 months longer than an equivalent Liquid build, depending on complexity.
The honest calculus: Headless is the right answer when the limitations of Liquid are genuinely blocking business goals — not when it sounds technically impressive.
When Headless Is the Right Call
There are clear scenarios where Hydrogen earns its cost premium:
- Deeply custom editorial experiences: Luxury brands that need rich content experiences — video-first landing pages, editorial storytelling, interactive lookbooks — that Liquid sections can't deliver without painful workarounds.
- Multi-region, multi-channel architectures: Brands selling across 10+ markets, multiple languages, and channels (web, mobile app, in-store kiosk) benefit from a single React component library that renders across all surfaces.
- Performance at massive scale: When your catalogue is 50,000+ SKUs and your peak traffic is millions of concurrent sessions, the fine-grained caching and edge delivery of a Hydrogen build can provide measurable performance uplift that translates directly to conversion rate.
- Complex integrations with existing systems: Brands with an existing ERP, PIM, or OMS that needs tight API integration often find headless gives them the flexibility to build exactly the integration layer they need.
When Standard Shopify (Liquid) Is the Better Choice
For the majority of Shopify Plus brands — even sophisticated ones — a well-built custom Liquid theme delivers better ROI:
- You want to go live in 8–10 weeks, not 16–20
- Your app stack relies on review apps, loyalty tools, or subscription platforms that don't yet support headless
- Your team doesn't have in-house React engineers to handle ongoing maintenance
- Your conversion challenges are UX and content problems, not Liquid limitation problems
The Comparison
| Factor | Liquid (Standard Shopify) | Hydrogen (Headless) |
|---|---|---|
| Time to launch | 8–12 weeks | 16–24 weeks |
| Build cost | £30K–£80K | £80K–£200K+ |
| App ecosystem | Full compatibility | Limited, custom integration |
| Maintenance complexity | Low–Medium | High |
| Frontend flexibility | Good | Unlimited |
| Performance ceiling | High (with optimisation) | Very high |
Our Recommendation Process
When a client asks us about Hydrogen, we work through a three-part diagnostic:
- Identify the constraint: What specifically can't you do in Liquid that you need to do? If the answer is vague ("we want more flexibility"), it's not a Hydrogen problem.
- Evaluate the real cost: Model the full cost — build, maintenance, integrations — against the revenue opportunity the headless capability would unlock.
- Assess internal capability: Who owns the frontend post-launch? If there's no in-house React capability, the ongoing maintenance cost will be prohibitive.
Most brands that come to us asking for Hydrogen end up with a high-performance custom Liquid build that solves their actual problems — faster, cheaper, and with a better app ecosystem. A handful genuinely need headless, and for those we build Hydrogen.
If you want a frank assessment of which is right for your situation, book a scoping call. No pitch — just an honest answer.