Home / Glossary

Constraint

Also called: Configuration rule, compatibility rule

A rule that says which combinations of options are allowed, required or impossible.

A constraint is the smallest unit of product knowledge in a configurator. “A fire-rated door cannot use the curved lever” is one sentence, but behind it sits a fire test, a certification and a reason somebody once got it wrong.

Kinds of constraints

KindExample
ExclusionMatte black is not available on a 2-1/4 in door
RequirementA storeroom function requires a cylinder
DefaultSatin chrome unless the customer chooses otherwise
CalculationSpindle length follows door thickness
DatedBronze can't be ordered after 1 January

Writing good ones

  • Say what can't be built, not everything that can. A model that lists what's impossible stays small as the product grows.
  • Keep the reason with the rule. “Not fire tested” is more useful than “Rule 418” when someone asks to remove it in five years.
  • Separate technical from commercial. “Can't be built” and “we choose not to sell it here” change for different reasons and should live apart.
  • Test every one. Each constraint gets at least one test configuration that proves it fires, and one that proves it doesn't fire when it shouldn't.

The Rules Lab has eight constraints and eighteen test configurations; you can read every one.

Questions people ask

How many constraints does a product need?

As few as describe what can't be built. Big rule counts often mean the same idea written many times.

What happens when a constraint is missing?

The configurator sells something the plant can't build. Somebody finds out at order entry or, worse, on the floor. That's order fallout.

Updated November 2026. Think I've got something wrong? Tell me.