How to plan and run a warehouse product recall

What a warehouse recall plan needs to answer

When a recall notice arrives, the questions are always the same, and they arrive in this order. What exactly is affected? Where is it right now? Who already has it? How do we stop it moving? What do we do with it? Can we prove what we did?

A recall plan is a written answer to each of those questions, prepared in advance, with names attached. It says which data you will query, who has authority to stop shipments, who contacts customers, where held stock goes and how the final count is reconciled. If a step depends on one person remembering how to filter a spreadsheet, it is not a plan yet.

This guide is operational. It does not cover the legal side of recalls. Operators in regulated categories, such as food, supplements, cosmetics, medical devices or vehicle safety parts, must follow the requirements that apply to them and should validate their plan against those requirements with qualified advice.

• Scope: which lots, SKUs, suppliers or dates are affected
• Location: every affected unit on hand, by bin, status and owner
• Exposure: what has been picked, packed, loaded or shipped, and to whom
• Containment: how movement stops within minutes, not hours
• Disposition: what happens to each unit, and who approves it
• Evidence: the record that shows the recall was complete

Build lot and supplier traceability before you need it

You cannot trace what you never recorded. Most recalls are scoped by lot or batch, sometimes by supplier or production date range, occasionally by serial number. If your receiving process does not capture the lot on every inbound line, the recall will be scoped by SKU instead, and you will hold (and possibly destroy) good stock alongside bad.

Capture traceability at the dock, because that is the last point where the information is easy to get. Record the supplier, the purchase order or ASN, the lot and expiry for every received line, and the pallet or carton identifier if you use license plates. When supplier cartons carry GS1-128 or DataMatrix barcodes, one scan can capture GTIN, lot and expiry instead of relying on someone to type them.

Then keep the link intact through every move. Stock that is split, relabeled or transferred between warehouses must still carry its lot. On the way out, the shipment record must say which lot went to which customer, not just which SKU. That outbound link turns a recall from "contact every customer who bought OIL-008 this year" into "contact the four customers who received LOT-0826". For the full chain, see our guide to inventory traceability.

• Receiving: supplier, PO or ASN, lot, expiry and serial where relevant
• Storage: the lot stays on the balance through moves, splits and transfers
• Kitting: record which component lots went into each built kit
• Shipping: each shipment line records the lot, the quantity and the customer

How to scope a recall hold

Scope is the first decision, and it is a trade-off. Too narrow and affected product keeps shipping. Too wide and you freeze good stock, miss orders and create a second problem. Start from the notice and translate it into warehouse terms: a list of lots, a SKU or set of SKUs, a supplier, a receipt date range, or a combination.

When the notice is vague, hold wide first and narrow later. It is far easier to release stock that turned out to be fine than to recover a unit that shipped during the hour you spent clarifying. A common pattern is to hold every lot of the SKU from that supplier immediately, then release lots one at a time as the supplier confirms they are unaffected.

The hold must stop stock in the system, not only on the shelf. An inventory hold should make the units unavailable for allocation, so no new order can reserve them and no pick list can send someone to fetch them. Check what happens to orders that had already reserved the held stock: they should be flagged for a decision, not shipped by default.

• By lot: the most precise scope, when lots were captured at receiving
• By SKU: when lots are unknown or the defect affects the whole product
• By supplier or ASN: when a single source or delivery is suspect
• By location or LPN: when contamination or damage is physical and local
• By date range: when the notice cites manufacturing or receipt dates

Finding recall exposure: from shelf to customer

Exposure is every affected unit that is not safely contained. Work through it stage by stage, because each stage has a different owner and a different fix.

In stock means units in storage or pick locations. List them by location, lot, status and owner so the team can pull them. Include receiving, returns, inspection and in-transit locations, which are the easiest to forget. Picked but not packed means units in totes or at the packing bench: stop the pack and send them to the hold area.

Packed or loaded means sealed cartons or pallets in staging, or on a truck that has not left. Pull them before dispatch. This is where a carton or pallet identifier saves an hour of opening boxes. Shipped means units that left the building. For each shipment you need the customer, the delivery address, the ship date, the lot and the quantity. If you fulfill for several brands, you also need the owning client, because the brand usually handles customer contact.

Report exposure as one table everyone works from, with a total that must balance: units received of the affected lots equal units still in stock, plus units in process, plus units shipped, plus units consumed, adjusted or destroyed. If the sum does not balance, you have a gap to investigate before you call the recall complete.

Recall communication: who tells whom

Decide the chain before the drill, not during it. The warehouse usually does not decide whether to recall; the product owner does. The warehouse's job is to confirm scope, report exposure fast and act on instructions. A third-party warehouse reports to its client, and the client contacts its own customers.

Write down names and a backup for each role. Keep a short template for the exposure report so it goes out in the same shape every time: affected lots, units on hand by status, units in process, units shipped by customer, and open questions. During an active recall, send updates at fixed intervals even when nothing has changed, so nobody fills the silence with guesses.

On the floor, tell the team what is held, why, and how to recognize it. A printed list of affected lot codes at every packing bench and one clear rule, such as "if the scan says hold, stop and call a lead", catches the unit that someone put in the wrong bin.

• Recall lead: owns the decision log and the final report
• Inventory lead: runs the hold, the pull and the counts
• Customer or client contact: sends notices and tracks responses
• Supplier contact: confirms scope, returns and credits
• Shift leads: brief each shift and handle exceptions

Quarantine and physical segregation

A system hold stops allocation. Physical quarantine stops mistakes. Move held stock to a marked quarantine area with its own location code, so a picker who ignores a warning still cannot take it from a normal pick face. Label pallets and cartons with the reason and the date.

Record every move into quarantine as a stock movement, not a note. The status should change to quarantine or hold, the location should change to the quarantine area, and both should reference the recall. Units that customers send back should come in through receiving into the same quarantine status, with the lot captured again, so they count against the recall instead of being restocked.

Keep quarantine small and visible. An area that slowly fills with unrelated damaged goods and old returns makes the recall count harder and slows every disposition decision.

Disposition, closure and recall record keeping

Every held unit ends with one disposition: return to supplier, destroy, rework or relabel on the owner's instructions, or release to available stock if it proves unaffected. Each disposition should be approved by the person with authority to make it, recorded with a reason, and reflected in the stock record as a movement.

Before closing, reconcile. Compare units received of the affected lots with the sum of every outcome, and explain any difference. Keep the evidence together: the notice, the scope decision and every change to it, each exposure report, customer and supplier correspondence, pull lists, return or destruction documents, and the final reconciliation.

How long you keep these records depends on your product category, your contracts and the rules where you operate. Set the retention period with whoever owns compliance for the product, and make sure the records survive a change of system.

• Return to supplier: supplier return reference and credit tracked
• Destroy: method, date, quantity and witness recorded
• Rework or relabel: only on the owner's written instruction
• Release: approval, reason and the evidence that the lot is unaffected

How to run a mock recall drill

A mock recall tests the plan without a real problem. Choose a real lot that you received a few months ago and that has partly shipped, give the recall lead a written mock notice, and start a timer. The point is to learn how long each step takes and where the data or the process breaks.

Set your own time targets and tighten them after each drill. As an illustration, a team might aim to produce a complete exposure report within two hours and physically locate all on-hand stock within four. The targets matter less than the trend and the gaps you find: a location nobody checked, a shipment line without a lot, a customer list that took a day to assemble.

Run drills at different times, including a busy shift, and vary the scope: one by lot, one by supplier, one by SKU. You do not need to block real stock for a drill if that would disrupt orders; producing the exposure report and physically verifying on-hand quantities is usually enough to test traceability.

• 1. Choose a lot with stock in several states: on hand, in process and shipped
• 2. Record the start time and hand the recall lead the mock notice
• 3. Produce the exposure report: on hand by location, in process, shipped by customer
• 4. Physically verify on-hand quantities against the report
• 5. Reconcile the received quantity against every outcome
• 6. Record the time for each step and every gap found
• 7. Fix one or two gaps, then schedule the next drill

How NextStock handles holds and recalls

In NextStock, lots, expiry dates, serial numbers and license plates are captured at receiving, including from GS1 barcodes, and stay on the stock record as it moves between locations and warehouses. A hold can be scoped by lot, SKU, location, LPN, supplier or ASN. A recall shows exposure in one view: what is still in stock, already picked, packed, loaded or shipped, and to which customers. Because every quantity change is a ledger movement with a reason and a reference, disposition and the closing reconciliation come from the same record. See holds and recalls for how it works.