KEY TAKEAWAYS • A recall can only be as narrow as your records. In early 2026 a frozen-foods processor’s recall grew from 3.4 million pounds to nearly 37 million pounds across 16 products and five brands, covering production from October 2024 through February 2026, after glass contamination was traced to a carrot ingredient. • BRCGS requires a traceability test in both directions with a quantity reconciliation, and expects it inside four hours — including traceability for rework. • In FSSC 22000’s first year on Version 6, Traceability System was the second most common major nonconformity and appeared among the most common critical findings. • Kroger required suppliers to send an EDI 856 Advance Ship Notice with lot data and matching pallet barcodes by June 30, 2025 — for all food products, not just the Food Traceability List, and well ahead of the federal date. • Bulk and commingled ingredients defeat loose lot definitions, and processors who compensate by declaring very large lots are pre-writing the size of their next recall.

 

Traceability Is Not a Document. It Is a Chain of Links.

Most processors can produce a traceability procedure. Far fewer can produce the links.

Lot traceability means knowing, for one specific batch, which supplier lots went into it, what quantity of each, what came out, how the output was labeled, where it was stored and exactly which customers received which portion. Miss one of those links and the chain does not weaken — it breaks, and everything downstream of the break becomes suspect.

That distinction decides how much product you destroy when something goes wrong.

Your Recall Is Only as Small as Your Lot

Consider a real 2026 sequence, documented in USDA FSIS recall notices.

On February 19, 2026, a frozen-foods processor recalled approximately 3,370,530 pounds of frozen chicken fried rice products that might contain glass, produced between September 8 and November 17, 2025. On March 3 the recall expanded by another 33,617,045 pounds — a combined total of roughly 36,987,575 pounds — across 16 products under five brand names, produced between October 21, 2024 and February 26, 2026. The cause: the establishment determined that a vegetable ingredient, specifically carrots, was the likely source of the glass, and that ingredient had reached the additional products. A further update clarified that products with the listed lot numbers were subject to recall regardless of best-by date.[1][2]

One ingredient. Eleven times the original volume. Sixteen months of production.

No software prevents a supplier from shipping contaminated carrots. What lot-level records determine is how precisely you can answer the next question: exactly which finished goods contained that ingredient lot? The tighter that answer, the smaller the recall. When the answer is fuzzy, the only defensible scope is everything that might have contained it.

Lot Genealogy Is the Whole Job

The technical term for the chain is lot genealogy: input lots linked to output lots, with quantities on both sides, at every transformation.

FSMA 204 makes this explicit. At the transformation critical tracking event, a processor must assign a new traceability lot code and link the input lot codes to it, recording product descriptions and quantities for inputs and outputs plus a reference document tying them together. Records must be provided to FDA within 24 hours of a request, in an electronic sortable spreadsheet when asked. Compliance is required by July 20, 2028 after a 30-month extension from the original January 2026 date.[3][4]

Industry guidance from the Institute of Food Technologists describes why processed foods make this harder than it sounds: a mid-sized processor may run dozens of formulas tailored to different customers, often across multiple co-manufacturers, and typically juggles three parallel code systems at once — the supplier’s lot codes on incoming materials, an internal code for intermediates and work in process, and the finished-goods code the customer sees. Traceability is only real when those three are connected in records, and when the new production code is recorded against the receiving code.[5]

Three code systems, connected by hand, on paper, at shift change. That is where chains break.

Bulk, Rework and Commingling: The Hard Cases

Two everyday practices quietly widen recall scope.

Bulk ingredients. Silos and tanks holding flour, oil, milk, sugar or grain are rarely emptied completely, so multiple supplier lots coexist in the same vessel. Researchers studying this problem note that because current practice often cannot describe what a given portion actually contains, firms compensate by defining very large lots — for example, everything produced over a whole period.[6] That is a rational workaround and an expensive one: it sets your minimum recall size in advance.

Rework. Product held back and reintroduced into a later batch carries its parent lots with it. BRCGS explicitly requires traceability to be maintained for rework.[7] If rework is logged as “added rework” with no source lot, every batch it touched inherits the uncertainty.

Neither problem is solved by a better procedure document. Both are solved by recording the identity and quantity of what actually went into the vessel, at the time it went in.

What Auditors Actually Test

Third-party audit schemes stopped accepting traceability as a claim some time ago.

BRCGS Clause 3.9 is a fundamental requirement: trace raw material lots, including primary packaging, from suppliers through all stages of processing and dispatch to customers — and in the reverse direction. It requires unambiguous identification for raw materials, work in process, part-used materials, finished goods and materials under investigation, a routine traceability test covering product groups with a mass-balance quantity check, traceability maintained through rework, and completion within a four-hour expectation.[7] SQF requires a documented, trained annual traceability exercise with results presented to senior management; FSSC 22000 requires both traceability and recall programs tested annually; PrimusGFS requires testing every six months.[8]

And processors fail these. In FSSC 22000’s first year under Version 6, Traceability System ranked second among the top 15 major nonconformities and fourth among all nonconformities, with the ISO 22000 traceability clause also appearing among common critical findings.[9]

Mass balance is the part that catches people. Quantities have to reconcile: what you received, what you used, what you produced, what you shipped, what you scrapped. A trace that names lots but cannot account for pounds is a story, not a record.

Your Customers Are Already Ahead of the Deadline

The federal date moved to 2028. Retail requirements did not wait.

Kroger notified suppliers that to support FSMA 204 it would collect traceability information on all food products entering its facilities — a wider scope than the Food Traceability List — and required suppliers to adhere to its EDI 856 Advance Ship Notice guideline, transmit an ASN for every shipment, align logistic-unit requirements to its receiving specification, and certify that palletized barcode labels on the physical freight correspond to the ASN data, with transition complete by June 30, 2025. Kroger uses GS1 Serial Shipping Container Codes to identify logistic units, and where multiple lots of an item share a pallet, each lot must be labeled separately.[10][11] Industry analyses report other national accounts issuing comparable ASN and case-barcode requirements on similar timelines.[12]

Note the operative word: correspond. The lot code on the paperwork has to match the lot code on the freight — not resemble it, not be reconcilable through a lookup someone maintains in a spreadsheet.

Meanwhile the packaging itself is changing. Under GS1’s Sunrise 2027 initiative, retail point-of-sale systems are being upgraded to read 2D barcodes, which can carry batch or lot number and expiration date alongside the GTIN.[13][14] Lot data is moving onto the pack, where it will be read by machines that do not accept “close enough.”

Where Manual Lot Tracking Runs Out

Spreadsheets and paper logs do not fail dramatically. They fail selectively — the one shift where the ingredient lot was not written down, the rework nobody attributed, the pallet relabeled by hand.

Those gaps are invisible until the day you need them, and on that day they are the difference between recalling four lots and recalling sixteen months.

How Lot Intelligence™ Keeps the Chain Intact

Lot Axis is built to capture the links rather than reconstruct them. Scanned receiving that ties each pallet to its supplier lot. Production records that link input lots to output lot codes with quantities on both sides, including rework. Labels printed from live data instead of retyped. Scanned shipping so every customer’s receipt of a specific lot is a record, not a recollection. Forward and backward trace with quantity reconciliation, in minutes.

That is Lot Intelligence™: capture once, at the point of work, and let the audit, the customer’s ASN and the recall all read the same chain.

Test Your Lot Traceability

• ✓ Can you run a forward and backward trace with a mass balance in under four hours?
• ✓ Does every finished-goods lot list its input lots and quantities, including rework?
• ✓ How large is your typical lot — one shift and one line, or one week?
• ✓ Does the lot code on your shipping paperwork always match the code on the freight?
• ✓ For bulk ingredients, can you say which supplier lots were in the vessel during a given run?

Ready to Tighten Your Lot Traceability?

Lot Axis gives food processors lot traceability, production tracking, inventory management, barcode labeling and warehouse scanning in one system — built for FSMA 204 records, GFSI traceability exercises and your customers’ ASN requirements.

Schedule a demonstration and bring one finished product. We will trace it backward to its ingredient lots and forward to its customers, and show you where your current chain has gaps.

Lot Intelligence™ — Label It. Track It. Trace It. Control It.

This article is general information, not legal or regulatory advice. Confirm your obligations under FDA and USDA requirements, your audit scheme’s current issue, and your customers’ supplier specifications.

 

Sources

Paste this list at the end of the published post. Keep it to 6–8 authoritative links. The full research package below stays internal.

1. USDA FSIS — Ajinomoto Foods North America expands recall for chicken and pork fried rice, ramen and shu mai products (March 3, 2026)

https://www.fsis.usda.gov/recalls-alerts/ajinomoto-foods-north-america-inc–expands-recall-chicken-and-pork-fried-rice-ramen/

2. USDA FSIS — original recall notice, February 19, 2026

https://www.fsis.usda.gov/recalls-alerts/ajinomoto-foods-north-america-inc–recalls-chicken-fried-rice-products-due-0

3. FDA — Requirements for Additional Traceability Records for Certain Foods (FSMA 204 final rule)

https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods

4. Food Safety Magazine — FDA traceability rule readiness exercises: coordination matters more than technology (confirms the July 20, 2028 compliance date)

https://www.food-safety.com/articles/11507-fda-traceability-rule-readiness-exercises-reveal-supply-chain-coordination-matters-more-than-technology

5. Institute of Food Technologists — Guidance document on best practices in food traceability (processed foods)

https://www.ift.org/siteassets/ift/4-policy-and-advocacy/docs/information-and-resources/processed.pdf

6. FSSC 22000 — One year of Version 6: top nonconformities and guidance (traceability among the most-cited major findings)

https://www.fssc.com/wp-content/uploads/2025/03/FSSC-22000-Webinar-Presentation-25.03.2025.pdf

7. GS1 US — Sunrise 2027: the transition to 2D barcodes carrying lot and date data

https://www.gs1us.org/industries-and-insights/by-topic/sunrise-2027

8. Journal of Agricultural Engineering — Open problems in traceability: from raw materials to finished food products (bulk mixing and lot size)

https://www.agroengineering.org/jae/article/view/jae.2013.s2.e30