← Guides

What records does FSMA 204 require, and how do production records feed them?

By Savi C., Co-Founder · Published Nov 16, 2026

How the rule is built

Subpart S applies to foods on the Food Traceability List, which FDA publishes and can update. The list includes foods such as certain fresh produce, shell eggs, nut butters, some cheeses, several kinds of seafood and ready-to-eat deli salads. Section 1.1305 sets out exemptions and partial exemptions, so check the current list and exemptions against your own products.

The rule defines a critical tracking event as an event in a food’s supply chain, such as harvesting, cooling, initial packing, first land-based receiving, shipping, receiving or transformation. A key data element is information associated with a critical tracking event for which a record must be kept. The traceability lot code ties them together: a new one may be assigned only at initial packing, first land-based receiving or transformation (1.1320), not when you simply ship or receive.

FDA has moved the compliance date for this rule, so confirm the current date on FDA’s FSMA 204 page rather than relying on older material.

Transformation key data elements and where they usually come from

Section 1.1350(a) lists what a manufacturer must record when it transforms a listed food. Most of it already exists in the batch or production record.

Key data element (1.1350)

Traceability lot code of each input food

Typical production record source

Material issue or dispensing record, copied from the receiving record

Key data element (1.1350)

Product description of each input food

Typical production record source

Material issue record and approved bill of materials

Key data element (1.1350)

Quantity and unit of measure used from each input lot

Typical production record source

Weigh and dispense entries, with partial lots recorded separately

Key data element (1.1350)

New traceability lot code for the output food

Typical production record source

Batch or production lot number assigned at the start of the run

Key data element (1.1350)

Location of transformation (traceability lot code source)

Typical production record source

Site and line identifiers on the production record header

Key data element (1.1350)

Date transformation was completed

Typical production record source

Final production step or packaging completion date

Key data element (1.1350)

Product description, quantity and unit of measure of the output

Typical production record source

Yield and packaging reconciliation

Key data element (1.1350)

Reference document type and number

Typical production record source

The production record itself or a work order, cited by number

Checks that keep production records traceability-ready

Inputs

  • Every listed-food input carries the traceability lot code from its receiving record, not an internal code with no link back
  • Receiving records hold all eight elements in 1.1345, including the traceability lot code source
  • Quantities used are recorded per input lot, so a recall can be scoped to the lots actually consumed

Transformation

  • A new traceability lot code is assigned at transformation, and the record links it to every input lot code
  • Output quantity reconciles against inputs within the expected yield, and variances are explained
  • Completion date and location recorded in a consistent format across lines and sites

Shipping and retrieval

  • Shipping records hold the elements in 1.1340, and elements one to seven reach the immediate subsequent recipient
  • The traceability plan describes record format and location, how lot codes are assigned, and a named point of contact (1.1315)
  • A mock request can be answered within 24 hours, including as an electronic sortable spreadsheet where 1.1455 requires one
  • Records kept for 2 years, and superseded traceability plans kept for 2 years after each update

How Litewave fits

Traceability failures in mock recalls usually start in the production record: a missing input lot code, a transcription error, or quantities that do not reconcile. Litewave reads paper or electronic records, checks every entry against your master record and specifications, and shows QA only the exceptions, each linked to the page it came from. Our published results come from pharmaceutical manufacturing, not from food, and we do not claim food customers or results. For the food safety side of the same records, see How should HACCP and CCP monitoring records be reviewed under FSMA?

Questions we get asked

Does FSMA 204 apply to every food?

No. It applies to foods on FDA’s Food Traceability List, with the exemptions and partial exemptions in 21 CFR 1.1305. Foods not on the list remain subject to the general records requirements that applied before.

Can we assign a new lot code when we ship or receive a food?

No. Under 21 CFR 1.1320, a traceability lot code is assigned at initial packing of a raw agricultural commodity, at first land-based receiving of food from a fishing vessel, or at transformation. Other activities must carry the existing code forward.

Can traceability records be on paper?

Yes. Section 1.1455 allows original paper or electronic records or true copies. But in an outbreak, recall or other public health threat, FDA can ask for the information as an electronic sortable spreadsheet within 24 hours, unless a size-based exemption applies.

Sources

  1. 21 CFR 1.1305, Exemptions from food traceability requirements (eCFR)
  2. 21 CFR 1.1310, Food traceability definitions (eCFR)
  3. 21 CFR 1.1315, Traceability plan (eCFR)
  4. 21 CFR 1.1320, Assigning traceability lot codes (eCFR)
  5. 21 CFR 1.1340, Records of receiving (eCFR)
  6. 21 CFR 1.1345, Records of shipping (eCFR)
  7. 21 CFR 1.1350, Records of transformation (eCFR)
  8. 21 CFR 1.1455, Maintaining and making records available (eCFR)
  9. FDA, Food Traceability List