Skip to content
dvnt.io

Resources · glossary

Headless commerce

A shop in which the sales engine — products, basket, payments — is separated from the presentation layer and connected to it through an API. You change the design and sales channels without touching the engine.

Also called
  • headless commerce
  • headless ecommerce
  • decoupled commerce
  • composable commerce
  1. 01

    Why separate them

    So that the same catalogue and the same basket can serve the shop, an app and sales through a partner without entering products three times. With a single channel this advantage is theoretical and not worth paying for.

  2. 02

    What you gain

    Freedom on the design side and usually a noticeably faster front end, because the presentation layer is no longer hostage to a theme and plugins. Changing a page layout stops being a risk to the checkout process.

  3. 03

    What you lose

    Ready-made themes, plugins and the whole part of the market that does “one-click installs”. What is a setting in a traditional shop can be developer work here — including things as ordinary as changing the product listing layout.

  4. 04

    When it pays off

    With many channels, a large catalogue and a team that can realistically maintain two components instead of one. Our platform quiz and TCO calculator work out this difference over three years, because over one year headless almost always looks more expensive.

Related terms

  • Headless CMSA content management system that stores content and serves it through an API but does not dictate how the site looks. The presentation layer is built separately, usually in a modern framework.
  • TCO (total cost of ownership)The sum of all the costs of a solution over its whole period of use, not just the price of implementation. It includes hosting, licences, maintenance, development and your team's work.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.