A lot trace report is only as true as the capture discipline behind it. Recalls are won or lost at the receiving dock, the pick face and the returns bench — months before anyone runs the query.
The recall notice arrives on a Friday afternoon, as they do. A supplier tells you that lot 24187 of an ingredient, a component, a chemical — pick your industry — failed a test after release, and you have until Monday to tell your customers which shipments contained it. What happens next was decided months earlier, at your receiving dock.
Most systems can print a lot trace report. The question is whether the report is true. A trace is only as good as the weakest capture point in the chain that feeds it, and every warehouse has a set of touches — receiving, putaway, replenishment, picking, packing, returns — where a lot number either got recorded or got waved through. If any one of them is optional, the report has holes exactly where the recall needs it to be solid.
Start at receiving, because everything downstream inherits it. A lot-controlled item must be impossible to receive without a lot number — not discouraged, impossible. The scanner flow should demand the supplier lot, the quantity and, where it applies, the expiry date before the pallet can move off the dock. The moment 'we will enter the lots later' is allowed once, later becomes never, and the lot on file becomes whichever one the clerk found on the top case.
Putaway and replenishment are where clean lots get blended. Two pallets of the same SKU with different lots dropped into one bulk location become, for the system, one undifferentiated pile — and the trace now says 'either'. Lot-controlled items need lot-level location balances, and every move needs to carry the lot with it. That is a data-model property, not a training issue: if the location record can only hold a quantity, no procedure will save it.
Picking is the half of traceability most operations forget. One-step-back — which supplier lot arrived — is receiving's job. One-step-forward — which customer got it — is picking's. The pick confirmation must capture which lot was actually taken, not which lot the system suggested. Where regulations or customers require first-expiry-first-out, the system should enforce the pick sequence and flag every override, because the exception you allowed is the shipment you will be searching for.
Then there are the flows nobody diagrams: returns that go back to stock, rework that merges two lots into a third, samples pulled for quality, transfers between branches. Each is a place where a lot either follows the goods or silently detaches from them. A traceability audit should walk every one of these paths with a test lot and check that the chain survives. Most operations fail first at returns.
Regulated distributors know the standard: the recall query has to complete in hours, not days. Food-safety rules, pharmaceutical serialization mandates and automotive quality standards all converge on the same test — given a lot, produce every receipt, every current location and every customer shipment, with quantities that reconcile. If gathering that means joining a warehouse spreadsheet to an invoicing system by hand, the answer is days, and the exposure window grows with every hour.
Run mock recalls the way you run fire drills. Pick a lot at random each quarter, start the clock, and produce the full trace: received quantity, on-hand by location, shipped quantity by customer, and the arithmetic that shows they reconcile to the unit. Time it. A mature operation completes the exercise in under an hour; the first attempt usually takes a day and ends with a quantity that does not balance — which is precisely the point of the drill.
The commercial argument is stronger than the compliance one. A distributor who can answer a recall in an hour ships the notice with the affected customer list already attached, quarantines the on-hand stock with one transaction, and keeps selling every lot that was not implicated. The one who cannot must over-recall — pulling everything adjacent because they cannot prove what is clean — and over-recalling is how a supplier's problem becomes your write-off.
So treat the report as the output and the workflow as the product. Make lot capture structurally mandatory at every touch, keep balances at lot-and-location grain, enforce expiry sequencing where it matters, and drill the trace until it is boring. When the Friday notice arrives, the difference between a bad afternoon and a bad quarter is whether your dock was disciplined in March.