Glossary
A commerce architecture where the front-end presentation layer is decoupled from the back-end commerce engine, communicating through APIs — letting a business change the customer-facing experience without touching the underlying commerce logic.
Why It Matters
Traditional commerce platforms bundle the storefront and the backend together, so changing how the store looks or works often means fighting the platform's built-in templating system. Headless commerce frees the front end to be built however makes sense — a website, an app, a voice interface — while the backend (inventory, pricing, checkout logic) stays stable underneath.
This is part of our Intelligent Commerce capability — commerce infrastructure built around the customer relationship, not just the transaction.
See the full Intelligent Commerce capabilityRelated Terms
Does headless commerce mean building everything from scratch?
Not necessarily — many commerce platforms now offer headless APIs on top of their existing backend, so a business can adopt a headless front end without replacing the entire commerce engine.
Is headless commerce right for every business?
It adds development complexity that isn't worth it for a simple storefront with no unusual front-end requirements. It earns its complexity when a business needs the front end and backend to evolve independently, or needs to power multiple front-end experiences from one commerce engine.