Headless commerce is an online store setup where the customer-facing storefront is separated from the commerce engine that handles products, carts, orders and payments, and the two talk through an API. It suits growing stores that need a custom frontend, several sales channels or tighter speed control than a theme allows. Most small stores do not need it yet.
| Question | Standard theme (Shopify or WooCommerce) | Headless commerce |
|---|---|---|
| Who builds the storefront? | The platform's theme system, edited by a designer or store owner | A custom frontend, for example React or Next.js, built by developers |
| Design freedom | Bound by theme templates and app blocks | Anything you can design and code |
| Sales channels | Mainly the website, plus the platform's own channel tools | Web, mobile app, in-store screens and more from one engine |
| Running cost | Platform plan plus apps | Engine plan, frontend hosting, developer time and monitoring |
| Team needed | Store owner and maybe a freelancer | Developers who own a codebase, plus a content owner |
| Main risk | Outgrowing theme limits | Paying for flexibility you never use |
Headless commerce splits an online store into two parts: the storefront shoppers see (the head) and the commerce engine behind it that holds products, prices, carts, orders and payments. The two parts exchange data through an API, so you can rebuild or replace one without touching the other.
Think of a shop with a window and a stockroom. In a standard store, the window and stockroom are built as one unit by the same supplier. In a headless store, you keep the stockroom, with its stock records and till, and design a completely new window that talks to it through a hatch.
The UK government's export guidance describes an e-commerce platform as software integrated into your website that enables you to sell your products over the internet. Headless keeps that software but changes how the website part connects to it.
If you also run a SaaS product, the content layer question overlaps with our earlier piece on headless CMS vs monolith for SaaS. This article stays on the shop side: carts, checkout and catalogues.
A theme is the storefront layer that comes bundled with the platform, so design, templates and checkout are tied to one system. Headless commerce replaces that layer with a separately built frontend, often in React or Next.js, which pulls product and cart data from the platform through an API. You gain control and take on more build work.
With a theme, you pick a design, adjust sections and add apps. WooCommerce is open source and runs on WordPress, so you have a lot of freedom, but the page still renders through WordPress templates. Shopify is a hosted all-in-one platform; you work inside its theme system and its app ecosystem.
With headless, nothing about the page is inherited. You decide how a product grid loads, what the basket drawer does, how search behaves and how pages are cached. That freedom is the whole point, and also the whole bill.
People searching "monolithic vs headless" are usually asking about the same split. A monolithic store bundles storefront, engine and admin into one system. A headless store separates the storefront. A composable store goes one step further and swaps in separate best-of-breed services for search, content, reviews and payments, all joined by APIs.
| Approach | What you get | Who it fits | Trade-off |
|---|---|---|---|
| Monolithic (theme) | One system, one login, one supplier | Most stores under about one sales channel and a standard design | Limited by the platform's templates and apps |
| Headless | Custom storefront on top of one commerce engine | Brands with a distinct design or several channels | You maintain a codebase |
| Composable | Many specialist services joined by APIs | Larger teams with in-house engineering | More vendors, more contracts, more integration upkeep |
For a growing UK or Northern European store, "headless on one engine" is usually the sensible middle. Full composable setups add vendors quickly, and each vendor adds a bill, a contract and a failure point.
The real benefits are three: pages you can tune for speed because you control the code, a custom frontend that is not limited by theme layouts, and one commerce engine feeding several channels such as web, mobile app and in-store screens. None is automatic; each depends on how well the frontend is built and maintained.

Themes load whatever the theme and its apps load. Every app can add scripts, and over time pages get heavier. A custom Next.js storefront lets you decide what ships to the browser, how images are sized, which pages are pre-rendered and what is cached.
The catch is that headless is not faster by default. We have seen the logic go both ways: a lean build beats a theme heavy with apps, and a sloppy build loses to a clean theme. Speed is a result of discipline, so ask any agency how it will measure it and what the target is before you sign.
Some products need more than a grid and a button. A furniture brand may want a room configurator. A subscription box may want a build-your-own flow. A B2B supplier may want quote lists and account pricing. These are awkward in a theme and natural in custom code.
Design matters as much as code here, which is why we pair the build with UI/UX design work done in Figma before any frontend is written. A custom storefront with weak design is just an expensive theme.
If the same catalogue and stock must show up on your website, a mobile app, a marketplace feed and a screen in a shop, headless avoids copying data between systems. Each channel is a different head on the same engine.
Our app development team builds cross-platform apps with React Native, so one codebase serves iOS and Android and can share API logic with a Next.js storefront. For first-time app owners, our explainer on cross-platform app development covers what that means in practice.
Growing stores outgrow spreadsheets. Stock lives in an ERP, customers in a CRM, parcels in a courier system. A small Node.js layer between storefront and back office lets you connect these in one place instead of through a stack of plugins. It is the same pattern we use for payment gateways, CRM connectors, ERP bridges and logistics APIs in other projects.
Headless costs more than a theme because you pay for the commerce engine and for a custom frontend, plus hosting and ongoing maintenance. One public UK listing shows a BigCommerce licence at £399 a month. You also need frontend developers, someone who knows the commerce API, and a person who owns content and merchandising.
That £399 figure comes from a supplier listing on the UK Digital Marketplace, which also notes a 15-day free trial. Treat it as one data point for an engine licence, not a standard price. Plans differ by vendor, store size and region, so check current pricing directly.
For a sense of day-rate scale, one supplier listing for composable and headless CMS implementation and support shows £525 to £1,800 a unit a day. That is a UK public-sector catalogue entry for CMS work, not an Axire quote, but it shows how widely rates can spread by supplier and seniority.
Suppose a store assumes 30 build days for a custom storefront. At the £525 to £1,800 daily range above, that is £15,750 to £54,000 for the frontend alone, before the engine plan, hosting and any content layer work. On the same assumption, a BigCommerce-style licence at £399 a month adds £4,788 over twelve months.
The 30 days is an invented planning figure, not a benchmark. The point is the shape: a theme store has almost no build line, and a headless store has a large one. For a wider view of where budgets leak, see our e-commerce website development cost breakdown.
Many small stores cannot staff that list. If you would be relying on one freelancer who may not be available in a year, treat that as a serious risk, not a detail.
A store should stay on a standard theme when its catalogue is small, its design needs are ordinary, it sells through one website, and it has no developer on call. In those cases a well-built theme with a few apps does the job for far less money and far less risk.

The first is losing SEO value. Rebuilding URLs, redirects, sitemaps, structured data and canonical tags is manual work in a custom frontend. Skip any of it and rankings can drop after launch.
The second is rebuilding checkout without a reason. Checkout is where payment rules such as PSD2 strong customer authentication, tax and local payment methods all meet. Unless you have a clear need, keep the platform's checkout and customise around it.
The third is forgetting the editors. If marketing cannot preview a page before it goes live, headless will frustrate them within a month. Preview and publishing flows need to be part of the build, not an afterthought.
One thing remains open even for us: how much of the frontend speed advantage survives once a store adds the same analytics, consent and chat scripts it had before. The answer differs store by store, so measure on your own pages.
Score your store against these checks. Each one has a pass mark that points you toward headless and a mark that tells you to wait.
| Check | Points toward headless | Walk away if |
|---|---|---|
| Design needs | You have tried theme customisation and a specific, valuable feature still cannot be built | Your wish list fits a theme with minor changes |
| Channels | Two or more channels need the same catalogue and stock, such as web and a mobile app | Everything sells through one website |
| Integrations | Your ERP, CRM or logistics tools need custom connections that plugins handle badly | Existing plugins already work without regular failures |
| Team | You have a retainer or in-house developers committed for at least a year | Nobody can own the code after launch |
| Budget | You can fund the build and a yearly maintenance line | The build would use money needed for stock or marketing |
| Proof | You can name the revenue or retention gain you expect and how you will measure it | The case is "it would be more modern" |
Our rule of thumb: if you pass four of the six, run a scoped discovery before committing. If you pass two or fewer, spend the money on theme improvements, product content and speed fixes first.
If your current site feels slow, our guide for SMBs turning a website into a full e-commerce app covers adjacent options worth comparing first.
We are a lean development studio based in Ahmedabad, India, working remotely with startups and businesses across Europe, with overlap with CET afternoons. We have been in digital transformation for over 3 years and are trusted by 10+ companies worldwide. Our storefront work uses React, Next.js, Node.js and Supabase.
Every project follows the same four steps: Discovery and Planning, Design and Prototyping, Development and Testing, then Launch and Support. For headless, discovery is where we test whether you need it at all. Sometimes the honest answer is a theme with a few targeted changes, and we would rather say so up front.
If you do proceed, our web development service covers the frontend and API layer, and the same team can add a mobile app later. You can see the full list on our services page, and past builds such as Media Mates, MustQR, Solace Sofas and Nextn on our projects page. More background reading sits in our article library.
Not automatically. A headless storefront can load faster because you control every script, image and rendering choice, but a badly built one is slower than a tidy theme. Speed comes from build quality, caching and how many third-party scripts you add, not from the architecture label alone.
It can be, but it is not a free upgrade. A Next.js storefront can render pages on the server so search engines see full content, and you control URLs and metadata. You must also rebuild redirects, sitemaps and structured data by hand, and mistakes there can cost rankings.
Yes. Either can act as the commerce engine while a separate frontend handles the storefront, since WooCommerce is open source and Shopify is a hosted platform with an API. Check each platform's current API limits and checkout rules before committing, because they decide what you can customise.
No. A mobile app is one reason, but not the only one. Custom design, speed targets and integrations with ERP or logistics systems can justify it alone. If an app is on your roadmap, a shared engine plus React Native can reuse the same product and order data.
Yes, though it takes work. Your products, customers and orders live in the commerce engine, so they stay put. You would lose the custom frontend and rebuild a theme, which is why a small pilot on one section of the store is a safer first step than a full switch.
Headless commerce rewards stores with a clear reason: a design a theme cannot deliver, several channels on one catalogue, or integrations that plugins handle badly. For everyone else, it is an expensive way to feel modern.
If you are weighing it up, tell us your platform, channels and what a theme cannot do today. Contact Axire Infotech or email hello@axire.in, and we reply within 2 hours during business hours with an honest view on whether headless commerce fits your store.
Let's discuss your project and create something amazing together.