Glossary

Composable commerce

Composable commerce assembles best-of-breed services for every layer of the ecommerce stack through APIs. Commerce, search, CMS, payment, CRM, and PIM each come from a specialist vendor.

Composable commerce is an architectural approach where each capability in an ecommerce stack comes from a separate specialist vendor and connects through APIs. It extends the decoupling principle of headless commerce to every layer of the stack.

Composable commerce is an architectural approach where each capability in an ecommerce stack — commerce engine, search, CMS, payment, CRM, PIM, OMS — comes from a separate specialist vendor and connects to the rest of the stack through APIs. Each capability is a Packaged Business Capability (PBC). The merchant assembles a working ecommerce system from best-of-breed services rather than buying a single monolithic platform. The term was popularized by Gartner in 2020 as the next stage beyond headless commerce. Where headless decouples the storefront from the commerce engine, composable decouples every layer of the stack from every other. ## Composable vs headless vs MACH The three terms overlap but are not the same. Headless decouples one boundary: the storefront from the commerce engine. Composable extends decoupling to every layer of the stack. MACH (Microservices, API-first, Cloud-native, Headless) is a stricter set of architectural principles formalized by the MACH Alliance in 2020. A MACH-compliant stack is composable by definition. A composable stack is not necessarily MACH-compliant. A composable stack is always headless; a headless stack is not always composable. ## Packaged Business Capabilities A PBC is the unit of composition in a composable stack. Common categories include commerce engines (Norce, commercetools, Shopware), search and discovery (Algolia, Hello Retail, Meilisearch), headless CMS (Storyblok, Contentful), PIM (Akeneo, Plytix), payment (Klarna, Stripe), CRM and CDP (Voyado, Klaviyo), reviews (Lipscore, Trustpilot), and order management (fluent commerce, nShift). A real composable stack picks one PBC per capability and integrates them through APIs. ## How Frntkey relates Frntkey is a frontend-as-a-service that fits into composable architecture. The storefront connects to Storyblok as the CMS, Meilisearch or Hello Retail for search, Klarna or Walley for payment, Voyado for CRM, and Lipscore for reviews — each a distinct PBC. The commerce engine is Norce or Shopware. The architecture is composable-ready without requiring full composable from day one. For the long-form explanation of composable commerce, including when to choose it and when not to, see the composable commerce pillar post. ## Related terms Headless architecture · Headless commerce · Headless CMS · MACH architecture

Frequently asked questions

Ready to talk?

See how Frntkey fits your stack. Book a 30-minute demo.

Book a demo