Headless commerce is an ecommerce architecture that separates the front end, the part customers see, from the back-end commerce engine that manages products, carts, orders and payments. The two communicate through APIs, so the storefront can be built and changed independently of the platform behind it.
In a traditional platform the theme, templates and commerce logic are tightly bundled. In a headless setup the back end exposes its functions as APIs, and a separate front end, often built with a JavaScript framework, requests product data and sends cart and checkout actions. The same back end can feed a website, a mobile app, a kiosk or a smart display.
Retailers adopt it when they want a highly customised experience, faster page loads, content-rich pages or a single commerce engine serving several channels and brands. It also lets a team redesign the storefront without replatforming the stock and order systems underneath.
The trade-off is complexity. Features that a standard platform provides out of the box, such as previews, plugins and checkout flows, may need to be built or sourced separately. Development effort, hosting and ongoing maintenance are usually higher, and a small business with straightforward needs may be better served by a conventional platform. Good API design and monitoring are essential because more moving parts can fail.
Headless commerce matters because it gives larger or fast-changing retailers room to adapt their customer experience without being locked to one template system. It suits businesses planning an omnichannel approach where web, app and store systems all draw on shared data.