What Is Headless E-commerce — And Should You Switch From Shopify?

Headless e-commerce means the storefront — the visible website your customers see — is decoupled from the commerce engine that handles cart, checkout, inventory and payments. You either keep Shopify on the backend (and talk to it through the Shopify Storefront API) or you swap in an open-source engine like Medusa or Saleor, and you build the frontend in React or Next.js as a fully custom application. The shop and the website become two systems that talk to each other instead of one welded-together platform.

It's been the trendy answer in e-commerce for about five years. It is also wrong for the majority of stores that try it. This post is the honest version — what headless actually is, when it pays for itself, and when staying on standard Shopify is the smarter call.

The five-second definition

A normal Shopify store is "headed." The frontend (themes, Liquid templates, theme apps) and the backend (products, cart, checkout, customers, orders) ship as one product. You log into the admin, edit a theme, and the storefront updates.

A headless Shopify store keeps the backend exactly the same — same products, same checkout, same admin — but replaces the frontend with a custom application built in React (usually Shopify Hydrogen, Next.js, or a similar framework). That frontend talks to Shopify through the Storefront API, fetching products and pushing cart events.

The "head" in headless is the storefront. Cutting the head off means you can build any frontend you want without being bound by Shopify's theme system.

What you actually gain

Three things, and only three things:

1. Frontend freedom. No more fighting Liquid templates or theme limitations. You can build any interaction, animation, or layout a designer can imagine. The frontend is plain React code.
2. Performance ceiling. A well-built headless storefront on Next.js or Hydrogen on Vercel can hit sub-1-second load times consistently. Standard Shopify themes — even premium ones — tend to land in the 2.5–4 second range on mobile.
3. Composability. You can swap pieces of the stack independently. Use Sanity for content, Algolia for search, Klaviyo for email, Stripe for B2B invoicing — each tool best-of-breed, none of them held together by Shopify's app ecosystem.

That's the entire upside. Everything else people say about headless (SEO, scale, multi-region) is downstream of those three.

What you actually lose

Equally important and rarely discussed.

• Shopify's theme ecosystem. Out: 100+ premium themes, thousands of theme apps that "just work." In: every storefront feature is now code you have to write or buy bespoke.
• The visual editor. Shopify's theme editor and section system goes away. Marketing can't drag a new section onto the homepage. Every storefront change becomes a developer ticket.
• Most theme apps. Apps that inject Liquid or storefront JavaScript don't work in a headless build. Anything that touched the theme — countdown timers, upsell popups, review widgets — needs to be re-integrated through the app's API (if it has one) or rebuilt.
• Speed of iteration. A theme tweak that took 20 minutes on standard Shopify now takes a developer half a day. A new landing page is a deploy, not a save.

If marketing is the centre of gravity in your business and they expect to ship pages without engineering, headless will hurt — not help.

The real platform landscape

The "headless" label covers a few quite different architectures. The ones worth knowing in 2026:

For 95% of Australian and New Zealand businesses asking the headless question, the realistic shortlist is Shopify Storefront API + Next.js, Shopify Hydrogen, or Medusa. The others are real options but only at specific scales.

What it actually costs

Numbers, in AUD, for the year of the rebuild and ongoing:

Standard Shopify, custom theme. Platform: $39–$399/mo. Theme: $0–$3,000 one-off. Custom theme dev: $8,000–$25,000. Apps: $100–$600/mo. Total year-one realistic: $12,000–$32,000.

Shopify Plus, custom theme. Platform: $2,000–$4,000/mo AUD equivalent (Plus pricing is revenue-tiered, USD-denominated). Custom theme dev: $15,000–$40,000. Apps: $300–$2,000/mo. Total year-one: $50,000–$90,000.

Shopify backend + headless frontend (Hydrogen or custom Next.js). Platform: same as standard or Plus, depending on revenue tier. Custom frontend build: $30,000–$80,000. Hosting (Vercel/Oxygen): $20–$1,000/mo. Apps replaced with custom integrations: $5,000–$20,000 spread across year one. Total year-one: $50,000–$120,000.

Medusa or Saleor headless (full stack). Platform: free (open source). Backend hosting (Postgres + compute): $100–$1,000/mo. Custom build (backend integrations + frontend): $50,000–$150,000. Ongoing dev/operations: a real cost — budget $20,000–$60,000/year. Total year-one: $80,000–$200,000.

The honest summary: headless typically lands $30,000–$120,000 AUD for the rebuild, plus $5,000–$15,000/year in additional engineering overhead compared to a standard Shopify theme. The cost is real and it is recurring.

When headless wins

Concrete situations where the maths works:

1. Catalogue over 5,000 SKUs with heavy filtering needs. Standard Shopify search and filter systems start to break down at scale. A custom frontend with Algolia or Typesense and faceted filtering is dramatically better — and headless is the only way to wire it in cleanly.
2. Brand-distinctive frontend is the product. If your store competes on visual experience — a fashion brand, a high-end skincare label, a furniture maker — and the standard Shopify theme constraints actively work against you, headless removes the ceiling.
3. Performance is conversion-critical. Sub-1-second mobile load times measurably move conversion. If you're doing $5M+ in annual revenue, a 10% conversion uplift from a faster storefront pays for the rebuild in months. Below $2M, the maths usually doesn't work.
4. Multi-region or multi-brand. Operating multiple stores from one backend with different frontends per market or sub-brand is genuinely hard on standard Shopify. Headless cleanly separates the layers.
5. Custom B2B flows. Quote-to-cart workflows, customer-specific pricing tiers, NET-30 invoicing, order approvals — these need backend logic that doesn't fit Shopify's standard checkout. Headless gives you a custom checkout that can do whatever you need.
6. You already have engineering. If you have 2+ in-house developers or a long-term agency relationship, the operational cost of headless is absorbed. Without that, headless is a different animal.

When headless is wrong

Equally concrete:

• Annual revenue under $1M AUD. The rebuild cost rarely pays back. Standard Shopify with a custom theme is almost always the better call.
• Catalogue under 1,000 SKUs. Shopify handles this volume effortlessly. You're paying for capability you don't need.
• Marketing-led team that ships pages weekly. Headless takes that ability away unless you also build a custom CMS layer (which adds $20,000+ to the build).
• No in-house technical lead. If nobody on the team can read a pull request, the operational cost of running a headless build will exceed what you saved by leaving the standard theme system.
• You're launching in the next 90 days. Headless builds are 3–6 month projects. Standard Shopify gets you live in 6–10 weeks. Speed-to-market often beats theoretical performance.
• Total budget under $30,000. The minimum cost of a credible headless build. Anything cheaper is either a partial build (frontend only, no integration work) or a freelancer cutting corners you'll pay for later.

Stay on standard Shopify if…

This is the section nobody writes, so we will.

Stay on standard Shopify if all of the following are true:

1. Your catalogue is under 2,000 SKUs.
2. Your revenue is under $3M AUD/year.
3. Your marketing team currently ships pages from the theme editor.
4. Your current PageSpeed Insights mobile score is above 50.
5. You don't have a specific frontend feature that Shopify's theme system genuinely can't support.

If all five are true, headless is the wrong investment for you right now. Spend the same money on a really good custom theme, better photography, a faster app stack, and paid acquisition. You'll get more return.

The right move for most stores under $3M is standard Shopify + a hand-coded custom theme built by someone who actually understands Liquid and Core Web Vitals. The performance gap between a thoughtful custom theme and a typical pre-built one is enormous — and far cheaper than going headless to chase the same gains.

The "should we switch?" decision in one paragraph

If you're doing under $1M AUD per year, the answer is no — stay on standard Shopify, invest in a better theme, fix the speed. If you're doing $1–5M with a marketing-led team and no in-house engineering, the answer is still probably no — the operational cost outweighs the gains. If you're doing $5M+, with a distinctive brand that needs a frontend Shopify themes can't give you, with engineering in-house, and you have a $50,000+ budget — then yes, headless probably pays back, especially with Shopify Hydrogen for the tightest integration. Everything else is somewhere between "maybe" and "wait."

The platform lock-in angle

One thing worth flagging: headless changes your lock-in profile, it doesn't eliminate it. A headless Shopify build is still tied to Shopify's commerce engine, billing tier, and Plus contract obligations. If Shopify raises Plus pricing or deprecates a Storefront API endpoint, you're affected. The frontend is portable; the backend is still Shopify.

Medusa and Saleor are less locked-in — you own the code — but you're locked into running it. That's a different shape of lock-in. We wrote a longer piece on this in the hidden cost of website platform lock-in which applies just as much to commerce as to marketing sites.

The honest recommendation

Pryce Digital builds custom websites and custom Shopify themes for Australian and New Zealand businesses. We do headless Shopify and Hydrogen builds when the maths makes sense. We turn away more headless projects than we accept, because most stores asking for headless would be better served by a sharper custom theme on standard Shopify.

If you want a one-page assessment of whether your store should go headless, book a free audit — we'll look at your current store, your revenue scale, your catalogue size, and your team makeup, and send a written recommendation within 48 hours. If the answer is "stay on Shopify standard, fix the theme," that's what we'll say. If it's "yes, headless makes sense, here's the realistic budget," that's what we'll say.

If you already know you want a custom build — headless or not — our custom web design service is the page to start. Related reading: why Webflow sites break in six months (same maintenance-cost argument applies to undisciplined headless builds), how much does a custom website cost in Australia in 2026, and signs your business has outgrown Squarespace for businesses earlier in the platform decision.