Shopify Theme vs Headless: How to Actually Choose
Alexander Mercer
Sep 1, 2026
Headless is the most over-recommended architecture in ecommerce. It is also, for a specific and identifiable minority of stores, exactly right. The difficulty is that the argument is usually conducted in terms of performance, where the honest answer is that a well-built Liquid theme and a well-built headless storefront perform about the same.
There are really three options, not two, and the middle one gets skipped far too often: stay on your theme and fix it, rebuild the theme properly, or go headless. Most stores asking about headless want the second one.
What you give up going headless
The theme editor, first and most consequentially. On a standard Shopify theme, a marketer rearranges sections, swaps a hero, launches a campaign landing page — all without a developer. Go headless and every one of those becomes a ticket, unless you also build and maintain a content management layer, which is a second product you now own.
The app ecosystem, second. A large share of Shopify apps inject their functionality through theme app extensions and script tags. On a headless storefront most of them simply do not work, and the ones that matter have to be reimplemented against their APIs — assuming they expose one.
Checkout is the exception that saves the whole model. Even headless, checkout stays with Shopify, which means you keep Shop Pay, PCI compliance and fraud analysis. That is not a limitation, it is the single best thing about the arrangement.
The signals that genuinely justify it
A frontend Liquid cannot express
Configurators, real-time personalisation, complex multi-step flows. Not "a nicer design" — something structurally beyond templating.
Multiple storefronts on one catalogue
Several brands, regions or B2B and DTC surfaces sharing inventory. Maintaining four themes in parallel is the pain headless removes.
Commerce inside a larger application
When the store is a feature of a bigger product rather than the product, the storefront belongs in that codebase.
Data from outside Shopify on the page
Live ERP stock, custom pricing logic, external availability. Achievable in Liquid up to a point, and past that point it stops being sane.
An engineering team that will still be there
The strongest signal, and the least technical. Headless is a permanent commitment to owning a frontend.
“A well-built Liquid theme and a well-built headless storefront perform about the same. If performance is the argument, you are having the wrong argument.”
HelloDevs
Why performance is usually the wrong reason
Nearly every slow Shopify store we audit is slow for the same handful of reasons, and none of them is Liquid. It is unoptimised imagery, a stack of analytics and marketing scripts loading synchronously, four apps injecting their own bundles, and a font strategy that blocks rendering.
Go headless without addressing any of that and you get a modern framework loading the same scripts, the same images and the same fonts. We have seen rebuilds land slower than the theme they replaced, because the new stack shipped a large JavaScript bundle to solve a problem that was never JavaScript's fault.
The productive sequence is to fix the theme first. It is faster and cheaper, and it tells you what your ceiling actually is. If you hit that ceiling and it is genuinely too low, the headless case is now evidence-based rather than aspirational.
Both halves of that sequence are things we do — Shopify theme development for the rebuild, and web development services when a headless storefront is the right answer.
The middle option nobody sells you
Online Store 2.0 changed what a theme can do more than most teams have caught up with. Section groups, app blocks, metafields and metaobjects between them cover a large amount of what people historically went headless to achieve — structured custom content, flexible layout, editor control over things that used to be hardcoded.
A properly rebuilt 2.0 theme, with a real performance budget and a deliberate approach to app scripts, is a substantially different product from a marketplace theme with nine years of modifications layered on it. It also costs a fraction of a headless build and keeps the entire app ecosystem and the theme editor.
For the majority of stores that come to us asking about headless, this is the recommendation. It is less exciting and it is usually correct.
How to decide
Write down the specific thing your current storefront cannot do. Not "it feels dated" — a concrete capability. Then ask whether Online Store 2.0 can express it. If it can, you have a theme project. If it genuinely cannot, and you have a team who will own a frontend for the next five years, you have a headless project.
If the specific thing turns out to be "it is slow", you have a performance project, and it is the cheapest of the three by a wide margin.
If you want an outside read on which of the three you are actually looking at, tell us what you are running.
Alexander Mercer
Senior Tech Writer at HelloDevs
Alexander covers software engineering culture, design systems, and frontend developer experience. When not writing, you can find him debugging React or exploring typography design.
Stay Updated
Get raw, honest dev-first tutorials and tech blog articles delivered straight to your inbox once a week.
Our guide
- A Shopify development agency builds and maintains the parts of a store Shopify does not give you out of the box. That means custom themes, apps, integrations with your other systems, and ongoing fixes. HelloDevs does all of this and also publishes its own Shopify apps.
- Yes. We work with merchants across North America, Europe, and Asia. Our process is async-first with scheduled overlap hours, so time zones have never been a blocker for a project.
- It depends on scope. Theme customisations typically start in the low four figures; custom apps and full builds range higher. After a free audit we give you a fixed quote — no hourly surprises.
- Absolutely. Private (custom) apps are a large part of our work — from small workflow automations to full ERP integrations that only your store uses.
- Every project ships with a support window, and most clients stay on a maintenance retainer: monitoring, Shopify update compatibility, and a direct line to the same developers who built it.
- Continuity and coverage. An agency gives you review processes, backup when someone is unavailable, and accumulated platform experience across many stores — with one point of accountability.
Didn't Got your answer?
If you still have questions or need further assistance, feel free to reach out to our team. We're here to help you every step of the way.
Our talk
Let's Connect!
Tell us your requirements and get a professional developer response.
