A configuration rule defines which product, service or solution choices are required, permitted or incompatible in a given context. Rules help ensure that a quoted configuration can be delivered and supported rather than merely assembled on a document.
Which rule types are common?
- Requires: one choice needs another component
- Excludes: two choices cannot be combined
- Cardinality: minimum or maximum quantity
- Eligibility: option allowed only for a customer or market
- Derived value: one attribute determines another
- Approval: selected combination requires review
How are rules evaluated?
The configuration engine reads selected attributes and applies the current rule set. It should block invalid outcomes, explain conflicts and identify the rule version used for the quotation.
Configuration rule vs. pricing rule
A configuration rule determines whether a combination is valid. A pricing rule determines the financial result for an eligible configuration. Some conditions affect both, but separating validity from price makes decisions easier to test and audit.
How should rules be governed?
Assign ownership, effective dates and test cases. Evaluate rule interactions and migration effects before release. A rule change should not silently alter an already approved quotation unless the business process explicitly requires recalculation.
