Do You Actually Need Headless Commerce? An Honest Shopify Guide

We get this request more than almost any other: "We want to go headless." It usually arrives with real conviction — a founder has read that headless is faster, more modern, more scalable, and has decided it's the upgrade their store needs.

Sometimes they're right. More often, they're about to spend three times the money for a performance gain they could have got by cleaning up their existing theme — and to take on a maintenance burden nobody warned them about.

So this is the honest version of the conversation we have with those brands. What headless actually is, what it genuinely does well, who it's really for, and why it's the wrong choice for most stores — including, quite possibly, yours. We build headless storefronts when they're the right call. We also talk people out of them regularly, because part of doing this well is telling you when you don't need the expensive thing.

What "headless" actually means

A normal Shopify store is coupled: the storefront your customers see and the commerce engine behind it (products, cart, checkout, orders) are part of one system. On Shopify, that front end is built with Liquid, Shopify's templating language, and Shopify hosts, scales, and renders the whole thing for you.

Headless splits those two apart. The commerce backend stays in Shopify — it still owns your products, inventory, cart logic, and checkout — but the storefront becomes a completely separate application that you build yourself, usually in a modern JavaScript framework like React. That front end pulls data from Shopify through the Storefront API and renders the customer experience independently.

On Shopify specifically, the official route to headless is Hydrogen — Shopify's React-based framework for building custom storefronts — deployed on Oxygen, Shopify's global edge hosting, which is now included at no extra cost on paid plans. You can also bring your own stack (Next.js on Vercel, for instance), but Hydrogen and Oxygen are the first-party path.

One detail that surprises people, and it matters: checkout stays with Shopify. Even in a headless build, you don't own the checkout — Shopify does. You own the discovery and browsing experience; Shopify owns the part where money changes hands. That single fact quietly removes one of the reasons people think they need headless.

A useful way to picture it: a Liquid theme is renting a well-equipped, fully-managed apartment. Headless is building your own house on land Shopify provides — total control, and total responsibility for everything you build.

What headless can actually do

Headless is genuinely powerful. When a store has outgrown what a theme can do, it unlocks things that are difficult or impossible on standard Liquid:

• Complete control over the front-end experience. You're no longer working within a theme's structure. Any interface, any interaction, any layout you can build in code, you can ship — bespoke product configurators, highly interactive experiences, unconventional storefronts that don't look or behave like "a Shopify store."
• Access to the full modern front-end ecosystem. React, the component libraries, the tooling, the developer workflows — the whole modern web stack becomes available, rather than Liquid's more constrained model.
• Best-in-class performance ceiling. A well-built Hydrogen storefront on Oxygen's edge network can achieve very fast load times through server-side rendering and edge caching. The ceiling is higher than a theme's — with the important caveat below.
• Composable / multi-channel content. If you're publishing the same commerce data across many surfaces — web, native app, kiosk, marketplace, editorial platforms — a headless architecture with a separate front end and a dedicated CMS can serve them all from one backend more cleanly than a theme.
• Freedom from theme constraints at scale. For very large or very unusual catalogues and experiences, not being bound by theme architecture is a real advantage.
  These are real benefits. The question is never whether headless can do impressive things — it can. The question is whether your store needs them enough to justify the cost.

Who headless is genuinely right for

Headless makes sense for a specific profile of merchant, not a general one. You're a real candidate if several of these are true:

• You have concrete front-end requirements a theme genuinely can't meet. Not "we want it to feel premium" — specific, nameable interactions or experiences that Liquid and Online Store 2.0 sections genuinely cannot deliver. If you can't name three, you probably don't need headless.
• You're at real scale. Enterprise-level traffic and revenue, where a few points of performance or conversion translate into enough money to justify a six-figure build and higher ongoing costs.
• You have (or will hire) dedicated front-end engineers. Headless is a standing engineering commitment, not a one-off project. A store that can't maintain a React application shouldn't own one.
• You're running a genuine multi-channel or composable operation. Many front ends, one commerce backend — the case headless was actually designed for.
• You need a custom CMS or content architecture deeply integrated with commerce in a way Shopify's native content tools can't support.
  Notice the pattern: these are enterprise and specialist scenarios. That's not an accident — it's who headless is for.

Why headless is the wrong choice for most brands

Here's the part the "go headless" hype skips. For the large majority of Shopify stores, headless is not an upgrade — it's a tax. The honest reasons:

The performance gap is smaller than you think. The most common claim is "headless is faster." It's true in principle and misleading in practice, because a clean, well-built Liquid theme is already fast. The real performance problem on most stores isn't Liquid — it's app bloat: a stack of third-party scripts dragging the site down. Fix that, and a Liquid theme performs comparably to Hydrogen for a typical store. The gain from going headless is often a marginal single-digit improvement — for a cost multiple of two or more. Architecture is rarely the actual fix; the apps usually are.

The "app tax" is real, and it surprises everyone. This is the biggest practical downside. The overwhelming majority of the thousands of apps in the Shopify App Store are built for Liquid themes — they inject scripts, add theme blocks, and hook into theme architecture that simply doesn't exist in a headless storefront. Reviews, loyalty, wishlists, upsells, subscriptions: in a headless build, many of these stop being a one-click install and become custom integration work against each vendor's API — if the vendor even offers a headless-compatible one. You lose a huge amount of the Shopify ecosystem's convenience overnight.

The cost is a different order of magnitude. A custom Liquid build is a defined project. A headless build is a custom software application — realistically starting around $30,000–$40,000 for a properly built storefront and rising substantially from there with scope, integrations, and app rebuilding. And that's before ongoing costs. Which brings us to the real one.

The maintenance never stops. This is the point most brands don't fully price in. When you go headless, you own the front end — the framework, the dependencies, the hosting configuration, the integrations. Frameworks update. Dependencies need patching. Things that "just work" on a Shopify-hosted theme become your team's responsibility on a headless build. A Liquid theme is maintained by Shopify at the platform level; a headless storefront is maintained by you, forever. That's not a one-time cost — it's a permanent line item.

You lose the operational simplicity that made Shopify attractive. Part of Shopify's whole value is that it handles the hard infrastructure so you can focus on selling. Headless hands a meaningful chunk of that back to you. For a brand whose advantage is its product and marketing, not its engineering, that's usually a step in the wrong direction.

For most brands, the honest calculation is this: headless front-loads a large cost and back-loads a permanent one, in exchange for a performance gain a well-built theme could largely match. That's a bad trade for anyone who isn't in the specific profile above.

How to actually make the decision

Skip the hype and ask these questions honestly:

1. Can you name three specific things a theme genuinely can't do that your business actually needs? Not aesthetic preferences — real functional or experiential requirements. If you can't, headless isn't your answer.
2. Is your current store actually slow because of Liquid, or because of apps? Audit the app bloat first. Most "we need headless for speed" problems are solved by removing scripts and optimising the existing theme — at a fraction of the cost.
3. Do you have, or will you commit to, dedicated front-end engineering? If maintaining a React application isn't realistic for your team, headless will become a liability the moment the agency hands it over.
4. Does your scale justify the cost? If a 5–10% performance improvement doesn't translate into meaningful money at your revenue, the six-figure build and ongoing maintenance won't pay back.
5. Which apps do you rely on, and do they work headless? Audit every app you run and confirm headless compatibility before you commit — this alone stops many headless projects that looked sensible on paper.
   If you're not clearly answering "yes, and here's specifically why" to most of these, the right move is a well-built theme — not headless.

The honest comparison: theme vs custom build vs headless

Three build options get conflated in these conversations. Here's how they actually differ:

Checkout stays Shopify-hosted in all three — even headless.

The row that matters most for the "do I need headless?" question is the one people ignore: a custom Shopify build gives you a genuinely bespoke, high-performance store — with full app access and low maintenance — without any of the headless overhead. For the vast majority of brands who think they want headless, what they actually want is a well-executed custom Liquid build. It delivers the "this doesn't feel like a template" result they're after, at a fraction of the cost and none of the ongoing burden.

And if you need Plus-tier capabilities — advanced checkout customisation, Shopify Functions, complex B2B, multiple storefronts — Shopify Plus gets you there while staying on Liquid, which means you keep the ecosystem and the low maintenance. Plus is a plan, not an architecture; you don't need to go headless to get enterprise features.

We cover the broader platform question in our guide on how to choose a platform, and what a bespoke build involves in our custom Shopify development work.

What to know before you commit

If, after all that, you're genuinely in the headless-candidate profile, go in with clear eyes:

• It's a standing engineering commitment, not a project. Budget for ongoing maintenance, framework upgrades, and dependency management — permanently, not just the build.
• Audit your apps first. Every app you rely on needs a headless-compatible path, or a plan to rebuild its function. Do this before you start, not after.
• Checkout still belongs to Shopify. If your reason for going headless was checkout control, reconsider — you don't get it.
• Performance still has to be earned. Headless raises the ceiling; it doesn't guarantee speed. A poorly built React storefront is slower than a clean Liquid theme. The framework is not the optimisation.
• You're taking on the front end forever. That's the deal. For the right store, it's worth it. For most, it's a cost with no matching return.

The honest bottom line

Headless is a powerful, legitimate architecture — for enterprise and specialist brands with concrete front-end requirements, real scale, and the engineering resources to own it. If that's you, it can be exactly right, and we're glad to build it.

But for most Shopify brands, "we want to go headless" is a solution looking for a problem. The performance gain is usually marginal over a clean theme, the app ecosystem gets harder, the cost is far higher, and the maintenance never ends. Nine times out of ten, the brand that came to us wanting headless is better served by a well-built custom Liquid store — often on Plus if they need enterprise features — that gives them the bespoke result they actually wanted without the permanent overhead.

That's the honest answer, even though headless is the more expensive thing we could sell you. If you're weighing it for your store and want a straight assessment of whether you're genuinely in the small group it suits — or whether a custom build would get you there for less — get in touch. We'll tell you honestly, either way.

FAQ

What is headless commerce on Shopify?
Headless commerce separates your storefront (what customers see) from your commerce backend (products, cart, checkout). On Shopify, the backend stays in Shopify while the storefront is built as a separate application — usually with Hydrogen, Shopify's React framework, hosted on Oxygen — that pulls data through the Storefront API. You gain complete control over the front-end experience, but you take on building and maintaining that front end yourself. Importantly, checkout remains Shopify-hosted even in a headless setup.

Do I need headless commerce for my Shopify store?
Most stores don't. Headless suits enterprise and specialist brands with concrete front-end requirements a theme genuinely can't meet, real scale, and dedicated engineering resources. For the large majority of brands, a well-built Liquid theme — or a custom Shopify build — delivers comparable performance and a bespoke result with full app access and far lower cost and maintenance. A good test: if you can't name three specific things a theme can't do that your business actually needs, you probably don't need headless.

Is headless Shopify faster than a Liquid theme?
It can be, but the gap is usually smaller than expected. A clean, well-built Liquid theme is already fast — most performance problems come from app bloat (too many third-party scripts), not from Liquid itself. Fix the app bloat and a theme performs comparably to headless for a typical store. Headless has a higher performance ceiling, but a poorly built headless storefront is slower than a good theme. The framework isn't the optimisation.

How much does a headless Shopify build cost?
A headless build realistically starts around $30,000–$40,000 for a properly built storefront and rises substantially from there depending on scope, integrations, and how many apps need rebuilding — significantly more than a custom Liquid build. Ongoing costs are also structurally higher, because you own and maintain the front end (framework upgrades, dependency patching, hosting) rather than Shopify maintaining it at the platform level. The maintenance is a permanent commitment, not a one-time cost.

What's the difference between headless and a custom Shopify build?
A custom Shopify build is a bespoke Liquid theme, built to your design and requirements, running on Shopify's hosted infrastructure with full app-ecosystem access and low maintenance. Headless replaces the Liquid front end entirely with a separate application you build and maintain yourself. A custom build gives most brands the "doesn't feel like a template," high-performance result they actually want — without the cost and permanent maintenance overhead of headless. For the majority who think they want headless, a custom build is the better fit.

Do I need to go headless to get Shopify Plus features?
No. Shopify Plus is a plan, not an architecture. You can access Plus features — advanced checkout customisation, Shopify Functions, complex B2B, multiple storefronts, higher API limits — while staying on Liquid, keeping full app-ecosystem access and low maintenance. Going headless is a separate decision about front-end architecture, and most Plus merchants run on Liquid, not headless.

Do Shopify apps work with headless?
Often not without extra work. Most Shopify App Store apps are built for Liquid themes and rely on theme architecture that doesn't exist in a headless storefront. Some vendors offer headless-compatible APIs, but many don't — so features like reviews, loyalty, and upsells may need custom integration or rebuilding against each vendor's API. Auditing every app you rely on for headless compatibility is an essential step before committing to a headless build.

Base X Tech is a custom Shopify agency. We build custom Liquid stores, Plus builds, and headless storefronts — and we give an honest read on which one you actually need. If you're weighing headless, get in touch and we'll tell you straight.