Product configurator rules: dependencies, exclusions and valid combinations

Capture rules in business language

Start with the people who currently approve configurations. Ask for ordinary orders, rejected combinations and the reasons behind them. Record the condition, affected choice and expected outcome. A spreadsheet containing only option names will miss the relationships that make the product model useful.

For a fictional modular display manufacturer, a wide frame might need an additional support and restrict one accessory. Document that as an approved product rule with an owner. Do not turn an illustrative example into an engineering recommendation; the manufacturer must provide and approve its own limits.

Distinguish several kinds of rule

Salesforce’s product-rule overview distinguishes validation, selection, filtering and alerts. These are useful categories for a buying brief: prevent an invalid result, add a required item, limit available choices or explain a condition.

Decide which response suits each business rule. Hiding an option, disabling it with an explanation and allowing a review request create different user experiences. A customer should understand why a choice is unavailable where that explanation helps them proceed. Keep the explanation consistent with the approved rule rather than inventing a technical justification.

Test changes to an earlier selection

Complete a valid configuration, then change its base product, size or material. Inspect every dependent choice, price and output. The system needs a defined response when a previously selected accessory becomes unavailable. Leaving the old value hidden in the saved record is not the same as removing or resolving it.

For the display manufacturer, ask whether the user must confirm replacement choices. Review what happens when a configuration is saved and reopened. Keep the visible selection, structured specification and quotation aligned. A fresh happy-path order may not expose a dependency error that appears only during revision.

Create a compact rule register

Give each rule a stable reference and owner. Include its source, such as an approved catalogue or engineering decision. Keep draft rules distinguishable from released ones so a developer is not asked to interpret conflicting informal instructions.

Keep visualisation and validation aligned

Configurix’s pergola overview connects catalogue dimensions and compatible choices with a visual sales workflow. In a procurement test, ask the supplier to show that the same saved choices feed the preview and the specification.

A rendered accessory should correspond to the selected option, while an invalid combination should have a consistent outcome across the interface and export. Test a configuration where the visual asset is not available. The team needs an honest representation of what the system knows, rather than a convincing image that conceals an unresolved rule.

Define exceptions without weakening the normal rules

Some enquiries need a specialist decision. Provide a route that preserves the request and marks it as unresolved. Avoid a universal override that silently turns every invalid combination into an approved order. Record who may approve an exception and which revision the decision covers.

For the display manufacturer, a custom mounting requirement could be sent for engineering review while the remaining specification stays intact. Once approved, the final record should explain the exception and its applicable scope. The CTO and ETO guide explores that boundary.

Maintain rules as part of the product lifecycle

Plan how a new material, discontinued accessory or changed dimensional limit reaches the configurator. Keep a regression set of ordinary and boundary cases. Review the result before releasing the updated model and define how existing quotes are handled.

The pricing-rule guide covers commercial calculations, while the Configurix profile provides vendor context. A useful rule model is understandable to its owners and testable after change; it should not depend on one developer remembering why a combination was blocked.

Frequently asked questions