Food traceability after the extension proposal: keep the dates separate

FDA announced a proposed 30-month extension on August 6, 2025. The proposal appeared in the Federal Register on August 7 as 90 FR 38084, with comments due September 8. It proposed moving the compliance date from January 20, 2026 to July 20, 2028. The agency’s announcement said the proposal concerned timing and did not amend the rule’s substantive requirements. September planning therefore followed a proposal, not a newly established final extension.

Sources: [1] [3]

The distinction matters. Section 780 is a restriction on the use of specified appropriated funds; it should not be rewritten as if Congress had published FDA’s proposed date amendment as a final rule. FDA’s current page says it intends to comply with the congressional directive. OIRA’s label Final Rule identifies the stage of the action under review, not proof that a final rule has been published. A business making a legal deadline decision needs a current review of the applicable record.

Sources: [4] [2] [5]

The FY2027 continuing appropriations law, enacted September 2, 2026, also carries forward funding under the prior Agriculture/FDA appropriations authority and conditions, subject to its temporary funding limits. This is a funding measure, not publication of the FDA compliance-date amendment.

Sources: [7]

The current-status observations above are dated October 5, 2026. They should not be projected backward into what a September 2025 planner knew, or treated as a permanent statement about future rulemaking. The unresolved future event is final disposition of the pending action. This article does not supply an unverified final-rule publication date or determine a particular business’s compliance deadline.

FDA describes the rule as additional recordkeeping for certain foods on the Food Traceability List, involving key data elements associated with critical tracking events. Current 21 CFR Part 1, Subpart S contains the scope and exemptions as well as shipping and receiving provisions. Applicability depends on the food, activity and circumstances. Assign that evaluation to qualified food-safety or compliance staff before turning a general summary into a requirement for every load.

Sources: [2] [6]

Carrier context is especially important. The regulation defines a transporter separately, and the shipping and receiving provisions refer to the subsequent recipient or previous source other than a transporter. The party physically moving a shipment is therefore not automatically the recipient meant by every recordkeeping provision. A provider may perform additional activities, so neither a blanket exemption nor a blanket duty should be inferred from the word carrier.

Sources: [6]

Choose a representative order from the business’s own process and have the responsible teams walk through it. Identify the product description, quantity and units used at origin, then compare them with what the receiver expects. Locate the source lot identifier where applicable and the shipment reference used to retrieve supporting records. This is a process exercise, not a declaration that those fields form a complete legal checklist for every product.

Ask what happens when the receiver sees a different quantity or an unfamiliar identifier. The useful answer names a contact, a correction process and the authority to decide whether the goods can be accepted or held under the business’s procedures. Do not solve a mismatch by inventing a replacement lot code in a transport note. Preserve the original information and have the responsible source resolve the discrepancy through the agreed process.

A hypothetical distributor may find that its supplier’s information is complete but arrives in a format the receiving team cannot readily connect with the delivery reference. Buying a new system is not the first conclusion supported by that finding. First define the missing link and ask whether the parties can exchange a consistent reference through an accepted channel. Any system decision should follow the actual requirement, the information flow and an assessment by the responsible teams.

A delayed enforcement expectation does not by itself improve the quality of the next handoff. Trading partners can use the planning period to locate missing contacts, clarify reference formats and practice exceptions. Keep that work proportional to the actual business and any applicable requirements. A buyer should not promise that a generic shipment document, tracking portal or temperature record alone satisfies every traceability obligation.

For the transport conversation, share the information the provider needs to perform the accepted movement and identify the records contact for questions beyond that scope. Keep cargo handling, shipment status and regulatory interpretation connected through responsible people, while preserving their different purposes. That approach supports a usable freight plan as the official date-setting process continues.