Two approaches
| Approach | How it works | Strengths | Limits |
|---|---|---|---|
| State in the URL | every characteristic is a URL parameter | no server needed, instantly shareable | long links; rule changes can break old links |
| Short code | the state is stored, the URL holds only an ID | short, can be read out on the phone | needs 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
- Versioning: store the rule version with each configuration, so it stays clear what was valid at the time.
- Check on opening: an old link may have become invalid. The configurator should say what no longer works rather than silently change it.
- No personal data in the URL: names and email addresses do not belong in a shareable link.
- 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.