Assign and manage a delivery
Use an order’s detail panel to assign or remove a driver and, when your account is permitted, update its delivery status. These are live operational changes, not preview controls.
Assignment and status actions depend on your role, the order’s business and driver-group scope, the order’s current state, and project configuration. Administrators, business managers, and driver managers can be permitted to assign a driver; the API applies additional validation to every request.
Before you make a change
- Confirm the order number, business, customer, current driver, and current status.
- Confirm that you are working on the intended delivery, not a similarly named or nearby order.
- Check the delivery’s business and the driver’s group. A selectable-looking driver can still be rejected by the server if the driver is not eligible for the order.
- Use an approved operational process for customer communication, refunds, or delivery recovery; these are separate actions.
The current source sends an order update when a driver, removal, or permitted status is submitted; it does not provide a draft step. The API source contains workload, tracking, history, websocket, notification, webhook, and logistics effect paths. Do not use a live delivery to test a selector, and do not treat a toast or refreshed panel as proof that downstream effects completed.
Assign an eligible driver
- Open Deliveries dashboard and locate the delivery.
- Open the delivery’s detail panel.
- In the driver selector, search for the driver if needed.
- Review the available driver groups and the assigned-order count shown next to the driver.
- Select the intended driver.
- If your project requires a manual assignment comment, enter the required comment and submit the assignment.
- Confirm that the detail panel shows the expected assigned driver and that no Dashboard error appears.
This procedure documents the source-defined controls only. No delivery, driver, location, order, websocket, notification, provider, or write request was executed to prepare it.
The selector groups drivers as Available, Busy, and Not available. The current UI disables drivers that its snapshot marks disabled, unavailable, or busy. The current API update source separately verifies that the selected user is a driver account, has an eligible enabled driver-group relationship to the order’s business, is not busy, and is within the caller’s permitted order scope. It does not make the UI snapshot proof of server acceptance.
If a driver is already assigned, Remove assigned driver submits a null driver assignment. Use it only when the delivery should no longer be assigned to that driver, then independently verify the current order state.
Update delivery status
The Order status selector in the detail panel can offer the statuses that your role and the order allow. Select a new status only after reviewing its operational effect; the Dashboard does not treat the choice as a draft.
API source can reject an update when the order is outside the caller’s scope, locked, incompatible with another assignment type, or invalid for the requested driver or status. Its update path can reach logistics queues, driver-company requests, delivery-location tracking, history, webhooks, websocket updates, and notifications; no effect was executed or verified here.
Do not document or promise a universal set of status choices. The visible options and their effects vary by order type, role, and configured logistics behavior.
Verify the result
- The detail panel still shows the intended order number and business.
- After reopening the order, the assigned driver or status shown is the change you intended.
- The Dashboard shows no error.
- Any follow-up is based on an approved operational record, not on a toast, websocket update, assumed notification, or automated assignment outcome.
Troubleshooting
Why is a driver disabled or missing?
The driver may be disabled, unavailable, busy, outside the order’s eligible enabled driver groups, or outside your account’s scope. Driver availability shown in the Dashboard is not a guarantee that the server will accept the assignment.
Why did the assignment fail?
The order may be locked, the driver may no longer be eligible or available, or your account may not be permitted for the delivery’s business or driver group. Review the Dashboard error and refresh the order before trying again.
Why can’t I change the order status?
Status controls and valid transitions depend on your role, the order’s state, and project configuration. Some delivery updates also require data such as driver location. Review the error and use the approved delivery process for that order.
Related guides: Delivery overview · Deliveries dashboard · View and manage an order · Update an order status