In March 2025, the FDA proposed a 30-month extension to the compliance deadline for the Food Traceability Final Rule, moving it from January 20, 2026 to July 20, 2028. Congress reinforced the extension through the Continuing Appropriations Act of 2026, directing FDA not to enforce the rule before that date.
For many operators, the news arrived as relief. For the operators who watch food safety carefully, it arrived as opportunity. The rule itself did not change. The Key Data Elements (KDEs), Critical Tracking Events (CTEs), Traceability Lot Codes (TLCs), and 24-hour record retrieval requirements are all still coming. Multi-unit food service operations that use the extra runway to build durable traceability systems will be in a far better position than those who pause and pick it up in 2027.
This article walks through what the rule requires of food service operators, who is and isn’t covered, and the practical work that should already be underway.
What the Rule Actually Requires
FSMA Section 204 establishes additional recordkeeping requirements for any business that manufactures, processes, packs, or holds a food on the Food Traceability List (FTL). The list focuses on higher-risk foods that are most often implicated in foodborne illness outbreaks, including:
Soft and semi-soft cheeses
Shell eggs
Fresh leafy greens, tomatoes, cucumbers, and herbs
Fresh-cut fruits and vegetables
Nut butters
Certain finfish, crustaceans, and mollusks
Ready-to-eat deli salads (refrigerated)
For each FTL food, covered entities must capture specific Key Data Elements at each Critical Tracking Event in the food’s supply chain journey, link those KDEs to a Traceability Lot Code, maintain a written Traceability Plan, and provide records to the FDA within 24 hours of a request.
Who Is Covered, and Who Isn’t
For food service, the question of who is covered is more nuanced than the headline suggests. Per the National Restaurant Association’s guidance and recent industry analysis, restaurants and retail food establishments (RFEs) that serve food directly to consumers have lighter obligations than upstream supply chain entities. They generally don’t need to assign new TLCs. They do still need to keep records of FTL foods received, including the Traceability Lot Code, food description, quantity, and previous source.
Operations most likely to face the full weight of the rule include:
Central kitchens or commissaries preparing food for multiple locations
Restaurants distributing food to other businesses, institutions, or third parties
Hybrid operations that also manufacture packaged products for wholesale or retail
Catering operations supplying institutional clients
Two key exemptions matter for food service:
The small-operator exemption: establishments with an average annual food sales volume of $250,000 or less (3-year rolling average, inflation-adjusted) are exempt from the rule.
The electronic spreadsheet threshold: establishments with average annual food sales of $1,000,000 or less are still subject to recordkeeping requirements but are not required to provide records to FDA in an electronic, sortable spreadsheet format.
Operators above $1 million in annual food sales handling FTL foods should assume they will need an electronic, sortable system capable of producing records on demand.
Critical Tracking Events and Key Data Elements
CTEs are defined supply chain moments where data must be captured. For food service operators, the relevant events are typically receiving and, in some cases, transformation (when an FTL food is processed into a different form) and shipping (when food is sent to other locations or institutions).
Required KDEs at receiving include:
Traceability Lot Code
Food description
Quantity and unit of measure
Date of receipt
Location identifier of the immediate previous source
Reference document type and number
These elements need to be linked together so the entire chain can be reconstructed quickly during a recall or outbreak investigation.
What the 2028 Extension Doesn’t Change
It is worth being explicit: the substance of the rule did not change. The 24-hour rule still applies. The KDEs and CTEs still apply. The Food Traceability Plan is still required. As of February 2026, the FDA granted a specific exemption for cottage cheese via Federal Register notice, but the broader FTL is intact.
What the extension changes is the runway. Operators now have time to do this work properly: assess current systems, engage suppliers, pilot new processes, train staff, and harden procedures before enforcement begins.
What Operators Should Be Doing in 2026
For multi-unit restaurant operators and food service companies, the practical work falls into five buckets:
Inventory the menu. Identify every FTL food currently used across all units, including ingredients in prepared items.
Map the supply chain. Document every supplier and distributor that provides FTL foods. Confirm each supplier’s plan to capture and pass through KDEs.
Draft the Traceability Plan. A written plan is required, must be kept for at least two years, and must be updated as practices change. It needs to describe how records are maintained, how FTL foods are identified on the menu, and who owns the plan internally.
Stand up the recordkeeping system. Operators above the $1M threshold should be evaluating digital systems now. Paper-based receiving logs will not produce a sortable electronic spreadsheet on a 24-hour clock during an active recall.
Train and rehearse. Staff at receiving, in central kitchens, and in management need to know what to capture, where it lives, and how to retrieve it. Mock recalls against FTL foods are the fastest way to find gaps.
Why Starting Now Still Matters
Operators that wait until 2028 will be implementing under deadline pressure. Operators that build now will use the extra two years to fix data quality, integrate suppliers, and treat traceability as an operational asset. Inspection and recordkeeping platforms like InspectU help multi-unit food service operators standardize how receiving data, supplier documentation, and food safety records are captured at each location, so the documentation needed for FSMA 204 is generated as part of normal operations rather than reconstructed under deadline.
The deadline moved. The work didn’t. The operators who recognize the difference will be the ones the FDA never has to chase.