The order from last Wednesday
A client emails on Monday: an order placed last Wednesday still has not shipped, and the customer is threatening a chargeback. You look it up. It has been on hold since it arrived because one of the three items had no stock at the pick location, although there was stock in a reserve location that nobody replenished. The WMS shows it in a status called 'awaiting stock'. Nobody was looking at that status.
It is not the only one. There are forty more orders in various hold statuses across twelve clients: addresses the carrier rejected, SKUs that do not exist in the WMS, orders waiting for a client's fraud check, a B2B order waiting for a booking reference.
Why held orders get forgotten
The daily rhythm of a warehouse is releasing and dispatching orders that can go. Anything that cannot go drops out of that rhythm. The WMS records a status, but statuses are often vague, several different problems share the same one, and there is no owner.
| Hold reason | Who can actually fix it |
|---|---|
| No stock at pick face, stock in reserve | Warehouse, by replenishing |
| No stock anywhere | Client, by sending stock or cancelling |
| Unknown SKU | Client or onboarding, by adding the product |
| Address rejected by carrier | Client, by confirming with the customer |
| Awaiting client approval or booking | Client |
| Label or carrier service error | Warehouse or carrier account settings |
Because the fix sits with different people, nobody feels responsible for the list as a whole.
What forgotten holds cost
Late orders that hit the client's customer reviews and their marketplace metrics. Chargebacks and refunds the client may try to pass on to you. And the feeling for clients that the warehouse lets things slip, which undermines everything else you do well.
Held orders also distort your service level reporting. An order held for stock is usually excluded from the dispatch KPI, but only if someone recorded why it was held. Otherwise it counts as your miss.
Inside the warehouse, the cost is wasted work. Stock that was allocated to a held order is locked up and unavailable for others, so a second order can be held for the same missing item even though there is enough stock on site to fill it.
The hold monitor we build
- A regular read of every order from your WMS that is not released, picked or dispatched, with its status and age.
- Reason detection beyond the status code: checking stock in reserve locations, whether the SKU exists, whether the carrier rejected the address and what it said.
- An owner for each reason: warehouse team, client, onboarding or carrier setup, with the specific action needed.
- Warehouse actions sent where they can be done, such as a replenishment task for stock sitting in reserve.
- Client notifications listing their held orders and what is needed from them, in one message rather than dozens.
- Escalation when an order has been held beyond an age you set, and hold reasons recorded against the order for SLA reporting.
What the team gets
A short list each morning of held orders with a named reason and owner. Clients hear about their holds before their customers complain. Replenishment problems stop masquerading as stock shortages. And service level reports reflect which holds were outside your control.
Are orders slipping through like this?
- Clients find held orders before you do.
- Several different problems share one hold status in the WMS.
- Orders wait for stock that is on site in a reserve location.
- Clients get held-order emails one at a time, if at all.
- Nobody owns the list of orders that cannot ship.