Key takeaways
The deadline moved, which is why a lot of traceability projects stalled last year. It did not go away.
FSMA 204, the FDA’s Food Traceability Rule, requires anyone who manufactures, processes, packs or holds a food on the Food Traceability List to assign traceability lot codes, capture specific data at defined points in the process, and produce the records electronically within 24 hours of an FDA request. Enforcement now starts on July 20, 2028.
For a processing plant, the work is not paperwork. It is knowing exactly which input lots went into which finished lot, on every batch, without relying on someone writing it on a sheet. That is a line data problem, and it is the reason this is worth starting well before 2028.
Where the Rule Stands
The Food Traceability Final Rule was published in November 2022 with a compliance date of January 20, 2026. In March 2025 the FDA announced a 30-month extension, publishing the proposed rule in the Federal Register in August 2025. In November 2025, Congress directed the agency not to enforce the rule before July 20, 2028 through the Continuing Appropriations Act of 2026, and the FDA has said it intends to comply.
The legal position is worth stating precisely, because it affects how you plan. The extension of the compliance date was proposed rather than finalized, while the non-enforcement direction from Congress is binding. The requirements themselves did not change at all. Only the date the FDA can enforce them did.
There is also evidence the extra time is needed. In readiness exercises run with industry, a minority of participants managed to carry the required lot code correctly across every step the rule covers. Most of the gap is in handoffs between systems and trading partners, not in intent.
Does It Apply to Your Plant?
The trigger is the product, not the size of the business. If you handle a food on the Food Traceability List, you are in scope unless a specific exemption applies. The list covers items such as leafy greens, fresh-cut produce, tomatoes, cucumbers, melons, peppers, herbs, sprouts, tropical tree fruits, shell eggs, nut butters, soft cheeses, finfish, crustaceans, bivalve molluscs and ready-to-eat deli salads.
Two points catch processors out. Foods that contain a listed ingredient can remain in scope even when the finished product is not itself on the list, so the question is what goes into the batch, not just what comes out of it. And exemption from the federal rule does not mean exemption from the requirement, because customers who are covered will push the same data requirements up the chain through their supply agreements.
What the Rule Actually Requires
- A written traceability plan. How you assign lot codes, who is responsible, and how records are kept and retrieved.
- Traceability lot codes. A code assigned at defined points, which then travels with the product.
- Key data elements at critical tracking events. Specific information captured at each defined event in the supply chain.
- Records within 24 hours. An electronic, sortable spreadsheet of the relevant records on FDA request.
The rule does not mandate any particular technology. In practice, the 24-hour sortable requirement and the need to exchange data with trading partners make paper batch records and disconnected spreadsheets very hard to sustain.
The Events That Matter Inside a Plant
Seven critical tracking events run from harvesting through to receiving. A processing plant typically deals with three of them.
| Event | What It Covers | What You Have to Be Able to Show |
|---|---|---|
| Receiving | Taking in raw materials and ingredients on the list | The lot code received, the supplier, quantity, date, and where it went in your plant |
| Transformation | Manufacturing, processing or changing the food | Which input lot codes went into which new lot code, the quantity, and the date and location |
| Shipping | Sending product to the next party | The lot code shipped, the quantity, the recipient, the date, and the reference to the transformation record |
Transformation Is the Hard One
Receiving and shipping are documentation problems that most plants can already handle. Transformation is different, because it is where many input lots become one output lot and the link between them has to be exact.
Think about a normal production day. A blend uses three lots of one ingredient because the first tote ran out mid-batch. A minor ingredient is charged from a partially used bag opened yesterday. Rework from the previous shift goes back into the mix. A bulk silo is topped up between batches. Each of those events changes which input lots are inside the finished product, and none of them are reliably captured by a batch sheet filled in at the end of the run.
When an investigator asks which finished lots contain a specific supplier lot, the answer has to come back in hours, and it has to be defensible. That is the test worth designing for, rather than the paperwork itself.
Where Manual Records Break
What to Automate Now
You do not need a new plant. You need the data to be captured where the material actually moves, rather than reconstructed later. Four points on a typical line do most of the work.
What Good Looks Like on the Floor
A plant that is ready does not look dramatically different from one that is not. The difference is in when data is captured and by whom.
At receiving, the supplier lot is scanned into the system as the pallet comes off the truck, and the storage location is recorded against it. At the line, the operator scans or the system reads the lot on each container as it is charged, and the weighment is logged automatically. The batch record builds itself as the batch runs, including anything added late. The finished lot code is generated by the same system and printed on the pack, the case and the pallet label.
Nothing there requires a rewrite of your operation. It requires the capture points to exist where material actually changes hands, which is usually a mix of scanners, load cells, line controls and a decision about who owns the data.
The Cost Question
Traceability work rarely gets approved on compliance alone, because compliance spend competes badly against capacity spend. The argument that tends to win is recall exposure.
A plant that can isolate affected lots in hours recalls a narrow slice of production. A plant that cannot has to recall by date range, which usually means far more product, more customer disruption and a longer investigation. The same records also shorten customer audits, speed up complaint investigations and give quality teams real batch genealogy for yield work.
If you are already planning an automation project for capacity reasons, adding the data capture at the same time is a fraction of the cost of retrofitting it later as a separate exercise.
The Retailer Deadline Has Already Passed
For plants supplying major retailers, the federal date is not the one that matters. Large grocery chains have been rolling out their own traceability requirements ahead of the FDA, including advance shipping notices carrying the required data elements, standardized pallet identifiers and case-level barcodes. Some of those requirements took effect in 2025 and are already backed by chargebacks.
This is the practical reason not to treat 2028 as the planning date. If you supply or want to supply national retail, the data requirement is commercial before it is regulatory, and it is being enforced through purchase orders rather than inspections.
Working With Trading Partners
Most of the failures in the FDA’s readiness testing were at handoffs, not inside plants. Your lot code has to arrive with the goods you receive and leave with the goods you ship, in a format the next party can actually use.
Three conversations are worth having now. Ask suppliers of listed ingredients how they will send lot data and in what format. Ask customers what they will require, and whether they have already set a standard. And agree with both sides what happens when a shipment arrives without the data, because that exception will occur and someone has to own it.
A 24-Month Plan
- Map your products against the list. Include products that contain listed ingredients, not just finished items on the list.
- Write the traceability plan. It is a requirement in its own right, and writing it exposes the gaps.
- Trace one product end to end on paper. Pick a real batch and try to answer the question an investigator would ask. Time how long it takes.
- Fix the transformation record first. This is where most plants fail, and where automation pays back beyond compliance.
- Standardize coding and labels. Agree formats with customers now rather than after they mandate them.
- Test the 24-hour response. Run a mock trace with real data and measure it, then repeat annually.
“Preparing for FSMA 204 requires more than purchasing traceability software. Manufacturers need connected equipment and reliable data capture at every critical production stage.”
See it in action
Mistakes to Avoid
Where Cybernetik Fits
Cybernetik builds the processing and packaging systems where this data is created, supporting US plants through Cybernetik Inc in Summerville, South Carolina, with more than 6,000 installations worldwide since 1989. Traceability is easier when the line is designed to produce the record, not to have one written about it.
We do not provide regulatory advice or certify compliance. Work with your food safety team or a qualified consultant on the plan itself. Our part is making sure the equipment produces records you can rely on.