The FSMA 204 food traceability rule's original compliance date was January 20, 2026. FDA has proposed moving the compliance date to July 20, 2028, and Congress directed it not to enforce the rule before then; FDA says it will comply. That's how FDA's own page described it when I read it on September 30, 2026. The rule itself hasn't changed: if you make, pack or hold foods on the Food Traceability List, the same records will be required, and your buyers may ask for them before FDA does.
The short version
- Original compliance date: January 20, 2026. Now: no enforcement before July 20, 2028.
- The requirements are the same. Only the date moved.
- FDA's proposed extension hasn't been published as a final rule in the Federal Register as of September 30, 2026; the 2028 date comes from FDA's proposal and Congress's direction.
- Use the time: find your listed foods, map your receiving, making and shipping, and get lot codes flowing with suppliers.
- TaroStack keeps those records as you work, so 2028 isn't a project. More below.
How the date got here
From FDA's pages and the Federal Register, read September 30, 2026:
| Date | What happened |
|---|---|
| Sep 23, 2020 | FDA proposes the rule |
| Nov 21, 2022 | Final rule published, with a compliance date of January 20, 2026 |
| Mar 20, 2025 | FDA announces it intends to extend the compliance date by 30 months (FDA) |
| Aug 7, 2025 | FDA's proposed rule to extend it to July 20, 2028 is published (Federal Register) |
| After that | The Continuing Appropriations, Agriculture, Legislative Branch, Military Construction and Veterans Affairs, and Extensions Act of 2026 directs FDA not to enforce the rule before July 20, 2028; FDA says it intends to comply |
| Feb 20, 2026 | FDA grants an exemption for certain Grade "A" cottage cheese, and publishes draft questions-and-answers guidance |
| May 28, 2026 | FDA announces a public meeting on lot-level traceability, with a discussion paper on possible flexibilities (Federal Register) |
In its proposal, FDA said the extension "does not amend" the rule's requirements, and that industry needed more time because the rule depends on accurate data passing between supply chain partners (FDA).
So the honest way to say it is the way FDA does: proposed, and not enforced before July 20, 2028. "It was extended" is close, but if a buyer or an auditor asks, quote FDA's page and its date, and read it again before you rely on it.
This is general information, not legal advice; FDA's own pages have the last word.
What the rule asks for, unchanged
If you manufacture, process, pack or hold a food on FDA's Food Traceability List, or a food made with one that's still in that form, the rule asks you to:
- Keep records of key data elements for each critical tracking event you perform: for a maker, receiving, transformation (making) and shipping.
- Assign a traceability lot code when you transform a food, and pass the lot code and other details to your customers.
- Write a traceability plan: how you keep the records, how you identify listed foods, how you assign lot codes, and who to contact.
- Provide the records to FDA within 24 hours of a request, as an electronic sortable spreadsheet in an outbreak or recall unless you're exempt from that format.
- Keep the records for two years.
There are exemptions, including for small farms and small retail food establishments and restaurants, covered in food traceability list exemptions. Several of them depend on sales thresholds adjusted for inflation, and FDA's inflation page says it intends to post those values for the traceability rule in a future update (FDA).
What to do with the extra time
The work is the same in 2026 as in 2028, and it's easier done in a quiet month than a rushed one.
- List the foods you handle that are on the Food Traceability List, including ingredients like fresh herbs, peppers or tomatoes that stay fresh in what you make.
- Write down the events you perform: what you receive, what you make from it, what you ship.
- Start recording lot codes at receiving and on every batch, now, for everything. It's the habit the rule depends on.
- Ask your suppliers whether they'll send traceability lot codes with deliveries, and how.
- Ask your big customers what they want and when. A retailer or distributor can ask for these records before FDA enforces them, and the buyer is the one who stops ordering.
- Run a practice trace once. The mock recall and traceability exercise is a way to do it.
The records themselves, with a template in Excel, are in the food traceability Excel template.
Where this stops working
The deadline was never the hard part. The hard part is that the records only work if they're kept every day: every delivery's lot code captured at the door, every batch noting which lots went in, every shipment noting which lot went out. On paper or in spreadsheets, that's a daily habit across several people, and the first time anyone checks it is the day FDA or a buyer asks, when the gaps are too late to fill.
How TaroStack does it
TaroStack keeps the records the rule asks for as a side effect of running the kitchen, so July 2028 isn't a project you start in June. Deliveries are received as lots, with the supplier's code or your own, and scanning a GS1-128 case label fills in the lot and the use-by date. Recording a batch takes ingredients from the lots that expire first and notes which lots it used. Shipping puts the lot on the order. Every list exports to CSV, which opens as a spreadsheet you can sort.
When someone asks, the recall report walks any lot to the batches it went into and the customers who received them, and timed, logged traceability drills show a buyer that it works. TaroStack keeps the records; it doesn't make anybody compliant, and it doesn't fill in FDA's forms for you.
Lots and recalls are on every plan, from $49 a month, and recording batches, which is where the transformation records come from, is on Standard at $99. The first 30 days are free. If you'd like a hand setting up, ask, and we'll do it with you.
