TL;DR
Recall management is the process of identifying, isolating and retrieving defective product from the supply chain and from customers. The defect determines that a recall happens. It does not determine how large the recall is. Scope is set by what you can prove about where affected material went, and those records were created months earlier at receiving and production.
Key Takeaways: Where lot-level traceability exists, a recall can be contained to specific production runs. Where it does not, regulators and counsel require recalling everything produced in the suspected window. FDA can require electronic traceability records within 24 hours. FSMA 204’s recordkeeping deadline moved to July 2028, but existing traceback authority is already in force. Scope cannot be improved after an incident begins.
What is recall management?
Recall management is the process of identifying, isolating and retrieving defective or non-conforming products from the supply chain and from customers, together with the notification, documentation and regulatory reporting that surrounds it.
It spans several stages: detecting the problem, establishing which product is affected, notifying regulators and customers, retrieving or disposing of the product, documenting the response, and closing out with the authority.
Most organizations discover the gaps in their recall process while they are already inside one. That is the central difficulty of the subject: it is a capability that is only tested under the conditions in which it cannot be built.
Scope is the variable, and it is set in advance
Here is the point that reframes the entire discipline.
The defect determines that a recall occurs. The records determine how much product it covers.
When a problem is found, the question regulators and your own counsel will ask is which product is affected. If you can tie a specific supplier lot to specific production runs, and those runs to specific shipments and customers, the recall covers those runs. If you cannot, the answer defaults to everything produced during the suspected window, because nobody can responsibly certify that the rest is clean.
The cost difference is not marginal. Published analysis describes a manufacturer with robust lot tracking containing a defect to a single production lot of 800 units at a total expense in the low hundreds of thousands, against Consumer Product Safety Commission estimates putting the average consumer product recall at eight to twelve million dollars in direct costs alone.
A recent food industry case illustrates the mechanism rather than the exception. Contamination originated in a single vegetable ingredient. That ingredient had fed sixteen products over sixteen months. The initial recall covered roughly 3.37 million pounds. After one expansion event, total scope reached nearly 37 million pounds.
Nothing about the defect changed between those two figures. What changed was how much product could not be excluded.
Why scope cannot be fixed during the incident
The records that limit a recall are created upstream, in the product and manufacturing record, long before anyone knows a recall is coming.
Three relationships determine scope, and all three are established in ordinary operations:
Inbound lot resolution. Whether a specific supplier lot is tied to specific receiving events, rather than to a date range.
Production-run linkage. Whether that inbound lot can be connected to the specific runs that consumed it. Shared ingredient streams across multiple lines or sites widen scope quickly where this link is weak.
Outbound distribution linkage. Whether finished lots can be tied to the specific shipments and customers that received them.
As one supply chain analysis puts it, logistics may be responsible for product withdrawal and customer notification, but it cannot create the lot-to-batch relationship after the incident has begun.
This is also why ingredient visibility is not traceability. Knowing that a product contains a given ingredient tells you nothing about which supplier lot of it went into which production run. The first is a formulation fact. The second is a records fact, and only the second limits a recall.
The 24-hour problem
The second structural difficulty is timing.
Under FDA rules, the agency can require electronic traceability records within 24 hours during a recall or outbreak investigation. That is a request for a sortable electronic record, not for a filing cabinet.
The question worth asking internally is a specific one. If a regulator called tonight and asked for the key data on one lot as it moved through receiving, transformation and shipping, would that come back as one linked record, or would somebody have to reconcile a supplier email, a shipping spreadsheet and whatever the ERP happened to capture, and hope the lot numbers on all three actually match?
Where the answer is reconciliation, the trace takes days rather than hours, and every hour of uncertainty is an hour in which scope cannot be narrowed and product keeps moving.
What FSMA 204 changes, and what it does not
The FDA’s Food Traceability Rule, generally known as FSMA 204, applies additional recordkeeping requirements to foods on the Food Traceability List. It requires a traceability lot code that persists through the supply chain until the food is transformed, and specific key data elements recorded at each critical tracking event: receiving, transformation and shipping.
Two points are commonly confused.
The compliance deadline moved. Originally set for January 2026, the recordkeeping requirement now sits at July 20, 2028.
FDA’s existing traceback authority is unaffected. It sits outside FSMA 204 entirely and is already in force, as is the agency’s mandatory recall authority under FSMA where there is reasonable probability of serious adverse health consequences.
There is also a scope limitation worth understanding. FSMA 204 covers foods on the Food Traceability List. In the ingredient case described above, the implicated vegetable was not on that list, so compliance with the rule would not have reduced that recall. The capability the rule is designed to force, a lot code that survives through production, limits recall scope whether or not a given item is covered by the rule.
Treating FSMA 204 as a 2028 compliance project rather than a present operational capability is therefore a misreading of what it is for.
Where the work actually goes
Look at what executing a trace requires and the character is unmistakable.
Someone retrieves the receiving records for the implicated supplier lot. Someone retrieves the production records for every run that consumed it, which requires the formulation or bill of materials to establish which products could have. Someone matches lot codes across those records, where the codes were entered by different people in different systems at different times. Someone retrieves distribution records to establish which customers received which finished lots. Someone assembles that into a single sortable record for the regulator. And someone drafts the notifications, which cannot go out until scope is settled.
Almost none of this is quality judgment. It is document retrieval and cross-referencing across systems that were never designed to reconcile, performed against a 24-hour clock, usually at night, by people who do this rarely.
One transposed lot number, one incomplete entry, one record held only in an email, and the chain breaks. When it breaks, scope widens, because the only defensible answer to an unanswerable question is to include more product.
Where automation fits
The constraint is reconciling records across systems rather than deciding what to recall, and that is where automation changes the outcome.
Automation that can read unstructured documents and reason about their contents can connect the chain continuously rather than reconstructing it under pressure: matching supplier lot codes from certificates and receiving documents to production records, linking those runs through the formulation to finished lots, and tying finished lots to the shipments and customers that received them.
Doing this as a standing capability rather than an incident response has a specific effect. It means the trace exists before the recall does, which is the only point at which scope can actually be influenced.
Because the output is submitted to a regulator and relied on to certify which product is unaffected, every link needs to be traceable to the document that evidences it. A lot relationship nobody can substantiate will not narrow a recall, because counsel will not let you rely on it.
To be clear about scope, Kognitos is not a traceability platform or a food safety management system. It does not assign lot codes, run quality programs, or replace the systems that hold production records. What it addresses is the reconciliation between them: reading receiving documents, production records, certificates and distribution data, and maintaining the linked chain with a record of how each connection was established.
For related material, see our guides on quality management systems, certificate of analysis, production planning, master data management, and supply chain automation use cases. To see how deterministic AI maintains linked records across systems with a full audit trail, book a demo or try the platform.
Getting started
Two exercises, and the first is deliberately harder than the standard version.
Run a mock trace starting from an ingredient, not a finished product. Most mock recalls begin with a SKU and work outward, which tests the easier direction. Start with one inbound supplier lot and establish every finished product it entered and every customer that received them. That is the direction a real contamination event runs, and it is the direction that determines scope.
Time it, and record where it stalled. The specific record that could not be produced, or the lot code that did not match across systems, is the gap that will widen your next recall. Most organizations have the capability to find this out on a quiet afternoon and choose instead to find out during an incident.
