FSMA 204 Food Traceability Rule
The compliance date is July 20, 2028, not January 2026. Here is what the rule actually requires, and where the traceability data is most likely to go missing before it ever reaches your system.
- Compliance date
- July 20, 2028
- Original date
- January 20, 2026
- Rule finalized
- November 2022
- Basis for the delay
- Continuing Appropriations Act of 2026
- Requirements changed?
- No
What changed, and what did not
The FSMA 204 compliance date is July 20, 2028. FDA finalized the Food Traceability Rule in November 2022 with a compliance date of January 20, 2026. In March 2025 the agency proposed a 30-month extension, citing the burden on smaller operators. Congress then made non-enforcement binding through the Continuing Appropriations Act of 2026, directing FDA not to enforce the rule before July 20, 2028.
The requirements did not move with the date. The Food Traceability List, the Critical Tracking Events, and the Key Data Elements are all the same as they were in the 2022 final rule. Readiness work done against the January 2026 date still counts.
This matters when you are researching. A lot of published guidance, including vendor content that ranks well, still asserts that the rule took effect in January 2026. Check the date on anything you read, and check it against FDA's own rule page and the Federal Register extension notice.
Two years is less runway than it sounds if the fix involves changing how documents arrive from several hundred suppliers.
The six Critical Tracking Events
A Critical Tracking Event is a point where the rule requires you to create a record. Which Key Data Elements you record depends on which CTE you are performing, so a receiving distributor captures a different set than a packing house.
| Event | Who performs it | What to know |
|---|---|---|
| Harvesting | Growers and harvesters of FTL produce | Records the field or growing area, the date, and the quantity harvested. No TLC yet at this stage. |
| Cooling | Anyone cooling an FTL raw agricultural commodity before initial packing | Links the cooling location and date back to the harvest record. |
| Initial packing | Packers and packing houses | This is where the Traceability Lot Code is assigned. Everything downstream inherits it. |
| Shipping | Anyone shipping an FTL food to another entity | The CTE GS1 US maps onto the EDI 856 ASN. Carries the TLC, quantity, location, and ship date to the receiver. |
| Receiving | Distributors, wholesalers, retailers, restaurants | Where most OrderSync customers sit. You record what arrived, its TLC, from whom, where, and when. |
| Transformation | Processors, repackers, commissaries, anyone changing the food | New TLCs are assigned to the output and linked back to every input lot consumed. |
What a receiver has to capture
If you are a distributor, wholesaler, or retailer, Receiving is your CTE. For each traceability lot you take in, you record the Traceability Lot Code, the quantity and unit of measure, the product description, the immediate previous source, the location where you received it, the date you received it, and a reference to the document that establishes the shipment.
None of those fields are exotic. Six of the seven already appear on an ordinary invoice or packing list. The one that usually does not is the Traceability Lot Code, and that is the one the whole rule hangs on.
The harder problem is format. FDA expects records produced in an electronically sortable format within 24 hours of a request. A folder of scanned PDFs is not electronically sortable, and neither is a spreadsheet someone rebuilds by hand after the request arrives.
Where OrderSync fits
OrderSync is not a traceability system, and we will not pretend otherwise. The ledger that holds your lot history and answers an FDA trace-back belongs in your food safety platform or your ERP.
We sit one step upstream, on the problem nobody else wants: the suppliers who are never going to send you an EDI 856. Every distributor has them. They are often the small growers and specialty producers handling exactly the FTL items in scope, and they trade in PDFs, emailed order forms, and faxes. Their paperwork is where traceability data goes to die, because the only way into your system is somebody retyping it.
OrderSync reads those inbound documents into structured line-level records with a full audit trail of what arrived, what we extracted, what a human corrected, and when it synced. Which fields get captured is configurable per trading partner. For partners who do send EDI, the 856 advance ship notice is the transaction GS1 US maps the Shipping CTE onto, and you can inspect a real one with our free EDI Inspector.
If most of your inbound FTL volume already arrives as a clean 856, your traceability vendor has you covered and you do not need us. If a meaningful share of it arrives as paperwork, that gap is the part of FSMA 204 readiness that does not solve itself.
Book My Intro CallFrequently asked questions
July 20, 2028. The Food Traceability Rule was finalized in November 2022 with a compliance date of January 20, 2026. FDA proposed a 30-month extension in March 2025, and Congress made non-enforcement binding through the Continuing Appropriations Act of 2026, which directed FDA not to enforce the rule before July 20, 2028. The requirements themselves were not changed by the extension.
No. Only the compliance and enforcement date moved. The Food Traceability List, the Critical Tracking Events, and the Key Data Elements are all unchanged from the November 2022 final rule. Any readiness work done against the original January 2026 date remains valid.
A Traceability Lot Code, or TLC, is the identifier assigned to a specific lot of a food on the Food Traceability List. It is the key that links every Critical Tracking Event together. It is assigned when the food is initially packed, received from a fishing vessel, or transformed, and it must travel with the product through every subsequent handler.
A Critical Tracking Event is a point in the supply chain where FSMA 204 requires you to create a record: harvesting, cooling, initial packing, shipping, receiving, and transformation. Key Data Elements are the specific fields you must record at each of those events. Which KDEs apply depends on which CTE you are performing, so a receiver records a different set than a packer.
No. It applies to foods on the FDA's Food Traceability List, which includes fresh leafy greens, fresh-cut fruits and vegetables, certain cheeses, shell eggs, nut butters, cucumbers, melons, peppers, sprouts, tropical tree fruits, herbs, tomatoes, finfish, crustaceans, and molluscan shellfish. Foods that contain FTL items as ingredients can also be in scope.
Most commonly on paperwork: a PDF invoice, an emailed packing list, a printed bill of lading, sometimes a fax. Someone has to convert that into structured data before your traceability system can hold it and before you can answer an FDA request in an electronically sortable format within 24 hours. Automating that conversion is the practical gap for most distributors, because the suppliers least likely to send an EDI 856 are often the small growers and specialty producers handling exactly the FTL items in scope.
The 856 advance ship notice. GS1 US publishes guidance mapping the FSMA 204 Shipping CTE onto the 856, which makes the ASN the natural vehicle because it already describes the shipment hierarchy down to the pack level. The 850 purchase order and 810 invoice carry reference numbers and quantities, but neither is designed to carry lot-level detail across the pack hierarchy.
The Shipping CTE on an 856
Segment by segment, where the Traceability Lot Code and the shipping KDEs actually sit in an ASN.
KDEs from non-EDI suppliers
What to do about the half of your supplier base that will still be emailing PDFs in 2028.
Grocery EDI guide
The transaction sets, scan-based trading, DSD, and cold chain documentation grocery actually runs on.