If you’ve been researching this topic for more than five minutes, you’ve probably hit a wall of conflicting advice. Some articles talk about “Shopify vs headless” as if they’re two separate platforms you have to choose between, like Shopify versus Magento. That framing is wrong, and it sends a lot of merchants down the wrong path before they’ve even understood the question.
Headless isn’t a rival to Shopify. It’s an architecture option available within Shopify, built on Shopify’s own Hydrogen framework and Storefront API. Your products, orders, checkout, inventory, and admin still run on Shopify either way. The only thing that changes is what powers the customer-facing storefront, a Liquid theme, or a custom frontend you build separately.
This post is a practical guide to that decision. We’ll cover what “headless Shopify” actually means, when a standard Shopify theme (Online Store 2.0) is genuinely the better choice, when the added complexity of headless is worth paying for, and a simple framework you can use to work out which camp your store falls into. Shopify headless commerce is a moderately searched term in Australia right now, largely because this confusion is so common, so if you’ve been Googling it wondering whether you’re missing out, you’re not alone.
What “headless Shopify” actually means
In a standard Shopify setup, Shopify handles both the back end (products, inventory, orders, customers, checkout) and the front end (the storefront your customers browse and buy from) through a Liquid theme. Everything lives inside one system, themes are built with Shopify’s templating language (Liquid), and Shopify’s Online Store 2.0 architecture handles sections, blocks, and metafields for flexible page building.
Headless commerce decouples the front end from the back end. Shopify still owns all the commerce logic, products, carts, checkout, orders, payments, tax, but instead of rendering that data through a Liquid theme, developers pull it via Shopify’s Storefront API (a GraphQL API) and build the storefront in a separate framework, most commonly Shopify’s own Hydrogen (a React-based framework built specifically for this) deployed on Oxygen (Shopify’s hosting for Hydrogen storefronts), or occasionally a different frontend stack like Next.js.
Two things are worth being precise about, because merchants often get them muddled:
- Checkout usually still runs on Shopify. Even in a headless build, most merchants hand off to Shopify’s native checkout rather than building a fully custom one, Shopify Plus merchants have more flexibility here via checkout extensibility, but a fully custom checkout outside Shopify’s is rare and generally not recommended.
- “Headless” and “Shopify Plus” are not the same thing either. You don’t need Shopify Plus to go headless, though the two often get bundled together because larger, more complex builds tend to need both.
Why the standard Shopify theme is the right call for most stores
This needs saying plainly, because a lot of content in this space is written by people trying to sell headless builds: most Shopify stores do not need to go headless. Online Store 2.0 with a well-built Liquid theme is a mature, fast, flexible system, and for the majority of merchants it’s not the bottleneck people assume it is.
A standard theme setup gives you:
- Faster time to launch. Themes (whether off-the-shelf or custom-built on Shopify’s framework) can go from kickoff to live store in weeks, not months.
- Lower ongoing cost. One codebase, one platform to maintain, no separate frontend hosting or deployment pipeline to manage.
- App compatibility out of the box. The vast majority of Shopify apps, reviews, upsells, loyalty, subscriptions, are built to drop into Liquid themes with minimal setup. Headless builds often need custom integration work for the same apps, because the app’s expected theme hooks don’t exist.
- Section-based flexibility. Online Store 2.0’s JSON templates let merchandisers and marketers rearrange homepage and landing page sections themselves, without a developer, which a lot of headless builds actually lose unless it’s deliberately re-engineered back in.
- Easier hiring and handover. Liquid developers are more common and easier to onboard than a bespoke React/Hydrogen codebase that only your original build team fully understands.
If your store’s real problems are things like slow page speed, a messy product catalogue, weak conversion rate, or unclear navigation, headless won’t fix any of that, those are usually theme, app-stack, or conversion rate optimisation problems, not architecture problems.
A quick checklist: is Online Store 2.0 enough for you?
If most of these are true, stick with a standard theme:
- Your storefront needs (product pages, collections, content pages, blog) look broadly like what a well-built Shopify theme can already deliver.
- You sell through one storefront, in one or two regions, without wildly different UX requirements per market.
- Your team wants to make content and layout changes themselves without a developer for every tweak.
- You rely on a lot of off-the-shelf Shopify apps for reviews, upsells, subscriptions, or loyalty.
- You don’t have an in-house or agency development team available for ongoing frontend maintenance.
- Speed and SEO issues you’re seeing are more likely caused by too many apps, unoptimised images, or bloated code, not a fundamental platform limitation.
When headless is genuinely worth the added complexity
Headless earns its cost in specific situations, not as a default upgrade. Here’s where it typically makes sense.
Highly custom or app-like frontend experiences
If you’re building something that behaves more like a native app than a traditional storefront, heavy client-side interactivity, custom configurators, non-standard navigation patterns, or a frontend experience that simply can’t be achieved within Liquid’s templating model, headless gives developers a blank canvas using modern frontend frameworks and full control over rendering and state.
Multi-brand or multi-region builds with shared back-end logic
Some merchants run several distinct storefront experiences (different brands, different regional sites with different UX, languages, or merchandising) off a shared or connected back end. Headless architecture makes it easier to give each frontend its own look and logic while keeping commerce data centralised, which is genuinely awkward to do cleanly with theme-based Shopify alone.
Non-standard tech stacks or existing frontend investment
If your business already has a frontend built in a specific framework, say, a marketing site or app built in Next.js that you want commerce woven into, headless via the Storefront API lets you bring Shopify’s commerce engine into that existing codebase rather than rebuilding everything as a separate Liquid theme.
Content-heavy or composable experiences beyond a typical store
Some brands need the storefront to behave more like a content platform or digital product than a shop, integrating with a headless CMS, complex personalisation engines, or non-retail experiences layered around the buying flow. Headless suits this better than trying to force it into a theme.
This is exactly the kind of decision worth getting a second opinion on before committing, because a headless build is a genuinely different engineering undertaking to a theme build, not a bigger version of the same job. If you’re weighing this up, a purpose-built headless Shopify development engagement is the right place to properly scope whether your requirements justify it, rather than guessing based on a blog post or a sales pitch from whichever side of the debate you spoke to first.
Be honest with yourself about the trade-offs
Headless is not a free upgrade, and any advice that skips this part isn’t being straight with you. Going headless typically means:
- Real ongoing engineering overhead. You now maintain a separate frontend codebase, its own deployment pipeline, and its own hosting (Oxygen, if using Hydrogen), on top of the Shopify back end.
- App integration work. Apps built for Liquid themes generally don’t just “work” headless. Reviews widgets, upsell tools, and loyalty programs often need custom API integration to appear in your headless frontend, which adds project time and ongoing maintenance.
- Longer build timeframes. A headless build with genuinely custom requirements typically takes meaningfully longer than a comparable theme-based build, because you’re building more of the experience from scratch rather than configuring an existing system.
- Fewer people who can maintain it. You’re relying on developers comfortable with Hydrogen/React and the Storefront API, which is a smaller pool than Liquid developers, and a bigger risk if your build team changes.
- SEO and performance aren’t automatic wins. Headless can be extremely fast when built well, but it can also be slower and worse for SEO than a solid Liquid theme if server-side rendering, metadata, and crawlability aren’t handled properly. Going headless purely chasing speed, without addressing what’s actually causing your current site to be slow, is a common and expensive mistake.
A simple framework for making the call
Work through these questions in order. The first “no” you hit is usually your answer.
- Is there a specific frontend requirement a Shopify theme genuinely cannot deliver? Not “would be nicer,” but cannot deliver. If no, stay on a theme.
- Do you have (or are you budgeting for) ongoing frontend development resourcing? Headless isn’t a “build once and forget it” project. If no, stay on a theme.
- Have you ruled out that your current pain points (speed, conversion, SEO) are actually caused by app bloat, poor theme customisation, or unoptimised assets rather than the platform itself? If you haven’t ruled this out, fix that first, it’s very likely to be the real issue.
- Does your business genuinely need multi-brand, multi-region, or app-like functionality that’s awkward inside a single theme? If yes, and the first three points hold up, headless is worth seriously evaluating.
FAQ
Is Shopify headless commerce a different platform to regular Shopify?
No. Headless Shopify still runs on the same Shopify back end, products, inventory, orders, checkout, and admin all stay on Shopify. The only thing that changes is the storefront, which is built separately using Shopify’s Storefront API (commonly via Hydrogen) instead of a Liquid theme.
Do I need Shopify Plus to go headless?
No, headless via the Storefront API and Hydrogen is available on standard Shopify plans, not just Shopify Plus. That said, businesses that need headless often also need Shopify Plus features (like checkout extensibility or higher API limits), so the two frequently get bundled together in practice.
Will going headless automatically make my store faster?
Not automatically. A well-built headless storefront can be very fast, but a poorly built one can be slower than a solid Liquid theme, especially if rendering and metadata aren’t handled correctly. If speed is your main concern, it’s worth confirming the actual cause before assuming an architecture change will fix it.
Will my existing Shopify apps still work if I go headless?
Some will, but not automatically the way they do on a theme. Apps built for Liquid themes typically need custom integration work to surface their functionality (reviews, upsells, loyalty, etc.) inside a headless frontend, which adds both build time and ongoing maintenance.
How do I know if my store actually needs headless, or if I’m just chasing a trend?
If you can’t point to a specific, concrete frontend requirement a Shopify theme cannot achieve, you probably don’t need it yet. Most performance, conversion, and SEO issues on Shopify stores come from theme and app configuration, not from the limits of Liquid itself.
Where to go from here
If you’re not sure which side of this decision your store falls on, that’s a completely normal place to be, it’s a genuinely nuanced call and getting it wrong in either direction is expensive. A good starting point is a Shopify audit to establish what’s actually driving your current pain points, or a call with our team to talk through your specific requirements and get a straight answer on whether headless is worth it for your store.
