A midsize sauce and preserves maker ran a mock recall drill because a major retailer required it. The scenario: a batch of hot sauce had to be traced from raw ingredients to the store shelves. The quality manager started looking through paper production logs from three months earlier. She found the batch number, then had to walk the warehouse to identify pallets because the records showed only “production run rough date.” Four hours and twenty minutes later, they could tell the auditor which stores received the batch. The retailer’s requirement: 20 minutes.
The problem was hidden in the pallet labels
In this plant, two workers filled and labeled jars on a fast line, writing batch references on a paper sheet at the start of each shift. When jars were packed onto pallets, the pallet stickers only showed the product name and the date. If two batches were packed on the same day, which many were, the information simply melted together. The quality manager confesses they had already shipped a batch with the wrong best-before label without noticing, and only a customer complaint about a sour jar revealed it.
ERPNext Consulting started with one question: what does the retailer need you to prove about one jar in your finished goods? The answer was a simple chain of evidence from raw material lots, through production, to the dispatch note.
The batch routine that produces usable records
The solution wasn’t exotic. It was discipline applied to three moments that already existed in the day:
- When production starts, a printed batch ticket is generated, and it accompanies the line until the run ends. The operator writes nothing by hand.
- When materials are issued from the store, the system keeps track of which raw material lot went into which production batch. Leftover ingredients are returned and recorded on the same day, not dumped back into the next shift’s pot.
- Every finished pallet gets a label with batch number, best-before date and location code. A pallet without a label is quarantined, not shipped.
That last rule hurt most. In the first week, three pallets were delayed because stickers had not been printed. The warehouse manager called it “stupid paperwork.” Two months later, during a surprise audit mock recall, the same drill took 90 seconds.
Why this matters beyond the audit checklist
Trackable batches also cut their write-offs. Previously, when one lot was suspected of a problem, the entire day’s production was blocked because they couldn’t tell which pallets were safe. With proper lot records, only the affected batch was quarantined. In one recall-like situation, that meant blocking 240 jars instead of 2,400. The value of traceability shows itself in the panic moment, not in the calm one.
If you sell food, cosmetics or any regulated product, test your own recall procedure this month. Run the drill exactly as the auditors would: pick a random batch and time how long it takes to find every receiving point. ERPNext Consulting often finds that the weak link isn’t the system — it’s pallets sitting somewhere missing a label to scan.