How do you prepare compatible options for a product configurator?
Start with the options for one product family. Here is what to review in your guided selling experience so you offer consistent choices before sharing your link.
Separate shared options from available values.
Two products can share an option while offering different values. A finish may be common across the range, while a dimension or attachment fits only certain models. Record these differences in your preparation material so buyers do not discover them only after sending their request.
In SmartSelect, options are defined within the configurator and assigned to products with their available values. Start with combinations you actually offer. A missing row in an incomplete document does not prove compatibility or incompatibility.
Describe a dependency in a statement you can verify.
A dependency identifies when a choice should be presented. For a fictional example: ‘The sensor is available only with the automatic controller.’ Documentation or a qualified person at the manufacturer must confirm that statement.
Record the source, the choice that controls availability and the products concerned. If two documents disagree, resolve the issue before publication. The assistant cannot replace missing technical validation.
| What to specify | Fictional example |
|---|---|
| The dependent choice | Sensor |
| The prerequisite | Automatic controller selected |
| The scope | Models confirmed by the manufacturer |
| The evidence to retain | Current product sheet or confirmation from your technical team |
Present choices in a coherent order.
Visitors should be able to choose a controller before seeing options that depend on it. This order makes the journey easier to follow. A display preference should not silently change your product logic.
Start with the first version created from your materials, then explore the choices as a customer. The AI assistant can explain how SmartSelect works and help with supported adjustments. You retain control of availability and conditions in the editor, including those that cannot be changed through conversation.
Test what happens when a buyer goes back.
Buyers do not always follow a straight path. They may select an option, return to an earlier question or compare a different product. Review both what becomes available and what is no longer available.
In the fictional Atlas Machinerie example, explore the products and choices to observe a configured journey. Then use your own business cases to validate your draft; a generic demonstration does not certify combinations in your catalog.
- Select a value when its prerequisite is satisfied.
- Change that earlier choice and check which options remain possible.
- Switch products and check the values available for the new model.
- Review the summary for any choice that has become inconsistent.
- Check items left for confirmation with sales when that permission is enabled.
Keep the context through the sales handoff.
A useful request identifies the product, its options and the information still to confirm. When several configurations are grouped together, each must remain identifiable: an option chosen for one model must not be attributed to another.
After an adjustment, repeat the affected cases in the draft. Explicitly publish changes once the review is complete. The salesperson retains responsibility for final advice and the commercial proposal.