What "headless" means
The term comes from e-commerce. With a headless Shopify storefront, for example, you choose the stack, framework and hosting for the front end; data such as products and capabilities such as cart and checkout come from Shopify through an API [1]. A headless configurator applies the same idea: the logic is a service, the interface is replaceable.
Coupled, embedded, headless
| Architecture | Logic and interface | Suits |
|---|---|---|
| Coupled | one application | one channel, quick start |
| Embedded | own page in an iframe, talking via messages [2] | several websites, little change to the CMS |
| Headless | logic as an API, front end per channel | shop, app, sales and dealers share the same rules |
Benefits and cost
The benefit: rules and data exist once. Change a size limit and it applies in the shop, the dealer portal and the quoting tool at the same time, the same idea as central product information management.
The cost: every channel needs its own interface, and the 3D view must mirror the logic's state exactly. For a single channel, a coupled or embedded configurator is usually simpler.
Things to plan
- A unique configuration ID so every channel can open the same state, see configuration code.
- A clear answer on which system wins on prices and availability.
- Versioned rules, so old configurations stay traceable.
How configurators connect to shop systems is covered under shop integration.