Deliveries at a glance

A delivery is a dispatched job, seen from the customer's side. Before dispatch, that work is an order — a request you can still shape. The moment you dispatch it, Nash creates a job: the unit of work Nash tracks from that point on, made up of one or more tasks, each a pickup and a drop-off. "Job" and "delivery" name that same unit of work from two different seats — the job is what you track, the delivery is what your customer watches move toward them. On the Deliveries page, the row you're looking at, the job, and the delivery are all the same thing.

That's the chain worth carrying into everything else here: order → job → task → delivery. An order becomes a job the instant it's dispatched to a provider or your own fleet; the job's tasks are what actually get picked up and dropped off; and "delivery" is simply that dispatched work as it plays out. For the pre-dispatch side of this — what an order is and how it gets to dispatch — see Orders at a glance.

Your live and completed dispatched work lives on the Deliveries page (select Deliveries in the sidebar). It's where you find a specific delivery, watch it move, and step in if something needs your attention — the working home for everything that's already been sent out, as distinct from the Orders page, which is where work lives before it goes out.

What you can do with deliveries

Working a delivery moves through a handful of everyday tasks, each with its own place to start:

• Find & monitor deliveries — search, filter, and watch your deliveries, live or completed, by table, map, or live health overview.
• Read a delivery — open a delivery to see everything on it: status, provider, recipient, proof of delivery, and history.
• Reschedule & edit deliveries — change something after dispatch, from a small field edit to a new pickup or drop-off time.
• Assign & reassign deliveries — pick a provider or driver yourself, or reassign one that isn't working out.
• Cancel & recover deliveries — stop a delivery, or sort out one that's failed, stuck, or off course.

Those five cover a delivery's whole working life once it's out the door: you find it, read what's happening on it, adjust it if plans change, assign or reassign who's carrying it, and cancel or recover it if something goes wrong. Most deliveries only ever need the first two — find it, watch it finish — but whichever one you're on, there's a dedicated place to do it.

Learn how it works

The task pages above tell you what to click. For the mechanics behind them — how a delivery relates to the order and job underneath it, what the status badge is actually tracking, and how assignment works — see How deliveries work. It walks through the object model in full, the customer-facing status lifecycle, and what you can and can't change once a delivery is moving.

Two reference pages fill in the details you'll want while you're actually looking at a delivery:

• Delivery status reference — every status a delivery can carry, what the portal calls it, and how the live health overview's stages roll up to it.
• Delivery fields reference — every column and field you can see on a delivery, including the difference between its Job ID and its Delivery ID.

One thing worth carrying into all of this: Nash dispatches the work and hands it to a provider or your own fleet — Nash itself doesn't carry the delivery. What you're managing on this side is the job and its status, not the drive itself.