A confirmed order. Routing decides who sees it through to dispatch, which is a different job from winning it.
What you would route on
Any field on the module can be used, including ones you have added yourself. These are the ones businesses reach for:
| Field | Why you would route on it |
|---|---|
| Customer | Keep a customer’s paperwork with their account manager. |
| Total | Large documents to somebody senior. |
| Branch | If you run more than one place of business. |
| Place of supply | Interstate vs within the state. |
| Delivery date | Urgent orders to whoever is coordinating dispatch today. |
A worked example
A trading company hands every confirmed order to the operations coordinator rather than leaving it with the salesperson who closed it — one rule, every record, one person. Sales stays on selling; operations owns delivery.
Caps and overflow
| Setting | Worth it here? |
|---|---|
| A cap per person | Yes. |
| An overflow owner | Yes. |
Where to go next
- Writing the rule
- When it runs — on create, on edit, or both
- Capping how much each person gets
- Where the overflow goes
Something missing or wrong here? Tell us. A question that needed asking usually means a page that needed writing.