The FDA’s Food Traceability Rule, commonly known as FSMA 204, now has a compliance date of July 20, 2028 rather than January 2026. The new date gives food manufacturers more time to do the work; but it does not make the underlying recall problem less urgent.
When a supplier flags a specific raw-material lot, the immediate question is not whether a manufacturer has an ingredient list. It is: where did that lot go? Which formulations used it? Which batches were made from those formulations? Which plants made them? What product is still in the supply chain, and where?
Those questions determine whether a company can isolate a problem quickly or has to start pulling purchasing records, batch logs, formulation files and spreadsheets to work it out.
The cost of uncertainty
Industry research is often cited to show the direct cost of a food recall, before lost sales and reputational damage are included. As per GS1 US in 2025 (https://www.gs1us.org/industries-and-insights/media-center/press-releases/food-safety-recall-survey), some 59% of Americans said they would be hesitant to purchase the same product or brand again after a food recall; 60% said they had avoided an entire food category following a recall, while 85% believed recalls protect public health and safety.
The precise number will vary widely by product, distribution footprint, customer relationships and the nature of the event. The operational point is more durable. A recall gets more expensive when a company cannot establish its scope quickly.
The same is true of the commercial impact. Frequently cited Harris Interactive research found that consumers often change their buying behaviour after a recall, sometimes temporarily, sometimes permanently, and sometimes across a manufacturer’s wider portfolio. The study is dated, but the premise remains familiar to food brands: removing product is only part of the job. Customers, regulators and internal teams also need to trust that the company understands what happened and has contained it.
That depends on being able to answer one question with evidence: exactly what does this affect?
Ingredient visibility is not lot-level traceability
Most food companies can tell you what ingredients are in a product. Ingredient lists, specifications and formulation records exist for that reason. But an ingredient list does not answer a recall question by itself.
It can tell you that a product contains soy lecithin. It cannot tell you which formulations used a supplier lot that was later flagged, which batches used those formulations, where those batches were made or which customer shipments may be affected.
That requires a connected chain: raw-material lot to formulation, formulation to production batch, and production batch to finished product and distribution records.
When the chain is fragmented across purchasing records, batch logs, formulation files, quality systems and spreadsheets, recall scoping becomes a research project. Teams pull reports, compare identifiers, search for prior versions and rely on experienced employees to explain how one record relates to another.
That work slows containment, customer communication and product-disposition decisions. It can also widen the practical scope of an event. If a team cannot establish precisely which batches are affected, it may need to hold or investigate a broader population while it works out the facts.
What FSMA 204 makes visible
FSMA 204 applies additional traceability recordkeeping requirements to foods on the FDA’s Food Traceability List. It identifies seven critical tracking events: harvesting, cooling, initial packing, first land-based receiving, shipping, receiving and transformation.
At those events, covered entities must maintain defined key data elements. Traceability lot codes are assigned at specified points, including initial packing, first land-based receiving from a fishing vessel and transformation. The applicable lot code then appears in records that support subsequent critical tracking events.
The operational challenge reaches well beyond logistics. A manufacturer cannot answer a lot-level recall question from shipping records alone.
The information needed to scope an incident is created upstream, in the product and manufacturing record:
- The formulation or bill of materials that defines what goes into a product
- The specification that defines applicable requirements
- The record linking a specific raw-material lot to a manufacturing batch
- The quality and release information associated with that batch
- The distribution record showing where finished product went
A recall procedure can be well designed and still struggle if those records are disconnected. Logistics may be responsible for product withdrawal and customer notification, but it cannot create the lot-to-batch relationship after the incident has begun.
The work belongs upstream
For manufacturers, recall readiness is often described as a supply-chain or compliance responsibility. Both labels are incomplete. The records needed to answer a recall question are created across formulation, quality, manufacturing and distribution.
The goal is not to replace recall procedures with a software project, but to ensure the procedure begins with usable information.
A manufacturer should be able to move from a flagged raw-material lot to the relevant formulations, batches and customer-facing product without asking people to reconcile records under pressure. It should be able to explain the relationship between those records without depending on a single employee who knows where the last version of a file is stored.
That is why FSMA 204 should not be treated as a 2028 filing deadline. It is a prompt to examine whether the lot-to-batch chain exists in a form the business can use when time matters.
Use the runway
The 30-month extension gives covered companies more time to coordinate traceability practices across complex supply chains. That matters. Suppliers, co-manufacturers, customers and internal sites do not necessarily use the same systems or data conventions.
But the extension does not reduce the exposure that prompted the rule. A supplier notice, contamination concern or customer complaint will still require a lot-level answer before July 2028.
The companies that know, before an incident, how a raw-material lot connects to formulations and finished batches will make faster, better-bounded containment decisions when one occurs. The companies that postpone the work will still face the same question when the next supplier notice arrives:
What, exactly, does this affect?
