---
title: Batch traceability and mock recall for a dairy or food plant, in four hours
canonical: https://naffo.tech/blog/batch-traceability-recall-dairy-food-plant
question: How do you set up batch traceability and run a mock recall in a food plant?
published: 2026-05-20
updated: 2026-08-08
author: naffo.tech manufacturing team (Plant systems and costing)
reviewed_by: naffo.tech implementation desk (Dairy and food plant rollouts)
publisher: naffo.tech — https://naffo.tech
category: Compliance & traceability
tags: traceability, recall, FSSAI, dairy, QC, batch
reading_time_minutes: 10
license: Free to quote with attribution to naffo.tech (https://naffo.tech/blog/batch-traceability-recall-dairy-food-plant)
---

# Batch traceability and mock recall for a dairy or food plant, in four hours

**Question:** How do you set up batch traceability and run a mock recall in a food plant?

**Answer:** Batch traceability needs seven unbroken links: supplier lot at GRN, incoming QC result on that lot, lot issued to a specific production batch, batch output with its own batch number, finished-goods QC release, batch allocated on each dispatch line, and the customer on that invoice. With those links, a mock recall runs in both directions — complaint back to supplier lot, and supplier lot forward to every affected customer. Target completion under four hours end to end, including customer notification lists.

## Key takeaways

- Traceability is not a report you buy, it is seven links you must not break. One manual step anywhere and the chain resolves to "ask Ramesh".
- One-up, one-down is the legal minimum. A real recall needs one-up, one-down at every hop, which is what makes it bidirectional.
- Batch allocation at dispatch is unrecoverable if skipped. It costs nothing at the time and cannot be reconstructed afterwards.
- Run a mock recall quarterly and time it. Untested traceability is a claim, not a capability.
- Rework is the link most often lost, because material from batch A ends up inside batch B without a record.
- The recall decision is a business decision made under time pressure — pre-write the roles, thresholds and notification templates while nobody is panicking.

## Key figures

- **7** — Data links that must remain unbroken for traceability (Basis: Supplier lot at GRN, incoming QC on lot, lot-to-batch issue, batch output identity, FG QC release, batch-to-dispatch-line allocation, dispatch-to-customer.)
- **< 4 hours** — Target time to complete a bidirectional mock recall (Basis: Practical target for a single-plant SME with the seven links captured in one system, including building the affected-customer notification list.)

## What traceability actually means on a shop floor

Every food business says it has traceability. Very few can answer this in one sitting: _"A customer in Rajkot has a complaint about a curd cup dispatched on 14 July. Which milk lots were in it, what were their incoming QC readings, which other customers received product from those same lots, and how much of it is still in the market?"_

That question is the whole discipline. Answering it does not require expensive software — it requires that seven specific links were captured at the moment the work happened, because none of them can be reconstructed later.

## The seven links that must never break

_Each link, when it is captured, and how it usually breaks_
| # | Link | Captured at | How it breaks in practice |
| --- | --- | --- | --- |
| 1 | Supplier lot identity | GRN / milk reception | Material received without a lot number, or all of a day's intake merged into one nominal lot |
| 2 | Incoming QC result attached to that lot | Before put-away | QC recorded in a separate register with no lot reference |
| 3 | Lot issued to a specific batch | Material issue | Issue booked to a product or department instead of a batch |
| 4 | Batch output identity | Batch close | Output added to stock without its own batch number and manufacturing date |
| 5 | Finished-goods QC release | Before stock becomes sellable | Product dispatched while QC result is pending, released verbally |
| 6 | Batch allocated per dispatch line | Dispatch / invoice | Invoice shows quantity only; batch decided by whoever loaded the vehicle |
| 7 | Customer on that dispatch | Invoice | Cash sale or distributor sale with no consignee detail |

> **Link 6 is the one that cannot be recovered**
>
> Links 1 to 5 can sometimes be reconstructed from registers with enough effort. Link 6 cannot. If the invoice does not record which batch went out, then after the vehicle leaves there is no source anywhere that knows. Batch allocation at dispatch costs about three seconds and is the difference between a four-hour recall and a blanket withdrawal of everything you shipped that week.

## One-up, one-down, at every hop

Regulators generally require one-up, one-down: you must know your immediate supplier and your immediate customer for any consignment. That is the floor. It is not enough for a real incident, because a real incident is bidirectional and multi-hop.

- **Backward trace (root cause).** Complaint → customer invoice → dispatched batch → batch record → issued lots → incoming QC → supplier. This tells you _what went wrong_.
- **Forward trace (exposure).** Suspect supplier lot → every batch that consumed it → every dispatch from those batches → every customer. This tells you _how big it is_.
- **The multiplier is rework.** If output from batch A was reworked into batch B, then batch B inherits batch A's exposure. Systems that do not record rework as a traced input silently understate the recall scope — this is the single most common traceability defect in food plants.

> **Why forward tracing is the frightening direction**
>
> A supplier lot of 4,000 L of milk is suspect. It was issued across three batches over two days: paneer PNR-118, curd CRD-0412 and a small ghee batch. Those three batches produced output dispatched to 31 customers, including two distributors who onward-sold to retailers you do not invoice directly.
>
> Backward tracing from a single complaint would have shown you one batch. Forward tracing shows you 31 customers and two distribution tiers. If you cannot do the forward direction, you will either recall far too much or far too little — and both are expensive, one financially and one reputationally.

## Withdrawal versus recall — decide the language before the incident

_Different situations, different responses. Agree the thresholds in advance._
| Situation | Typical response | Trigger | Who decides |
| --- | --- | --- | --- |
| Product still under your control | **Stock withdrawal / hold** | QC failure found before dispatch, or in your own warehouse | QC in-charge |
| Product at distributor or retailer, no health risk | **Market withdrawal** | Labelling error, weight variance, quality complaint without safety implication | Plant head with owner informed |
| Product reached consumers, potential safety issue | **Recall** | Contamination, allergen, foreign matter, microbiological risk | Owner, with regulatory notification |
| Uncertain whether risk exists | **Hold and investigate on a clock** | Ambiguous complaint or borderline result | QC with a defined maximum decision window |

The fourth row is the one plants handle worst. "We're looking into it" with no deadline is how a withdrawal becomes a recall. Set a maximum decision window — for example four hours for a safety-adjacent complaint — and name the person who must decide within it.

## The mock recall drill

Traceability is a claim until you time it. Run this quarterly, on a different product each time, and never announce which batch you will pick.

1. **Pick a real batch dispatched 7–20 days ago** — Old enough that people have moved on, recent enough that the product may still be in the market. Do not pick a convenient batch.
2. **Trace backward** — Customer invoice → finished batch → every raw material and packaging lot issued → incoming QC readings → supplier and supplier's lot reference.
3. **Trace forward** — Those lots → every other batch that consumed them, including via rework → every dispatch → every customer and consignee.
4. **Quantify exposure** — Produced, dispatched, in your warehouse, at distributors, and estimated already consumed. Four numbers, on one page.
5. **Draft the actual notification** — Customer name, contact, invoices, batch numbers, quantity, dispatch date, instruction. If you cannot produce this list, you do not have traceability — you have records.
6. **Record every break and time it** — Every phone call, register lookup or estimate is a broken link. Log the total elapsed time; under four hours is a pass for a single-plant SME.
7. **Assign corrective actions with dates** — One owner and one date per break. Re-run in 90 days on a different product and compare times.

> **TIP**
>
> Keep the drill output. A dated file of mock recall reports with elapsed times and corrective actions is one of the most persuasive documents you can put in front of an auditor, a large customer's vendor-approval team, or an export buyer. It demonstrates a working system rather than a written policy.

## Records to retain, and for how long

- **Batch manufacturing record** per batch: recipe version, materials and lots issued, process parameters, output, by-product, rework, rejection with reasons, operator and shift.
- **Incoming QC records** per supplier lot, including rejected and conditionally accepted consignments with rate adjustments.
- **Finished-goods QC and release records**, with the name of the person who released the batch.
- **Dispatch records with batch allocation** per invoice line, plus vehicle and e-way bill reference.
- **Cleaning, sanitation and calibration logs** for the equipment used in the batch — these are what an investigation asks for second.
- **Complaint register** with batch lookup, response time and corrective action closure.
- **Retention period:** follow your applicable regulatory requirement, and as a practical rule keep records for at least shelf life plus a safety margin. Verify current requirements with FSSAI or your certification standard, since retention rules differ by product category and scheme.

## How this looks when the chain is in one system

The reason plants fail the drill is almost never absent records. It is records living in six places — a reception register, a QC notebook, a production diary, a stock register, an invoice book and a Tally company — with no shared key between them.

**The shared key**

```
Supplier lot → material issue → production batch → FG batch → dispatch line → invoice → customer
```
One identifier chain. Every document references the previous one, so the trace is a query rather than an investigation.

This is what naffo.tech's manufacturing chain implements: incoming QC recorded against the supplier lot before put-away, FEFO-driven material issue tied to a specific batch, batch records carrying by-product, rework and reason-coded rejection, finished-goods QC release, batch stock with manufacturing and expiry dates, and batch allocation on dispatch lines that flows into the GST invoice and e-way bill. The mock recall then becomes two screens instead of two days.

Related: [the full 14-stage food ERP workflow](/blog/ideal-erp-workflow-food-manufacturing), and [how to test a vendor's traceability in a demo](/blog/best-erp-food-manufacturing-india).

## The five failures that show up in almost every first drill

1. **Merged intake.** A whole day's milk from twelve farmers or two tankers recorded as one lot, so backward tracing stops at "14 July intake".
2. **QC in a separate book.** Results exist but carry no lot reference, so they cannot be attached to the batch under investigation.
3. **Rework untracked.** Batch B contains material from batch A with no record, so forward exposure is understated.
4. **Dispatch without batch allocation.** The invoice says 40 crates; nothing says which batch, so exposure becomes the whole week.
5. **Distributor tier invisible.** You know the distributor received it, and nothing about where it went next. Agree in your distributor contract that they will provide onward dispatch details within a stated time on request.

Fix these five and most plants move from "we could probably work it out in a couple of days" to a timed, evidenced four-hour capability — which is also, incidentally, the thing that gets you approved as a vendor by large institutional buyers.

## Run a bidirectional mock recall drill

1. **Pick a real dispatched batch at random** — Choose a batch dispatched 7–20 days ago. Do not pick a convenient one, and do not warn the team which batch you will use.
2. **Trace backward to supplier lots** — From the customer invoice, identify the finished batch, then every raw-material and packaging lot issued to it, with the incoming QC results for each.
3. **Trace forward to all customers** — From those supplier lots, list every other production batch that consumed them, and every customer and dispatch that received output from those batches.
4. **Quantify exposure** — Total quantity produced, quantity dispatched, quantity still in your warehouse, quantity at distributors, and quantity likely already consumed.
5. **Build the notification list** — Customer name, contact, invoice numbers, batch numbers, quantities and dispatch dates — the actual list you would send.
6. **Time it and record the breaks** — Note every point where you had to phone someone, open a register or guess. Each is a broken link to fix before the next drill.
7. **Close out with corrective actions** — Assign each break to an owner with a date, and re-run the drill in 90 days on a different product.

## Frequently asked questions

### What is one-up, one-down traceability?

It is the requirement to know your immediate supplier and immediate customer for every consignment — one step up and one step down your supply chain. It is the regulatory floor rather than an operational capability. A real incident needs bidirectional, multi-hop tracing: backward from a complaint to the supplier lot for root cause, and forward from that lot to every affected customer for exposure.

### How long should a mock recall take?

For a single-plant SME with the seven data links captured in one system, under four hours end to end — including quantifying exposure and producing the actual customer notification list. If it takes days, the failure is almost always missing batch allocation at dispatch or QC records that carry no lot reference, not missing records overall.

### What is the difference between a withdrawal and a recall?

A withdrawal removes product that has not reached consumers, typically for a quality or labelling issue with no safety implication. A recall retrieves product that may already have reached consumers because of a potential safety risk, and generally carries regulatory notification obligations. Agree the thresholds and decision-makers for each in advance, including a maximum decision window for ambiguous cases.

### How do you keep traceability through rework?

Record rework as a traced input, not as an adjustment. When output from batch A is reworked into batch B, batch B's record must list batch A as a consumed input so that forward tracing from a suspect lot picks up both. Untracked rework is the most common reason a forward trace understates recall scope, and it is invisible until a drill exposes it.

### How long must food manufacturing batch records be retained?

Retention depends on your product category, regulator and any certification scheme you hold, so verify the current requirement with FSSAI or your certification body. As a practical operating rule, retain batch manufacturing records, QC results and dispatch records for at least the product's shelf life plus a safety margin, and keep mock recall reports indefinitely as evidence of a working system.

### Can traceability work if we sell through distributors?

Partly — you can trace to the distributor, but not beyond unless they cooperate. Put an obligation in the distributor agreement to provide onward dispatch details within a stated time on request, and include the distributor tier in your mock recall drill. Plants that skip this discover during a real incident that their trace ends at the warehouse door.

## References

- [FSSAI — food recall guidance and regulations](https://www.fssai.gov.in/)
- [Codex Alimentarius — principles for traceability in food inspection and certification](https://www.fao.org/fao-who-codexalimentarius/en/)

## Related articles

- https://naffo.tech/blog/ideal-erp-workflow-food-manufacturing
- https://naffo.tech/blog/best-erp-food-manufacturing-india
- https://naffo.tech/blog/reduce-wastage-food-factory

---

Published by naffo.tech, an all-in-one business management and manufacturing ERP platform for Indian SMEs — GST compliance, invoicing, inventory, batch manufacturing, yield and wastage control, and double-entry accounting in one system. https://naffo.tech

Markdown source: https://naffo.tech/blog/batch-traceability-recall-dairy-food-plant/markdown