GenFrontier homeScope a project
Menu
Filed under
Deliver toFood safety, quality, operations and IT leads at food businesses

FSMA 204 food traceability records

The Food Traceability Rule asks for specific records at each step a listed food takes, and for those records to come back fast when FDA asks. We build the capture and the export around the systems you run.

Map your KDEs with the worksheet
solutions / food-traceability
A single apple on a wooden crate slat with a thin red thread tied to its stem, the thread running off the edge of the frame

FDA’s Food Traceability Rule, which implements section 204 of the FDA Food Safety Modernization Act (FSMA), requires additional traceability records for foods on FDA’s Food Traceability List. The hard part is rarely reading the rule. It is that the records are spread across receiving paperwork, ERP lot fields, production sheets and shipping documents, and nobody has tried to pull them together against a clock.

This page explains the records and the software work behind them. It is not legal advice. Whether the rule applies to you, which exemptions you may qualify for and how to comply are questions for your counsel and for FDA’s own guidance.

Where the dates stand

  • FDA’s original compliance date for the rule was January 20, 2026.
  • On August 7, 2025, FDA proposed extending the compliance date by 30 months, to July 20, 2028.
  • Congress then directed FDA, in the Continuing Appropriations, Agriculture, Legislative Branch, Military Construction and Veterans Affairs, and Extensions Act, 2026, not to enforce the Food Traceability Rule before July 20, 2028. FDA says it intends to comply with that directive.

So today, FDA will not enforce the Food Traceability Rule before July 20, 2028, under a congressional directive. As of November 2026, the proposed extension had not been finalized. Ask your customers too: large buyers can set their own supplier timetables.

CTEs, KDEs and traceability lot codes

The first two definitions below are quoted from 21 CFR 1.1310.

  • Critical tracking event (CTE): “an event in the supply chain of a food involving the harvesting, cooling (before initial packing), initial packing of a raw agricultural commodity other than a food obtained from a fishing vessel, first land-based receiving of a food obtained from a fishing vessel, shipping, receiving, or transformation of the food.”
  • Key data element (KDE): “information associated with a critical tracking event for which a record must be maintained and/or provided in accordance with this subpart.”
  • Traceability lot code (TLC): the code that identifies a lot of food in the records. A new code is assigned at initial packing, at first land-based receiving of food from a fishing vessel, and at transformation. At shipping and receiving, the existing code travels with the food, together with the location of the traceability lot code source or a source reference.

The KDEs differ by event. A shortened view of three common ones:

CTE Some of the KDEs required
Receiving Traceability lot code, quantity and unit of measure, product description, immediate previous source, where and when received, traceability lot code source, reference document
Transformation Input lot codes, descriptions and quantities used; the new lot code, where and when transformation was completed, product description, quantity, reference document
Shipping Traceability lot code, quantity and unit of measure, product description, immediate subsequent recipient, where shipped from, date shipped, traceability lot code source, reference document

Full lists for every CTE, with citations, are in the FSMA 204 KDE worksheet.

The 24-hour request

Under 21 CFR 1.1455(c)(3), records must be provided to FDA “within 24 hours (or within some reasonable time to which FDA has agreed) after the request, along with any information needed to understand these records”. When needed during an outbreak, a recall or other threat, the information must be provided in an electronic sortable spreadsheet. Certain small farms and small businesses are exempt from the spreadsheet requirement.

For software, that paragraph sets the design:

  • Records for one lot code must be found together, even when receiving, production and shipping live in different systems.
  • Internal codes must resolve to plain names for locations, suppliers, customers and products. Those names are part of the “information needed to understand these records”.
  • The export must filter by product, lot code and date range, and produce one sortable file.
  • The export must be tested, with a timed mock request, before anyone needs it.

The Food Traceability List

FDA’s list currently covers cheeses other than hard cheeses, shell eggs, nut butters, fresh cucumbers, herbs, fresh and fresh-cut leafy greens, melons, peppers, sprouts, tomatoes, tropical tree fruits, fresh-cut fruits and vegetables, finfish (including smoked finfish), crustaceans, molluscan shellfish (bivalves) and refrigerated ready-to-eat deli salads. The requirements also reach foods that contain a listed food, when the listed food remains in the same form. Under 21 CFR 1.1465(c), a deletion from the list takes effect immediately, and an addition takes effect two years after the Federal Register notice unless the notice says otherwise. In software terms, “on the list” should be an item attribute with an effective date, not a hard-coded assumption.

What we build

  • A listed-food attribute on each item, and a map of the CTEs at each site.
  • Receiving by scan that captures the supplier’s traceability lot code and its source with the receipt, instead of on paper.
  • Lot code assignment at packing or transformation, printed on the case label as a barcode.
  • Transformation records that link every input lot code to the output lot code.
  • Shipping records that pass the lot code and its source to customers in an agreed format, such as an advance ship notice.
  • The sortable spreadsheet export, tested with a timed mock request.

The work sits on top of your ERP and WMS through inventory management software and barcode and RFID labeling, and starts with requirements analysis to find where each KDE lives today.

Example (fictional). A fresh-cut processor makes a salad kit, item EX-SK-210, from romaine, cucumbers and tomatoes, all foods on the list. Each production run is a transformation: three input lot codes from three suppliers become one new lot code. A mock request for one week of the kit shows that input lots were written on the line sheet but entered in the ERP only as item numbers, so the trace stopped at the plant door. The written requirement becomes: “At the start of each run, the line lead scans each input case label. A run cannot close until every input has a traceability lot code. The export lists each output lot code with its input lot codes, suppliers and dates.” The acceptance test is a timed mock request for one output lot code and date range.

Before you start

Fill in the KDE worksheet for one product and one site. Mark which KDEs you already capture, in which system, and which live only on paper. That list is the first input to a Scope and plan engagement, and it is useful on its own in talks with customers, suppliers and counsel.

Scope your project.

Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.