Headless commerce is the default recommendation from a lot of agencies, partly because it is more interesting to build and considerably more expensive to buy. It is a genuinely superior architecture for a specific set of stores. For everyone else it converts a solved problem into an ongoing engineering commitment.
What headless actually changes
In a standard Shopify build, the theme layer renders your storefront. Going headless means you build the storefront yourself and talk to Shopify through its APIs, keeping the cart, checkout and back office while replacing everything customers see.
You gain total control of the experience and can compose data from other systems freely. You take on responsibility for things the theme layer handled for free: rendering, caching, SEO output, accessibility, and every app integration that assumed a theme existed.
Stay on a theme if most of these are true
- Your catalogue is under a few thousand SKUs with conventional merchandising.
- You rely on apps that expect theme integration.
- You have no in-house engineers and no plans to hire any.
- Your conversion problems are speed and clarity, not missing capability.
- You need to be trading in weeks rather than quarters.
Go headless if several of these are true
- Your storefront must combine commerce with substantial editorial or user-generated content.
- You sell across several brands or regions from shared inventory.
- You need merchandising logic the theme layer genuinely cannot express.
- You have engineering capacity to own a front end long-term.
- Storefront performance is a real competitive differentiator in your category.
If the honest reason for going headless is that the current site feels dated, you want a redesign. That is a fraction of the cost and most of the benefit.
The cost nobody quotes
The build is the visible number. The ongoing one is maintenance: dependency updates, API version migrations, and the fact that every future app integration becomes a development ticket rather than an install button. Budget for that as a permanent line item, not a one-off.
A pragmatic middle path
You do not have to choose all at once. Several of our clients run a headless front end for high-traffic landing and collection pages while leaving standard product and checkout flows on the theme. You capture the performance gains where traffic concentrates without taking on the whole surface area at once — and you can always go further later.