Lot coding for produce: how to design codes that survive a recall

Rule one: unique, forever

A lot code must never be reused, not across seasons, not across products, not "because the old lot is finished". Two lots sharing a code makes every future trace ambiguous, and an auditor will treat ambiguity as a gap. Enforce uniqueness in whatever system issues the codes rather than relying on habit.

Encode the useful, skip the clever

A good produce lot code answers two questions at a glance: when, and from what. A date-based prefix plus a daily sequence (for example R-260704-02 for the second receival on 4 July 2026) is readable on the dock without a lookup table.

Resist encoding everything, grower, block, variety, grade, into the code itself. Codes that carry too much meaning become long, error-prone to transcribe, and wrong the moment something is re-graded. Keep the code short and let the record behind it carry the detail.

New transformation, new code, kept link

When received fruit is packed, the output is a new lot with a new code, and the critical discipline is recording which input lots fed it. That link is the trace chain. A pack run that consumes three grower lots and produces one packed lot must record all three parents, or a recall stops at the pack line.

Let the system do the numbering

Handwritten codes drift: transposed digits, reused sequences, formats that change mid-season. The reliable pattern is system-issued codes at the moment of receival and packing, printed straight onto carton and pallet labels. Fernable issues date-sequenced codes automatically, enforces uniqueness at the database, and keeps the parent-child links, so the trace chain builds itself while the line runs.