Skip to content

Headless commerce

Headless commerce separates the storefront from the commerce system. Interfaces connect its data and commerce capabilities.

E-Commerce

Developing the storefront and commerce system separately

Headless commerce is an architectural approach that separates the visible storefront from the commerce system behind it. The frontend obtains data and commerce capabilities through interfaces. It can therefore be built with its own design tools while capabilities such as products and the cart come from the commerce platform. This separation does not determine whether commerce is provided by one platform or several specialised services. The connection between the parts remains necessary for purchasing.

In a fictional service-equipment shop, a customer selects a grey tool bag. The custom frontend displays that version; the cart in the commerce system must receive the same variant. Incorrect identifier mapping could send another version to the cart even though the product view looks right. A planned change would therefore need to trace the same selection through the interface into the cart. A separate frontend can be designed independently, but its handovers must still fit the commerce system.

Sources

Related terms

Articles on this topic

Insights · E-Commerce2 minHeadless shop: which customer task justifies the work?A custom storefront needs a concrete purpose. An example separates brand presentation, specialised buying workflows and ongoing operation.Daniel HartmannNov 13, 2026
Insights · E-Commerce2 minAssess B2B ordering separately before replacing the ERPA new customer interface can build on the existing ERP. Reliable data access, confirmed orders and integration limits determine whether it works.Lena FischerNov 13, 2026
Insights · E-Commerce2 minSelling in several countries needs more than translated textLanguage, delivery country, currency and payment are separate settings. A fictional country switch shows what needs to be checked together.Anna NeumannNov 13, 2026
Insights · E-Commerce2 minReconcile cart abandonment with order statusCompare missing purchase events with linked order and payment data. Three fictional journeys show different next investigations.Anna NeumannNov 13, 2026
Insights · E-Commerce2 minReturn analysis needs the product information shown at purchaseA return reason needs links to the variant and product information at purchase before changing shop software. The current catalogue may show a different version.Lena FischerNov 13, 2026
Insights · E-Commerce2 minAssess a shop relaunch by version and customer journeyEvaluate visible purchase journeys and internal processing together after a relaunch. Version links and comparable observations inform the next change.Lena FischerNov 13, 2026
Insights · E-Commerce2 minDesign customer and field sales apps around their tasksCustomer reordering and field sales work for assigned customers need clear flows. An example shows where company context, drafts and shared components matter.Lena FischerNov 13, 2026
Insights · E-Commerce2 minChoose payment methods for customer needs and operationsFor each additional payment method, assess the missing customer route, technical suitability, refunds and operational reconciliation.Lena FischerNov 13, 2026

E-Commerce with ASES

Online shops, marketplaces and B2B portals

Request a quoteMore on E-Commerce