The headless commerce conversation in 2026 has gone from "the future of e-commerce" to "a serious tradeoff with a clear right answer per merchant". The hype has settled. What is left is a genuine architectural choice — and one that most agencies still pitch badly in both directions.
This post is the honest 2026 framing: what headless actually means, when it wins, when Shopify-as-built wins, and how to tell which one your store needs without buying a rebuild you do not need.
The honest summary
- Shopify (with a Shopify 2.0 theme) is the right call for most merchants under roughly $1M in annual revenue, with standard product catalogs, no in-house engineering team, and no strong brand-storytelling requirement that breaks templates.
- Headless Shopify (Next.js or Hydrogen on the storefront, Shopify on the backend) is the right call for merchants with a strong design brief that templates fight, a content strategy that lives outside the product catalogue (lookbooks, editorial, education), or a roadmap that includes apps, kiosks, or other surfaces beyond a single website.
- Fully headless (Medusa, Saleor, custom commerce backends) is a niche choice for merchants with very specific data-model requirements that Shopify's catalogue cannot accommodate. It is rarely the right call below enterprise scale.
The line is not "size of merchant". It is "how much does the storefront need to do that a Shopify theme cannot do well?"
What "headless" actually means
In the simplest terms: headless commerce separates the storefront (what customers see) from the commerce backend (catalogue, cart, checkout, orders, inventory).
In a traditional Shopify build, the storefront is a Liquid theme that runs on Shopify's servers. The frontend and backend are coupled — Shopify renders both.
In a headless build, the storefront is a separate codebase (typically Next.js or Hydrogen) that talks to Shopify via the Storefront API. The catalogue, cart, and checkout still live in Shopify; only the rendering is yours.
What you gain: complete control over the frontend. Custom design that does not fight Liquid's constraints. Component reuse with the rest of your app surfaces. Modern performance defaults. Cleaner integration with content systems that are not Shopify (Sanity, Contentful, MDX).
What you give up: the simplicity of the Shopify theme ecosystem. Most Shopify apps assume a theme they can inject into; a headless storefront has to integrate them deliberately. Operational complexity goes up — you now own deployments, infrastructure decisions, and a frontend codebase.
When Shopify-as-built wins
A well-built Shopify 2.0 theme is the right answer in more cases than agencies will admit. Specifically:
- Standard catalogue, standard merchandising. Products, collections, variants. The data model fits, and the templates are flexible enough.
- Marketing-driven, not editorial-driven. Your conversion path is product page → cart → checkout, not a content journey that ends at a product.
- Small or no in-house engineering team. Shopify's ecosystem absorbs a lot of work — apps for reviews, search, email, loyalty, shipping. A headless build has to wire each of those deliberately.
- Speed to launch matters more than long-term flexibility. A good Shopify 2.0 build ships in 3–6 weeks. A good headless build ships in 8–14 weeks.
- The business will live on Shopify for the next 3–5 years. You are not planning to migrate the catalogue.
We build plenty of Shopify-native stores and do not feel weird about it. Most of the merchants we talk to should choose Shopify-as-built. They just deserve an agency that can do it well, not one that defaults to it because they have not learned anything else.
When headless wins
Headless wins on a smaller set of cases, but the cases are clear:
- Premium brand, design-led conversion. When your buyer is choosing partly on how the site feels, Liquid theme constraints start to fight you. Custom animations, complex page transitions, scroll-driven storytelling, magnetic interactions — all are possible in Liquid but you are working uphill.
- Editorial commerce. Stores that sell through content. A skincare brand with an education library. A specialty food brand with recipes. A fashion brand with lookbooks. The storefront and the content system both want first-class treatment, and a headless build with a structured CMS gives you that.
- Multiple storefronts, one catalogue. B2B and DTC. Multiple geographies with different content. A wholesale portal. Mobile app. A headless backend serves all of them; multiple Shopify themes do not scale that way.
- Custom commerce flows. Quote-to-cart for B2B. Configurators for made-to-order products. Subscription flows that go beyond the standard plans. Each of these is possible on Shopify but starts to bend the platform; on a headless build they are first-class.
- Performance as a competitive moat. A fast Shopify store can hit "good" Core Web Vitals; a well-built headless store routinely lands in the top 5% of e-commerce sites globally. On a category where speed is part of the brand promise, the gap matters.
Headless is the right answer when the storefront has to do more than a Shopify theme does well. Not when it is faster, not when it is trendier — when it has to do more.
The Hydrogen vs Next.js sub-debate
If you have decided on headless, the next decision is the framework. Two main options:
Shopify Hydrogen — Shopify's official React-based framework, built on Remix. Tighter integration with the Shopify ecosystem (analytics, customer accounts, checkout extensions). Deploys to Shopify's Oxygen hosting by default. Strong choice if you are committed to staying on Shopify long-term.
Next.js + Storefront API — a Next.js storefront calling Shopify's Storefront API directly. More portable; the storefront code does not assume Shopify and could be repointed at another backend later. Wider engineering pool. Better fit if your business has multiple surfaces beyond the store (marketing site, app, dashboards) that benefit from sharing components and infrastructure.
We use both. The honest tiebreaker: if the store is the only commercial surface, Hydrogen is slightly simpler. If the store is one of several surfaces, Next.js wins on consistency.
The cost delta
A well-built Shopify 2.0 store in our pricing: $4,800–$12,000 depending on scope. A well-built headless Shopify store in our pricing: $12,000–$32,000 depending on scope.
The headless premium is real and unavoidable. You are buying more code, more infrastructure, more integration work. The premium is justified when the brand or business case requires what a Shopify theme cannot deliver — and a sunk cost when it does not.
A useful test: if you cannot articulate three things the storefront has to do that a Shopify theme would do badly, you do not need headless yet.
What about Medusa, Saleor, fully custom?
The fully-headless options — running the entire commerce backend yourself — are a different conversation. They make sense when:
- Your catalogue or pricing model genuinely does not fit Shopify. Complex B2B with negotiated pricing per customer. Marketplace dynamics with multiple sellers. Subscription products with custom billing logic Shopify cannot express.
- You have engineering capacity to own the commerce backend long-term. That includes payment integrations, tax, fraud, fulfilment, inventory — all the work Shopify absorbs invisibly.
- You are at a scale where the platform fees on Shopify Plus ($2,000+/month) plus app subscriptions become large enough that running your own is competitive.
Below those conditions, the cost of running your own commerce backend is almost always larger than the platform fee you are trying to avoid.
How to decide for your store
Three questions, in this order:
- What is the storefront required to do that a Shopify theme cannot do well? If you can name three real things, headless. If you can name zero, Shopify-as-built. If you can name one or two, you probably need a better Shopify build, not headless.
- Do you have engineering capacity (in-house or through a long-term agency relationship) to own a frontend codebase? A headless storefront is a real software product. It needs updates, security patches, dependency upgrades. If the answer is no, Shopify-as-built.
- What is the revenue and roadmap horizon? Headless pays back over 2–4 years on conversion lift, brand differentiation, and reduced platform constraints. If you are in growth mode and the storefront is the front door, the math works. If you are validating the business, the headless premium is a tax on uncertainty.
The honest verdict for the median merchant: a great Shopify build is the right answer, and you should be more sceptical of any agency that pushes headless without working through these three questions on your specific business.
Pick the substrate that fits the business, not the substrate that flatters the agency. Both Shopify-as-built and headless are right answers — for different stores. The question is which one is right for yours.
