Order fields & settings reference
Last updated: October 12, 2026
This is a field-by-field reference for the order Edit drawer: every input that has a label in the portal, grouped by what it controls. It doesn't cover how to create, dispatch, or troubleshoot an order — for that, see How orders work and the related articles linked at the bottom.
Open any order and you'll find the same set of tabs: Pickup, Dropoff, Delivery Details, Merchant, Delivery Windows, Warnings, Notes, Activity, and Documents. The tables below follow that structure, grouped by subject rather than by tab, since Pickup and Dropoff share the same set of fields and Delivery Details covers several different concerns at once.
Warning
Once an order is dispatched, it's locked. Most fields can no longer be changed at all — edits are refused outright, or silently dropped without being saved. A small, organization-level exception exists for Items and Dropoff instructions, but it isn't on by default; whether it applies to your organization varies. Don't count on editing a dispatched order — treat dispatch as the point of no return.
Order identity
These sit in the drawer header, not in a tab, so they stay visible whichever tab you're on. None of them are editable here — they're the order's identifying information.
Field | What it does | Notes/constraints |
|---|---|---|
Order ID | Nash's identifier for this order. | Read-only. |
Package Identifier | The order's package identifier, repeated in the header so you can see and copy it from any tab. | Only appears when the order has one. Read-only here — to change it, edit Package Identifier on the Delivery Details tab (see Items & package below). |
Delivery ID | Links to the job this order created. | Only appears once the order has dispatched. Selecting it opens the delivery. |
Created At | When the order was created. | Read-only. |
External Group ID | Your own reference ID, if the order was created as part of a group. | Read-only; set at creation, not editable here. |
Contact
The same three contact fields appear on both the Pickup tab and the Dropoff tab — one set for the person or business you're picking up from, one for the person or business you're dropping off to.
Field | What it does | Notes/constraints |
|---|---|---|
Business Name | The business at that stop, if any. | Optional; used alongside or instead of a person's name. |
First Name / Last Name | The contact person at that stop. | At least a name or a business name is required — the order can't validate with both blank. |
Contact email for that stop. | Optional. | |
Phone Number | Contact phone number for that stop. | Required on both pickup and dropoff — an order without a valid phone number won't pass validation. |
Pickup & dropoff addresses
Also on the Pickup and Dropoff tabs, alongside the contact fields above.
Field | What it does | Notes/constraints |
|---|---|---|
Address | The full street address for that stop, entered with autocomplete. | Typing here is what drives the rest of the address fields below. |
City | The city, derived from the address. | Read-only — set by the address lookup, not typed directly. |
State | The state, derived from the address. | Read-only. |
Zip Code | The postal code, derived from the address. | Read-only. |
Country | The country, derived from the address. | Read-only. |
Instructions | Free-text delivery or pickup instructions for that stop. | Optional. Long instructions get an AI-generated summary alongside the text you entered. |
Barcodes | Barcodes tied to that stop. | Optional, under an advanced/collapsed section. |
Note
If a stop matches an address you've saved before, the portal shows a saved-location badge and lets you pick from your saved locations instead of retyping the address.
Scheduling & delivery mode
On the Delivery Details tab.
Field | What it does | Notes/constraints |
|---|---|---|
Delivery Mode | Whether the order goes out now or at a scheduled time. | Choosing "Scheduled" reveals the time and timezone fields below. |
Timezone | The timezone the scheduled times are interpreted in. | Only shown when Delivery Mode is Scheduled. |
Pickup Start Time / Pickup End Time | The window the pickup should happen in. | Only shown when Delivery Mode is Scheduled. Start must come before end. |
Dropoff Start Time / Dropoff End Time | The window the dropoff should happen in. | Only shown when Delivery Mode is Scheduled. |
Note
Delivery windows are a separate, org-specific concept from the scheduling fields above — see the next section.
Delivery Windows
A separate tab from Delivery Details scheduling. Instead of typing start/end times directly, you pick from a list of windows your organization has already defined, and the portal shows you which ones this order is eligible for.
Field | What it does | Notes/constraints |
|---|---|---|
Window name | Which delivery window the order is assigned to. | Selected from a list, not typed. |
Start time / End time | The window's delivery hours. | Shown for reference; set on the window itself, not per order. |
Cutoff time | The latest time an order can still book into that window. | Shown for reference. |
Price | What the window costs, if your organization charges for delivery windows. | Shown for reference. |
Remaining capacity / Maximum capacity | How much room is left in the window versus its total capacity. | Shown for reference; an order can't be assigned to a full window. |
Minimum order value | The lowest order value the window accepts, if set. | Shown for reference. |
Note
The Delivery Windows tab only appears for organizations that use delivery windows. Availability varies by organization — if you expect to have it and don't see it, reach out to Nash.
Items & package
Also on the Delivery Details tab.
Field | What it does | Notes/constraints |
|---|---|---|
Items Count | The total number of items in the order. | |
Currency | The currency the order's value is stated in. | |
Value | The declared value of what's being delivered. | Required — an order without a value won't pass validation. Can't be more than 100,000 in the order's currency. When you create an order with a value above 1,000, the portal asks you to confirm it first — a guard against typing an order number into this field by mistake. |
Package Identifier | An optional reference string for the package. | Optional. Once set, it also shows in the drawer header — see Order identity. |
Description | A free-text description of what's in the order. | Optional. |
Tags | Labels you attach to the order for filtering and reporting. | Optional. |
Dimensions — Weight / Height / Width / Depth | The overall size and weight of the package. | Optional, under an advanced/collapsed section. |
Per-item detail
Selecting into the item list on the Delivery Details tab opens per-item fields — useful when an order has more than one distinct item and you want to track them individually.
Field | What it does | Notes/constraints |
|---|---|---|
Item ID | Identifies the individual item. | |
Count | How many of this item. | |
Weight | The item's weight. | Optional. |
Value | The item's individual value. | Optional. |
Description | A free-text description of the item. | Optional. |
Barcode | A barcode for the item. | Optional. |
Dimensions — Height / Width / Depth | The item's size. | Optional. |
Sub-items | Items nested underneath this one. | Optional; used when an item is itself a bundle of smaller items. |
Dispatch & optimization
Also on the Delivery Details tab. These fields control how the order gets picked up and carried — by a delivery network Nash dispatches to, or by your own fleet — rather than what's in it.
Field | What it does | Notes/constraints |
|---|---|---|
Dispatch Strategy | Which strategy governs how this order gets dispatched — which providers or fleets are eligible and under what conditions it dispatches automatically. | Required. The strategy's own settings (allowed providers, auto-dispatch conditions, fee limits) aren't edited here — only which strategy the order uses. |
Optimization Strategy | Which strategy governs how this order gets grouped and sequenced with others when building routes. | The strategy's own settings aren't edited here — only which strategy the order uses. |
Requirements | Special handling requirements the order has. | Optional. |
Minimum Vehicle Size | The smallest vehicle size that can carry the order. | Optional. Narrows which providers or drivers are eligible. |
Driver Tip | A tip amount for the driver, with quick preset buttons. | Optional. |
Merchant
On the Merchant tab. Unlike every other section here, this one is display-only — there's nothing to set.
Field | What it does | Notes/constraints |
|---|---|---|
Name | The merchant associated with the order. | Read-only. Only present on orders that carry merchant information. |
Fee | The fee associated with that merchant. | Read-only. |
Advanced fields
A handful of fields sit under an "Advanced" section on the Delivery Details tab, collapsed by default because most orders don't need them.
Field | What it does | Notes/constraints |
|---|---|---|
Reference ID | An additional reference string beyond Identifier. | Optional. |
Pickup Service Time / Dropoff Service Time | How long the stop is expected to take once a driver arrives. | Optional; feeds route timing estimates. |
Metadata | Free-form key/value data you attach to the order. | Optional. |
Note
A superuser-only JSON field for raw optimization parameters also lives in this section. It isn't part of the standard operator workflow, so it isn't covered here.
What's not a field
Four more tabs on the order round out the drawer, but none of them are fields you set:
Warnings only appears when an order has a validation problem the portal doesn't have a labeled field for. It shows the raw error and asks you to contact support — it's an escalation surface, not something to edit.
Notes holds internal notes your team adds to the order — a running thread rather than a field. See read an order.
Activity is a read-only timeline of what's happened to the order. When an order is archived, the reason given shows next to the Order Archived entry.
Documents lists any documents attached to the order.
Related
How orders work — the order lifecycle, and what dispatch locks down.
Create an order manually — filling in these fields for the first time.
Resolve orders — what happens when a required field fails validation.