Build a Rule Set

With rules you make sure your customers only put together configurations you can actually deliver. A rule checks a condition – for example “drive is solar” – and triggers an effect: it hides values or whole characteristics, pre-selects values or shows a message.

The principle

• Rule groups organise your rules, e.g. “Drive”, “Dimensions”, “Colours”. You create every new rule in a rule group.
• Every rule consists of a Condition (IF) and an effect that depends on the rule type.
• Rules are checked again with every selection. When the condition no longer applies, the effect ends too – a hidden value reappears.

Step by step

1. Open the component and switch to the Rules tab on the left.
2. Create a rule group with + next to Rules (Add rule group). Use the cog (Group settings) to give it a Group title.
3. Click + (Add rule) on the group. The rule “New rule” of type Blacklist is created.
4. On the right, under Rule settings, enter a Rule label and choose the rule type (field Validation type).
5. In the middle, build the condition under Condition (IF) (see Conditions).
6. On the right, define the effect – it differs per rule type (see Rule types).
7. Save and test in the Preview. Like every change, a rule only applies in the shop after you publish.

Delete rule at the bottom of the rule settings removes a rule. Deleting a rule group removes all rules in it.

Rule types

What “Legacy” and “V3” mean is explained in Frontend Engine: Legacy or V3.

Blacklist

On the right you see all characteristics, sorted by group.

• Hide single values: expand a characteristic and tick the values that should no longer be selectable.
• Hide a whole characteristic: tick the box in front of the characteristic's name (Blacklist entire option). The characteristic disappears completely, including from the price and the summary.

Select all and Deselect all mark all entries of a group or a characteristic at once.

Predefined values

For each characteristic you choose a mode:

Then you choose the value to be set. The rule does not set a value that a blacklist is currently blocking.

Dynamic value (Legacy only): instead of a fixed value, the rule takes the current value of another characteristic. For characteristics with values you define whether the match is made via the Value (Match by value) or the ID (Match by ID). V3 skips dynamic presets.

For input fields, V3 only pre-fills numbers, Legacy also text.

Predefined qty (Legacy only)

Applies to characteristics with Quantity enabled. You enter Min. quantity and Max. quantity. With Dynamic you take the limits from another characteristic. V3 ignores this rule type.

Predefined min/max (Legacy only)

Changes the allowed range of an input field, e.g. “with material wood at most 180 cm width”. For the characteristic you set Yes and enter the range as min-max, e.g. 40-180 (whole numbers). Input fields with an Allowed input are offered. V3 ignores this rule type – if your component runs with V3, limit dimensions with an Error / Warning rule instead.

Error / Warning

This is how the engines behave:

Conditions

You build the condition in the middle under Condition (IF):

1. Choose the characteristic.
2. Choose the comparison (operator).
3. Choose the value or enter it.

+ Rule adds another row, + Group a subgroup. With and / or you decide whether all rows must apply or one is enough.

Operators

For characteristics with values (Select, Radio buttons, Checkbox, List with images …) the editor only offers in, not in, is empty and is not empty. You can give several values at once – the condition applies if one of them is selected. For Checkbox and Multi-selection it is enough if one of the ticked values is in your list.

What works as a condition

Subgroups: note for Legacy

V3 evaluates nested groups exactly as they appear in the editor. Legacy, however, always links a subgroup with and to the row directly before it – even if or is set outside – and cannot evaluate a subgroup in first position. For components with Legacy: never put a subgroup at the start and only combine it with and. If you need an or between groups, create two rules instead.

Legacy also treats the number 0 as empty for is empty.

When several rules meet

• Blacklists add up: everything that at least one applying rule hides is hidden.
• Chains: a characteristic that a rule hides and a blocked value don't trigger any further rules. Both engines re-evaluate until nothing changes any more. Legacy clears the selection of the hidden characteristic in the process; V3 remembers it and shows it again as soon as the rule no longer applies.
• Presets for the same characteristic: one rule wins.
  • In V3 the Weight decides: the rule with the higher value wins. With equal weight, the rule further down the list wins.
  • In Legacy the Weight is not evaluated. The order in the list applies.
• Messages are sorted by weight in V3, the heaviest first.

You set the Weight in the rule settings (default 0). Rules with a weight other than 0 show it as a badge in the list, e.g. +5.

Order

You change the order of rules and rule groups by dragging the handle ⠿ in the rule list. Rules outside groups are evaluated first, then the groups from top to bottom.

Test rules

1. Save the component.
2. Switch to Preview in the middle and click through typical and critical combinations.
3. Check whether values disappear and reappear, presets apply and messages appear.

The preview runs with the configured frontend engine. If you switch the engine later, test the rules again – especially subgroups, presets and error messages.

Which rules affect a characteristic is shown in the characteristic on the right in the Referenced in tab. From there you jump straight to the rule.

Rules via the AI agent

You can also describe rules instead of clicking them: “If the material is wood, the colour RAL 7016 should not be selectable.” The AI agent creates the rule. Check it afterwards in the Rules tab and in the preview. More: AI Agent: Define Rules via Chat.

Practical examples

1. Colour doesn't match the drive Rule type Blacklist. Condition: Drive in Solar. Effect: tick the value White under Colour.

2. Accessory only with motor Rule type Blacklist. Condition: Drive in Crank. Effect: tick Blacklist entire option for the characteristic Remote control.

3. Sensible pre-selection Rule type Predefined values. Condition: Model in Basic. Effect: Colour set to No selection or default value, value White. If the customer has already chosen their own colour, it is kept.

4. Size not available Rule type Error / Warning. Condition: Material in Wood and Width > 180. Error type Error, Error message “Wood is available up to 180 cm width.”

5. Legacy only: limit the range Rule type Predefined min/max. Condition: Material in Wood. Effect: Width set to Yes, range 40-180.

Troubleshooting

1. The rule doesn't apply at all – check the operator: for characteristics with values you need in, not =. Also check whether the component is published; the shop shows the last published version.
2. The rule only applies sometimes – is there a subgroup at the start, or is it linked with or? Legacy evaluates that differently (see Subgroups).
3. Predefined qty or Predefined min/max has no effect – the component runs with V3, which doesn't know these rule types.
4. Two presets contradict each other – set a Weight in V3; in Legacy change the order.
5. The customer can order despite the message – check the Error type: only Error blocks the cart, a Warning only informs.

Next steps

• Frontend Engine: Legacy or V3
• AI Agent: Define Rules via Chat
• Add Characteristics & Values
• Feature Groups & Display Modes
• Set Up Pricing