> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usenash.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Nash exposes two MCP servers. The docs MCP server at https://docs.usenash.com/mcp searches this documentation and needs no credentials. The Nash MCP server at https://mcp.usenash.com/mcp operates an organization's deliveries and needs a Nash API key. See https://docs.usenash.com/reference/build-with-ai.
> Use the Sandbox environment (https://api.sandbox.usenash.com/v1) for anything that creates or dispatches deliveries during development.

# Find and act on a list of orders

> Paste a list of Nash IDs, external IDs, or reference IDs into the Portal's Orders table, see every match, and dispatch, mark as picked up, archive, or unarchive the orders each action applies to.

**Paste IDs** on the Portal's Orders table takes a list of order identifiers from a spreadsheet, an email, or a warehouse export and shows you those orders, whatever date or status they're in. From there you can run an action on the ones it applies to. It's available to organizations with the Orders page turned on.

## 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.

When you're looking for work by what it has in common — a pickup location, a date, a tag — use the table's filters instead. Paste IDs is for when you already know which orders you mean.

## Find the orders

<Steps>
  <Step title="Open Paste IDs">
    Open **Orders** in the table view and select **Paste IDs**, beside the search box. It isn't on the map view.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

Matching is exact and case-sensitive: `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.

| Action | What it does |
| - | - |
| **Dispatch** | Turns each eligible order into a job (delivery) and sends it to your dispatch strategy. You review the list and confirm first. |
| **Mark as picked up** | Records customer pickup orders as collected. You review the list and confirm first. |
| **Archive** | Asks for a reason, then archives. The reason is saved on each order. |
| **Unarchive** | Restores archived orders. It runs as soon as you choose it. |

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

<CardGroup cols={2}>
  <Card title="Routes" icon="route" href="/reference/routes">
    Plan the orders you found onto routes from the Orders map.
  </Card>

  <Card title="Dispatch strategies" icon="shuffle" href="/reference/dispatch-strategies">
    What happens to an order once you dispatch it.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.