Headless commerce is the most oversold concept in ecommerce right now. Every agency pitches it. Every conference talks about it. But about half the brands we talk to don't actually need it. Here's how to figure out which side you're on.
What headless actually means
Headless commerce separates your storefront (what customers see) from your commerce engine (Shopify's backend). Instead of Shopify rendering your pages with Liquid templates, a custom React frontend fetches data from Shopify's APIs and renders it independently.
You keep everything Shopify is good at: checkout, payments, inventory, order management. You replace the part that themes handle: the frontend rendering, content management, and page composition.
The result is a store that your engineering team controls completely, and one that your marketing team accesses through a proper CMS rather than the Shopify theme editor. Understanding when that tradeoff is worth making is what this article is about.
The case for headless
Design without constraints
Shopify themes are flexible, but they have a ceiling. Liquid templates, section schemas, and the theme editor define what's possible. If your brand needs page layouts, interactions, or content structures that don't fit within theme conventions, headless removes the ceiling entirely. You're building a custom React application with Shopify powering the commerce layer underneath.
This matters most for brands where the editorial and brand experience is as important as the product catalogue. Lookbooks that blur into product pages, scroll-driven storytelling, interactive size guides, video-first product pages with real-time inventory: these are difficult to build well within theme constraints and straightforward in a headless React environment.
Performance that matters
Headless storefronts built with Hydrogen and deployed on Oxygen or Vercel serve pages from the edge with server-side rendering. For brands where page speed directly correlates with conversion rate, which is most brands doing serious volume, the performance improvement from headless is measurable and meaningful.
The performance gains come from multiple places: edge rendering that puts your pages closer to the customer geographically, granular control over what JavaScript loads and when, and the ability to implement streaming and progressive rendering patterns that aren't possible within a Liquid theme.
Content beyond products
If your content strategy includes editorial features, lifestyle content, lookbooks, interactive guides, or any content that lives outside the product catalogue, a headless CMS like Sanity gives your team tools that Shopify's built-in content system can't match.
Sanity gives your content team a structured, real-time editing environment. Every content block has a defined schema. A hero section has typed fields for headline, body, CTA, and background. An editorial feature has a defined structure for images, pull quotes, and product references. Your content team can build and preview pages without touching code, and those pages render with the same performance characteristics as your product pages.
Multi-storefront architecture
Running multiple storefronts from a single Shopify Plus backend, across different brands, markets, or channels, is cleaner with headless. Each storefront gets its own frontend while sharing the commerce infrastructure underneath. This architecture also positions you well for agentic commerce, where AI agents interact directly with your structured data and catalogue via Shopify's MCP servers.
The case against headless
Cost
A headless build typically costs 2-3x what a well-built theme costs. You're building a custom application, not configuring a template. Budget $80K-$150K+ for a headless Shopify Plus build versus $30K-$60K for a solid theme build. You can read more about the real cost of going headless before committing to either direction.
Ongoing dependency
Theme stores can be updated by non-developers using the Shopify editor. Headless stores need a developer for structural changes. Your CMS handles content updates, but layout changes, new page types, and feature additions require dev work. This is not a dealbreaker if you have a retainer relationship with an agency or an in-house developer. It is a dealbreaker if you expected to manage the store independently after launch.
Ecosystem friction
Some Shopify apps don't work with headless storefronts. Most modern apps have API-based alternatives, but you'll spend more time on integration than you would with a theme. Reviews, loyalty, search, personalisation: each of these needs to be evaluated for headless compatibility before you commit to the stack. We've written about our default headless stack and why we chose each tool in it.
A word from our CTO
[CTO contribution to be added here: the technical perspective on when headless is the right architectural decision, and what the build and maintenance reality looks like from an engineering standpoint.]
The hybrid path
There's a middle ground that most agencies don't talk about because it's less exciting than a full headless pitch. You can run a Shopify theme for your core commerce pages, products, collections, cart, checkout, and use a headless CMS for content-heavy sections like your blog, landing pages, and editorial content.
This gives you the best of both: your marketing team uses Shopify's editor for commerce pages and a proper CMS for content. You get the performance and flexibility benefits where they matter most without the cost and complexity of a full headless build. We've taken this approach with brands like Carwyn Cellars and Byron Bay Cookie Co, and it's often the most commercially sensible starting point for brands that aren't yet certain they need full headless.
How to evaluate your stack
Before making this decision, it's worth understanding how ecommerce architecture has evolved from monolithic platforms to headless to the agentic commerce patterns emerging now. The architectural decisions you make today affect how well-positioned you are for what comes next.
It's also worth reading our piece on rebuilding your ecommerce store in 2026 and the stack that actually makes sense, including when a rebuild is the right call and when iteration on what you have is smarter. If you're choosing between rebuilding and iterating, we've written specifically about that decision too.
The decision framework
Go headless if three or more of these are true: your design team regularly hits theme limitations, your content strategy extends significantly beyond product pages, you're running or planning to run multiple storefronts, page speed improvements would meaningfully impact your revenue, and your budget supports $80K+ for the initial build plus an ongoing dev retainer.
Stay on themes if your content needs are primarily product-focused, your team is small and doesn't include developers, your budget is under $60K, and you value being able to make changes without dev support.
Consider the hybrid path if you need better content tools but your commerce pages work well, your budget sits in the $40K-$80K range, or you want to validate the content architecture before committing to a full headless build.
Either way, having the right Shopify Plus development partner matters more than the architecture choice. The best architecture decision is one your team can actually operate and your business can sustain. If you're not sure which path fits your situation, talk to the Flux team and we'll give you an honest answer.
A Shopify Plus Agency for Strategic Design & Advanced Engineering
Building something ambitious?
- Headless adds cost, complexity, and ongoing dev dependency - it's not a free upgrade
- Go headless if you need complete design control, sub-second load times, or content beyond product pages
- Stay on themes if your team is small, your content needs are straightforward, and your budget is under $60K
- The hybrid path - Shopify theme with headless content sections - is often the smartest move
