Dispatcher Configuration

Creating a Dispatcher

Via the Portal

Go to Dispatchers > New Dispatcher
Name your dispatcher
Set the priority (lower numbers evaluate first)
Define conditions or select a condition set
Choose an action
Enable/disable the dispatcher
Save

Via the API


POST /api/dispatchers
Content-Type: application/json
 
{
  "name": "Route CA orders to West warehouse",
  "priority": 10,
  "enabled": true,
  "conditionSetId": "uuid-of-condition-set",
  "action": {
    "type": "add_tag",
    "value": "west-warehouse"
  }
}

Dispatcher Fields

Field	Type	Description
`name`	string	Human-readable name
`priority`	number	Evaluation order (lower = first)
`enabled`	boolean	Whether this dispatcher is active
`conditionSetId`	string	Reference to a saved condition set
`conditions`	object	Inline conditions (alternative to conditionSetId)
`action`	object	Action to take when conditions match
`stopOnMatch`	boolean	Stop evaluating further dispatchers after match

Actions

Dispatcher actions are the same as operation actions:

update_status
add_tag / remove_tag
add_note
push_fulfillment

Priority and Ordering

Dispatchers evaluate in priority order. When stopOnMatch is true, no further dispatchers are evaluated after a match. This lets you create fallthrough logic:

Priority 1: VIP customers → express shipping (stop)
Priority 2: CA orders → West warehouse
Priority 3: All others → default warehouse