Composable commerce, headless commerce and MACH architecture are three labels that vendors, agencies and analysts often use as if they meant the same thing. They do not. Headless commerce is a way of separating a shop’s front end from its back end. Composable commerce is a strategy for building the whole commerce stack from interchangeable business capabilities. MACH is a set of technical principles, policed by an industry body, that describes how those capabilities should be built.
The distinction matters because each label commits you to a different budget, team and timeline. A headless storefront can be live in months on the platform you already run. A composable commerce programme can take years and several vendor contracts. And since 2026 the MACH Alliance no longer leads with its four-letter acronym at all: it now describes MACH as three principles, open, composable and connected, with AI agents firmly in view.
This guide defines each term in plain English, sets out the differences side by side, reviews what the latest research says, compares UK skills data and public platform prices, and finishes with a practical way to decide which approach fits your business. Every statistic is dated and sourced, and where a figure comes from a vendor-funded body, we say so.
Table of contents
- Composable Commerce, Headless and MACH: Three Terms Defined
- Composable Commerce vs Headless vs MACH at a Glance
- Headless Commerce Explained: What It Changes and What It Doesn’t
- Composable Commerce Explained: Packaged Business Capabilities
- MACH Architecture and Composable Commerce: Four Letters, Three Principles
- What the Research Says About Composable Commerce Results
- Composable Commerce Costs and Trade-Offs
- Headless vs Composable Commerce: Which Problem Are You Solving?
- Migrating to Composable Commerce Without a Big-Bang Rebuild
- Composable Commerce in the Age of AI Agents
- Choosing Platforms for Composable Commerce or Headless in the UK
- Composable Commerce vs Headless vs MACH FAQs
- References
Composable Commerce, Headless and MACH: Three Terms Defined
The fastest way to untangle the three terms is to ask what each one separates, and who decided what it means. One describes a layer, one describes a strategy and one describes a standard.
Headless commerce: separating the front end
Headless commerce splits the “head”, the customer-facing storefront, from the “body”, the commerce engine that holds products, prices, carts and orders. The two talk through APIs instead of sharing one code base and one template system.
That split lets a design team rebuild the storefront in a modern framework such as React or Next.js, or serve the same catalogue to a website, an app, a kiosk and a marketplace feed, without touching the engine underneath. We covered the customer-experience side in our earlier guide to headless e-commerce that people love.
Composable commerce: assembling business capabilities
Composable commerce goes much further. Instead of one platform supplying search, checkout, promotions, content and order management, each capability is chosen separately, often from a different specialist vendor, and connected through APIs. You compose the stack the way you would assemble a team: the best person for each job.
Gartner named composable commerce in 2020 and described its building blocks as packaged business capabilities, or PBCs. A composable commerce stack is therefore almost always headless, because a stack with no single platform also has no single built-in storefront.
MACH architecture: the technical standard
MACH originally stood for Microservices based, API-first, Cloud-native SaaS and Headless. The MACH Alliance, launched on 23 June 2020 by commercetools, Contentstack, EPAM Systems and Valtech, used the acronym to define what a modern commerce component should look like, and it certifies vendors and integrators against that definition.
So MACH is not a product or a strategy. It is a checklist for the parts. A composable commerce strategy built from MACH-certified parts is what most vendors mean when they say “MACH architecture”.
The one-sentence version
Headless separates the storefront, composable commerce separates every capability, and MACH describes how each separated part should be engineered. You can go headless without composable commerce, but you cannot really do composable commerce without going headless.
Composable Commerce vs Headless vs MACH at a Glance
The table below sets the three approaches side by side, from what each one separates to the risk that most often derails it.
| Aspect | Headless commerce | Composable commerce | MACH architecture |
|---|---|---|---|
| What it is | A front-end architecture pattern | A strategy for the whole stack | Technical principles plus a certification |
| What gets separated | Storefront from commerce engine | Every business capability from every other | Every service and interface |
| Who defines it | No single owner | Named by Gartner in 2020 | MACH Alliance, founded June 2020 |
| Unit of change | The presentation layer | A capability such as search or checkout | A microservice or API |
| Vendors involved | Usually one platform plus a framework | Several specialist vendors | Any certified vendor |
| Typical first step | A new storefront on the current platform | Replacing one weak capability | Vendor shortlisting against the standard |
| Main risk | A fast head on a slow back end | Integration sprawl and many contracts | Treating a badge as a business case |
Layer, strategy and standard
Read across the first row and the pattern is clear. Headless is a layer decision that an engineering team can make on its own. Composable commerce is a strategy decision that needs finance, operations and marketing at the table, because it changes contracts, data ownership and support. MACH is a procurement and engineering standard that helps you judge whether a vendor will fit either plan.
How the three nest inside each other
Think of three circles. Headless sits inside composable commerce, because every composable storefront is headless. Composable commerce sits largely inside the MACH principles, because the Alliance’s certification is built around modular, API-connected components. But the outer circles are not compulsory: plenty of successful retailers run a headless front end on a traditional suite and never adopt anything else.
Headless Commerce Explained: What It Changes and What It Doesn't
Headless is the most widely adopted of the three approaches because it solves a visible problem, a slow or design-locked storefront, without forcing a rebuild of everything behind it.
How a headless storefront works
In a traditional set-up the commerce platform renders every page from its own templates. In a headless set-up a separate front-end application requests products, prices and cart data from the platform’s APIs, then renders pages itself, often at the network edge for speed.
Content usually moves the same way. Marketing teams edit pages in a headless content management system, and the storefront pulls that content in alongside product data. Our comparison of WordPress vs headless CMS explains the trade-offs on the content side.
What headless leaves untouched
Headless changes how pages are built, not how the business runs. Pricing rules, promotions, stock logic, tax and order management all stay inside the original platform. If those are the bottleneck, a new storefront will look better and load faster while the real constraint stays exactly where it was.
That is the most common disappointment we see: a business funds a headless rebuild expecting composable commerce benefits, then discovers that merchandising still waits on the same release cycle because the promotions engine never moved.
Headless on the big platforms
Every major platform now offers a headless route. Shopify’s Hydrogen is an open-source React framework built on React Router 7, and Shopify includes Oxygen edge hosting for it at no extra cost on paid plans. Salesforce offers its Composable Storefront, built on the PWA Kit. Adobe unveiled Adobe Commerce as a Cloud Service at Adobe Summit 2025, a multi-tenant SaaS edition that is headless by default and serves its storefront through Edge Delivery Services.
So headless no longer means leaving your platform. It usually means using the platform’s APIs and framework instead of its templates.
Composable Commerce Explained: Packaged Business Capabilities
If headless is about the shop window, composable commerce is about the whole shop. It treats every capability as a replaceable part.
Where the term came from
Gartner introduced composable commerce in 2020, the same year the MACH Alliance launched. Its widely quoted prediction was that by 2023, organisations adopting a composable approach would outpace competitors by 80% in the speed of new feature implementation. Vendors still cite that figure, but it was a forecast, not a measured result, so treat it as a statement of intent.
The idea built on a decade of microservices practice and on the cost of monolithic suites, where one upgrade could take a year. We made the same argument about ERP in why fixed ERP suites are failing.
What a packaged business capability is
Gartner defines a packaged business capability as a bounded collection of data schema and a set of services, APIs and event channels. In plain terms, a PBC is a complete business function, such as product search, that owns its own data and can be swapped without rewriting its neighbours.
The word “complete” matters. A single microservice that calculates shipping rates is not a PBC. A shipping capability with its own rules, data, admin screens and APIs is.
A typical composable commerce stack
Most composable commerce stacks are built from the same eight or nine capabilities. The vendors below are examples that appear in MACH Alliance membership lists and analyst coverage, not recommendations.
| Capability | What it handles | Example vendors |
|---|---|---|
| Commerce engine | Catalogue, cart, checkout, pricing | commercetools, Elastic Path, Commerce.com |
| Content | Pages, campaigns, editorial | Contentful, Contentstack, Amplience |
| Search and discovery | Site search, ranking, recommendations | Algolia, Constructor, Bloomreach |
| Product information | Enriched product data for every channel | Akeneo, Salsify |
| Order management | Stock, routing, fulfilment | Fluent Commerce, Kibo |
| Payments | Card, wallet and local methods | Stripe, Adyen |
| Promotions and loyalty | Coupons, rules, rewards | Voucherify, Talon.One |
| Front end and hosting | Storefront build and edge delivery | Next.js on Vercel or Netlify, Hydrogen on Oxygen |
| Integration | Moving data between capabilities | Patchworks, MuleSoft |
Product data is often the first capability to break away from the suite, because it feeds every channel. Our PIM software guide covers how to choose one.
MACH Architecture and Composable Commerce: Four Letters, Three Principles
MACH gave composable commerce its engineering vocabulary. Each letter answers a practical question about a component you are about to buy.
Microservices
Microservices means the software is split into small, independently deployable services. A fault or an upgrade in one does not take the others down, and each can scale on its own, so the checkout can grow for Black Friday without paying to scale the content service too.
API-first
API-first means every function is exposed through a documented API before any user interface is built on top of it. If a vendor’s admin screen can do something its API cannot, the product fails this test, and your integrations will hit that wall eventually.
Cloud-native SaaS
Cloud-native SaaS means the vendor runs, scales and upgrades the service for you, with no version numbers to migrate between. It builds on the economics of cloud computing, and most such services are multi-tenant; our guide to single-tenant vs multi-tenant architecture explains what that means for isolation and cost.
Headless
Headless, the final letter, closes the loop: the component ships without a fixed front end, so you decide how and where it is presented. That is why every MACH stack is headless, while plenty of headless stacks are not MACH.
From four letters to three principles in 2026
The MACH Alliance now leads with the MACH Principles rather than the acronym: open, composable and connected. On its MACH Principles page, composable in practice means “microservices, headless architecture, best-of-breed selection”, while connected means “API-first design, MCP connectivity, event-driven integration” and multi-agent coordination. Open covers transparent APIs, observable services and portable data.
So the four letters survive inside the new wording, and composable commerce has become the Alliance’s headline idea. The visible addition is MCP, the Model Context Protocol that lets AI agents call software tools. The Alliance says it has more than 100 certified members.
What the Research Says About Composable Commerce Results
The most detailed research on composable commerce outcomes comes from the MACH Alliance itself. It is useful, but read it knowing who paid for it.
The 2025 adoption survey
The Alliance’s fifth annual survey, published on 14 January 2025, collected answers from 561 IT decision-makers at director level and above in the US, UK, Germany, France, Canada and Australia, all at companies with at least 5,000 employees and $500 million in turnover. It found that 87% had widely implemented MACH technologies and 9 in 10 said MACH had met or exceeded their ROI expectations.
The top benefits cited were greater automation through better systems integration (54%) and greater agility (50%). The biggest barriers were a lack of board or leadership support and IT teams resistant to change, which is a reminder that composable commerce is an organisational change before it is a technical one.
The 2026 AI readiness report
On 18 February 2026 the Alliance published its Enterprise Technology Report, a survey of 600 enterprise technology decision-makers in seven markets. Its headline finding links architecture maturity to AI returns.
Mature composable architecture is strongly associated with AI success in the Alliance’s 2026 survey:
The 78% against 13% gap is the “6X” figure in the Alliance’s press release. The same report found 37% of organisations cite integration complexity as a primary concern and 45% flag data privacy and security, while 89% say standards and certifications for AI in composable environments are missing.
Reading industry-body research with care
These surveys come from an alliance whose members sell composable commerce software and services. That does not make the numbers wrong, but it does shape the questions. A correlation between mature architecture and AI returns may also reflect bigger budgets and stronger engineering teams, which mature adopters tend to have anyway.
Gartner gives a more balanced signal. Its Hype Cycle for Digital Commerce, 2026 tracks composable commerce and modular commerce as separate entries among 27 technologies, and, as quoted by commercetools, says “composable commerce solutions are ideal for evolving AI and agentic commerce applications”. The separate modular entry matters: it broadly covers suites whose modules can be swapped, a middle path many buyers now prefer.
Composable Commerce Costs and Trade-Offs
Most composable commerce business cases underestimate the same three costs: contracts, integration and people.
Licences multiply
A suite is one contract. A composable commerce stack can be eight or nine, each with its own pricing model, renewal date, service levels and support desk. Procurement effort, legal review and vendor management all scale with that number, and none of it appears in a vendor’s demo.
Integration is the real bill
Every capability has to exchange data with the others: product changes to search, stock to checkout, orders to fulfilment, customer events to marketing. Someone has to build, monitor and own those connections. In practice the integration layer, whether an iPaaS, an event bus or custom middleware, becomes a product in its own right, with its own roadmap and on-call rota.
This is why the 2026 survey’s 37% integration-complexity figure is the most honest number in it. A badly governed composable commerce stack simply moves the monolith’s problems into the gaps between vendors.
Skills: what the UK job market shows
Composable commerce needs strong API, cloud and front-end engineering, and the UK job market shows how unevenly those skills are spread. Generic microservices skills are plentiful; platform-specific composable skills are rare.
UK permanent job adverts citing each skill tell the story, in the six months to 5 October 2026:
Bar widths are each count divided by the 2,098 microservices adverts. ITJobsWatch’s microservices data puts that skill’s median salary at £72,500, against £65,000 for Next.js, £42,500 for Magento and £40,000 for Shopify. Contentful and commercetools adverts were too few to give a meaningful median, and commercetools fell from 12 adverts in the same period of 2025 to 2.
The practical reading: you will hire general API and cloud engineers and train them on your chosen vendors, or rent that knowledge from a partner. Either way, budget for it from day one.
Speed and flexibility you can actually measure
The upside is real when the stack is governed well. Teams can upgrade one capability without a platform-wide release, test a new search vendor on one market, and add channels without rebuilding checkout. Measure that by lead time per change and by the cost of replacing a component, not by the number of vendors in the diagram.
Headless vs Composable Commerce: Which Problem Are You Solving?
The right choice depends on where your constraint sits. Start with the symptom, not the architecture diagram.
| Your situation | Likely best fit | Why |
|---|---|---|
| Slow or design-locked storefront, back office works | Headless on your current platform | Fixes the visible problem fast |
| One capability, such as search, holds back growth | Composable, one capability at a time | Replace the weak part only |
| Several brands, regions or B2B and B2C on one stack | Composable commerce | Shared services, different heads |
| Small team, no in-house developers | Stay on a SaaS suite | Apps cover most needs at low cost |
| Forced replatform on a tight deadline | Modular suite, composable later | Limits risk while keeping options open |
| AI agents must browse and buy | Any stack with full API coverage | Agents need APIs, not screens |
When headless alone is enough
If customers complain about speed, the brand team wants freedom the theme system will not give, or you need an app and a website from one catalogue, headless is usually enough. It is also the cheapest way to learn API-led delivery before committing to more.
When composable commerce pays off
Composable commerce earns its overhead when a business has outgrown what any single suite does well: several brands sharing one order system, marketplaces alongside direct sales, or a capability, such as complex B2B pricing, that no platform handles out of the box. It also suits firms with a strong engineering team that wants to own differentiating features.
When a suite is still right
A modern SaaS suite remains the right answer for most small and mid-sized UK retailers. If your needs are standard and your team is small, every extra vendor is cost without advantage. Our build vs buy vs low-code framework applies the same logic to software decisions generally.
Migrating to Composable Commerce Without a Big-Bang Rebuild
The firms that succeed with composable commerce rarely switch everything at once. They move one capability at a time while the old platform keeps trading.
Start with the head
Going headless first is the lowest-risk opening move. It puts an API layer between customers and the platform, which every later step depends on, and it gives the team experience of running a separate front end before the back end changes.
Strangle the monolith gradually
The strangler fig pattern, named by Martin Fowler, is the standard approach: route one function, such as search, to a new service, keep everything else on the old platform, then repeat. Each step is small enough to roll back, and the business sees value long before the migration ends.
Decide who owns the data
Before moving any capability, decide which system is the source of truth for products, prices, stock, customers and orders. Most failed composable commerce projects can be traced to two systems both believing they own the same record.
Put governance around the parts
Give every capability a named business owner, a technical owner and a service level. Hold quarterly reviews of vendor performance and cost. Without that discipline, a composable stack drifts into the very vendor sprawl it was meant to avoid.
Composable Commerce in the Age of AI Agents
The newest argument for composable commerce is not speed for human shoppers. It is access for software ones.
Why agents need APIs
Agentic AI changes who does the shopping. AI agents shop by calling software, not by clicking buttons. An agent comparing products, checking stock and placing an order needs clean, documented APIs for each step. A stack where key functions only exist behind an admin screen is invisible to them. This is where the connected principle and MCP support stop being jargon and start deciding whether your products can be bought by an assistant.
Shopify now points developers building shopping agents to its Universal Commerce Protocol, which exposes a store’s catalogue, cart and checkout to agents through MCP servers, and the Alliance’s 2026 principles name MCP connectivity explicitly. Expect MCP support to become a standard line in commerce platform tenders.
Certification and the Agent Ready award
On 8 July 2026 the Alliance named more than 30 members, including commercetools, Contentstack, Algolia, Stripe and Vercel, as the first recipients of its Agent Ready Award. The award sits on top of MACH certification and requires named agentic work in production, independently reviewed by the Alliance. At MACH X in Amsterdam on 30 September 2026, Bloomreach, Braze, Constructor, Hightouch, Patchworks and Voucherify won its Agentic Achievement awards.
“The conversation around agentic AI has moved on from what’s possible to what’s actually working,” said Jason Cottrell, president of the MACH Alliance. Treat awards as a shortlist signal, then ask every vendor for a reference customer running agents in production.
Choosing Platforms for Composable Commerce or Headless in the UK
Most UK buyers will compare a handful of platforms. Of the commercial platforms below, only Shopify publishes an enterprise list price; the others quote per deal.
| Platform | Approach | Headless route | Published price |
|---|---|---|---|
| Shopify Plus | SaaS suite | Hydrogen, with Oxygen hosting included | From US$2,300 a month on a 3-year term |
| Commerce.com (BigCommerce) | SaaS suite with open APIs | APIs plus the Makeswift visual builder | Enterprise on quote |
| commercetools | API-first commerce engine | Headless only; bring your own front end | On quote |
| Salesforce Commerce Cloud | Enterprise suite | Composable Storefront on PWA Kit | On quote |
| Adobe Commerce as a Cloud Service | Multi-tenant SaaS | Headless by default, Edge Delivery Services | On quote |
| Medusa | Open-source, MIT licence | Headless; bring your own front end | Free licence; you pay to host and build |
Reading the price table
Shopify Plus pricing starts at US$2,300 a month on a 3-year term or US$2,500 on a 1-year term, and higher-volume businesses move to a variable platform fee. On those list prices, a year costs US$27,600 on the longer term against US$30,000 on the shorter one. Licence fees are only part of the total: build, integration and support usually cost more over three years.
Note the name change too. BigCommerce Holdings became Commerce.com, Inc. on 31 July 2025, with its Nasdaq ticker moving from BIGC to CMRC, and the BigCommerce product continues under the new parent alongside Feedonomics and Makeswift.
Questions to ask every vendor
Ask which functions are available through APIs and which only through the admin screen. Ask how upgrades are delivered and whether you can defer them. Ask for a UK reference customer of similar size, which cybersecurity certifications cover the service, how data is exported if you leave, and whether the vendor supports MCP or publishes an agent integration roadmap. Then ask your integration partner the same questions about their own code.
Composable Commerce vs Headless vs MACH FAQs
Is headless commerce the same as composable commerce?
No. Headless separates only the storefront from the commerce engine. Composable commerce separates every business capability, from search to order management, and lets you source each one independently. All composable commerce is headless, but most headless commerce is not composable.
Is MACH the same as composable commerce?
Not quite. Composable commerce is the strategy; MACH is the set of engineering principles the parts should meet. The MACH Alliance now describes those principles as open, composable and connected, so the two ideas overlap more than ever.
Does the MACH acronym still matter?
Yes, as shorthand. Microservices, API-first, cloud-native SaaS and headless still describe what a good component looks like, and they now sit inside the Alliance’s three principles rather than leading them.
Can a small business use composable commerce?
It can, but it rarely should at the start. A small team usually gets more from a SaaS suite and its app store. Going headless, or swapping one capability such as search, is a sensible first step if a specific limit appears.
Is Shopify headless or composable?
Both, depending on how you use it. Standard Shopify is a suite with its own themes. Hydrogen and the Storefront API make it headless, and enterprise brands can use individual Shopify components inside a wider composable commerce stack.
Does composable commerce cost more than a suite?
Usually yes in years one and two, because of multiple licences, integration and specialist skills. The payback comes from faster change and from replacing weak components without a full replatform, which only materialises if the stack is well governed.
Whichever route you take, headless, composable commerce or a modern suite, the hard work sits in the integrations and the data. If you need an API layer, a headless storefront or a phased migration plan built around how your business actually trades, our software development team can help you scope it.
References
MACH Alliance: MACH Principles
MACH Alliance: Principles Explained
MACH Alliance: 6X More Organizations Achieve AI ROI With a Composable Foundation
MACH Alliance: 2025 Global Annual Research Report
Gartner: Hype Cycle for Digital Commerce, 2025
commercetools: Gartner Hype Cycle for Digital Commerce, 2026
Commerce.com: Second Quarter 2025 Financial Results
