Almost every compliance calendar in the US food industry now shows 20 July 2028 as the FSMA 204 deadline. That date is real, but it is not a compliance date. It is the date before which Congress has told the FDA it may not spend money enforcing the rule.
The compliance date is still 20 January 2026. It passed 229 days ago. No rule has ever changed it.
This is checkable in one query. The proposed extension carries regulation identifier number 0910-ZC21. Ask the Federal Register for every document filed under that RIN and it returns exactly one: the proposed rule of 7 August 2025. There is no final rule. There has been none for 395 days since the proposal published, and 363 days since its comment period closed on 8 September 2025.
We flagged this gap ourselves last month, in our analysis of what the Food Traceability List does and does not cover, where we wrote that we could not find a document closing out whether the proposed rule had been finalised, as distinct from the date being enforced through the appropriations rider. This piece answers that question. It has not been finalised.
Three dates, three different instruments
| Date | What it is | Instrument | Status |
|---|---|---|---|
| 21 November 2022 | Final rule published | 87 FR 70910 | In force |
| 20 January 2023 | Effective date, 60 days after publication | Same final rule | Passed |
| 20 January 2026 | Compliance date, three years after the effective date | Stated in section VI of the final rule’s preamble, not in the codified text | Passed; unchanged |
| 7 August 2025 | Proposal to move the compliance date to 20 July 2028 | 90 FR 38084, RIN 0910-ZC21 | Proposed; never finalised |
| November 2025 | Bar on spending appropriated funds to administer or enforce the rule before 20 July 2028 | Section 780, Pub. L. 119-37 | In force |
The middle row is why a rulemaking was needed at all. FDA did not codify the compliance date in 21 CFR Part 1, Subpart S; it stated it in the preamble to the 2022 final rule. Moving it therefore requires notice-and-comment rulemaking rather than an announcement. FDA started that process and, as of today, has not completed it.
Practical consequence: if your compliance position rests on “the deadline moved”, identify which document you believe moved it. If the answer is the August 2025 proposal, your position rests on a proposal.
What Section 780 actually says
The operative sentence, as quoted by the Safe Food Coalition in its 12 August 2026 letter to congressional leaders, is: “[n]o funds appropriated by this Act may be used to administer or enforce [FDA’s traceability rule] prior to July 20, 2028.” Both bracketed alterations are the coalition’s; the rest is the statutory text as it quotes it.
Four words in that sentence do the work: funds appropriated by this Act. The provision is a spending restriction attached to a particular appropriations act. It does not amend 21 CFR Part 1, Subpart S. It does not repeal the recordkeeping obligations. It does not move the compliance date. It removes FDA’s ability to spend that Act’s money on administering or enforcing the rule.
FDA has described the effect in its own words. In the Federal Register notice announcing its June 2026 public meeting, the agency wrote that the Act “directed FDA not to enforce the Food Traceability Rule prior to that same date of July 20, 2028”, and added: “FDA intends to comply with this Congressional directive.” Not that the compliance date changed. That it will not enforce.
Practical consequence: enforcement discretion is not a safe harbour for anything other than FDA enforcement. Contractual traceability requirements imposed by a customer, state enforcement, and the evidentiary position in private litigation all key off the regulation, not off FDA’s funding.
FDA’s own page says both things
Read the FDA’s Food Traceability Rule page today and one section states: “The original compliance date for all persons subject to the recordkeeping requirements of the Food Traceability Rule was Tuesday, January 20, 2026.” The same passage records that FDA proposed a 30-month extension and that Congress directed non-enforcement.
Scroll down to the “Getting Started” material and the same page says: “The compliance date is January 20, 2026. Start working on this today!”
Both statements are on the page as we read it on 6 September 2026. Neither is wrong. The first describes the enforcement posture; the second describes the regulation. That an agency cannot state its own deadline in one tense on one page is the clearest available evidence that the two have come apart.
The rule is not dormant
The most common reading of the rider is that FSMA 204 is parked until 2028. FDA’s docket says otherwise. Since the compliance date passed, the agency has:
| Date | Action | Federal Register |
|---|---|---|
| 20 February 2026 | Granted an exemption for cottage cheese regulated under the Grade “A” Pasteurized Milk Ordinance, effective immediately | 2026-03362 |
| 20 February 2026 | Issued draft guidance, “Questions and Answers About Requirements for Additional Traceability Records for Certain Foods” | 2026-03363 |
| 28 May 2026 | Announced a public meeting on lot-level traceability and released a discussion paper, comments to docket FDA-2014-N-0053 by 15 July 2026 | 2026-10603 |
| 11 June 2026 | Submitted the rule’s information collection request to OMB for review | 2026-11760 |
An agency does not grant exemptions from a rule it considers suspended, and it does not carry an information collection request to OMB for recordkeeping nobody must keep. Every one of those actions treats Subpart S as operative law.
Practical consequence: the cottage cheese exemption is the tell. Exemptions are only worth granting against a live obligation. If you hold a food that might qualify for a similar carve-out, the exemption route is open now and does not depend on the enforcement question.
The requirement itself is now in play
The August 2025 proposal was explicit about its own scope: “This compliance date extension does not amend, nor do we intend to amend, the requirements of the final rule”.
Section 780 goes further than the proposal did. Beyond the funding bar, it directs FDA to engage quarterly with regulated entities and to “identify and implement, as appropriate, additional flexibilities for satisfying the Food Traceability Rule’s lot-level tracking requirement”, and to give industry recommendations within 180 days of enactment.
Lot-level tracking is not a peripheral feature of FSMA 204. Traceability Lot Codes are the mechanism — the identifier assigned at initial packing or transformation and carried unchanged through the chain. A directive to find flexibilities in lot-level tracking is a directive to reopen the core of the rule.
FDA’s own position, stated in May 2026, is that with most of the quarterly engagements still ahead, “we have not made a decision about the scope of flexibilities that would best address the challenges being faced by regulated entities while still protecting public health and maintaining the benefits of the Food Traceability Rule.”
So the position for a covered entity is: the obligation is in force, enforcement is defunded for roughly two years, and the substance of what compliance requires may change before enforcement resumes. That is three different kinds of uncertainty stacked on one rule.
Practical consequence: systems work that encodes today’s Key Data Elements is safe; systems work that hard-codes today’s lot-code architecture may not be. Build the data model so the traceability lot code is a field you can redefine, not an assumption baked into the schema.
Who in this sector is actually covered
For most of the companies this publication covers, the answer is still no. As we set out in August, neither cultivated meat nor precision-fermented protein appears on the Food Traceability List, and the list is the rule’s entire scope.
The exposure runs through inputs and finished-product categories rather than through the novel ingredient. The FTL covers shell eggs; soft, semi-soft and fresh cheeses; finfish, crustaceans and molluscs; leafy greens; fresh herbs; melons and tropical tree fruits; nut butters; and ready-to-eat deli salads. A hybrid product built on leafy greens, a fermentation-derived ingredient sold into a fresh cheese, or a plant-based product marketed into a listed category can pull an otherwise-uncovered business into scope. Our earlier piece flagged the fresh-cheese boundary specifically as unresolved, and nothing since has resolved it.
The counter-argument
The strongest case for ignoring all of this: FDA has said it will not enforce, the agency has proposed the extension it intends to finalise, and Congress has told it to stand down. In practice, no entity will face an FSMA 204 enforcement action before July 2028, and building to a January 2026 date that nobody is policing wastes capital during a period when capital in this sector is scarce.
That is largely right on the enforcement question and it is why most operators have reprioritised. Two things survive it.
First, the rider is drafted against funds appropriated by one Act. Whether an equivalent restriction carries into subsequent appropriations depends on Congress re-enacting it, and eleven consumer and labour organisations are actively asking Congress not to. The Safe Food Coalition’s August letter is a live attempt to remove the restriction, made against the background of a Cyclospora outbreak the letter puts at nearly 30,000 illnesses and two deaths.
Second, FDA’s enforcement posture governs FDA. It does not govern a customer’s supply agreement, and it does not settle how a court would treat records that a regulation in force required a defendant to keep.
What we could not establish
- The full text of Section 780. We worked from the operative sentence as quoted by the Safe Food Coalition and from FDA’s characterisation of the section in the Federal Register. We did not retrieve the enrolled text of Pub. L. 119-37 itself, so we cannot rule out qualifying language elsewhere in the section that we have not seen.
- Whether the restriction lapses. The provision is drafted against “funds appropriated by this Act”. What happens at the end of that appropriation period is a question of how the next appropriations act is written, and we make no prediction. We are not lawyers, and a covered entity should not treat this article as advice on its own exposure.
- Whether a final rule is imminent. RIN 0910-ZC21 shows one document. We did not find a Unified Agenda entry giving FDA’s projected date for final action, and we do not know whether the rulemaking is being held pending the flexibilities review.
- The 180-day recommendations. Section 780 required FDA to give industry recommendations on lot-level flexibilities within 180 days of enactment. As of May 2026 FDA said it had not decided the scope. We did not establish whether a recommendations document has since been issued.
- The scale of the outbreak. The 30,000-illness and 22,683 figures are the coalition’s own, stated in its August letter. We did not verify them against CDC surveillance data.
What to watch
Whether the final rule ever appears. The cleanest test in this piece. Query the Federal Register for RIN 0910-ZC21. If a final rule appears, the compliance date has legally moved and everything above becomes history. If July 2028 arrives with the proposal still outstanding, the industry will have spent two and a half years planning to a date that no instrument ever set.
What FDA proposes on lot codes. The discussion paper on flexibilities for lot-level tracking is the substantive question. If FDA proposes anything that weakens the carry-unchanged requirement for Traceability Lot Codes, the systems most companies have already built will need rework, and the retailers the coalition names — Kroger, Albertsons, Walmart — will have built ahead of a standard that moved.
Whether the rider is re-enacted. This is the binary that decides whether the gap between obligation and enforcement closes in 2028 or persists. Watch the next agriculture and FDA appropriations text for a successor to Section 780.