Delivery status reference

Last updated: August 26, 2026

This is the definitive list of delivery statuses — the badge label you see on a delivery row, what it means, and whether it's terminal. For the lifecycle these statuses form and how the three status vocabularies relate, see How deliveries work.

The badge status set

The badge status is the customer-facing status — the one on the delivery row and the one your customer's tracking page reflects. A delivery moves through it roughly left to right, with a handful of exception branches that can happen at nearly any point.

The main spine

Status What it means Terminal?
Created The task exists but hasn't been sent to a provider yet. No
Scheduled The delivery has a pickup or drop-off window set and is waiting to move to the next step. No
Sent to provider A provider (or your own fleet) has the job and hasn't attached a driver yet. No
Not Assigned Driver The provider has accepted but no driver is attached yet — a narrower point inside "assigned," not a separate branch. No
Assigned driver A specific driver or courier is attached to the delivery. No
Started The driver has begun working the delivery. No
Pickup enroute The driver is traveling to the pickup location. No
Pickup arrived The driver has arrived at the pickup location. No
Pickup in progress The driver is actively working the pickup — collecting items, confirming the order. No
Pickup complete The driver has collected the package from the pickup location. No
In transit The package is moving from pickup toward drop-off. No
Dropoff enroute The driver is traveling to the drop-off location. No
Dropoff arrived The driver has arrived at the drop-off location. No
Dropoff complete The package has been delivered. This is the normal terminal state. Yes

Note

Pickup and drop-off each break into enroute / arrived / in-progress / complete sub-steps, but you won't see every one of them on every delivery — how granular the badge gets depends on what signal the provider or driver app actually reports back.

Exception and terminal branches

These sit off the main spine and can occur at nearly any point in a delivery's life, not just at the end.

Status What it means Terminal?
Delayed The delivery is running behind its expected timing but is still moving. It's a warning, not a dead end — a delayed delivery usually resolves back onto the main spine. No
Failed The delivery could not be completed. Yes
Expired The delivery's window passed without the work ever being carried out. Yes
Returned / Returned to store The package is on its way back to the merchant rather than forward to the customer, most often after a failed drop-off. Yes
Canceled by Customer The customer canceled the delivery. Yes
Canceled by Merchant You (the merchant/operator) canceled the delivery. Yes
Canceled by Nash Nash canceled the delivery — typically an automatic cancellation, including one tied to a reassignment. Yes
Canceled by Provider The provider canceled the delivery. Yes

Important

Terminal statuses lock the badge. Once a delivery lands on Dropoff Complete, Failed, Expired, Returned, or any Canceled By variant, the portal stops accepting status edits on it. Terminal doesn't mean the record disappears — a failed, returned, or canceled delivery stays visible and searchable. Working through one is covered in cancel & recover deliveries.

Note

Delayed is the one status on this page that isn't terminal despite sitting off the main spine. Treat it as a flag that a delivery needs a look, not as an ending.

How Live Monitoring stages roll up the badge

Live Monitoring is a health-overview panel that tracks deliveries still in flight. It groups a subset of badge statuses into four coarse stages, then tags each delivery On Time, At Risk, or Late based on how it's tracking against its expected timing.

Live Monitoring stage Badge statuses it rolls up
Pending Assignment Created, Not Assigned Driver, Sent to provider
Pending Pickup Assigned driver, Started, Pickup enroute, Pickup arrived, Pickup in progress
Pending Dropoff Pickup complete, Dropoff enroute, Dropoff arrived
Dropoff Complete Dropoff complete

Not every badge status maps into one of these four stages. Scheduled, In transit, and Delayed all fall outside the rollup entirely — a delivery sitting in any of those doesn't get a health status and won't appear on the Live Monitoring panel at all. That's deliberate for Delayed: it isn't folded into whichever stage a delayed delivery would otherwise be in, so rather than showing up there with an At Risk or Late tag, a delayed delivery simply drops out of Live Monitoring. The exception and terminal branches fall out the same way once they're reached — Failed, Expired, Returned, Returned to store, and every Canceled By variant stop appearing on the panel, since there's no further pickup or drop-off progress left to track.

Tip

If a count on Live Monitoring doesn't match what you'd expect from scanning badge statuses on the table, check two things: which of the four stages a status falls under, and whether it falls under one at all. Scheduled, In transit, Delayed, and the exception/terminal statuses (other than Dropoff complete) never show up in a Live Monitoring count.

Note

Live Monitoring is a health-overview surface, and availability varies by organization. If you don't see it, reach out to Nash about access rather than assuming something's misconfigured.

Task status vs. delivery status

The badge shows delivery status — that's everything on this page so far, and it's what "delivery status" means unless stated otherwise.

Task status is a separate, internal layer underneath it, tracking the state of one specific attempt a provider or driver is working — created, running, completed, failed, canceled, and a couple of narrower states in between. You mostly don't see task status by name in the portal: the status cell you look at resolves delivery status first. Task status exists because reassigning a delivery doesn't edit the current attempt in place — it spins up a new attempt and lets the earlier one go. A delivery that's been reassigned once has two attempts behind it even though you only ever see a single badge status on the row. If you notice a "tasks to cancel" prompt while reassigning or canceling a delivery with more than one attempt, that's this layer surfacing — it's asking what to do with the earlier attempt, not adding a status you need to track day to day.

Related