Skip to main content

Fulfilment routing

When an order arrives, something has to decide which of your sites fulfils each line. That is routing, and the answer becomes the order's fulfilment groups — one group per site.

Routing has to be switched on first​

The routing engine is off until your organisation turns it on. Until then, incoming orders are assigned to your channel's default site and none of your rules run.

It is a feature toggle under your organisation's settings, called Order routing engine, and it needs organisation-admin access. Everything on these pages assumes it is on.

If you have set up a rule set and nothing appears to be happening, check this before anything else — it is the most likely explanation.

Rules narrow, they do not score​

The engine does not give each site points and pick a winner. It starts with every site as a candidate and takes candidates away.

First a hard gate: sites without enough stock for the line are removed before any of your rules run. Then your rules run in order, each filtering what is left. The moment one site remains, the engine stops — later rules never get a say.

That is why the order of your rules matters more than their number, and why understanding routing as successive narrowing is the thing that makes your own configuration predictable. See how routing works.

Editing rules never disturbs work in flight​

An order records which version of your rule set routed it, the first time it is routed. That version is never re-evaluated afterwards. So you can change your rules whenever you like without re-routing orders already being picked.

Where the screens live​

Both are organisation administration and need organisation-admin access: rule sets under Routing rules, and the queue of disagreements under Routing exceptions.

Concepts​

How to​

Reference​