Delivery fields & columns reference

Last updated: August 26, 2026

This is a field-by-field reference for the Deliveries list and detail view: which columns you can show on the table, what each of the several IDs a delivery carries actually identifies, what's on the detail view, and what the Delivery Activity timeline shows. It doesn't cover delivery status — for that, see Delivery status reference — or the object model behind a delivery, for that see How deliveries work.

List columns

The Deliveries table is customizable — you choose which columns show, in what order. Seven show by default; the rest are available whenever you want them.

Shown by default

Column What it shows
Status The delivery's current badge status.
Adjusted Pickup Time The pickup time as currently scheduled, after any changes since creation.
Pickup Location Where the delivery is picked up from.
Adjusted Dropoff Time The drop-off time as currently scheduled, after any changes since creation.
Dropoff Location Where the delivery is dropped off.
Provider Who's carrying the delivery — an outside provider or your own fleet.
Action The row-level menu — assign, reassign, cancel, and the rest.

Available to add

Column What it shows
Creation Time When the delivery was created.
Original Pickup / Dropoff Time The window the delivery was first scheduled against, before any changes.
Actual Pickup / Dropoff Time When pickup and drop-off actually happened, once they have.
Pickup / Dropoff ETA The live estimated arrival time for the current leg.
Vehicle The vehicle assigned, for own-fleet deliveries.
Driving Distance The distance the delivery covers.
Flag Whether the delivery has been flagged for attention.
Package A summary of what's being delivered.
Fees The fees associated with the delivery.
Merchant The merchant the delivery is associated with, if any.
Provider Batch Id The provider's own identifier for the batch this delivery is part of, if it's part of one.
Job External Id Your own reference ID for the job, if one was set.
Package External Id Your own reference ID for the package, if one was set.
Reference Id An additional reference string beyond the external IDs.
Tag Labels attached to the delivery for filtering and reporting.
Created By Who or what created the delivery — an operator, an integration, or a workflow.
Price What the delivery cost.
Tip The tip amount attached to the delivery.
Provider Fees The fees the provider charged.
Courier The driver or courier working the delivery.
Provider Delivery Id The provider's own identifier for this delivery attempt — see the ID map below.
Provider Reference Id The provider's own reference string for the delivery.
Organization Which organization the delivery belongs to, useful if you manage more than one.

Note

A Custom agent column also exists, showing which Nash Agent handled the delivery if one did. Availability varies by organization — reach out to Nash if you expect it and don't see it.

The table footer shows two running counts as you filter: Deliveries and Packages. They usually match, but a delivery carrying more than one package will make the Packages count run ahead of the Deliveries count — that's expected, not a bug.

The ID map

Open a delivery and you'll find several IDs, not one. They aren't duplicates — each identifies a different layer of the same delivery, and knowing which is which saves confusion the moment you're pasting an ID into search or a provider's support form.

Job ID is the one you use day to day, and it's not the same thing as Delivery ID. Job ID is the identifier on the row, the one you search by, and the one Nash's own tooltip describes as "a unique identifier for this delivery." Delivery ID is narrower: it identifies one specific attempt by one specific provider, not the delivery as a whole — a reassigned delivery has had more than one attempt behind it, and each attempt gets its own Delivery ID, while the Job ID stays constant across all of them. Use the Job ID for search, support, and reporting; reach for the Delivery ID only when you specifically mean the current attempt, such as when a provider's support team asks for the ID of the attempt their driver is running.

The table below covers every ID a delivery carries, including the provider's own identifiers (Provider Delivery Id, Provider Reference Id) and the other objects a delivery is built from or tied to:

ID What it identifies
Job ID The delivery itself — what you search by.
Delivery ID One specific provider attempt underneath the job, not the delivery as a whole.
Provider Delivery Id The provider's own ID for that same attempt.
Provider Reference Id The provider's own reference string for that attempt.
Task ID The pickup-and-drop-off pairing for a single package that the attempt is carrying out.
Job Configuration ID The internal record that splits a job's packages across its deliveries.
Package ID The specific package the delivery is carrying.
Batch ID / Provider Batch Id The multi-order grouping the delivery is part of, if it was dispatched as part of a route. Provider Batch Id is the provider's own ID for that same grouping.
Route ID The route the delivery came from, if it was dispatched from one.
Job External Id / Package External Id Your own reference IDs, set at creation.
Reference Id An additional reference string beyond the external IDs.
Winner Quote ID The specific quote that was selected to carry the delivery.
Contract ID The contract governing the terms with the provider carrying it.
Dispatch Strategy ID The strategy that chose the provider, if the delivery was auto-dispatched. Reassigning removes it.

Tip

When in doubt, search and support conversations both key off the Job ID. Everything else on this list is there to answer a narrower question — which attempt, which provider, which package — once you've already found the delivery.

Delivery detail sections

Opening a delivery gives you more than a single page's worth of information, organized into a handful of sections and tabs. This is a tour of what's there, not a walkthrough of how to use it — for that, see Read a delivery and the rest of the "Read a delivery" articles.

  • Highlights — the identity strip at the top: the status badge, the short code, the IDs covered above, when the delivery was created, whether it was created via a workflow, any restricted-item badges, and a Related Deliveries / Part of batch link to the other deliveries from the same order or batch.
  • Status and map — the current badge status alongside a live map of the delivery in progress, when tracking data is available.
  • Quotes / Provider tabs — the offers a delivery received before assignment, and once assigned, the Provider Details, Driver Details, and Vehicle Details for who's carrying it, plus a PIN-verification field and any Notes From Driver or customer feedback tied to the attempt. See Find provider and driver details.
  • Notes and Flags — team notes your organization has added, kept separate from the read-only notes a driver leaves, and whether the delivery has been flagged for attention.
  • Merchant, Package, and Location details — who the merchant is (if any), what's being delivered and its item-level detail, and the pickup versus drop-off location and recipient information for each stop.
  • Proof of delivery — the photos and confirmation captured at drop-off, plus (where available) an AI photo-validation result — see below, under the Delivery Activity timeline. To review, verify, or delete the underlying photos, see Review proof of delivery photos.
  • Delivery Activity — the timeline of everything that's happened to the delivery. Covered in detail below; see also Track delivery progress on the timeline.

The Delivery Activity timeline

The Delivery Activity tab shows every recorded event for a delivery, in order. The event types you'll see include:

  • Created and Sent to provider
  • Picking completed / items pick complete
  • Delivered
  • Returned
  • Driver updated and Delivery timing updated
  • Driver offered, accepted, declined, and expired — the offer lifecycle each time a driver is asked to take the delivery
  • Customer feedback submitted
  • Auto-dispatch failed
  • A handful of narrower system events — an agent-handled call, a task status sync, or a delivery ingested via email, depending on how the delivery came in

Alongside the event list, a Delivery Checklist & AI Analysis block gathers proof-of-delivery photos with their photo-validation result, confidence score, and failure reason where applicable. To review, verify, or delete the underlying photos, signatures, and barcode scans, see Review proof of delivery photos.

Operators can also add a custom event to the timeline — useful for logging something that happened outside Nash's own tracking, like a phone call with the customer that isn't otherwise captured.

Availability

Not every column, section, or ID on this page will be visible on every organization — a few (the custom-agent column and the AI photo-validation result among them) depend on features that vary by org. If something described here is missing for you, reach out to Nash rather than assuming it's broken.

Related