Is Headless Commerce Worth It? A Practical Guide
No7 Engineering Team
Growth Architecture Unit

Headless commerce is one of those terms that gets thrown around a lot. Agencies love to sell it, platforms love to promote it, and brands often wonder if they're missing out by not doing it. So let's cut through the noise.
What Headless Actually Means
In a traditional setup, your storefront and your backend are tightly connected. With headless, you separate them. The backend (Shopify, BigCommerce, whatever) handles products, orders, and payments. The frontend is a separate application—usually built with React, Next.js, or Shopify's Hydrogen framework.
This separation gives you more control over the user experience. You can build exactly what you want, without being constrained by theme limitations.
When It Makes Sense
Headless isn't for everyone. Here's when it genuinely adds value:
Complex User Experiences
If you need features that standard themes can't deliver—think 3D product configurators, complex filtering systems, or heavily personalised content—headless gives you the freedom to build them properly.
Performance Is Critical
Modern headless frameworks like Hydrogen and Next.js can deliver significantly faster page loads than traditional Liquid themes. If your store's speed is hurting conversions, this matters.
Multi-Channel Selling
When you're selling through multiple touchpoints—web, mobile app, kiosks, even IoT devices—having a decoupled backend that serves all of them makes life easier.
When It Doesn't
If your current theme does what you need, headless is probably overkill. It adds complexity, costs more to build and maintain, and requires more technical expertise to manage.
A well-optimised Liquid theme can be fast. A poorly-built headless site can be slow. The architecture doesn't guarantee better performance—execution does.
Complexity Comparison:
- Custom Liquid Theme: Lower complexity, faster to market, easier to maintain
- Headless Build (Hydrogen/Next.js): Higher complexity, more flexibility, requires dedicated development resources
- Ongoing Maintenance: Headless requires more technical expertise to maintain and update
Our Approach
We've built both. Plenty of Liquid themes, plenty of Hydrogen storefronts. Our recommendation depends entirely on what you're trying to achieve, not what sounds impressive on a proposal.
If you're curious whether headless is right for your specific situation, we're happy to have an honest conversation about it.
Adjacent reading: once you've decided headless is the right call, the next decision is the framework — see our engineering deep-dive on Catalyst vs Hydrogen for the trade-offs that actually matter in production.
Frequently Asked Questions
The questions buyers and engineers ask us most about this topic.
Is headless commerce worth it?
Only when your frontend requirements exceed what a theme can reasonably deliver — unique product configurators, deep personalisation, multi-channel content, or non-standard brand experiences. For most stores, a well-engineered Shopify Online Store 2.0 theme or BigCommerce Stencil build outperforms a poorly-executed headless implementation at a fraction of the cost and complexity. Headless makes sense when UX requirements, not ambition, demand it.
What does a headless commerce build actually cost?
Realistic ranges in 2026: £30,000 to £120,000 for a Catalyst (BigCommerce) or Hydrogen (Shopify) build with standard scope. Add £30,000 to £100,000 for multi-region, B2B, or custom configurator work. The hidden cost is ongoing engineering: a headless storefront needs at least 0.5–1 FTE of engineering attention indefinitely to keep up with API changes, performance regressions, and new features. Theme stores need a fraction of that.
When should I avoid going headless?
Avoid headless when your team has no in-house frontend engineers, when your roadmap is dominated by merchandising and operations work rather than UX, or when your annual GMV is under roughly £1M (the engineering overhead rarely pays back). Most stores below that threshold get more value from optimising a fast theme and integrating better apps than from a headless rebuild.