# Saved Orders

Lets the cashier save an in-progress order and resume it later. Loads the saved-orders list filtered by current location (or all locations) and the active user, with optional column customisation. Includes navigation guards that block tab close / page navigation when an unsaved order is in progress.

## Available in

* Order Form modules **only**

## When to use

* Cashier registers where a customer steps away mid-sale and the cashier needs to handle other customers in the meantime.
* Multi-shift workflows where one cashier starts an order and another finishes it.
* Anywhere "save this for later" is part of the natural flow.

## Settings

| Setting       | Description                                                                      |
| ------------- | -------------------------------------------------------------------------------- |
| **Configure** | Opens the configuration modal — button labels, column selection, location scope. |

The configuration modal supports:

* **Saved Orders Button Label** — text on the *open saved orders* button. Default: *Saved Orders*.
* **New Button Label** — text on the *new order* button. Default: *New*.
* **Save Button Label** — text on the *save current order* button. Default: *Save*.
* **Columns** — which columns to show in the saved-orders list. Available: Order Name, Order Number, Date, Customer Name, Logged-in User, Authorized User, Quantity, Total. All enabled by default.
* **Show All Location Orders** — show saved orders from all locations (Yes) or only the current location (No). Default: No.

## How it works

1. Loads saved orders via SuiteQL, filtered by:
   * Current location (or all locations if Show All Location Orders = Yes).
   * Subsidiary.
   * Module name (so the list is workflow-specific).
2. Parses each order's `custrecord_brm_order_items` JSON to compute item count and total.
3. The user clicks *Save* — a modal appears asking for an optional order name.
4. The user clicks *Saved Orders* — sees the list, picks one to load.
5. **Loading** clears the current order state, then populates customer + line items (marks line items as `source: 'savedOrder'`).
6. **Deleting** soft-inactivates the saved-order record (no hard delete).
7. **Navigation guard** — if the user has an in-progress order with unsaved changes, navigation is blocked (with a confirm prompt) via `beforeunload` + the TanStack Router blocker.

{% hint style="info" %}
Use **Show All Location Orders = Yes** in environments where cashiers move between registers and need to pick up where they left off regardless of which physical location they're at.
{% endhint %}

## Examples

**Standard cashier hand-off.** Saved Orders with default settings. Cashier saves a sale, walks away, another cashier opens the saved orders list, picks it up, and completes the transaction.

**Multi-location warehouse.** Saved Orders with Show All Location Orders = Yes. Pick from any saved order across all warehouses.

**Compact saved-list view.** Columns trimmed to just Order Name, Customer Name, Total — for a tighter list on small screens.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Order Lines</strong></td><td>The block that holds the items being saved or resumed.</td><td><a href="/pages/0XacQvdUpwJMX7gVJCf4">/pages/0XacQvdUpwJMX7gVJCf4</a></td></tr><tr><td><strong>Customer/Vendor Selection</strong></td><td>The customer that's saved alongside the order.</td><td><a href="/pages/km19hjFIFOFjRK0yQAJp">/pages/km19hjFIFOFjRK0yQAJp</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/transaction-components/saved-orders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
