User Manual
Help Center/User Manual/Dispatch Center: configuring the rule engine

Dispatch Center: configuring the rule engine

Last updated 2026-10-15

Build IF/THEN rules, order them by priority, and dry-run any order to see which rule matches — before anything goes live.

Rules decide "which load goes to whom, at what price" — without code. Each rule is IF (conditions) THEN (action): when an order matches, the engine assigns per the rule. Rules run top-down by priority; the first match wins.

Building a rule#

  1. IF: add conditions — shipper, origin, destination, lane, equipment, weight, freight amount, mode, or "own fleet available". Combine with AND/OR.
  2. THEN: pick the assign strategy — top score, lowest price, own fleet first, sequential tender, or a specific carrier — plus the price strategy (contract rate or DAT market rate).
  3. Timeout: how many minutes to wait for confirmation, and what happens then — move to the next carrier, or send to the manual pool.
  4. Priority: drag the ▲▼ arrows — higher rules are evaluated first. VIP-customer rules usually sit at the top.

Test mode (dry run)#

Before a rule goes live, test it: pick any order and the panel shows which rules match and why — without saving or dispatching anything. Use it after every change: a rule that matches nothing, or matches everything, is a rule worth fixing.

Starter set: ① VIP shipper express (specific carrier, short timeout, goes to manual on timeout — VIP loads never auto-cascade); ② standard lane auto-dispatch (own fleet first, then top score); ③ small-load auto (under $500 and under 100 mi). Tune from there.

Per-shipper rule config#

The shipper selector at the top of every rule page lets you tune rules for one shipper only. Leave it on "All (tenant default)" for the shared config; pick a shipper to override just for them — other shippers are unaffected. Priority: shipper config > tenant default > system default. Each row carries a badge showing where its settings come from: purple = shipper, blue = tenant, gray = system.

  • When to use it: a VIP shipper needs special treatment — e.g. own fleet always first, or a higher weight on damage rate. Tune under that shipper's name instead of changing the tenant default.
  • Conflicts: some rules are mutually exclusive. If a save is rejected with a conflict message, adjust the conflicting rule first, then retry.
  • Preset templates apply to the tenant default only — they are disabled while a shipper is selected. What-if test runs against the tenant default config.
Example: a key account wants the damage-rate rule weighted higher. Select that shipper, raise the weight, save — every other shipper keeps the tenant default.