Commercetools: Fully API-first microservices-based commerce engine

What is Commercetools?

An API-first e-commerce platform delivers all commerce logic (pricing, inventory, orders, payments) through REST and GraphQL APIs, without a ready-made shop around it. Commercetools is the most consistent implementation of that idea. You build your frontend in React, Vue or whatever your team uses, and connect your own CMS, PIM, analytics and fulfilment. The platform runs as managed SaaS: infrastructure, scaling and monitoring are handled by Commercetools.

What makes Commercetools different?

It was designed as a set of APIs from the ground up. Many platforms are a shop system with an API bolted on later; Commercetools is the API, with a management interface (the Merchant Center) on top that you can tailor to your own needs. For you, that means no dependency on their UI, data model or upgrade cycle. You build what you need and leave out the rest.

That freedom has a downside. Because there is no ready-made shop, every implementation is a build project. A demo storefront comes up quickly; a production implementation with all your integrations does not. Without your own developers or a good partner you will get stuck.

Where Commercetools really shines is complexity. Five brands on one inventory, B2B and B2C side by side, multiple countries with their own pricing and campaigns: every channel gets its own frontend on the same commerce engine.

Strengths.

Full freedom in your frontend: no standard features getting in the way, you build exactly what your customers need

Multi-brand and multi-country by design: several brands, countries and channels on a single engine

Strong B2B support: company accounts, bulk ordering, quote flows and permissions come as standard

No upgrade cycles: APIs stay backward compatible, so your own code does not break on a new release

Managed SaaS: no infrastructure to run yourself

Who uses Commercetools?

Commercetools targets enterprise organisations and has a solid customer base in retail, automotive and B2B:

Ulta Beauty: large American cosmetics chain, multi-channel

Frasers Group: British retail group (Sports Direct, House of Fraser, Flannels) running several brands on one platform

BMW Group: parts commerce and B2B channels through the Commercetools APIs

Cepheid: medical diagnostics, B2B commerce with supply-chain integrations

Our vision.

In our experience, Commercetools is the standard for large organisations with complex commerce requirements. It is not a platform you switch on and use. You build something on it, and that takes a technical team and time. Once it is in place, you have a commerce stack that you control. How well it fits depends mostly on the maturity of your organisation.

Suitable for

Large organisations with complex commerce requirements: multi-brand, multi-tenant, custom workflows

Retailers with their own tech team of fullstack and frontend developers

Companies that want to work composable, with the best tool for each function (CMS, PIM, analytics, fulfilment)

International environments with multiple currencies, languages and compliance regimes

Note upon

It is a build project. With an experienced partner and commercetools for Builders (since June 2026: a library of AI skills for Claude Code, Cursor and v0) you can go live in a few weeks to a few months; complex enterprise projects with multiple order streams and ERP integrations run closer to 9 to 12 months, sometimes longer

It is expensive. Custom development, Commercetools engineers and integration partners quickly add up to an investment of €300k to well over €1 million

Smaller companies find it too bare. Without your own tech team you become dependent on consultancy

Data residency: Commercetools runs on GCP by default, with AWS as an option. You choose the region per project; Europe is available on both (Belgium on GCP, Frankfurt on AWS)

Is Commercetools suitable for enterprise?

Yes. This is what the platform was built for. Where Shopify Plus puts limits on custom workflows, pricing logic and B2B complexity, Commercetools has none. The price you pay is time and money. For large multi-brand environments it is, in most cases, the best choice.

Summary: Commercetools gives you maximum freedom if you are willing to invest. It is a commerce engine your team builds on, not enterprise software you install. For organisations that want full control and have the developers for it, little else comes close. For the smaller mid-market it is usually too heavy.

Need help choosing a commerce platform? We are happy to think along about Commercetools, MACH architecture and implementation, no strings attached.

Schedule a call

In practice.

Integrations & ecosystem

Because everything is an API, Commercetools connects to almost any system:

Frontends: React, Vue, Next.js, Remix, or a storefront framework such as Frontastic (part of Commercetools)

CMS: Contentful, Sanity, Storyblok, or a traditional CMS

PIM: Akeneo, Salsify, custom solutions

Order management: SAP, Oracle, custom OMS

Payments: Adyen, Stripe, PayU, local gateways

Fulfilment: any WMS, you build the integration yourself

Analytics: custom pipelines to Segment, Datadog or a data warehouse

The Commercetools Marketplace offers over a hundred ready-made connectors. The starting point is still that you do the integrating.

Implementation

Timeline: a few weeks to a few months for a focused implementation with an experienced partner, especially since commercetools for Builders. Full enterprise projects with ERP integrations and multiple order streams run 9 to 12 months, sometimes longer.

Learning curve: steep. Your team needs to understand GraphQL, REST API design and event-driven architecture. This is not a platform for non-technical users.

What to expect: first design the commerce architecture and API strategy, then build the frontend and integrations, then test, train and optimise. How those phases balance out depends on your scope and on how much your partner has built before.

Support & community

Support: enterprise support with SLAs and technical account managers. No chat support; this is dedicated professional support.

Community: smaller than Shopify's, but technically stronger. An active Slack community, Stack Overflow and plenty of blogs from implementation partners.

Documentation: excellent. The API docs are among the best in the market, with tutorials and best practices for commerce patterns.

AI & further development

Current: Commercetools has an MCP server (Model Context Protocol) that lets AI agents such as Claude work directly with the commerce APIs. This makes agentic commerce possible: an agent that searches products, fills a basket and places an order. Since June 2026 there is also commercetools for Builders: a library of AI skills that lets you generate a storefront, catalogue and checkout from Claude Code, Cursor or v0.

Roadmap: the focus is on agentic commerce, better composability and event-driven commerce logic, where everything reacts to events rather than polling.

Compare with alternatives.

How does Commercetools compare to Shopify?

They sit at opposite ends of the spectrum. Shopify goes live fast, with a lot of standard functionality and little to configure. Commercetools needs a longer build: you configure the commerce logic and build the frontend yourself. For SMEs, Shopify is faster and cheaper. For enterprise organisations with complex requirements, Commercetools is more flexible and gives more control in the long run.

See also our analyses of other solutions:

Shopify: all-in-one SaaS, fast to market, less flexibility

BigCommerce: middle ground, SaaS with a larger API surface

Frequently asked questions.

How long does a Commercetools implementation take?

Highly dependent on scope: with an experienced partner a few weeks to a few months for a focused implementation, 9 to 12 months or longer for large enterprise projects with complex order streams and ERP integrations.

What does Commercetools cost?

On request. Pricing depends on complexity (B2C or B2B, order streams, integrations) and order volume, and typically sits in the higher enterprise segment. Budget a further €300k to well over €1 million for the implementation.

Can I use Commercetools headless?

Yes, that is the whole idea. You build your own frontend in React, Vue or another framework; Commercetools provides the APIs.

Is Commercetools suitable for B2B?

Yes, and well suited. Company accounts, bulk ordering, quote flows and permissions come as standard.

Do I need my own tech team?

Yes, or an experienced implementation partner. At minimum fullstack developers and a product owner. Without your own developers you depend on consultancy.

What is the MACH Alliance?

An industry body that defines best practices for Microservices, API-first, Cloud-native and Headless architecture. Commercetools is a co-founder.

Need help choosing your e-commerce platform?

Breakfast helps you make the right choice. Independent advice, no hidden agendas.

Schedule a discovery call