Terminology
Last updated: March 23, 2026
Understanding the terminology of Nash Fleet will help you and your team to better operate within the portal. Here are just some of the terms you'll need to know.
Orders vs. Deliveries - An Order is created and can be changed, planned, or combined with other orders, while Deliveries are finalized dispatch units that can no longer be changed. Orders → become → Deliveries
Job - the actual delivery process. A job holds the package(s) to be delivered, the quotes from fleets willing to deliver the package(s), and the current delivery status if one was selected.
Job Configuration - contains detailed information on how the delivery will be executed.
Task - A single quoting/dispatching unit within a delivery. Each time a delivery redispatches, a new task is created.
Internal Fleet - Drivers employed by your organization who complete deliveries using the Nash Fleet Driver App.
3PL - Third Party Logistics companies that you hire to complete a delivery on your behalf.
Drivers/Couriers - the people who complete deliveries using the Nash Fleet Driver App or other software application. These could be internal or 3PL drivers.
Driver Groups - A way to organize your internal fleet drivers into logical groups.
Vehicles -- Assets assigned to drivers that influence how deliveries are executed. A delivery may require a certain vehicle.
Shifts -- Scheduled time windows that define when drivers are available to work.
Routes -- A sequence of stops assigned to a driver for delivery execution.
End-to-end lifecycle -- The full process of managing deliveries from setup through execution and monitoring.
Entity ID reference -- A standardized system of prefixes used to identify entities within Nash. You can identify the type by prefix:
cor_(courier)job_, (job)ord_, (order)tsk_, (task)qte_(quote)