--- title: "Assign and manage a delivery" description: "Assign an eligible Driver and manage permitted delivery-status actions from an Ordering.co Dashboard order detail panel." canonical: https://docs.ordering.co/docs/products/dashboard/delivery/manage-delivery/ --- # Assign and manage a delivery Use an order's detail panel to assign or remove a Driver and, when your account is permitted, submit a delivery-status update. These are live operational actions, not previews. A displayed status, a Driver App action, or a Dashboard confirmation does not independently prove that a Driver arrived at a place, reached a customer, or completed a delivery. > **Availability** > > Administrators, business managers, and Driver managers can be permitted to assign a Driver. Assignment and status actions depend on your role, the order's business and Driver-group scope, the order's current state, and project configuration. The visible selectors and valid transitions can differ between delivery orders. ## Before you make a change - Confirm the order number, business, customer, current Driver, and current status. - Confirm that this is the intended delivery, not a similarly named or nearby order. - Check the delivery's business and the Driver's group relationship. - Use the approved process for customer communication, refunds, delivery recovery, or incident handling; those are separate actions. > **These changes have operational effects** > > Selecting a Driver, removing a Driver, or submitting a permitted status can update the order. Do not use an active customer delivery to test a selector. A successful UI response does not prove that every related notification, webhook, queue, tracking event, or external service completed. ## Assign an eligible Driver 1. Open **Deliveries dashboard** and locate the delivery. 2. Open the delivery's detail panel. 3. In the Driver selector, search for the intended Driver when needed. 4. Review the available Driver groups and assigned-order count shown for the Driver. 5. Select the intended Driver. 6. If your project requires a manual-assignment comment, enter it and submit the assignment. 7. Reopen the detail panel and confirm the Driver shown for the intended order. ![Deliveries dashboard controls used to locate a delivery before opening its details](https://docs.ordering.co/img/docs/dashboard/delivery/manage-delivery-controls.jpg) The selector can group Drivers as **Available**, **Busy**, and **Not available**. A selectable-looking Driver can still be rejected if the account is not a Driver, has no eligible enabled group relationship to the order's business, is busy, is unavailable, or is outside your account's order scope. If a Driver is already assigned, **Remove assigned driver** submits a removal of that relationship. Use it only when the delivery should no longer be assigned to that Driver, then confirm the current order state through the approved operational record. ## Understand delivery-status actions The **Order status** selector can offer the transitions available to the current order and account. Choose a new status only after you understand its operational meaning; the choice is not a draft. Some delivery workflows can show Driver App actions such as **Arrived to business** and **Delivery complete**. When a permitted Driver selects one of these actions, it can submit a status event that the Dashboard later reflects. The event records an action in the workflow; it is not independent proof of physical arrival, customer handoff, delivery completion, or customer satisfaction. ![Driver App delivery status action](https://docs.ordering.co/img/help-center-import/4f8885cd184ddc2e6b4227ea.png) Where the configured flow allows it, a sequence can include statuses such as **Accepted by business**, **Accepted by driver**, a business-arrival or en-route status, and a Driver-completed delivery status. Do not treat this as a universal status catalog or transition map. The labels, available actions, and conditions are specific to the delivery type, role, and project configuration. ![Driver App delivery status update](https://docs.ordering.co/img/help-center-import/717710f6f2c6df5a8f3386a0.png) ## Keep capacity, events, and outcomes separate - A Driver shown in an assignment selector is a candidate returned to the view, not a confirmed assignment. - A submitted status action is an event request, not proof that all downstream effects occurred. - A map location or an arrival-labeled action is not independent proof of physical arrival. - A completed-status update is not, by itself, proof of customer receipt or satisfaction. - A **Review customer** action, when available, lets a Driver submit feedback; it does not guarantee that feedback will be submitted. ![Driver App delivery completion view](https://docs.ordering.co/img/help-center-import/abb8bd9090b2e641a3e4ed4a.png) This distinction helps operators verify the actual order record and follow the approved exception process when an outcome matters. ## Verify the result 1. Confirm that the detail panel still shows the intended order number and business. 2. Reopen the order and verify the assigned Driver or status that was intended. 3. Review any visible Dashboard error. 4. Use the approved operational record for follow-up instead of relying only on a toast, websocket update, assumed notification, or automatic-assignment expectation. ## Troubleshooting ### Why is a Driver disabled or missing? The Driver can be disabled, unavailable, busy, outside the order's eligible enabled Driver groups, or outside your account's scope. A Driver shown as available is not a guarantee that the assignment will be accepted. ### Why did the assignment fail? The order can be locked, the Driver can no longer be eligible or available, or your account may not be permitted for that business or group. Review the Dashboard error and refresh the order before making another approved attempt. ### 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 changes can require related data, such as a Driver location. Review the returned error and use the approved delivery process for the order. ### Why does the Dashboard differ from the Driver App? The two surfaces can show different information while data is being refreshed or while a request is rejected. Reopen the order and use the approved operational record to establish the current state before acting on the difference. --- **Related guides:** [Delivery overview](https://docs.ordering.co/docs/products/dashboard/delivery/) · [Deliveries dashboard](https://docs.ordering.co/docs/products/dashboard/delivery/deliveries-dashboard/) · [View and manage an order](https://docs.ordering.co/docs/products/dashboard/orders/view-manage-order/) · [Update an order status](https://docs.ordering.co/docs/products/dashboard/orders/update-order-status/)