Blocked reasons

Every order row shows why it is stuck in plain words — not a status code. If someone rings up asking about their order, you can read the reason out loud.

On this page

• The vocabulary
• Short of stock
• Allocation states
• See also

The vocabulary

Reason	Means
Waiting for payment	Payment has not settled yet.
Possible fraud	Flagged for review before it ships.
Address problem	The delivery address needs fixing.
Waiting for stock	Held until stock arrives.
Waiting for production	Held on a build or work order.
Waiting for supplier stock	Held on an inbound supplier delivery.
Customer asked to wait	The customer requested the delay.
Other reason	Anything else, with the note explaining it.

The last three matter for expectation-setting: they say plainly that the warehouse is not the thing that is late.

Short of stock

Where an order is short, the row does not just say so — it tells you how many SKUs are missing. One click shows which ones, broken down per warehouse, with a link straight to that product’s stock page.

That chain — row → missing SKUs → per-warehouse stock → the documents causing each number — is the fastest path from “this order is stuck” to “this is why, and here is the receipt that fixes it”.

Allocation states

Underneath the blocked reason sits the line-level reservation state, shown in the same plain register:

State	Means
Reserved	Stock is set aside for this line.
Being picked	A picker is walking it now.
Not enough stock	The reservation could not be made — a shortShort pickWhen a bin does not hold what the system expected. Recording it marks the line as not enough stock and posts the discrepancy against that specific bin, rather than quietly under-picking the order. Read more → .
Reservation released	The reservation was given back.
Fulfilled	Shipped and consumed.

See also

• Holds — applying and releasing a hold with a reason and a reference.
• Views — the Blocked and Backordered views.
• Stock — where the missing-SKU link lands.

Last updated: 23 August 2026