Rule set fields
Rule sets live under Routing rules in your organisation's settings and need organisation-admin access.
| Field | Default | What it does |
|---|---|---|
| Rules | Empty | The ordered list of rules. Priority is lowest number first |
| Fallback site | Unset | Where a line goes when no eligible site has stock. Required before the set can be activated |
| Single-source preference | On | Prefers one site for the whole order where a single site could fulfil every line |
| Version | 1 | Increments on every edit. Orders record the version that routed them |
| Active | — | Exactly one rule set is active per organisation |
Fallback site
The activate button stays disabled until one is chosen. This is the step people get stuck on.
It is for lines nothing can fulfil, not for orders the rules find ambiguous — a distinction covered in the fallback site.
Single-source preference
A pass that runs after per-line routing. It only consolidates where one site could take everything; it never holds an order back waiting for that to become true. See keeping an order together.
Version
Every edit creates a new version rather than changing the current one in place. The previous version is retained for orders that recorded it.
An order stamps the version in force the first time it is routed, and it is never re-evaluated — so editing rules never moves work already in flight. See rule sets and versions.
Active
One active rule set per organisation, and that is the one the engine uses.
Not on the rule set
Whether a channel's location hint is honoured is a per-channel setting, not a rule set field, though the organisation's routing default applies when a channel leaves it unset. See channel settings fields.