Stock Status & Quality Holds
Mark stock as quarantined, awaiting inspection, damaged or expired so it stops being treated as sellable — then release it or dispose of it with a record of the decision.
Not all stock on a shelf is stock you can sell. Inventory → Stock Status lets you set a status on a specific quantity in a specific place, which is how "this pallet is pending inspection" becomes a fact the rest of the system respects rather than a note on a whiteboard.
The Statuses
Stock in a location carries one of these: Available, Reserved, Allocated, Quarantined, Inspection pending, Damaged, Expired, Returned, In transit, or Consigned. Some of these are hold statuses — the screen labels which — and stock under a hold is not available stock.
Hold, Release, Dispose
- Hold a quantity with a reason: goods arrived damaged, a batch is under recall, an inspection is outstanding.
- Release it back to available when the inspection passes. A partial release is fine — you can free part of a held row.
- Dispose of it when it fails. Disposal is a real stock movement, so it raises an adjustment rather than making quantity disappear.
All three actions need the same permission as adjusting stock, and the same rules apply whether you act from the web screen, the scan console, or the mobile app — one set of decisions behind three doors, so nothing you are refused in one place is allowed in another.
The Working Screen
The status list is deliberately a working screen, not a full inventory listing: it shows the largest quantities first and is capped, and you reach a specific row by filtering to the item. A summary at the top shows how much stock is currently held and under which statuses.
Where This Shows Up Elsewhere
Held stock is the usual explanation for the two most common "the numbers are wrong" reports: a count variance that nobody can source, and an item that looks in stock but cannot be promised to a customer. Check holds first — see Stock Mismatch and Batch, Lot & Serial Traceability.
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.