Composable Commerce Mental Model

Understand where Commercetools ends, where your enterprise platform begins, and how to avoid over-customizing the commerce core.

35 min

3 sections

architecture

composable-commerce

platform

01. Start with ownership boundaries

Section 1 of 3

Commercetools should be treated as the commerce system of record for catalog, cart, order, pricing, discount, customer, B2B, and extensibility resources. Your experience layer, orchestration services, ERP, OMS, PIM, tax provider, payment gateway, search stack, and data platform should integrate around those resource boundaries instead of turning the platform into a generic database.

text

Enterprise reference boundary:

Frontend / BFF
  -> Customer session, personalization, UX composition

Commercetools Composable Commerce
  -> Products, Product Projections, Carts, Orders, Prices, Discounts
  -> Customers, Business Units, Stores, Channels, Payments
  -> Types, Custom Fields, API Extensions, Subscriptions

Enterprise services
  -> ERP inventory truth, OMS fulfillment, fraud, loyalty, tax, search, analytics

Projects, API Clients, Auth, and Scopes

Back to Course