Product configurators: freedom of choice needs clearly recorded constraints
Show option dependencies and give an unambiguous result: handle conflicts, changes, resets and saving selections for an order.
Article language: English

In this article
A customer builds an organiser from modules, choosing a wide base, two containers and a lid. At the end they discover the lid fits only the narrower version. They must reverse several decisions but do not know which parts they will lose. The configurator offers plenty of freedom and very little orientation.
Customers should be able to see the relationships between choices. A configurator should help them build one result that can be ordered or quoted. It needs rules, explanations and a way back. An impressive preview may help, but it cannot replace a definition of what the company can actually provide.
First establish what the customer is building
Choosing a ready-made variant and assembling a set are different tasks. In the first, the customer finds one existing version. In the second, they select components that form a combined result. If ordinary product variant selection (in Polish) is enough, there is no need to call it an elaborate configurator or add steps that contribute no decision.
A set, on the other hand, need not be a single item with several labels. It can consist of separate products, quantities and parameters. Shopify's bundle documentation distinguishes fixed and customised bundles, the latter also intended for more complex selection of components. Adapt your own scope to the result and the system in use.
Record what should exist at the end: an order, a request for a quote or a saved idea for discussion. Each result needs a different degree of certainty in the data. Do not call a configuration a ready order if a staff member still needs to confirm feasibility. The customer should recognise the stage without reading fine print under the button.
For modular equipment, collect actual rules from the product owner. A designer does not determine permissible loads or technical compatibility from how parts look. They can help record confirmed conditions and translate them into understandable choices. Structural calculations and an extensive pricing engine need separate scope and appropriate responsibility.
A rule should have a reason the buyer can understand
Imagine a fictional organiser system where a particular lid fits only one type of container. This dependency can be shown from the start, explained after an earlier choice or applied as a condition for the next step. Hiding an incompatible option may be quick, but it can make the full offer harder to understand. Choose the presentation to suit the buyer's task.
Not all constraints mean the same thing. Some concern compatibility, others availability, quantities or fulfilment. "Cannot be selected" does not distinguish them. The customer should know whether to change the base, wait for a part or simply reduce the number of accessories. The reason points towards a remedy.
Record the rule outside the mockup too. Content and implementation need an unambiguous definition: what is checked, at which choice, and what counts as a valid result. Include a matching example and a conflict. Otherwise the design may show one interpretation while the store's mechanism rejects the configuration under another.
Check the dependency in both directions. If the container is selected first, lid choices may be narrowed automatically. If the customer returns and changes the container, the earlier lid needs reassessment. This step is often missed: the interface works on the way forward but loses meaning after the first deliberate change of mind.
Do not silently erase the entire set. Show which decisions remain valid and which need correction. Preserve independent items if the system can. When a change affects the whole set, explain its scope before confirmation. The customer should not discover lost work only by seeing an empty preview.
Option names should show the difference. Two similar accessories need an explanation of their uses, not just two catalogue numbers. A layout used for comparing two services (in Polish) may help, but the criteria must concern the actual components. Do not create a false "good, better, best" hierarchy when the customer is choosing different functions.
Follow one hypothetical conflict. A customer chooses a wide base, a high-sided container and a flat lid. Product rules allow that lid only with a low container. The interface should identify that exact relationship. A message saying the whole configuration is invalid is not enough when two of the three components still fit.
You could suggest changing the lid or returning to the container type. Show the effect of each route before the decision. If the customer needs a high interior, changing the container is not equivalent. They know why they made the choice. The design helps them judge consequences instead of treating every formally valid configuration as an equally good answer to their task.
In the rule list, distinguish hard conditions from suggestions. An aesthetic recommendation should not block a purchase like a confirmed incompatibility. If you recommend a combination, name the criterion. This preserves freedom where the product allows it and firmly stops a choice where necessary.
Show the state of the assembled result
During the process, the customer needs to see what they have chosen and what is missing. A summary need not occupy half the screen, but it should identify the set and outstanding decisions. "80% complete" is less useful than explaining that a closure still needs to be selected for one module.
Distinguish a working selection from a confirmed one. If the preview updates only after a stage is confirmed, say so. If it changes immediately, do not leave an old image beside a new parts list without indicating that an update is pending. Microinteractions (in Polish) should confirm the effect, not merely decorate option switches.

Price needs separate attention. It may be known for the complete set, indicative or available only after a quote. Name the nature of the number and show missing conditions. Presenting prices (in Polish) helps organise the decision, but a stronger button label should not turn an estimate into a store commitment.
If the result uses a calculation, separate inputs and assumptions. The number of modules may depend on the space entered, while suitability for the specific use needs additional knowledge. Our article on a website calculator (in Polish) explains that boundary. Here you also need a relationship between the calculated number and the parts actually offered.
The visual preview should show the selected state. Establish whether it faithfully represents the set or illustrates the idea. Do not allow a text change to leave the old arrangement of parts in the image. If the view is simplified, clearly state what it does not show. Sometimes a simple drawing and a list are enough to explain the differences.
Aeneia Design
We design configurators from the offer's rules and the intended result. Let us agree the option dependencies, the summary and the implementation scope needed for your store or enquiry.
Going back and resetting are part of the design
If customers can start from a ready-made set, label it as a starting point. They should see which parts were present initially and which they changed themselves. This makes it easier to return to the original without confusing it with an empty configuration. A default set should not look like a personal recommendation if it was chosen only to demonstrate possibilities.
In reset labels, distinguish returning to the starting set from removing every selection. Show the result after the action. If the price was recalculated or parts replaced, customers should be able to check without repeating the whole form. Remember someone may have opened an existing configuration from a received link rather than starting with an empty page.
A customer may want to go back one step, change one component or start over. These are three different actions. Control names and placement should distinguish them. Do not put "clear everything" where the user expects only to close an accessories panel. Saving a few pixels can cost the customer their entire unfinished configuration.
Show the effect of a changed decision. Some parts may remain, while others become incompatible. If you provide an automatic correction, make it understandable and inspectable. A formally valid set does not necessarily still match the buyer's intention. Changing the base does not authorise the interface to choose a new function on its own.
On a phone, keep the current stage and summary accessible without jumping between the top and bottom of the page. A long form need not become a chain of tiny windows. A normal layout with well-labelled sections may be easier. Check whether a user can compare two choices without losing the existing set when closing a supporting view.
When an error occurs, preserve as much valid work as possible. An incomplete configuration should identify what is missing; a data retrieval problem should suggest an appropriate way to recover the state. These messages must not look identical. A person should not have to correct valid options when the cause is a temporary lack of response from the system.
A saved configuration must be recognisable later
If customers can share their selection, decide what is actually saved. The preview's appearance alone does not identify parts and quantities. You need a state that can be restored and associated with an offer version. Otherwise an account manager receives a pretty screenshot but still has to ask which part was selected on the left. When a configuration enters a saved-for-later product list (in Polish), distinguish a remembered idea from a set that remains available.
MDN describes URLSearchParams as a way to work with address parameters. These can carry selections, but their presence in an address does not guarantee reconstruction. The application must read the values, check their meaning against the current catalogue and show the result appropriate to that state.
Open a saved link in a new session and compare the parts list with the original selection. Also inspect the address after the offer changes: a withdrawn component, a new compatibility rule or a renamed variant. Do not silently substitute the first available option. Explain that part of the old set needs a new decision while preserving the remaining information.
A result sent with an enquiry should contain enough data for a person to understand the subject. A summary, identifier and version may matter more than a long marketing description. If the customer still needs to add a material or explain the use, show that gap directly. Sending a configuration does not automatically confirm feasibility.
Before building, an interactive demo (in Polish) can test understanding of dependencies. Label its scope and sample data. This trial can assess the selection journey before integrations exist, but should not be treated as proof that the real catalogue, inventory or order logic works.
Aeneia Design brings structure, content and interactions together within an agreed scope. Bring real options and several conflicts that customer service already knows how to resolve. Freedom of choice can then lead to a concrete set, without a customer needing an employee to interpret a grey button.











