Shopify is an excellent commerce platform, and it’s one we’ve been using and continually testing alongside other ecommerce technologies for a long time.
Our starting point is always fairly simple: how do we give our clients the best possible ecommerce experience?
That means helping them attract more customers through search, convert more of those visitors into buyers, and ultimately make more money from their website.
There are good reasons Shopify is so often part of that conversation.
It is mature, reliable and familiar. Millions of customers already recognise the Shopify checkout experience, and retailers get a powerful back office for managing products, orders, inventory, payments and promotions.
For many businesses, a conventional Shopify store using a good theme is absolutely the right answer.
But there is a point where the theme itself can start getting in the way.
You have an idea for improving the buying experience. You want to test a different way of presenting a product. You need a new interaction, configurator, landing page or merchandising feature.
Then you discover that it doesn’t quite fit the theme.
So the theme gets customised.
Then customised again.
A script gets added here. A new section gets built there. An app injects something else. CSS overrides another part of the theme. Something that should have been a relatively simple experiment gradually becomes a development project.
And every change creates the possibility of another knock-on effect somewhere else.
This is what we think of as theme debt. Theme debt is one form of what we call digital bloat, the unnecessary code, content, integrations and complexity that websites gradually accumulate over time. Read more about digital bloat and how to prevent it.
Themes are incredibly useful until you start fighting them
Shopify themes solve an enormous number of problems.
They give you product pages, collection pages, navigation, baskets, promotional components and responsive layouts without having to design and develop all of those things from scratch.
A premium Shopify theme can therefore be an extremely efficient way to launch an ecommerce site.
The trade-off is that you are starting with someone else’s system.
The theme has assumptions about:
- how product pages should work;
- how collections should be presented;
- what content blocks are available;
- how navigation behaves;
- how components respond at different screen sizes;
- how styling is structured;
- and how merchants can edit the site.
If your requirements broadly match those assumptions, brilliant.
The difficulty comes when your business grows and the experience you want starts moving further away from them.
At that point, developers are no longer simply configuring a theme. They are modifying, overriding and extending it.
And that is where theme debt starts accumulating.
Theme debt is real
A Shopify store rarely becomes complicated overnight.
It usually happens through lots of perfectly reasonable decisions.
You install a reviews app.
Then you customise the product page.
Then there is a new promotional mechanic.
Then a redesign changes the way the product cards work.
Then another app is installed.
Then an old feature is removed, except some of its code remains.
Then somebody adds some CSS to fix something introduced by an earlier change.
Each decision makes sense individually.
Three or four years later, the store can contain layers of Liquid, JavaScript, CSS, app code, third-party scripts and historical customisations that nobody would choose if they were starting again today.
The theme might still look perfectly good from the outside.
Underneath, seemingly straightforward changes become harder to estimate and riskier to release.
Performance can become harder to control.
And experimentation slows down because every new idea has to be considered in the context of everything that has already been added.
That matters commercially.
If you want to test whether changing a product comparison tool, buying journey or product page improves conversion, you don’t want the cost and complexity of implementing the test to outweigh the likely benefit.
The alternative: keep Shopify, lose the theme
This is where headless Shopify becomes interesting.
A headless architecture separates the ecommerce engine from the customer-facing website.
With our approach:
Shopify runs the shop.
It handles your products, inventory, pricing, orders, promotions, cart and checkout.
Next.js runs the website your customers experience.
We build that frontend using React 19 and TypeScript, with a design system created specifically for the business rather than adapting an existing Shopify theme.
The two communicate through Shopify’s Storefront API.
Vercel delivers it to customers.
The frontend is deployed through Vercel’s global infrastructure, giving us a modern development and deployment environment designed specifically for applications like this.
Another way of putting it is:
You keep the parts of Shopify it is exceptionally good at, without having to let a Shopify theme dictate what your website can be.
Headless Shopify has traditionally had one big problem: cost
None of this is particularly new.
Headless commerce has been available for years.
The problem has traditionally been economics.
Building a completely bespoke frontend application requires more architecture, more engineering and more specialist development expertise than installing and customising a Shopify theme.
We’ve seen headless ecommerce projects where the starting point is around £70,000, before getting into particularly complicated requirements.
For many businesses, that makes the decision straightforward.
The additional flexibility might be desirable, but not £70,000 desirable.
This is one of the reasons we’ve spent a significant amount of time working on the development process behind our own headless Shopify builds.
Making headless development dramatically more efficient
Working with partners in the industry, we’ve developed an ultra-modern, AI-supported development workflow around Next.js and Shopify.
More importantly, we are not starting from a completely blank repository every time.
We’ve built and refined the underlying framework that handles much of the communication between the storefront and Shopify.
Products.
Collections.
Cart functionality.
Checkout.
Common ecommerce behaviour.
The foundations already exist.
That means our development time can be concentrated much more heavily on the thing that should actually be unique:
your customer’s experience.
We can design and develop the frontend components quickly, while working from a proven commerce architecture underneath.
The result is that we’re able to bring the cost of developing a headless Shopify storefront much closer to the cost of developing a genuinely premium, highly customised Shopify theme.
And that changes the calculation considerably.
The question is no longer:
“Is headless worth spending several times our website budget on?”
It becomes:
“If the cost is comparable, would we rather customise someone else’s theme or build the experience we actually want?”
Design what you want, rather than what the theme allows
This is perhaps the biggest practical difference.
On a conventional Shopify project, conversations can sometimes become:
That’s a good idea, but we’d need to work out how to make it fit the theme.
With our headless approach, we can start from a different position:
What would make this experience better for the customer?
Of course there are still technical constraints. Every technology has them.
But we’re no longer trying to squeeze each idea into the predefined structure of a Shopify theme.
If you have an idea for how customers should discover, compare, understand or purchase your products, there is a very good chance we can build it.
That could mean:
- an interactive product finder;
- sophisticated comparison tools;
- custom product configurators;
- unusual collection experiences;
- editorial content integrated directly with products;
- highly bespoke product pages;
- richer search and filtering;
- personalised buying journeys;
- or something we haven’t thought of yet.
This becomes particularly powerful when you treat the website as something that continually evolves.
Build, measure, test, improve
We don’t really believe in the idea that a good ecommerce website is ever “finished”.
Whether your store uses a Shopify theme or a headless frontend, leaving it untouched for several years isn’t a particularly good strategy.
Customer expectations change.
Products change.
Search changes.
Competitors change.
Devices and browsers change.
And most importantly, you learn more about what makes your customers buy.
The advantage of a clean headless storefront is that experimentation doesn’t have to mean continually adding another layer of customisation to an existing theme.
We can introduce an idea, measure it, learn from it and iterate.
If it works, we develop it further.
If it doesn’t, we remove it.
That’s a much healthier model than allowing years of experiments to accumulate inside a theme until nobody is completely sure which code is still doing what.
For ecommerce businesses with meaningful traffic, continuous conversion-rate optimisation should be part of running the store, not something reserved for the next redesign.
The technology should make that easier.
What about maintenance?
One of the arguments sometimes made in favour of a traditional Shopify theme is that it requires very little maintenance.
We think that’s slightly optimistic.
The Shopify platform itself certainly removes a huge amount of infrastructure maintenance. You are not managing ecommerce servers, patching the checkout or maintaining a payment platform.
That’s a major benefit, and it remains true in our headless architecture.
The custom frontend itself is also relatively lightweight from a maintenance perspective.
There isn’t a CMS theme constantly being patched or a large collection of plugins all independently updating themselves.
The main piece we need to keep an eye on is the integration between the frontend and Shopify, including API versions and dependencies. That’s something we test and maintain as part of looking after the platform.
But we’d argue that every commercially important ecommerce website should already have someone looking after it.
A conventional Shopify theme should still be reviewed.
Are apps adding unnecessary scripts?
Has performance deteriorated?
Are there old features that should be removed?
Has the theme accumulated technical debt?
Are customers behaving differently?
Could the buying journey perform better?
Are there opportunities to improve organic search?
Maintenance shouldn’t simply mean installing updates when something breaks.
It should mean continually protecting and improving the commercial performance of the website.
That applies whichever architecture you choose.
What about Shopify apps?
This is one area where there is a genuine difference.
The Shopify app ecosystem is one of the strengths of the platform, and many apps are designed specifically to inject functionality into Shopify themes.
When the theme is removed, those frontend integrations don’t necessarily work automatically.
That doesn’t mean you can’t use apps.
Many have APIs that allow us to integrate their functionality directly. Others operate primarily within the Shopify backend and continue working as normal. Sometimes it makes more sense for us to build the functionality ourselves rather than introducing another third-party layer.
But it does mean integrations need to be considered properly.
For us, that’s part of the discovery process.
We look at what the business already uses, what each system actually does, and how it should fit into the new architecture.
Sometimes an integration represents additional work.
Sometimes removing the dependency on an app actually makes the resulting site simpler.
What about editing the website?
Shopify’s visual theme editor is genuinely useful.
If giving internal teams the ability to build almost any page by dragging sections around is a central requirement, a conventional theme may remain the better option.
But there’s another side to that flexibility.
The more control a content editor has over layout, spacing, components, colours and presentation, the easier it is for the consistency of the website to gradually deteriorate.
Our preference is normally to give teams structured flexibility.
Content that should be editable is editable.
Products remain managed in Shopify.
Reusable content can be managed through appropriate fields or content systems.
Campaign and landing-page requirements can be designed into the platform.
But the underlying design system remains controlled.
That helps preserve the quality and consistency of the customer experience over time.
So when would we still recommend a Shopify theme?
Quite often.
Headless isn’t automatically better simply because it uses newer technology.
If you are launching a straightforward ecommerce business, your requirements are well served by an existing premium theme, budgets are tight and speed to market matters more than differentiation, we’d probably tell you to use the theme.
That’s one of Shopify’s strengths.
Headless becomes much more interesting when:
- your current theme increasingly feels like a constraint;
- custom development has created significant theme debt;
- your customer experience is an important competitive advantage;
- you want to experiment frequently with conversion;
- performance has become difficult to control;
- your products require a more sophisticated buying journey;
- your website needs to integrate deeply with other systems;
- or you simply have ideas that don’t fit comfortably into a conventional Shopify storefront.
Until relatively recently, we’d have added another criterion:
you have a very substantial development budget.
That’s the part we think has changed.
A different economics for headless Shopify
The technologies that make headless commerce possible have existed for some time.
What’s changing is how efficiently we can build with them.
Modern frameworks, reusable architecture and AI-supported development are allowing us to compress work that once made bespoke ecommerce applications prohibitively expensive.
Our aim is to bring the economics much closer to those of a premium Shopify build while retaining the advantages of a genuinely custom frontend.
You still get Shopify where Shopify makes sense.
Products. Orders. Inventory. Cart. Checkout. Administration.
But the customer-facing experience belongs to you.
No inherited theme.
No fighting against somebody else’s layout assumptions.
Much less opportunity for years of theme debt to accumulate.
And a much cleaner foundation for continually testing, learning and improving.
For the right ecommerce business, that’s a much more interesting way to build.
Is your theme holding back your bottom line?
Get in touch with our team for a custom store audit, or explore our case studies to see how we’ve helped brands transition from off-the-shelf templates to high-converting bespoke builds.
