Auto-Dispatch

Auto-dispatch assigns drivers to delivery orders automatically, so routine assignments happen in seconds without a dispatcher touching them. You choose how aggressive the automation is, how drivers are ranked, and what happens when no driver accepts — and you can monitor how well it’s performing from your reports.

Three assignment methods

Auto-dispatch supports three strategies. Pick the one that matches your fleet culture and volume:

One-by-one

The system offers the order to the best-ranked driver first. If they decline or don’t respond in time, it moves to the next-best driver, and so on down the ranked list.

Best for: fleets where you want the right driver, not just the fastest finger; predictable, orderly assignment.
Trade-off: slightly slower to assign when top-ranked drivers decline.

Send-to-all

The order is offered to all eligible drivers at once; the first to accept gets it.

Best for: speed of assignment, gig-style fleets, peak hours when seconds matter.
Trade-off: the fastest accepter isn’t always the best-positioned driver.

Nearest-available

The system picks the nearest available driver and assigns the order.

Best for: dense areas where proximity dominates everything else; minimal driver interaction.
Trade-off: the most automatic, least driver-choice-driven of the three.

How drivers are scored

For ranked methods, eligible drivers are scored and ordered. Scoring starts from a base score and applies configurable weights, primarily:

Distance — how close the driver is to the pickup. Closer scores higher, and distance is the largest default factor.
Current load — how busy the driver already is. Less-loaded drivers score higher, spreading work across the fleet.
Driver type bonus — a configurable bonus for preferred driver types.

The weights are adjustable in your auto-dispatch settings, so you can tune whether proximity or load-balancing dominates. Driver positions come from live location tracking in the partner app, so scoring reflects where drivers actually are right now.

Retries and fallbacks

Assignment doesn’t always succeed on the first pass — drivers decline, time out, or none are eligible. Auto-dispatch handles this:

Retries — unaccepted offers are retried per your configuration, moving down the ranked list (one-by-one) or re-offering.
Escalation to humans — orders that automation can’t place surface to the dispatcher panel for manual assignment. Automation handles the volume; your dispatchers handle the exceptions.
Taking over manually — while auto-dispatch is still searching for a driver, staff can press Cancel Auto-Dispatch on the order and assign it by hand — useful when a dispatcher already knows who should take it.
Notifications — failed or struggling assignments are visible to your operations team rather than failing silently.

Enabling and scoping

Auto-dispatch is configured in Dashboard → Settings → Basic Settings → Logic (/settings/settings/logic-settings):

Enable it marketplace-wide, then tune behavior per your operation.
Per-zone and per-outlet behavior — settings can be adjusted so different areas or merchants dispatch differently, with outlet-level overrides where a specific merchant needs them (for example an outlet with its own delivery arrangements).
Choose the assignment method, scoring weights, timing, and retry behavior that fit each context.

Start conservative (one method, default weights), watch the results for a week or two, then tune.

Monitoring performance

Auto-dispatch has a dedicated report at Dashboard → Reports (/reports/driver-auto-dispatch):

A daily summary of dispatch activity — assignment outcomes and how often orders needed manual rescue.
Trends over time, so you can see whether assignment is getting faster or slower.
Performance broken down by driver, by outlet, and by assignment method — useful for comparing one-by-one against send-to-all on your real traffic.

Marketplace-wide reports add the surrounding context (delivery timing across zones and outlets).

The numbers to watch: time-to-assign (how long orders wait for a driver), acceptance rate (are offers reaching drivers willing to take them), and manual-intervention rate (how much still lands on dispatchers). Rising intervention rates usually mean fleet supply or scoring weights need attention, not that automation is broken.

Auto-dispatch and delivery networks

Auto-dispatch assigns your own fleet. If you also use third-party delivery networks, those orders are fulfilled by the network’s couriers instead. Many operators combine both: own fleet (auto-dispatched) for core coverage, networks for overflow or areas without fleet density.

Practical guidance

Match the method to your fleet size. Small fleets often do better with one-by-one (respects driver ranking); large gig fleets benefit from send-to-all speed.
Don’t over-weight distance in sparse areas. With few drivers, load balancing prevents your one nearby driver from drowning while others idle.
Re-tune after fleet changes. Doubling your driver count or changing shift patterns changes what good scoring looks like.
Watch declines per driver. A driver who declines everything distorts one-by-one assignment timing — that’s a fleet-management conversation, not a settings change.

Dispatcher panel — the human side of dispatch
Drivers — building the fleet auto-dispatch assigns
Delivery networks — third-party fulfillment
Reports — measuring dispatch performance