Order
An Order represents the delivery details for package(s) in the real world.Package
A Package is a container, like a box, to be delivered. It may contain multiple items.Job
A Job represents 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. One or more Orders become a Job when dispatched. For instance, a job could consist of multiple Orders from a single merchant being delivered together to a customer.Batch Job
A Batch Job is a group of packages delivered by the same courier, thereby using the same provider. A batch job comprises more than one package, in contrast to single jobs (non-batch), which contain a single package. For example, if a merchant has five items for different customers in close proximity, these could be consolidated into a batch job for more efficient delivery.Job Configuration
Each job includes a Job Configuration that contains detailed information on how the delivery will be executed. This configuration encompasses particulars on the dispatch strategy, any special instructions, and additional settings that govern how the job should be managed. The Job Configuration may determine if special handling is required due to item fragility or temperature sensitivity.Task
Within each Job Configuration, there exists a list of Tasks. A Task is where operational activities take place, involving a set of Quotes and a Delivery object. When you create a new Task, you solicit quotes from various providers for the delivery. For example, a Task might request quotes from different delivery providers, allowing the merchant to choose the best option based on cost and delivery time.Quote
A Quote is a pricing estimate for a delivery task. Quotes are generated for specific orders or jobs and contain important information such as price and provider. Quotes can be created, selected, and refreshed within the Nash system.Delivery
The Delivery object retains critical information concerning the progress of the delivery, including the status, estimated delivery time, courier details, and proof of delivery. It is instantiated before selecting a quote for a Task and becomes active when the quote has been selected. For example, customers can check the Delivery object to see if the courier has picked up the package and is en route to the destination.Dispatch Strategy
A Dispatch Strategy is a set of configurations that can be attached to Nash jobs during creation that enable features such as Auto Dispatch, Auto Reassign on Provider Failure, and Auto Reassign based on Pickup/Dropoff Time(s). These strategies help minimize manual oversight in monitoring and modifying jobs. For instance, you might configure a dispatch strategy to automatically reassign a job if the original provider fails to pick up the parcel within a specified timeframe.Provider
A Provider is the delivery company responsible for fulfilling your order. This company may be an internal fleet or a third-party provider that Nash partners with to offer diverse delivery options.Workflow
A Workflow is an automation that responds to an event in Nash and runs a series of actions — applying dispatch strategies, modifying orders, sending notifications, and more. Built from nodes connected by edges plus a trigger, workflows let you encode operational decisioning so the platform handles it instead of your application.Route
A Route is a planned, ordered sequence of stops for a vehicle or delivery agent. Where a single job is one pickup-to-dropoff delivery, a route bundles many stops into one itinerary — the unit used when a driver completes several deliveries in a single trip.Zone
A Zone is a geographic delivery area defined by a polygon boundary. Zones model where delivery is available, can be associated with one or more store locations, and support coverage lookups that answer which zones contain a given location.Store Location
A Store Location is a physical origin — a restaurant, warehouse, or store — that deliveries depart from. You register store locations once and then reference them from orders, associate them with zones, and answer coverage questions about which store serves an address.Store Catalog
A Store Catalog is the master data behind item-level fulfillment, pairing a product catalog (your canonical list of items) with store inventory (what each store location has on the shelf, including availability, pricing, and aisle location). Together they power pick & pack.Delivery Window
A Delivery Window is a bookable time slot for scheduled deliveries, tied to a store location and bounded by a maximum capacity. Customers reserve a window for an order, and once the window’s cutoff passes the orders booked into it are dispatched together.Shift
A Shift is the grouping of a delivery window’s orders for bulk dispatch. Orders are batched by organization, store location, pick shift name, and cutoff date, and the whole shift is dispatched together once its cutoff passes — firing theshift.dispatched webhook.
Activity / Optimization
An Activity is an asynchronous operation tracked by Nash; the optimization activity (POST /v1/activities/optimization) runs route optimization, solving the Vehicle Routing Problem (VRP) over a set of orders. You poll the activity by ID until its status reaches SUCCESS, then dispatch the resulting routes.