Glossary · E-commerce

Configuration code and share link

In short

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.

Two approaches

ApproachHow it worksStrengthsLimits
State in the URLevery characteristic is a URL parameterno server needed, instantly shareablelong links; rule changes can break old links
Short codethe state is stored, the URL holds only an IDshort, can be read out on the phoneneeds storage and retention rules

In the browser, configurators read and write URL parameters with the URLSearchParams interface [1]. history.replaceState() updates the address on every change without adding a new history entry [2], so the back button does not step through every single click.

What the code is for

  • Buyers save a state, come back later or show it to someone.
  • Sales open exactly the variant the buyer saw, straight from the enquiry.
  • Dealers receive a configuration without retyping it, see dealer handover.
  • Shop and ERP match order and configuration, see shop integration.

What to plan

  1. Versioning: store the rule version with each configuration, so it stays clear what was valid at the time.
  2. Check on opening: an old link may have become invalid. The configurator should say what no longer works rather than silently change it.
  3. No personal data in the URL: names and email addresses do not belong in a shareable link.
  4. No price in the link: the system recalculates prices on opening, see price logic.

Where the code appears in an enquiry is shown in enquiries, surveys and dealers.

Related terms

  • Request for quote (RFQ)

    A request for quote (RFQ) is how a configurator ends when no fixed price is possible: the checked configuration goes to sales or a dealer, who turn it into a binding quote.

  • Dealer handover

    Dealer handover is the step in which an enquiry from the configurator goes to the responsible dealer, installer or field sales – complete, traceable and without anyone retyping the configuration.

  • Headless configurator

    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.

  • 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.

  • Lead qualification

    Lead qualification means sorting an incoming enquiry by how well it fits your offer and how urgent it is: product, size, region, timing, the enquirer's role. A configurator gathers much of this along the way, because the buyer provides it while configuring.

More in our guides

Sources

  1. MDN Web Docs: URLSearchParams
  2. MDN Web Docs: History.replaceState()

← All terms in the glossary