Your Theme Is Holding You Back
Your Shopify store does EUR 2 million in revenue. The standard theme worked great at EUR 200,000. Now you need custom product configurators, location-based pricing, and a checkout flow that doesn’t make B2B buyers fill in the same information five times.
You’ve already stretched the theme with 14 apps, three custom Liquid snippets, and a JavaScript hack that “mostly works.” Sound familiar?
That’s the moment teams start searching for “shopify headless.” As of 2025, around 67% of companies were adopting or improving a headless commerce setup. They’re not doing it because headless is trendy. They’re doing it because standard templates break at scale.
What Shopify Headless Commerce Is
Shopify headless commerce means decoupling your storefront from Shopify’s theme layer: Shopify’s backend still runs inventory, orders, and payments, but a custom frontend (built with any framework) handles everything the customer sees, pulling data through the Storefront API.
In a traditional setup, the frontend and the backend are tightly coupled. The Liquid theme controls presentation. Shopify controls logic. You work within their constraints.
Headless splits the two apart. You build exactly the experience you want: any framework, any design, any interaction pattern you like. Shopify keeps running the commerce engine underneath.
The trade-off is real. You need developers who can build and maintain a custom frontend, and a theme tweak that took 30 minutes now takes actual development work.
But the ceiling is gone.
Shopify Themes vs. Headless: A Side-by-Side
The honest comparison: themes win on speed and cost, headless wins on flexibility and performance. Here’s where each one lands.
| Standard theme | Shopify headless | |
|---|---|---|
| Setup time | Days | Weeks to months |
| Upfront cost | Low (theme + apps) | Higher (custom build) |
| Design freedom | Constrained by theme | Unlimited |
| Peak performance | Capped by Liquid + apps | 90+ Lighthouse achievable |
| Maintenance | Click-to-update | Developer-owned |
| Multi-storefront | One store per theme | One backend, many frontends |
| Who it fits | Most stores under EUR 1M | Complex or high-traffic stores |
Read that table the right way. Headless isn’t an upgrade everyone graduates to: it’s a different tool for a different problem. If your store fits the left column, the left column is the correct answer. Seriously.
When Headless Makes Sense
Not every store needs headless. A straightforward DTC brand selling 50 SKUs with standard checkout? Stick with a theme.
Headless earns its keep when you’re hitting limits. Four situations make the case.
Complex product configuration. When customers customize products across dozens of options, standard themes buckle. We’ve seen configurators bolted onto a theme with three apps and a tangle of Liquid: slow to load, and dropping the cart every time someone changes an option. Rebuilt headless, that same configurator updates instantly and feeds straight into Shopify’s cart.
Multi-storefront from one backend. You want a consumer store, a B2B portal, and a mobile app, all pulling from the same inventory. Headless lets each frontend be purpose-built while sharing one commerce backend.
Performance is revenue-critical. Core Web Vitals affect both your rankings and your conversion rate, and only 42% of mobile sites pass all three. A properly optimized React frontend clears that bar in a way a Liquid theme stacked with apps rarely does.
Omnichannel surfaces. In-store kiosks, digital signage, WhatsApp ordering. When the “storefront” isn’t a browser at all, headless is the only option. The same Storefront API that feeds your website feeds the kiosk, so inventory and pricing stay in sync without a second integration.
Shopify Hydrogen: The First-Party Path
Shopify built Hydrogen specifically for headless storefronts. It’s a React framework, and as of late 2024 it runs on React Router v7 (it used to be built on Remix, so older guides will tell you otherwise). It’s designed to work hand-in-glove with the Storefront API.
Oxygen is Shopify’s hosting platform for Hydrogen. Deploy directly from your repo, get global edge delivery, and skip the separate hosting bill. Oxygen is included free on every paid Shopify plan.
The real win: Hydrogen keeps you inside the Shopify ecosystem. Shopify Checkout still handles payments, so you keep Shop Pay, Shopify Payments, and every checkout optimization Shopify ships.
The catch? Hydrogen is React-specific.
If your team lives in Vue, Svelte, or something else, you’ll skip Hydrogen and hit the Storefront API directly. The API is well-documented and framework-agnostic, so that’s a perfectly good path. For the architectural mindset that makes it work, see our take on API-first architecture.
The Composable Commerce Alternative
Headless changes the frontend. Composable changes everything.
Composable commerce breaks the whole stack into modular, API-first services. Instead of Shopify doing it all, you pick best-of-breed pieces: Algolia for search, Contentful for content, Shopify for checkout, Akeneo for product information.
For most SMBs, this is overkill. The operational overhead of five vendors, five APIs, and five billing relationships only pays off at serious scale.
But it’s worth knowing the components exist. Start headless with Shopify. Peel off individual services only when Shopify’s built-in version becomes a genuine bottleneck. Not before.
What Shopify Headless Costs
A focused Shopify headless build runs around EUR 30,000 to 80,000 as of 2026. A full-parity agency build with B2B, custom checkout logic, and multi-region storefronts can climb well past EUR 150,000. The number depends almost entirely on scope, not on headless itself.
The framework and hosting add nothing: Hydrogen is open source and Oxygen is free. Your spend goes to development time, plus any third-party services you bolt on (a CMS, search, monitoring).
Now the honest part. Headless only pays back when speed actually moves your numbers.
Every 100ms of load time costs roughly 1% in conversions, so a faster storefront is real money. Rakuten 24 rebuilt around Core Web Vitals and saw revenue per visitor jump 53% and conversion climb 33%.
For a store doing EUR 2 million, even a 5% conversion lift is EUR 100,000 a year. That’s the math that justifies the build.
But below roughly EUR 5 million in revenue, the same budget spent on acquisition and conversion-rate optimization usually returns more than a headless rebuild. We’ll tell you that to your face before you sign anything.
Headless is a performance and flexibility play, not a growth hack. If you’re still proving the store works, fix the funnel first.
For a fuller breakdown of how to budget a build like this, read what custom software actually costs. And for how headless fits a broader modernization plan, see our digital transformation playbook or our guide to choosing the right tech stack.
So, Is Shopify Headless Right for You?
Three questions cut through it. Are you hitting a wall the theme can’t get past? Is page speed costing you conversions you can measure? Are you past the revenue point where a rebuild beats just buying more traffic?
If you answered yes to all three, headless is probably your move. If not, your theme is fine. Don’t let anyone talk you into a six-figure rebuild to solve a problem you don’t have.
Outgrowing your Shopify theme? Let’s figure out if headless is right for your store. We’ll evaluate your current setup, estimate the performance gains, and scope the migration honestly.
