What the FDA Food Traceability Rule Requires, and What to Automate Before 2028

If you make, process, pack, or hold a food on the FDA's Food Traceability List, your deadline to comply with the Food Traceability Rule (FSMA Section 204) moved to July 20, 2028. For a Chicago food or beverage maker, that is not a reason to stop. It is a reason to fix the records now, while there is still room to test and train. Illinois has the third-largest food manufacturing workforce in the country, about 98,222 workers, and the Chicago metro ranks third among large metros, so many local processors handle listed foods and will owe these records (Trace One analysis of BLS data).

The useful answer to "what should we do about FSMA 204 now" is narrow: get your lot codes and supplier data clean at receiving, decide which events your plant actually performs, and automate the record-keeping that would otherwise collapse during a traceback. You do not need to buy a dedicated traceability platform this quarter. Below is a map of the records the rule asks for, applied to one processor's receiving, transformation, and shipping, and then what to automate first.

What changed: the deadline, not the work

The rule itself did not get easier. FDA proposed a 30-month extension in August 2025, and in November 2025 the Continuing Appropriations Act of 2026 directed FDA not to enforce the rule before July 20, 2028; FDA has said it intends to comply (Barley Snyder). The extension does not change the rule's substantive requirements (LIDD), and the original compliance date had been January 20, 2026 (Manufacturing Dive).

See the operating problems Clairvance helps food and beverage producers work through.

FDA is also still working on the hardest part. In early 2026 it opened a stakeholder-engagement effort, including quarterly listening sessions with the Partnership for Food Traceability on lot-level tracking and implementation problems, and issued a question-and-answer guidance covering farms, restaurants, retail, intracompany shipments, and commingling (Food Safety Magazine). Treat that as a signal to build a records foundation that can flex, not a rigid system wired to one reading of the rule.

Does the rule even apply to your plant?

It applies only if you handle a food on FDA's Food Traceability List. That list includes foods such as fresh leafy greens, tomatoes, shell eggs, crustaceans, and ready-to-eat deli salads (Manufacturing Dive). Many products are not on the list, and exemptions exist. FDA, for example, finalized an exemption for Grade A cottage cheese on the Interstate Milk Shippers list, though those facilities still keep records of the immediate previous source and immediate subsequent recipient (Food Safety Magazine). Check your own products against the current FDA list before you spend a dollar; that one screen decides the scope of everything below.

What the rule actually asks you to record

The rule rests on two ideas: critical tracking events and key data elements. A critical tracking event is a point where listed food moves or changes, such as harvesting, packing, shipping, receiving, and transformation (making or processing a food, or commingling, repacking, or relabeling it). For each event you perform, you record specific KDEs and link them to a traceability lot code (LIDD). For a shipping event, for instance, those elements include the traceability lot code, the quantity and unit of measure, a product description, and location descriptions for where the food came from and where it went (Manufacturing Dive).

Two obligations make clean data non-negotiable. You must keep a written traceability plan that describes how you keep these records and who is responsible for them, and you must be able to give records to FDA within 24 hours of a request, or within a reasonable time FDA agrees to (LIDD; Barley Snyder). The rule lets you keep paper or electronic records (Manufacturing Dive), but a 24-hour clock during an outbreak investigation is exactly where paper fails.

A capture map for one processor's three events

Illustrative example: take a Chicago processor that buys listed produce, turns it into a ready-to-eat deli salad, and ships it to distributors. It performs three critical tracking events, so its map has three rows. This is a method for organizing the work, not a compliance guarantee.

The real output of the map is the link column. A traceback asks you to connect a shipped lot back to the exact inbound lots it came from. If transformation never records which input lots went into which finished lot, you cannot answer in 24 hours, no matter how clean receiving is.

What to automate first, and what to leave to a person

Automate the data foundation before you automate anything clever. This ordering is our recommended method, not a rule requirement.

1. Capture the inbound lot code and supplier data at receiving, ideally by scanning the supplier's label into your ERP or warehouse system so the code is entered once and never rekeyed. This is the cheapest fix and the one most plants get wrong.
2. Link inputs to outputs at transformation, in the batch record or ERP, so a finished lot can name its inputs automatically. This is the hard, high-value step.
3. Carry the lot code onto shipping documents so it travels to the distributor without a clerk retyping it.

Leave judgment to people: resolving a lot that arrives without a code, deciding whether two inputs were genuinely commingled, and signing the traceability plan. A review queue is not a finished system; name who works it and what happens when the source system is down. And configure what you already own first. An ERP or warehouse system you run today can often hold these data elements and lot links before you license a separate traceability product.

What the extension does not settle

Because FDA is still refining lot-level expectations through its 2026 engagement, the safe move is a foundation you can adjust: consistent lot coding, supplier data captured at the door, and input-to-output links recorded at the batch. Starting now buys time to test the data, train the line, and course-correct before 2028, which is the real point of the extra runway (LIDD). Waiting until 2028 to design any of this is how a plant ends up rekeying years of lot codes under a 24-hour deadline.