# FSMA 204 Deadline: July 20, 2028, Not January 2026 > The FSMA 204 compliance date moved to July 20, 2028. Here is the full timeline, the statutory basis for the delay, and what did not change when the date did. The FSMA 204 compliance date is July 20, 2028. The Food Traceability Rule was finalized in November 2022 with a January 20, 2026 date. FDA proposed a 30-month extension in March 2025, and Congress made non-enforcement binding through the Continuing Appropriations Act of 2026. The requirements themselves did not change. If you searched for the FSMA 204 deadline and got two different answers, you are not confused. The date moved, and a large amount of published guidance never got updated. Here is the timeline, with sources, and what it means for work you may already have underway. ## The timeline | Date | What happened | | --- | --- | | November 2022 | FDA publishes the final Food Traceability Rule under FSMA Section 204 | | January 20, 2026 | Original compliance date | | March 2025 | FDA announces its intent to extend the compliance date by 30 months | | September 8, 2025 | Public comment period on the proposed extension closes | | November 2025 | Congress passes the Continuing Appropriations Act of 2026, directing FDA not to enforce the rule before July 20, 2028 | | **July 20, 2028** | **Current compliance date** | The important nuance is in that last row. This was not only an agency decision that a later agency could quietly reverse. Congress directed the non-enforcement through appropriations, which is a firmer floor than a proposed rule sitting in comment. ## What did not change The extension moved the date. It did not touch the substance: - The **Food Traceability List** is the same. 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. - The **Critical Tracking Events** are the same six: harvesting, cooling, initial packing, shipping, receiving, and transformation. - The **Key Data Elements** required at each CTE are unchanged. - The **24-hour, electronically sortable** record production requirement is unchanged. If your team did readiness work against the January 2026 date, none of it was wasted. You got two more years to finish it. ## Why so much published guidance is wrong Search results for FSMA 204 are full of pages asserting the rule "went into effect in January 2026." Some are vendor pages that ranked well in 2024 and were never revisited. Some are law firm updates that predate the appropriations act. This matters practically. If you are building a compliance plan off a page that has the wrong date, you may also be reading the wrong things about scope and phase-in. Check the publication or update date on anything you read, and check the deadline against primary sources: - [FDA: FSMA Final Rule on Requirements for Additional Traceability Records for Certain Foods](https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods) - [Federal Register: Compliance Date Extension](https://www.federalregister.gov/documents/2025/08/07/2025-14967/requirements-for-additional-traceability-records-for-certain-foods-compliance-date-extension) We keep a dated status block at the top of our [FSMA 204 compliance guide](/fsma-204) showing when we last verified the deadline against those sources. ## Two years is not as long as it sounds The temptation with a delay is to shelve the project. That works if your traceability gap is a software purchase. It works less well if the gap is in how data reaches you. Ask a narrower question: for the FTL items you handle, what fraction of inbound volume arrives with a usable Traceability Lot Code already in structured form? For most distributors the answer splits sharply. The large suppliers send an [EDI 856 advance ship notice](/guides/edi/856-ship-notice) and the data is there. The small growers and specialty producers send a PDF invoice or an emailed packing list, and the data is there too, just not in a form any system can sort. Closing that second gap means changing something on the supplier side or automating the document side. Both take longer than two years of calendar suggests once you multiply by a few hundred trading partners. We wrote about the practical options in [getting FSMA 204 KDEs from suppliers who do not send EDI](/blog/fsma-204-kde-capture-non-edi-suppliers). ## What to do with the extra time 1. **Inventory your FTL exposure.** Which SKUs you handle are actually on the list. This is usually smaller than people fear and never zero. 2. **Segment suppliers by how their documents arrive.** EDI, PDF, email body, fax, portal download. The split tells you the size of the manual problem. 3. **Confirm who owns the ledger.** Your food safety platform or ERP holds the lot history and answers the FDA request. Decide this before you buy anything else. 4. **Fix the intake, not just the storage.** A traceability system with nothing feeding it cleanly is a place to retype paperwork faster. If you want to see what your inbound documents actually contain today, our [free EDI Inspector](/edi-inspector) parses an 856 and shows you the hierarchy and reference segments in plain language. For the non-EDI side, [multi-format order processing](/multi-format-orders) covers how PDF, email, and CSV orders get normalized into the same structure. ## FAQ ### Is the FSMA 204 deadline definitely July 20, 2028? That is the current date, set by congressional direction through the Continuing Appropriations Act of 2026 and reflected in FDA's extension rulemaking. Deadlines have moved once already, so verify against FDA and the Federal Register before making a budget decision on it. ### Does the extension apply to everyone equally? The extension applies to the compliance date for the rule as a whole. It did not create new tiers or carve-outs. Existing exemptions in the original rule, such as those for certain small producers and farms below specified sales thresholds, are unchanged. ### Should we stop our FSMA 204 project? Pausing a software purchase is defensible. Pausing supplier data work is riskier, because that is the part with a long lead time and it depends on other companies changing their behavior, not just yours.