204FSMA 204FDA Food Traceability Rule

The compliance date: why it moved to July 20, 2028

The operative fact for a buyer is short: FDA will not enforce the Food Traceability Rule before July 20, 2028. The path to that date, and what it does and does not change, matters for how you plan.

As at July 12, 2026

The dates, in order

The Food Traceability Rule was finalized in November 2022 with an original compliance date of January 20, 2026. As that date approached, FDA proposed a 30-month extension to July 20, 2028. That proposed rule was published in the Federal Register on August 7, 2025 (document 2025-14967, "Requirements for Additional Traceability Records for Certain Foods: Compliance Date Extension").

Then Congress addressed it directly. Through the FY2026 continuing appropriations and extensions act, Congress directed FDA not to enforce the Food Traceability Rule before July 20, 2028, and FDA has stated it intends to comply with that directive. So the July 2028 non-enforcement date does not rest on the rulemaking alone; it is backed by statute.

That distinction is worth stating plainly, because it is the harder fact. The cleanest way to describe the current position is not "the deadline was moved to 2028" as if the regulation text itself were the only basis. It is: FDA will not enforce the Food Traceability Rule before July 20, 2028, on the basis of the proposed extension plus the congressional non-enforcement directive.

What did not change

The extension is limited to the compliance date. The substantive requirements of the rule are unchanged. The Critical Tracking Events, the Key Data Elements at each event, the traceability plan, the traceability lot code, and the 24-hour records demand all stand as finalized. If you were building toward the January 2026 date, none of that work is wasted; you simply have more runway.

Why later does not mean "wait"

A softer deadline lowers urgency, but it does not change the size of the job, and there are good reasons to build now rather than in 2028.

  • The work is upstream of a date. Assigning a lot-code scheme, wiring capture into receiving and shipping, and getting your supply-chain partners to pass the required data forward are process changes, not paperwork you do the week before. They take iteration.
  • Your records are only as good as your partners' records. If the packer upstream of you does not pass the lot code and the shipping data, your receiving record has a gap you cannot fix alone. Aligning partners takes lead time.
  • A mock records pull tells you the truth. The real test is whether you can produce the required records as an electronic sortable spreadsheet within 24 hours. The first time you try that, you will find gaps. Better to find them with two years of runway than under an FDA request.

Treat the date as a moving fact

Because the extension was still a proposed rule as of August 2025 and the July 2028 floor rests on appropriations, this is a fact that can move again. We re-verify the enforcement date and whether the extension rule has been finalized every quarter and on any FDA constituent update, and we stamp the check date on every page. Confirm the current position against the FDA page before you rely on any date, and see our sources for the primary documents.

Use the runway. Get a role-specific report with your tracking events, per-event record templates, a traceability-plan starter, and a dated action checklist working back from July 20, 2028. Get my report →

Next: Are you exempt?