Composable Commerce Explained — Without the Buzzwords

Composable commerce is one of the most used — and most abused — terms in the e-commerce industry right now. It gets thrown into sales presentations, analyst reports and procurement documents, often without anyone in the room being able to explain it to a colleague in the finance department. This is an attempt to do exactly that: explain composable commerce in plain English, without buzzwords, and above all answer the question that actually matters — when is it worth anything to your business?

What composable commerce means — in one minute

Traditional e-commerce platforms are monoliths: one large piece of software containing everything — product catalogue, cart, checkout, promotions, content, search. Everything is connected, everything is upgraded together, and if you want to replace one part you often have to replace the whole.

Composable commerce is the opposite idea: the e-commerce solution is assembled from separate parts that talk to each other via APIs. Product information can live in one system, the checkout in another, search in a third, and the customer-facing interface — the store you see — can be built independently on top. Each part can be replaced without tearing down the rest.

That is the whole idea. The rest is variations on the theme. Terms you will encounter in the same breath:

• Headless — separating the store’s interface (the front) from the business logic (the back). A subset of composable, not a synonym. We have written separately about when headless is worth it.
• API-first — the system’s capabilities are built to be accessed by other systems, not just by its own interface.
• Best-of-breed — choosing the best component in each category instead of one vendor’s bundle.
• MACH — an acronym (Microservices, API-first, Cloud-native, Headless) describing the same architectural ideal.

The problem composable commerce solves

The weakness of monoliths shows over time. The store grows, requirements change, and suddenly you are stuck: the search is too weak but cannot be replaced, the promotion engine cannot handle B2B prices, and every upgrade is a project because everything is connected. Many Magento merchants will recognise this — major version upgrades that are in practice rebuilds. Our comparison with Magento goes deeper into exactly that.

Composable solves this through replaceability. If you need better search, you replace the search engine, not the platform. If you want to open a new sales channel — an app, a marketplace, in-store screens — that channel fetches the same product data and prices via API, without a new build underneath. The business value, in other words, is not the architecture itself. It is pace of change: being able to alter one part of the solution tomorrow without putting the whole at risk.

That is also why the concept has taken hold in B2B specifically. Business commerce carries more logic than consumer commerce — contract prices, assortment control, integrations with ERP systems — and in a monolith every such custom piece means building yourself deeper into something you will one day have to leave. In a composable architecture, the logic lives where it belongs and is reached from there by every channel.

What the sales presentations skip

Here comes the part of the explanation that is usually missing. Full-scale composable — where you select and connect every component yourself — moves responsibility from the vendor to you:

• The integration responsibility. Ten best-of-breed systems means nine connections that someone has to build, monitor and maintain. That someone is your team or your agency.
• The troubleshooting. When the price shows up wrong in the checkout — is it the PIM, the pricing engine, the API layer or the frontend? In a monolith there is one vendor to call. In a self-assembled solution, you are the systems integrator.
• The cost. Multiple licences, multiple contracts, more developer time. Composable in its purest form is built for organisations with their own development teams.

The conclusion is not that composable is wrong — it is that the degree of composable has to match your organisation. A global brand with twenty developers can own the whole map. A Nordic merchant with three people on e-commerce should not have to become their own IT company to get a modern architecture.

Composable with common sense: the Nordic middle way

There is a middle way, and it is the one we have chosen ourselves with HDL Commerce: a composable platform where the core — product data, prices, orders, B2B and B2C in one core, with a built-in PIM — is cohesive and managed by one vendor, while everything around it is open and replaceable via APIs and ready-made integrations.

You get replaceability where it creates value: switch ERP, switch frontend, add channels, connect new services. But you avoid taking on the systems integrator role for the core flows, and you have one vendor responsible for operations — in our case hosted and operated in Sweden, with 99.3% uptime. The point is not that our model is the only right one, but that “composable” is not a yes/no choice. It is a scale, and the right position on that scale is determined by your team, your integration map and your pace of change — not by what sounds most modern.

Three questions that decide whether composable is right for you

Strip away the jargon and the decision boils down to three questions. Answer them honestly — preferably in writing, together with whoever owns the budget — before any vendor gets to show architecture diagrams:

1. How often do you need to change? If the store is in practice stable year after year, you are paying for flexibility you never use. If you are constantly building new things — channels, markets, services — the replaceability pays for itself quickly.
2. Who will maintain the connections? In-house development team: full-scale composable is feasible. Small team: choose a platform where the vendor owns the integrations.
3. Where does custom-built make a real difference? Spend your flexibility budget where the customer notices it — often the frontend and the channels — and buy proven standard for the rest.

Want to see how it works in practice?

The easiest way to understand composable commerce is to see it running, not to read more about it. Book a demo and we will show you how the core, the PIM and the integrations fit together in HDL Commerce — and if you are considering leaving a monolith, we will do a free migration analysis of your current solution. Get started here.