Assigning drivers

Assignment connects an order (or a whole route) to a driver so it appears in the driver app.

Assign a single order

1. Open the order on the dispatch board.

2. Choose Assign (from details or the assignment modal).

3. Pick a driver. Prefer drivers who:

• Are on duty

• Are assigned to the order’s location

• Are near the pickup (map) when that matters for your SLA

1. Confirm. Status moves to Assigned (or similar).

Acceptance

By default, the driver may need to accept the assignment in the app before it’s fully theirs. Some businesses enable auto-accept, and route workflows can force-accept depending on configuration. If a driver never accepts, check the app notification and whether they’re on duty.

Unassign

From order details, unassign if the wrong driver was chosen or the driver went off duty. The order returns to the unassigned / queued pool for someone else.

Bulk assign

When the UI offers bulk assignment:

1. Filter the list to the right date/location.

2. Select multiple unassigned orders.

3. Choose one driver and confirm.

Use bulk assign for same-area bursts—not for mixing distant stores.

Location eligibility

Drivers should be linked to the locations they cover (Settings → Drivers → location assignment). If a driver never appears as a good option:

• Confirm they’re invited and active

• Confirm location membership

• Confirm they’re on duty for that location when your process requires it

Routes vs single assign

• Approach: Single assign · Use when: One-off deliveries, express, or sparse volume

• Approach: Route · Use when: Multi-stop runs, batch windows, driver already leaving with several bags

Assigning a route assigns the driver to the whole stop sequence. See Building and optimizing routes.

After assignment

Dispatch should see the driver on the order details and (when on duty) on the map. The driver sees the work under Active / Queue (and Route if enabled).

Next steps

• Building and optimizing routes

• Driver app overview

• Messaging and inbox