FDA’s Food Traceability Review Puts Recall Precision and Small-Business Costs in Focus
When a foodborne illness investigation reaches a grocery store or restaurant, knowing the supplier’s name is only the beginning. Investigators need to distinguish one shipment from another, connect it to the place where a traceability code was assigned and follow the food through businesses that may have split cases, combined ingredients or repacked products. The quality of those connections can determine how quickly authorities identify a source and how broadly a recall must reach.
That operational problem sits at the center of the Food and Drug Administration’s latest review of its Food Traceability Rule. The agency’s November 6 public-meeting agenda focused on lot-level tracking and possible implementation flexibilities. A separate October draft would give certain smaller retail food establishments and restaurants relief from enforcement of the rule’s requirements. Neither the meeting nor the draft amounts to a blanket exemption for the food supply chain.
Two comment windows remain relevant. The small-retailer draft guidance asks for comments by November 23, 2026, to ensure consideration before FDA begins finalizing it. Comments for the broader November meeting are due December 6 under a separate docket. The two dockets address related but distinct questions: who should face the additional requirements, and how the information should move.
What a lot code adds to a supplier’s name
The Food Traceability Rule, published in final form on November 21, 2022, establishes additional records for covered businesses that manufacture, process, pack or hold foods on FDA’s Food Traceability List. It is not a universal new recordkeeping system for every grocery item. The list includes categories such as fresh leafy greens, fresh cucumbers and tomatoes, fresh-cut produce, certain cheeses, shell eggs, nut butters and specified seafood, with the rule’s exemptions and category descriptions determining the precise coverage.
At the core are critical tracking events and the key data elements associated with them. Events include harvesting, cooling before initial packing, initial packing, first land-based receiving of food from a fishing vessel, shipping, receiving and transformation.
A traceability lot code links the food to those records. For relevant produce, the code is assigned at initial packing; for food obtained from a fishing vessel, it is assigned by the first land-based receiver; transformation can require a new code. The code generally then stays with the food as it moves through the chain unless transformation occurs. The code’s source identifies the physical location where it was assigned, giving investigators more than a string of letters or numbers to work with.
July 2028 is an enforcement milestone, with an important legal distinction
FDA’s current rule overview distinguishes two actions often compressed into the phrase “deadline extension.” The original compliance date was January 20, 2026. FDA proposed a 30-month extension to July 20, 2028. Subsequently, Congress directed the agency not to enforce the rule before July 20, 2028, and FDA says it intends to follow that direction.
The October draft repeats that distinction. Its discussion of the future small-business policy anticipates that the policy would be in effect when the compliance date is reached and continue as the agency considers longer-term solutions. It does not describe the November 6 meeting as changing the enforcement date, and its status page explicitly says the draft is not for implementation.
Nor does the additional time suspend all existing food-tracing responsibilities. FDA’s frequently asked questions explain that the earlier “one-up, one-back” recordkeeping requirements in a different regulatory subpart remain in effect. The new rule adds a more detailed layer for listed foods. A firm deciding how to use the time before July 2028 must therefore distinguish its existing obligations from the additional system being implemented and from any future enforcement discretion.
Which smaller businesses the October draft would cover
The five-page draft guidance proposes enforcement discretion for all Food Traceability Rule requirements applicable to retail food establishments and restaurants with an average annual monetary value of food sold or provided above $250,000 but no more than $1 million. Both figures must be adjusted for inflation using 2020 as the baseline, and the calculation uses the preceding three years on a rolling basis.
Those are sales or food-value thresholds, not employee counts or profit tests. FDA’s existing explanation of the small-establishment calculation considers all food sold or provided at a single establishment, rather than only foods on the traceability list. It uses an annual average, not the sum of three years of sales.
The rule already fully exempts qualifying establishments at or below the inflation-adjusted $250,000 threshold. Establishments in the next band, above $250,000 through $1 million, already have an exemption from the requirement to provide an electronic sortable spreadsheet and may provide required information in an alternative format. The draft would go further for that band by declining enforcement of all the additional rule’s requirements. Calling it merely a relaxation of spreadsheet formatting would understate the proposal.
FDA says these businesses can face limited staffing and insufficient resources for training and technology even when they exceed the smallest-business exemption. The draft cites estimates that establishments with annual sales under $1 million account for about half of retail food establishments and restaurants but roughly 6 percent of their annual sales. Those figures describe the broader under-$1-million group, including businesses already exempt. They are not a count of establishments newly receiving relief under this draft alone.
What the rule asks of a restaurant, and what it does not
A restaurant covered by the rule generally needs receiving records for listed foods from its suppliers. FDA’s restaurant FAQs explain that it does not have to link incoming lot codes to individual recipes or to the specific dishes sold directly to consumers. Transformation and shipping records are not required for food that a restaurant prepares and sells or sends directly to its customers in that situation.
A central kitchen transforming food and shipping it to another business is different. It functions as a manufacturer or processor for those activities, so the transformation requirements can apply. The broader review includes questions about simplified recordkeeping for retail-kitchen shipments to affiliated stores, but discussion of that idea is not adoption of a new exemption.
There is also no general requirement to put the traceability lot code on the food’s label or packaging. The rule is about maintaining and sharing information, and FDA says paper or electronic records can be used.
The distribution-center problem: precise records versus operational burden
FDA’s May discussion paper on additional flexibilities describes a recurring challenge at distribution centers. Pallets can arrive containing multiple lots, and lots may mix in storage or picking areas. Some operators say identifying each outgoing case’s actual code would require case-by-case scanning that is difficult or costly at their throughput. The paper asks whether alternatives could preserve useful traceability without imposing the same process everywhere.
One option under discussion is a reasonable range of possible lot codes for shipments from distributors to retailers. Another is an inferred code, based on inventory placement, receipt timing and picking practices, accompanied by information about other codes that might have been included. The first explicitly describes a range of possibilities; the second identifies a likely lot while acknowledging uncertainty. Neither should be presented as a finalized regulatory permission in the materials examined here.
The difference has public-health consequences. If a shipment can be narrowed to one actual lot, investigators may be able to separate affected food from unrelated inventory more readily. If a shipment could contain several lots, a precautionary response may need to encompass more food. Conversely, an inference that excludes the actual lot could create a misleadingly narrow search. A workable flexibility therefore needs an honest account of uncertainty as well as an estimate of the labor it saves.
The October Federal Register notice summarizes 26 earlier comments from industry, trade associations and technology partners. Many supported range-based or inferred codes, often with safeguards such as documented practices, validation exercises and keeping the range as small as possible. Some warned of weaker product-specific traceability and unnecessarily broad recalls. Those are the agency’s summaries of prior comments, not a verified account of what participants said at the November 6 meeting.
Broken cases, returns and donated food
Another practical issue arises when a full case becomes individual units, known in distribution as “eaches.” The case may carry information that is not printed on each item. Sending a few units to several customers can separate the physical product from the easiest record of its origin. Returns and reclamations introduce further departures from the straightforward path of a sealed case moving from supplier to store.
FDA’s notice reports support for flexibility around those movements and for clearer treatment of donated food so that recovery of usable food is not discouraged. The public interest cuts in both directions: burdensome processes can make donation harder, while an unclear record can make it harder to find donated food after a safety problem emerges. Describing all charitable food distribution as outside the traceability system would overlook the obligations of other businesses in the chain.
FDA’s FAQ gives a specific example. When listed food is sold to a nonprofit food establishment qualifying for an exemption, that establishment is exempt, but other covered businesses in the supply chain are not automatically exempt. The shipper still has applicable recordkeeping and information-sharing requirements. The nonprofit may voluntarily retain the information it receives. That illustrates why an exemption attaches to a defined entity or activity rather than erasing the entire history of the food.
An FDA exercise found coordination mattered more than the software
A separate FDA traceability-readiness report provides concrete evidence of the implementation challenge. Between March 9 and April 1, 2026, the agency conducted exercises involving 15 volunteer companies across six supply-chain scenarios. The foods included soft-ripened or semi-soft cheese, wild-caught finfish, whole-head and fresh-cut leafy greens, and nut butter. FDA requested traceability information within 24 hours and asked for a traceability plan if one was available.
Most firms responded within the 24-hour window. In at least two instances, retailers or restaurants coordinated with suppliers to submit data covering the full supply chain within that initial period. FDA said that cooperation accelerated the tracing process compared with making successive requests upstream. The report’s broader finding was that agreement among trading partners about what information to capture and share mattered more than the sophistication of their technology.
Speed did not always mean completeness. Only 40 percent of participants’ records captured a properly assigned lot code across every critical tracking event they performed, and 27 percent captured complete code-source information across every such event. Some records identified a cooling facility as the code source even though the firm’s plan said the produce had been packed in the field. A plausible location is not necessarily the correct location for the record investigators need.
These percentages are not national compliance rates. The sample was small, participation was voluntary and the simplified exercises were not mock outbreak investigations. Several scenarios ended without a fully identified code source, including cases where suppliers did not participate or a firm could not definitively identify the immediately preceding supplier. The report identifies practical weaknesses without establishing how common those weaknesses are across the entire industry.
The next decisions will shape how useful the records are
FDA does not endorse a particular commercial technology or data standard for compliance. Its FAQ recognizes that common standards such as GS1 can reduce ambiguity and make exchanges more consistent, while leaving each firm responsible for meeting its obligations. The readiness report also notes that buyers sometimes impose differing requirements that go beyond the rule, forcing suppliers to build customer-specific solutions. Harmonizing those demands could lower costs without removing useful information.
The November 23 deadline concerns the proposed small-retailer enforcement policy under docket FDA-2025-D-6952. The December 6 deadline concerns the broader lot-level meeting under FDA-2014-N-0053. As those discussions continue, the decisive measure will be whether flexibility preserves information that can actually be used under pressure. Fewer forms and faster electronic responses are valuable only if the chain still leads investigators to the right food and the right place.
Comments
Post a Comment