Headless commerce has been one of the most hyped concepts in ecommerce technology over the past few years. The promise is compelling: complete frontend freedom, blazing performance, and the ability to deliver custom experiences across any channel. The reality is more nuanced.
For UK ecommerce brands evaluating whether to go headless with Shopify or stick with traditional Liquid themes, the decision is not about which approach is technically superior — it is about which approach delivers the best business outcome for your specific situation, budget, and team.
I have built stores using both approaches and have strong opinions about when each makes sense. This comparison is honest about the trade-offs of both.
What headless actually means
In a traditional Shopify setup, the storefront (what customers see) and the backend (product management, orders, inventory) are tightly coupled. Your theme uses Shopify's Liquid templating language and runs on Shopify's servers. The two are inseparable.
In a headless setup, the storefront is decoupled from the backend. Shopify continues to handle all commerce logic — products, orders, payments, inventory — through its Storefront API and Admin API. But the storefront is built as a separate application, typically using a JavaScript framework like React (via Shopify Hydrogen) or Next.js. This separate application communicates with Shopify's backend through APIs.
The headless storefront can be hosted anywhere, built with any technology, and designed with complete creative freedom. You are no longer constrained by Shopify's theme architecture — but you are also no longer benefiting from its simplicity.
Shopify Hydrogen and Oxygen
Shopify's answer to headless commerce is Hydrogen — a React-based framework designed specifically for building custom Shopify storefronts. Hydrogen includes pre-built components for common ecommerce patterns (product cards, cart drawers, variant selectors), hooks for interacting with Shopify's APIs, and utilities for managing commerce data.
Oxygen is Shopify's hosting platform for Hydrogen storefronts. It provides global edge deployment, meaning your headless storefront runs on servers close to your customers worldwide. Oxygen is included with Shopify plans that support headless, eliminating the need to manage separate hosting infrastructure.
The Hydrogen/Oxygen combination addresses two of the biggest traditional headless challenges: it provides a Shopify-native development framework (rather than building everything from scratch) and managed hosting (rather than configuring your own infrastructure).
For more on Shopify's theme architecture, see our custom theme development guide and our comparison of OS2.0 vs custom themes.
Traditional Liquid: the strengths
Before diving into headless benefits, it is worth acknowledging what traditional Shopify Liquid themes do exceptionally well:
- Simplicity. The theme editor allows non-technical users to manage content, layouts, and design. No developer needed for routine changes.
- App ecosystem. The Shopify App Store has 10,000+ apps that integrate directly with Liquid themes through app blocks and script tags. Most of this ecosystem does not work with headless storefronts.
- Checkout. Traditional Shopify themes use Shopify's hosted checkout, including Shop Pay. This checkout has been optimised across billions of transactions.
- Speed to market. A traditional Shopify store can be launched in weeks. A headless build typically takes months.
- Lower maintenance. Shopify handles hosting, CDN, SSL, and platform updates. With headless, you manage more of this yourself.
- Broader developer pool. More developers know Liquid than Hydrogen. Finding and hiring is easier and cheaper.
Performance comparison
The performance claim for headless is that JavaScript frameworks with server-side rendering can deliver faster page loads and smoother interactions than server-rendered Liquid templates. In theory, this is true. In practice, the difference is often smaller than expected.
A well-optimised Liquid theme (like Dawn) scores 90+ on Google PageSpeed Insights. A well-built Hydrogen storefront can achieve similar or slightly better scores. But a poorly built Hydrogen storefront can score much worse because JavaScript frameworks introduce their own performance challenges — large bundle sizes, hydration delays, and rendering complexity.
The performance advantage of headless is real but conditional on the quality of the implementation. For most ecommerce use cases, the performance difference between a well-built Liquid theme and a well-built Hydrogen storefront is not significant enough to justify the additional cost and complexity. For Shopify performance optimisation strategies, see our guide on Shopify checkout optimisation.
Cost comparison
| Component | Traditional Liquid | Headless (Hydrogen) |
|---|---|---|
| Initial build | £15,000-£40,000 | £40,000-£150,000+ |
| Hosting | Included with Shopify | Oxygen included or £200-£500/mo |
| Annual maintenance | £2,000-£6,000 | £8,000-£24,000 |
| Developer hourly rate | £50-£120 | £80-£180 |
| CMS integration | Not needed | £5,000-£20,000 (for external CMS) |
Headless is substantially more expensive — typically 2-5x the cost of a traditional build. This is driven by the additional development complexity, the need for more specialised (and expensive) React/JavaScript developers, and the ongoing maintenance of a custom application.
Developer requirements
Traditional Liquid development requires knowledge of Shopify's Liquid templating language, HTML, CSS, and JavaScript. These are widely understood skills, and the UK has a large pool of Liquid developers.
Headless development requires React (or another JavaScript framework), GraphQL, server-side rendering, edge computing concepts, and API architecture. These are more specialised skills, and developers who possess them command higher rates. Finding a Shopify Hydrogen developer in the UK is more challenging and more expensive than finding a Liquid developer.
For Shopify development projects, the developer skill requirement should factor into your architecture decision.
SEO implications
Headless storefronts can handle SEO well if properly implemented — server-side rendering ensures search engines receive fully rendered HTML. However, there are additional SEO considerations:
- You must manually implement structured data, meta tags, sitemaps, and canonical URLs
- Shopify's built-in SEO features (automatic sitemaps, canonical handling, etc.) do not apply to headless storefronts
- URL routing must be manually configured
- Preview and social sharing meta tags require explicit implementation
With traditional Liquid themes, these SEO elements are largely handled by the platform automatically. With headless, they become developer responsibilities.
App compatibility
This is one of the most significant practical drawbacks of headless. Most Shopify apps are designed for traditional storefronts. They inject JavaScript through script tags, use app blocks, or modify the theme directly. These integration methods do not work with headless storefronts.
For headless stores, app functionality must be replicated through API integrations, custom code, or the app's backend API (if available). This means: review widgets need custom frontend integration, loyalty programmes require API-level integration, live chat tools need separate JavaScript embedding, and analytics tools need explicit implementation.
Some apps are adapting to support headless, but the ecosystem is still heavily tilted towards traditional storefronts.
Content management
Traditional Shopify themes include a visual content editor — the theme customiser. Non-technical team members can update content, rearrange sections, and manage pages without developer help.
Headless storefronts typically use a separate CMS (like Contentful, Sanity, or Prismic) for content management. This provides more powerful content modelling but adds another system to manage, another subscription to pay for, and another tool for your team to learn.
When headless makes sense
Headless Shopify genuinely makes sense in specific scenarios:
- Multi-source content: Your storefront needs to pull content from multiple sources — a CMS, a PIM, multiple Shopify stores, and custom data services
- Highly interactive experiences: Your products require complex configurators, real-time visualisation, or app-like interactivity
- Multi-platform storefronts: You need the same commerce backend to power a web store, a mobile app, and in-store kiosks
- Brand-defining UX: Your brand's competitive advantage is a customer experience that cannot be achieved within Shopify's theme architecture
- Enterprise content strategy: Your content operations require a dedicated headless CMS with structured content models
When headless does not make sense
- Your requirements can be met by a traditional OS2.0 theme (most can)
- Your budget is under £50,000 for the initial build
- You do not have access to React/JavaScript developers for ongoing maintenance
- You rely heavily on Shopify apps that do not support headless
- Speed to market is a priority
- Your team needs to make content changes without developer involvement
- Performance "good enough" is truly good enough (and it usually is)
The verdict
For the vast majority of UK ecommerce brands, traditional Shopify with Liquid themes is the right choice. Online Store 2.0 provides sufficient flexibility, the app ecosystem is unmatched, the theme editor empowers non-technical users, and the cost is dramatically lower.
Headless is the right choice for a small percentage of brands with specific requirements that genuinely cannot be met by traditional Shopify. If you are considering headless, make sure you are doing it for the right reasons — because your business requirements demand it, not because it sounds technically sophisticated.
The most expensive headless mistake is building a headless storefront that could have been a traditional theme. The second most expensive is underestimating the ongoing maintenance cost of a custom React application.
If you are evaluating whether headless Shopify is right for your brand, get in touch. We will give you an honest assessment based on your specific requirements — including telling you if traditional Shopify is the better choice.