Order
Background
Overview of Nash Orders (and their relation to Jobs)
An Order represents the delivery details for package(s) in the real world. It’s the most flexible way to initiate deliveries in Nash.
Orders enable you to:
- Update the delivery details before a delivery is created (contact details, addresses, times, and requirements) e.g. E-Commerce Checkout Experience
- Understand whether the order meets the criteria to become a delivery (validation) e.g. Error handling as early as possible
- Batch orders through Nash Platform (not optimized or batched on your end) e.g. Optimizing catering routes
When one or more Orders are dispatched, they become a Job.
Order Data Model
Order status
needs_attention
: The order requires attention due to some data issues (e.g. invalid address)valid
: The order is valid and is ready to be dispatched to a Nash Job & Delivery.dispatched
: The associated Nash job is found in order_metadata or by clicking on the action “view dispatched job”archived
: The order has been archived and is moved to archived tab in the Nash portal.
Note: All timestamps are in UTC and in this format %Y-%m-%dT%H:%M:%S.%f