Harvest Lot Traceability
Harvest Lot Traceability connects documented harvest origin to later lot records—without treating supplier statements as direct observations or assuming quantities that were never recorded.

On this page · 6 sections
How does Harvest Lot Traceability apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01Meaning and documented boundary
Harvest Lot Traceability is the practice of linking a recorded harvest origin to the food initially packed from it and to later lot relationships supported by records. This food-focused definition distinguishes the origin a supplier reports from events the packhouse observes and relationships later records establish.
- Supplied evidence: a grower’s ticket or linked harvest record identifies the farm, field or growing area, and harvest date. Record those details as supplier-reported unless there is separate evidence of independent verification.
- Observed evidence: a packhouse documents its own receipt count or packing event. Observing those events does not mean it observed where or when the food was harvested.
02Harvest and cooling information are different handoffs
For harvesting and cooling before initial packing that are subject to § 1.1325, the retained records and required handoff are not identical. This table summarizes the produce information; it is not an aquaculture checklist.
| Event | Records to keep | Information to provide to the initial packer |
|---|---|---|
| Harvesting — § 1.1325(a) | Immediate subsequent recipient’s location description, excluding a transporter; commodity and variety if applicable; quantity and unit; farm location description; grower’s field or growing-area name, or an equally precise harvest-location identifier; harvest date; reference-document type and number. | The recipient, food, quantity, farm, field-or-equivalent and harvest-date information, plus the harvester’s business name and phone number. Paragraph (a)(2) does not include reference-document type and number in its required handoff. |
| Cooling before initial packing — § 1.1325(b) | Immediate subsequent recipient’s location description, excluding a transporter; commodity and variety if applicable; quantity and unit; cooling location description and date; harvest farm location description; reference-document type and number. | The recipient, food, quantity, cooling-location/date and farm information. Paragraph (b)(2) does not include reference-document type and number in its required handoff. |
Both handoffs may reach the initial packer directly or through the supply chain, in electronic, paper or other written form. Cooling information does not substitute for the separate harvest-origin information.
03Initial packing, lot codes and the exempt-supplier branch
Section 1.1310 defines initial packing as packing a raw agricultural commodity, other than food obtained from a fishing vessel, for the first time. For covered initial packing, § 1.1320(a) requires the initial packer to assign a traceability lot code (TLC). A TLC uniquely identifies a traceability lot within the records of its code source.
A supplier or grower code is not automatically that TLC. Treat the upstream identifier and the initial packer’s TLC assignment as distinct facts, and preserve their documented relationship rather than assuming the codes are interchangeable.
Section 1.1330(a) requires information linked to the traceability lot, covering origin, receipt, applicable cooling, the assigned TLC, packed-food identity and quantity, initial-packing location and date, and reference-document type and number. Its 16 numbered entries include conditional and aquaculture items—not 16 universally mandatory produce fields.
When food is received from a person to whom Subpart S does not apply, § 1.1330(c) provides a different, 10-entry branch. It still requires received-food identity, receipt date and quantity/unit, the supplier’s location description, assigned TLC, packed-product description and quantity/unit, initial-packing location and any applicable code-source reference, packing date, and reference-document type and number. This is not a waiver of all records.
The additional sprouts branch in § 1.1330(b) is outside the cucumber example below. This definition does not determine any supplier’s exemption status; a missing field entry is not evidence of exemption.
04Recorded identity is not inferred quantity allocation
Under § 1.1310, repacking can be transformation when the output is a food on the Food Traceability List; initial packing and preceding activities are excluded from that definition. Section 1.1320 requires TLC assignment on transformation. Shipping unchanged food generally keeps the existing TLC: paragraph (b) prohibits a new code for other activities such as shipping, except as otherwise specified in the subpart.
As an evidence practice, distinguish a run-level association from a supported input-to-output link. A record listing growers for a repacking run does not prove that every output received food from every grower. Input and output totals also do not establish each grower’s precise contribution to each output. Do not invent equal or proportional allocations; describe allocation as unestablished unless records support it.
05Worked comparison: the ticket omits the field
This fictional comparison uses fresh cucumbers and stipulates applicability of the harvesting requirements and ordinary initial-packing branch. FDA’s Food Traceability List includes all varieties of fresh cucumbers; the “fresh” designation excludes previously frozen forms.
| Available evidence | What the packhouse can establish | What it cannot conclude |
|---|---|---|
| A ticket identifies the farm, harvest date, 40 bins and supplier code G-17. A packhouse count confirms 40 bins. No field or equally precise harvest-location information is available. | The farm and harvest date are supplier-reported. The receipt quantity is supported by the packhouse count. | Field-level origin remains unestablished. Neither the count nor G-17 supplies the field-or-equivalent information required by § 1.1330(a)(5). |
| The same records, plus a linked grower supplement naming its field East 2. | Field origin is now documented as grower-supplied information linked to the food. | The supplement is not direct packhouse observation of harvesting and does not establish that every other required record is complete. |
Section 1.1455(f) permits supplementing existing records to include required information. As a recordkeeping practice, preserve the link between the supplement and ticket and identify who supplied the field information. Do not silently fill the gap from a supplier’s usual field or a naming convention.
06Records availability and limits
- FDA access: § 1.1455(c)(1) requires records and information needed to understand them within 24 hours of an authorized FDA request, or a reasonable time FDA agrees to. This is a records-response deadline, not a recall-completion deadline.
- Spreadsheet requests: the electronic sortable spreadsheet requirement applies to specified information requested under § 1.1455(c)(3) in its stated outbreak, recall or other public-health circumstances, subject to the exceptions referenced in paragraph (c)(3)(ii). It is not the required format for every record or every request.
- Retention: § 1.1455(d) generally requires retention for two years from creation or receipt of the records, except as otherwise specified in the subpart.
- Electronic records: § 1.1455(e) provides a qualified exemption from Part 11. Records satisfying Subpart S that are also required under other applicable statutory provisions or regulations remain subject to Part 11 if not otherwise exempt.
Source boundary: the legal discussion uses the supplied text of §§ 1.1310, 1.1320, 1.1325, 1.1330 and 1.1455, current through October 23, 2026. The FDA list and status excerpts were fetched October 27, 2026. The update date is not a claim that the legal text was current through October 27. Applicability is stipulated for the example, not established for every grower or farm.
Frequently asked questions
Q.What can a packhouse establish when the grower ticket omits the field name?+
It can distinguish supplier-reported farm and harvest details from its own receipt observations. A ticket omission does not prove that all field evidence is absent: a linked harvest record or grower supplement may supply it. Where § 1.1330(a)(5) applies, the record needs the grower’s field or growing-area name, or an equally precise harvest-location identifier. A receipt count or supplier code alone cannot establish that origin.
Q.Is a supplier lot code automatically a traceability lot code?+
No. An upstream code is not automatically the TLC for the relevant traceability lot. For covered initial packing, the initial packer assigns the TLC. Preserve the relationship between the supplier identifier and that assignment rather than treating the labels as interchangeable.
Q.Does repacking prove every output received a precisely allocated amount from each grower?+
No. A run-level association establishes only the relationship actually recorded. It does not prove every grower contributed to every output, and total input/output quantities do not justify precise per-output shares. Keep unsupported allocations explicitly unestablished.
Primary sources
- 21 CFR § 1.1310 — Definitions
- 21 CFR § 1.1320 — Traceability lot code assignment
- 21 CFR § 1.1325 — Harvesting and cooling records
- 21 CFR § 1.1330 — Initial-packing records
- 21 CFR § 1.1455 — Records maintenance and availability
- FDA Food Traceability List — fresh cucumbers entry and fresh-food note
- FDA Food Traceability Rule — compliance date and enforcement status
Further reading
Want to see how Harvest Lot Traceability could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
