Anatomy of a rule
- Category — the domain it belongs to: capacity, assortment, ordering, transfer, pricing, distribution, or compliance.
- Enforcement mode — what happens when it triggers:
- Block — the action is rejected.
- Warn — the action proceeds with a warning.
- Log — the firing is recorded silently.
- Check level — what it evaluates: shop, brand, product, variant, inventory item, plan, or plan item.
- Condition — the test (a threshold or value), backed by live data fetched at evaluation time.
- Scope — which shops, brands, suppliers, products, variants, or collections it applies to. An empty dimension means “all”.
- Validation hooks — the moments it fires (see below).
- Violation message — the message shown when it triggers.
- Priority — the evaluation order.
When rules fire — validation hooks
Rules are attached to hooks that fire at specific points per plan type:Templates
Rather than building rules from scratch, start from a template in the catalog — e.g. max plan value, max items per shop, max quantity per variant, OTB envelope caps, size-curve deviation, markdown discount/margin guards, and supplier policies. Pick a template, set its threshold and scope, choose Block or Warn, and assign it to a ruleset.Working with rules
1
Open the Business Center
Go to Intelligence layer → Business Center / Business rulesets.
2
Create or pick a ruleset
Create a named ruleset (e.g. Strict Q4), or edit the default.
3
Add rules from templates
Instantiate templates, set thresholds and scope, and choose the enforcement mode.
4
Set the default
Mark one ruleset as the organization default.
5
See them in action
Blocks and warnings appear in the plan’s validation panel as you build plans.
Every rule evaluation is recorded, so you can review which rules fired on a plan and
why. For the technical model (hooks, enforcement, paradigms, phases, the operations
layer), see Business rules engine.