When to use this
- Your warehouse sent the orders that are packed and ready, and you want to dispatch exactly those.
- A set of orders from another system has to be archived, or brought back.
- You need the current state of a list that spans several days and statuses.
Find the orders
1
Open Paste IDs
Open Orders in the table view and select Paste IDs, beside the search box. It isn’t on the map view.
2
Paste your list
Nash order IDs, your external IDs, and reference IDs can all go in the same list. Separate them with new lines, commas, semicolons, or tabs. A space isn’t a separator, so an ID with a space in it stays whole. Nash strips a pair of quotes around a value and removes repeats, telling you how many it dropped.A list holds up to 1,000 distinct IDs. Past that, nothing is sent and the dialog tells you how many to remove.
3
Find orders
Select Find orders, or press Cmd+Enter (Ctrl+Enter on Windows). The table now shows the matching orders, with a Matched ID column saying which identifier found each one, and a line above it counting how many of your IDs matched. Select the not found count to see the IDs that matched nothing, with Copy IDs to take them back to whoever sent the list.
so-104417 doesn’t find SO-104417. One external or reference ID can belong to several orders; Nash shows all of them and says the ID matched more than one. An order found by more than one of your IDs is listed once.
While a lookup is active, the table’s date range, status, route, and other filters don’t apply to it, and those controls are disabled. Your organization and your location access still do — an ID for an order you couldn’t otherwise see comes back as not found. The Pasted IDs tab holds every match, and the status tabs beside it narrow them. Edit IDs reopens your list. The lookup isn’t saved in the URL or in a saved view, and it clears when you switch organizations.
Run an action
The Actions menu works on the orders in the tab you’re looking at. Each action shows how many of them it can change and how many it will skip, with the reason. Orders an action doesn’t apply to are skipped, never changed.
An order is skipped when the action doesn’t fit its state: it’s already dispatched or already archived, it needs attention, it’s on a route, or it’s a delivery order and the action is for customer pickups. The review lists what will change, what will be skipped, and the IDs that weren’t found, each with Copy IDs.
One run changes at most 1,000 orders. If the tab holds more, narrow it with a status tab first.
A user scoped to specific store locations can dispatch and mark orders as picked up in bulk, but not archive or unarchive them; those two actions are disabled, with the reason shown.
Check the outcome
A run shows its progress as it goes, then a summary of the orders that were done, skipped, or failed, with the reason for each failure. If a run stops partway, the summary lists the orders it couldn’t confirm. Some of those may have gone through, so check them before running the action again.Related
Routes
Plan the orders you found onto routes from the Orders map.
Dispatch strategies
What happens to an order once you dispatch it.