Headless Shopify explained and whether your store actually needs it

What headless Shopify actually means

A normal Shopify store is one system. The backend (products, orders, inventory, checkout) and the frontend (what your customers see) are tied together. You pick a theme, customise it, and that's your store.

Headless Shopify splits those two apart. You keep Shopify's backend. It still handles your products, payments, and orders. But you replace the theme layer with a custom frontend built from scratch using something like React and NextJS.

The two halves talk to each other through Shopify's Storefront API. Your custom frontend asks Shopify for product data, prices, and cart information. Shopify sends it back. The customer never knows the difference.

Shopify's own version of this is called Hydrogen. It's a React framework built for headless Shopify stores, and it runs on their hosting platform called Oxygen. It's matured a lot since launch and it's now the default path for custom Shopify frontends.

That's all headless means. The frontend and backend are separate instead of joined.

Benefits of headless Shopify

Speed is the obvious one. A headless Shopify store using server side rendering can hit perfect Lighthouse scores. Pages load fast because you control every line of code. No theme bloat, no app scripts you didn't ask for, no third party code dragging things down.

That speed matters. Google's Core Web Vitals directly affect your search rankings. And faster stores convert better.

I built Led & Collared as a headless Shopify store using NextJS and Prismic. It's a New Zealand pet gear business selling custom made collars, leads, and harnesses. Search "custom dog collar" in New Zealand and it sits in the first position on Google. That ranking comes from clean code, fast page loads, and good content structure. You get full control over those things when you go headless. You lose that control when you're working inside a theme.

Design freedom is the other big gain. With a Shopify theme, you're working inside constraints. Some of those constraints are fine. But if your product needs something specific, you hit walls fast.

Led & Collared is a good example. Every product is made to order. A customer buying a dog collar doesn't just pick a size. They choose the colour, hardware finish, buckle type, whether to add a name tag, what text goes on it, optional extras. The product page is a configurator that walks them through every decision and feeds a clean structured order back to the maker. You can't build that inside a Shopify theme. It needed a custom frontend with variant logic underneath that maps dozens of combinations to the right Shopify line items.

You also get full control over your URL structure, which matters for SEO. And you can pull content from a headless CMS like Prismic alongside your Shopify product data, which makes it easier for non-developers to manage pages and posts without touching code.

Headless Shopify is the most oversold thing in ecommerce right now. Every agency pitch deck has it. Every trend article lists it near the top. And most of the stores being pushed toward it don't need it.

I build headless Shopify stores. I also build regular ones. I've been doing this for over 20 years and I've got no reason to talk you into one over the other. So here's what headless actually means, when it makes sense, and when you're better off spending that money elsewhere.

When headless Shopify makes sense

Not every store needs this. Here's when it pays off.

If your current store is slow and you've tried everything else. You've optimised your images, cut your apps back, picked a lightweight theme. Your Core Web Vitals are still poor. That's usually an architectural problem. Headless solves it at the root.

If your dev team spends more time working around theme limitations than building features. You're paying for friction. Headless removes the ceiling.

If you need your website to actually sell, not just exist. MEC Bikes came to me with a custom PHP site that barely loaded. No mobile experience. Online sales were zero. I rebuilt it as a headless Shopify storefront with NextJS, Prismic for content, and Accumula bridging Shopify to their Lightspeed POS across two retail stores and a warehouse. Inventory updated in realtime across all channels. Within months, customers were buying $15k bikes online. The website went from something the business avoided talking about to making six figures a year. That business was eventually acquired by Specialized, who entered the NZ market directly. A three month build that became a two year engagement.

That kind of result doesn't come from a theme.

If you're selling across multiple channels and want one backend. Your products appear on your website, a mobile app, in store screens, or other platforms. Headless lets you use Shopify as the single source of truth for all of them. One product catalogue, many frontends.

And you need access to developers who can build and maintain it. This is the one people forget. A headless store is a custom application. It needs developers who know React, NextJS, and the Shopify Storefront API. If you don't have that, or don't want to pay for it ongoing, headless will cause more problems than it solves.

When you don't need headless Shopify

Most NZ ecommerce stores fall into this category. And that's fine.

Shopify 2.0 themes are better than they used to be. Sections everywhere, better metafields, more flexibility in the theme editor. For a lot of stores, that's enough. But they're still Liquid based, still running inside Shopify's theme framework, and still limited by what that framework allows. Whether that matters depends entirely on what your store needs to do. A store selling ten products in three sizes has different requirements to a store selling custom made gear with dozens of variant combinations. The answer isn't headless or not headless. It's what does your business actually need.

A well chosen Shopify theme, properly optimised, can still be fast, look good, and sell. It won't give you the same level of control, but for most stores a small scale it doesn't need to.

If you rely on a lot of Shopify apps, headless gets complicated. Most apps are built for the theme layer. Reviews, wishlists, loyalty programs. They all need custom integration in a headless setup.

If your current store converts well, loads fast and ranks highly in Google, don't fix what isn't broken.

What headless Shopify costs in New Zealand

A traditional Shopify store built on a premium theme with customisation typically runs between $5k and $25k NZD depending on complexity.

A headless build starts from around $10k NZD and can go above $80k for larger stores with complex requirements. That's the build cost. You'll also need ongoing development support, which is more specialised than standard Shopify theme work.

I work independently, so you're not paying agency overheads. That makes a difference on a build this size. But the gap between a theme build and a headless build is still real. The decision should come down to whether the return justifies the spend.

Headless Shopify vs traditional Shopify

Go headless if your store is doing strong revenue, your current setup is limiting growth, you need speed and design control that themes can't give you, and you have the budget and technical support to maintain it.

Stay on a theme if your store is newer, your team needs to manage it without developers, your current performance is fine, or your budget is better spent elsewhere.

Headless Shopify developer in New Zealand

I use React, NextJS, and TypeScript with Shopify's Storefront API. For content I use Prismic as the headless CMS, which lets store owners manage blog posts, landing pages, and editorial content without touching code.

I've been building headless Shopify stores for NZ businesses for years. MEC Bikes went from zero online revenue to six figures and scaled into an acquisition. Led & Collared ranks first on Google for its primary search term, has over 190 five star reviews, and I still maintain it today. Both are headless builds on the same stack.

If your Shopify store is hitting its limits, get in touch.