Option Restrictions

A restriction says: when these choices are made, these other options may only take these codes. Restrictions are configured as a decision tree: every branch has conditions (the when) and a result: one or more option restrictions (the then).

WHEN  Woningtype = HW
THEN  Beukmaat may only be 5400, 6000
      Dakvorm  may only be ZADEL

There are no "requires / excludes / implies" rule types; all of those are expressed as allowed-code lists. "Kitchen = Premium requires Appliances ∈ {Premium, Standard}" is a branch Kitchen = Premium → Appliances: [Premium, Standard]. "Package = Budget excludes the premium options" is a branch Package = Budget → each affected option with its non-premium codes.

Creating a restriction branch

1. Open the type and go to Restricties.
2. Create a restriction tree (a group of branches that share a purpose), then Nieuwe tak.
3. Left column: When selected: pick the code(s) that trigger the branch. Selecting several codes creates one branch per combination.
4. Right column: Then allow: for every option you want to limit, tick the codes that stay allowed. Options you don't mention stay unrestricted.
5. Save. The tree chart shows the new junction; the Doorsnede card shows the net effect.

How restrictions stack

All active restriction trees are evaluated for the current choices. For each option, the allowed codes are the intersection of what every fired branch allows; an option nobody mentions keeps all its codes. Stapeling controleren shows, per tree, whether it fires for the chosen codes and what it cuts away.

When a choice becomes disallowed because of another choice, the configurator reports a consequence: the first allowed code of that option is proposed as the forced change.

Where restrictions apply

• Configurator / buyer portal: disallowed codes are hidden or blocked; consequences are shown.
• Concept coverage: when computing which static-model names a type needs, combinations that violate an active restriction are skipped, so no coverage is demanded for impossible models.
• Exhaustive leaves: virtual expansions that violate a restriction are dropped the same way.

Testing

Use Test keuzes above the tree chart to see which branch fires for a set of choices and the path the tree takes, or the configurator sandbox for the combined effect of all trees.