What it means
A picker may scan a shelf expecting ten units and find only eight. The order cannot be completed as planned, but the cause may be a misplaced carton, an unposted transfer or a count error.
An exception process tells the picker what to do rather than improvising a substitution or closing the pick as complete. Record the item, location, order, expected and found quantities, and condition, using a specific reason code where possible.
If the item is elsewhere in the warehouse, a qualified person can direct a re-pick and correct the location data. If stock is truly unavailable, customer service should know before making a delivery promise.
Separate the immediate order decision from the stock investigation, since a substitute, partial shipment or cancellation may need customer or buyer approval. The inventory balance may require a recount or adjustment, but changing it just to clear the screen can erase evidence.
Keep photos or scans if they clarify damaged or mislabelled goods, and keep a work-exception log, which can help managers distinguish missing stock from a picking workflow error. Look for repeated exceptions by item and zone, because frequent "not found" errors may point to poor putaway, replenishment timing or barcode problems.
A high exception count on one shift may mean a process change, not necessarily picker performance, so compare with volume and complexity before drawing conclusions. Make the workflow quick enough for operations, so a picker can flag the issue and move to the next task while a supervisor owns resolution.
Critical orders need a time limit for escalation, and the system should not let the same missing stock be allocated repeatedly without a real fix. For managers, the exception is a chance to protect a customer promise and improve stock accuracy at the same time, not merely a line to remove from a dashboard.
In practice
Real-world examples.
Example
A picker finds an empty location for a paid order of 12 units. The supervisor checks nearby bins and the last transfer before marking the item unavailable, and customer service is told only after the check is complete.
Example
A carton is present but damaged, so the picker records the condition with a photo. The team quarantines the carton and asks whether another saleable unit elsewhere in the warehouse can fulfil the order on time.
Example
A barcode scans as the wrong product variant, prompting a product-code and putaway check before shipping. The supervisor finds a similar-looking item in the same bin, moves it to its own location and updates the exception record with the cause.
Formula
Calculation
Pick exception rate = Order lines with a recorded pick exception / Order lines attempted to pick x 100
Worked example. A fictional warehouse attempts 2,000 order lines in a day. Forty lines have recorded exceptions, including missing, damaged and wrong-location cases.
- Exception rate = 40 / 2,000 x 100 = 2%.
- The team should classify causes; the rate alone does not tell which issue matters most.
A line with multiple alerts should be counted consistently to avoid inflating or hiding the rate.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Willow Parts, an invented spare-parts distributor. Pickers repeatedly skipped a small component shown in stock because its usual bin was empty. Customer service kept promising next-day delivery based on the system quantity, then apologised when parcels shipped short. Willow created a pick exception route with an owner and a time limit for checking nearby stock.
The investigation found a replenishment carton had been put away under a similar part code. Staff corrected the location and counted the affected items; customer service updated open orders with verified availability. The report showed a recurring location-control issue, not a need to blame pickers for reporting it. New scans at putaway reduced repeat exceptions.
Willow checks the exception log after the location fix. A later short pick at another bin has a different cause: stock was allocated but the replenishment had not completed. The team changes the replenishment trigger rather than applying the first incident's remedy to every exception.
Watch out
Common mistakes.
- Closing an order line as picked when the item was not found, making customer and stock records wrong.
- Substituting a different variant without required customer or product approval.
- Adjusting inventory immediately without checking transfers, locations and evidence of the discrepancy.
Questions
People also ask.
Is a pick exception the same as a stockout?
Not always. Stock may exist in another location or under a wrong record. Investigate before confirming a stockout.
Who should tell the customer?
The responsible service or order team should communicate a verified change to the fulfilment promise.
How can the rate be reduced?
Review reason patterns, putaway accuracy, replenishment, labels and system allocation rather than pressuring staff not to log issues.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%