Glossary · Configurators

Headless configurator

In short

A headless configurator separates the configuration logic (options, rules, prices, result) from the interface. The logic is reached through an API, and each channel – shop page, app, 3D view, dealer portal – builds its own front end.

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

ArchitectureLogic and interfaceSuits
Coupledone applicationone channel, quick start
Embeddedown page in an iframe, talking via messages [2]several websites, little change to the CMS
Headlesslogic as an API, front end per channelshop, 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.

Related terms

  • Embedding with an iframe

    Embedding with an iframe runs the configurator as its own document inside your page. The two sides exchange data such as the finished configuration safely via postMessage, and loading="lazy" defers the frame until it comes near the viewport.

  • Shop integration (Shopify, Shopware, WooCommerce)

    Shop integration means the configurator hands the chosen configuration to Shopify, Shopware or WooCommerce so that basket, price, order and production all see the same details. The core question is what becomes a variant and what becomes an extra property.

  • Configuration code and share link

    A configuration code (or configuration number) is a unique ID that reopens a configuration exactly as it was. As a share link it sits in a web address that buyers can pass on or attach to an enquiry.

  • Product data and PIM

    Product information management (PIM) is the process of managing the information needed to market and sell products, from one central hub that feeds websites, catalogues, marketplaces and partners. For a configurator, a PIM can be the source of options, texts and part numbers.

  • 3D configurator

    A 3D configurator is a product configurator that shows every choice immediately on a 3D model the buyer can turn in the browser. Visual feedback is described as a core feature of configuration systems. More: [3D configurator](/en/3d-configurator/)

More in our guides

Sources

  1. Shopify Dev Docs: Headless commerce
  2. MDN Web Docs: Window.postMessage()

← All terms in the glossary