Batch
Definition
A batch is a defined quantity of product made in one process — or one series of processes — under conditions you can reasonably call uniform. In practice, it’s the unit of identity: the thing you test, trace, hold, release, and recall.
Key facts
- “Batch” and “lot” mean essentially the same thing in food; don’t get tangled up — pick one term and use it consistently.
- Every batch gets a unique code printed on the pack. That code is a thread you can pull: it leads back to the raw-material lots, the production date, the line, the shift, and the QC results.
- Quality checks happen per batch, and batches live or die individually — one batch can sit in hold while the next one ships.
- When a recall comes, the batch code draws the boundary. Precise batch definition is the difference between recalling 2,000 units and 200,000.
- Continuous processes (pasteurizers, flour mills) don’t have natural batches, so you define them: a time window, a silo fill, a raw-material lot change.
Why it matters
Mock recalls succeed or fail on batch discipline alone. The plants that sail through can pull a code off a pack and have the full genealogy — ingredients in, product out — within the hour, identifying every ingredient lot in a finished batch and every finished batch containing an ingredient lot. The ones that struggle invariably have fuzzy batch boundaries: “well, it was sometime Tuesday.” The common failure is rework and partial pallets breaking the chain — companies that pass treat lot coding as a system: label printers, scanner verification, rework tracking, not just ink on a bag. If your batch definition wouldn’t survive a 2 a.m. recall with regulators on the phone, tighten it now.
Quick reference
| Concept | Detail |
| Batch/lot code | Unique identifier on each unit |
| Links to | Raw materials, process records, QC results |
| Recall scope | Defined by batch codes affected |
| Continuous processes | Batches defined by time or vessel |