Photo: free stock photography (Unsplash licence) — see imprint
What commercetools actually is
A commerce API. No storefront, no admin theming, no CMS — a very good, very scalable set of services that your team assembles into a product. For a large retailer with several channels and an in-house platform team, that is genuinely the right architecture.
The part the sales deck skips
You now own the storefront, the CMS, the search integration, the admin tooling your merchandisers use and the glue between all of it. That is a permanent engineering team, not a project. Companies that buy composable without that team end up with an expensive API and a half-built shop.
Shopware's middle path
Shopware gives you a complete product and lets you go headless where it pays — Store API for a custom frontend, apps for extensions, the standard storefront everywhere else. You get most of the composable benefit exactly where you need it, without owning the parts you did not want to build.
The honest threshold
If you cannot name the five engineers who will own your storefront for the next three years, you are not ready for composable — and that is not a criticism, it is arithmetic. Come back to it when the constraint is genuinely the platform and not the team.
- commercetools is an API; you build the rest, forever.
- Composable without a permanent platform team is a trap.
- Shopware lets you go headless only where it pays.
Frequently asked questions
Probably not, and that is arithmetic rather than criticism. If you cannot name the five engineers who will own your storefront for the next three years, composable is not for you yet. It pays when the platform itself is genuinely the constraint — several channels, a real in-house platform team, requirements a complete product cannot express. That is a smaller set of companies than the market suggests.
The storefront, the CMS, the admin tooling your merchandisers work in, the search integration and all the glue between them. commercetools is a commerce API, and a very good one; the product your customers see is yours to build and yours to keep building. That is not a hidden catch — it is the architecture. It just has to be in the budget as a team, not a project.
Yes, via the Store API — and the useful part is that you choose where. Build a custom frontend for the channel that justifies it, keep the standard storefront everywhere else, extend with apps. You get the composable benefit at the points where it pays, without owning the CMS, the admin and the merchandising tools forever. Less pure, considerably cheaper to live with.
They end up with an expensive API and a half-built shop. The storefront ships late because there is no team to finish it, merchandisers work in tooling nobody had time to build, and every small change becomes an engineering ticket. Nothing failed technically. The architecture simply assumed a permanent platform team that was never hired.
We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.
Talk to an engineer