Holds
A holdHoldA deliberate block on an order, recorded with a reason, a note and usually a reference to the document being waited on. A hold is a decision, not a failure. Read more → is a decision, recorded. It stops an order reaching the floor and says why, so nobody has to guess and nobody picks something that should not ship.
On this page
Section titled “On this page”- Applying a hold
- The document reference
- Releasing a hold
- See also
Applying a hold
Section titled “Applying a hold”Holds are applied and released on the order detail page (/orders/:id). Each one takes three things:
- A reason — from the fixed list (waiting for payment, possible fraud, address problem, waiting for stock, waiting for production, waiting for supplier stock, customer asked to wait, other).
- A note — free text for the specifics.
- A reference — the document you are waiting on, if there is one.
The reason drives everything downstream: the Blocked tab groups by it, Needs attention ranks by it, and the order row shows it verbatim.
The document reference
Section titled “The document reference”Where the hold is waiting on something, you can record what:
| Kind | Typical reference |
|---|---|
| Purchase order | PO-1042 |
| Transfer | The inbound transfer you are expecting |
| Work order | The build that has to finish first |
| Bundle build | The kit assembly this order needs |
Releasing a hold
Section titled “Releasing a hold”Releasing takes the block off and moves the order back into the normal flow — allocation re-runs, and if stock is available the order becomes ready to ship.
Both the apply and the release land on the order’s timeline with who did it and when, so a hold is never an unexplained gap in an order’s history.
See also
Section titled “See also”- Blocked reasons — the full vocabulary.
- Order detail — the Waiting stage a hold creates.
- Needs attention — holds grouped by reason on Home.