Headless Commerce with commercetools

commercetools is an API-first, headless commerce platform built for businesses that have outgrown Shopify Plus or Magento and need a commerce backend that their engineering team can build on rather than around. Unlike monolithic platforms where the frontend, business logic and data layer are coupled, commercetools provides the commerce primitives (product catalogue, cart, checkout, orders, payments, inventory) as individual APIs and you compose them into whatever architecture your business requires. This article covers when commercetools is the right choice, how the architecture works, what it costs to build on, and how it connects to Amazon SP-API and other marketplace channels.

TL;DR

• commercetools is an API-first commerce backend. You get commerce primitives as APIs and compose your own architecture.
• It fits businesses doing $10M+ in annual GMV that need custom checkout logic, multi-channel orchestration, or marketplace integration that Shopify Plus cannot support.
• Build cost for a commercetools implementation starts at $11,000. Platform licensing starts at approximately $2,000 per month.
• The headless architecture makes marketplace integration (Amazon, eBay, Shopify storefronts) cleaner because commerce logic lives in the API layer, not in the frontend.

What commercetools is and what it is not

commercetools is a commerce backend, not a website builder. It does not come with a storefront, a theme, or a page editor. What it comes with is a set of APIs that handle the commerce operations every online business needs: product information management, pricing, inventory, cart, checkout, orders, payments, customer accounts, and discount rules. Your engineering team builds the frontend (React, Next.js, a mobile app, a kiosk, or all of the above) and connects it to commercetools via GraphQL or REST. This is what 'headless' means in practice: the head (frontend) and the body (commerce logic) are decoupled.

This decoupling matters for businesses that need commerce logic in multiple channels. If you sell through a website, a mobile app, a B2B portal and Amazon, the commerce logic (pricing rules, inventory, order routing) should live in one place. With a monolithic platform, that logic is embedded in the website layer and you end up duplicating or synchronising it across channels. With commercetools, the logic lives in the API layer and every channel calls the same APIs. The custom ecommerce tools team builds these multi-channel architectures.

When commercetools is the right choice

commercetools fits when three or more of the following are true: your annual GMV exceeds $10M and the platform fee scales better than Shopify Plus's percentage-based pricing. Your checkout logic is custom (B2B pricing tiers, multi-currency with tax-jurisdiction rules, or complex shipping calculations that Shopify's checkout extensions cannot handle). You sell through more than two channels and need a single source of truth for commerce operations. You have an engineering team that can build and maintain a custom frontend. You need to integrate deeply with marketplace connectors like Amazon SP-API where order and inventory data flows bidirectionally.

It does not fit when you are a single-channel D2C brand doing under $5M in annual GMV, when your checkout is standard, or when you do not have engineering capacity to build and maintain a custom frontend. In those cases, Shopify Plus or BigCommerce is the right answer. The headless commerce development guide covers the broader headless landscape and when it makes sense.

Architecture of a commercetools implementation

A typical commercetools architecture has four layers. The commerce layer is commercetools itself: product data, pricing, inventory, cart, checkout, orders. The integration layer connects commercetools to external systems: ERP for financials, PIM for product enrichment, payment processors (Stripe, Adyen), shipping providers, and marketplace APIs. The frontend layer is a custom React or Next.js application (or multiple applications for different channels). The orchestration layer handles business logic that spans multiple systems: order routing, inventory reservation, and cross-channel pricing rules.

The integration layer is where most of the engineering effort goes. commercetools has a marketplace of pre-built connectors for common integrations, but for anything custom (which includes Amazon SP-API development, complex ERP mappings, or multi-marketplace inventory sync), you build the connector yourself. The API integration service handles these custom connectors.

Marketplace integration with commercetools

For businesses selling on Amazon, eBay and their own storefront, commercetools becomes the commerce orchestration layer. Product data lives in commercetools. When a product is listed on Amazon, the listing data is pushed from commercetools to Amazon via SP-API. When an order comes in on Amazon, it flows back into commercetools for fulfillment routing. Inventory is managed in commercetools and synced outward to each channel. This is the same reconciliation pattern described in the Shopify to Amazon inventory sync article, but with commercetools as the source of truth instead of a purpose-built middleware.

Build cost and timeline

A commercetools implementation for a single-channel D2C storefront with standard checkout starts at $11,000 and ships in 10 to 14 weeks. A multi-channel implementation with marketplace integration (Amazon, eBay), custom checkout logic and ERP integration starts at $38,000 and ships in 16 to 24 weeks. commercetools platform licensing starts at approximately $2,000 per month and scales with GMV. Ongoing engineering support (feature development, connector maintenance, monitoring) runs from $2,200 per month depending on complexity. The custom software development page covers the broader development scope.

The customization layer: API Extensions and Subscriptions

commercetools provides two mechanisms for injecting custom business logic into the commerce flow without forking the platform. API Extensions are synchronous hooks that fire during an API call (for example, before a cart is updated or an order is created) and can modify the request or reject it. Subscriptions are asynchronous messages published when a resource changes (order created, inventory updated, customer registered) and delivered to a message queue (AWS SQS, Google Pub/Sub, Azure Service Bus). Extensions handle validation and enrichment (check stock before allowing add-to-cart, apply custom pricing rules). Subscriptions handle downstream workflows (send order to warehouse, update analytics pipeline, trigger email). Together, they replace the plugin and hook system that Magento developers are familiar with, but without the version-coupling and upgrade conflicts that make Magento extensions fragile.

commercetools versus Shopify Plus

Frequently Asked Questions

What is commercetools?

An API-first headless commerce platform. It provides commerce primitives (products, cart, checkout, orders, inventory) as APIs. You build the frontend and compose the architecture.

When should I use commercetools?

When annual GMV exceeds $10M, checkout logic is custom, you sell through 3+ channels, and you have engineering capacity for a custom frontend.

How does it connect to Amazon?

Via a custom integration layer using SP-API. Product data pushes from commercetools to Amazon. Orders flow back for fulfillment. Inventory syncs bidirectionally.

What does it cost to implement?

Single-channel from $11,000. Multi-channel with marketplace integration from $38,000. Maintenance from $2,200 per month.

How long does implementation take?

Single-channel: 10 to 14 weeks. Multi-channel with marketplace and ERP integration: 16 to 24 weeks.

How does it compare to Shopify Plus?

commercetools gives full control over checkout, native multi-channel, and better GMV-based pricing at scale. Shopify Plus is faster to launch and does not require an engineering team.

Do I need an engineering team?

Yes. commercetools is an API platform, not a website builder. You need engineers to build the frontend, the integration layer, and the orchestration logic. Expect a minimum team of two backend engineers and one frontend engineer for the initial build phase.

Can it handle B2B commerce?

Yes. Custom pricing tiers, account hierarchies, approval workflows and multi-currency are all built via the API. No plugin or theme limitations.