Skip to content

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.

  • Applying a hold
  • The document reference
  • Releasing a hold
  • See also

Holds are applied and released on the order detail page (/orders/:id). Each one takes three things:

  1. 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).
  2. A note — free text for the specifics.
  3. 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.

Where the hold is waiting on something, you can record what:

KindTypical reference
Purchase orderPO-1042
TransferThe inbound transfer you are expecting
Work orderThe build that has to finish first
Bundle buildThe kit assembly this order needs

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.