Change record: FDA proposes a 30-month Food Traceability Rule compliance-date extension
FDA proposed moving the compliance date from January 20, 2026 to July 20, 2028 while stating that the proposal would not amend the substantive requirements.
What changed
FDA proposed moving the compliance date from January 20, 2026 to July 20, 2028 while stating that the proposal would not amend the substantive requirements.
This entry preserves the event separately from maintained provider and capability conclusions. A rule, announcement, release, enforcement record, or market transaction can be material before enough evidence exists to revise a company classification or comparison.
Operating consequence
Vendor and buyer readiness claims need to preserve proposed status, the old and proposed dates, and the unchanged record requirements instead of labeling the rule delayed without context.
Teams should identify which records, populations, systems, transactions, jurisdictions, products, or decisions fall within the change. Then assign an accountable owner, response date, evidence requirement, and disposition. Broad reassessment is not always necessary, but a material event deserves a documented decision.
Capabilities to revisit
Critical Tracking Event And Key Data Element Capture
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for critical tracking event and key data element capture.
Traceability Lot Code And Lot Genealogy
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for traceability lot code and lot genealogy.
Electronic Sortable Spreadsheet And Authority Response
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for electronic sortable spreadsheet and authority response.
Questions for operating teams
- Which exact population and effective date does the source establish?
- Does the change alter authority, policy, content, workflow, integration, evidence, or only market positioning?
- What customer-controlled interpretation, configuration, or process remains outside a provider's responsibility?
- What test case would show whether the operational consequence has reached production?
- What record will close, defer, or supersede this review?
Evidence boundary
The source class is Official proposed-rule update. It establishes only the statements supported by the linked record and does not, by itself, establish implementation depth, market-wide availability, transaction-specific applicability, independent efficacy, or a universal buyer conclusion.