Composable commerce
An online store assembled from separate catalog, search, content, payment, and fulfillment services that can be replaced independently.
See it
What it is
Composable commerce builds a store from separate capabilities rather than buying one platform that does everything. A team might combine commercetools for catalog and carts, Contentful for editorial content, Algolia for search, and Stripe for payments behind one storefront. The MACH Alliance, formed in 2020, put the label on it: microservices, API-first, cloud-native, headless.
Reach for it when different parts of the business need genuinely different tools or must evolve on separate schedules. Each capability gets a clear contract, so search or promotions can be replaced without rewriting the whole customer experience. That flexibility pays off only when the organization can own the integration layer.
Gotcha: a stack of products is not automatically an architecture. Someone must define which system owns products, prices, customers, inventory, and orders, then handle failures between them. Without stable interfaces, observability, and a migration plan for each service, the result is more vendors and more failure modes, not more freedom.
Ask AI for it
Design a composable commerce backend-for-frontend that combines commercetools for products and carts, Contentful for editorial content, Algolia for search, and Stripe PaymentIntents for payment. Define a typed adapter interface for each capability, keep system-of-record ownership explicit, and expose one storefront API that returns composed product pages without leaking vendor response shapes. Add webhook signature verification, idempotent event consumers, OpenTelemetry traces, timeouts, retries with exponential backoff and jitter, circuit breakers, cached read fallbacks, contract tests, and a feature-flagged path for replacing any one adapter.