How Nash works

Last updated: September 2, 2026

Nash runs on a handful of connected objects. Once you can name them and see how they fit together, most of the portal explains itself, and questions like "why is this order on two screens" have obvious answers.

The path a delivery takes

An order is the work you want done: a pickup, a drop-off, and the items in between. Orders hold packages, and each package knows the store location it leaves from and the one it goes to.

When you dispatch an order, Nash creates a job. The job is the dispatched unit of work, and it is where responsibility shifts from planning to execution. A job breaks into tasks, one per stop, and each task collects quotes from the providers that can serve it. The quote you accept produces a delivery, which is carried by a courier when it runs on your own fleet.

That chain is the spine of the whole system:

Order → Package → Job → Task → Quote → Delivery

What shapes the path

Several objects never move, but they decide what the chain above can do.

Object What it decides
Delivery window when you promised the drop-off, and how much you can take on
Zone where a provider operates, so which quotes appear at all
Store location the pickup and drop-off points a package moves between
Contract the commercial terms that make a provider eligible, and at what rate
Dispatch strategy which provider gets the job when you dispatch
Optimization strategy how orders are grouped and sequenced into routes

Grouping work

A route groups orders into a single run. Routes are why an order can appear in two places at once: a routed order still counts as ready to dispatch, but you dispatch it through its route rather than on its own.

When something goes wrong

A refund request hangs off the job and the task it relates to, which is why refund eligibility depends on what actually happened on that specific stop rather than on the order as a whole.

Reading this back in the portal

Every object above has an ID prefix, and you will see these in URLs, exports, and support conversations:

Object Prefix
Order ord
Job job
Task tsk
Delivery dlv
Quote qot
Route rte
Refund request rfrq
Delivery window dlw
Zone zone
Store location stl
Courier cor

Note

Nash dispatches the work. The delivery itself is carried by a provider or by your own fleet.