Lot
Somewhere on every food package there’s a code most consumers never notice. But when an outbreak hits, that code becomes the most important thing in the building — it’s the thread investigators pull to find where the problem started and where the product went.
Definition
A lot is a defined quantity of food produced, packed, or received under essentially uniform conditions, identified by a unique lot code. In most food contexts, “lot” and “batch” are interchangeable — pick one term and stay consistent.
Key facts
- The lot code on a pack links backward to ingredient lots, production records, and QC results — and forward to distribution records showing who received it.
- One-up-one-down traceability operates at lot level: each business records which lots came in and which lots went out to whom.
- Recall scope lives or dies on lot precision. Sharp lot identity means recalling the affected pallet; fuzzy identity means recalling the month.
- Continuous processes define lots artificially — by time window, shift, or raw-material lot change — because the traceability logic still has to work.
- Regulators on both sides of the Atlantic think in lots: it’s the unit of enforcement, investigation, and recall.
Why it matters
In outbreak investigations, crisp lot coding leads investigators to the source in hours — while blurred lot identity turns a focused recall into a blanket one costing many times more. The lot code is a humble thing: ink on a package. But it’s the thread that ties the entire traceability system together, and when it breaks, everything downstream breaks with it. If your lot definitions wouldn’t survive a 2 a.m. recall, fix them now — calmly, before you need them frantically.
Sources: Codex Alimentarius; FDA; WHO.
Quick reference
| Concept | Detail |
| Lot code | Unique ID on each unit/case |
| Traceability | One-up-one-down at lot level |
| Recall scope | Defined by implicated lots |
| Continuous lines | Lots defined by time or material change |