What a rule is
A configuration rule links a condition to a consequence. Common forms:
- Dependency: option B is only available with option A.
- Exclusion: drive C does not fit widths B1 and B2.
- Size limit: width between 3.00 and 7.00 m in 10 cm steps.
- Calculation: a value follows from others, such as an area, a quantity or a volume.
- Default: choosing X sets Y automatically.
Without rules, the number of combinations multiplies. Wikipedia uses the example of a truck maker: the chosen chassis limits the possible engines, the engine in turn limits the trailers, and with many options the problem becomes a combinatorial explosion [1].
Where rules live
In ERP systems rules are often called dependencies. In SAP they exclude impossible combinations and select the matching components and operations [2]. In a web configurator they are best held as data rather than scattered through the code, so they can be tested and maintained by people who know the product. Keep one authoritative source: rules kept in two places drift apart.
How a rule shows itself
A good configurator does not silently grey out an option; it says why. In the chemical store example the sliding door is locked with a hint outside the permitted layout, and the container counters stop at the free places. Fictional product, example rules.
Writing rules down
Write each rule as one line: condition, consequence, message to the user. That table doubles as specification and test plan. Which rule applies to a real product is the manufacturer's decision; the configurator only implements it, see manufacturer responsibility. A worked example for a spiral staircase is in spiral staircase configurator rules.