Gerber’s Heavy-Metals Lawsuit Raises the Bar for Ingredient-to-Lot Traceability

A food manufacturer cannot manage a contaminant concern with a certificate stored in one system, laboratory results in another, and shipment history buried in spreadsheets. When a question arises, the business needs to identify which ingredient lots entered which production batches, where the finished goods went, and what evidence supported their release. Anything less turns a targeted quality event into a network-wide search.

That is the operational lesson from Texas’ lawsuit against Gerber. The allegations have not been proven, and supply-chain teams should not treat them as findings of liability. They should treat the dispute as a sharp reminder that food safety controls must be traceable, time-stamped, and executable at lot level—from supplier origin through the customer order.

Allegations become an evidence problem

Supply Chain Dive reports that Texas alleges Nestlé-owned Gerber knowingly sold baby food containing dangerous levels of arsenic and lead while misleading consumers about product safety. Gerber disputes the allegations and says its products meet applicable safety requirements. That distinction matters: a responsible operating analysis can examine control design without presuming the legal outcome.

The regulatory landscape also complicates the task. According to the report, the U.S. Food and Drug Administration has established limits for lead in this context, but not for every heavy metal at issue. It also cites September testing by Consumer Reports that found heavy-metal levels in baby food had declined over time while some products still showed concerning inorganic arsenic levels. A manufacturer therefore may have to reconcile legal limits, internal specifications, customer requirements, evolving scientific guidance, and results produced by different test methods.

This is not an isolated category risk. Reuters reported in 2025 that several manufacturers, including Gerber, had to face nationwide litigation alleging heavy-metal exposure from baby food. Reuters also noted that more than 80 lawsuits followed a 2021 congressional report. Whatever the eventual outcomes, repeated disputes make record integrity a material supply-chain capability rather than a back-office compliance exercise.

Build one traceability chain, not six partial records

The minimum usable chain begins before a truck reaches the receiving dock. Each inbound ingredient lot should carry a unique identifier tied to supplier, farm or processor where available, country and region of origin, purchase order, production date, transport conditions, and the supplier’s certificate of analysis. The receiving event should add arrival time, seal status, quantity, sampling plan, sample identity, laboratory method, and disposition.

That record must continue into manufacturing. Consumption transactions should connect every ingredient lot to each production batch, line, shift, recipe version, processing parameters, packaging-lot code, and finished-goods lot. Rework and blending cannot become blind spots: if material from one batch enters another, the genealogy must retain both directions of the relationship.

Outbound execution completes the chain. Finished-goods lots should be associated with pallet identifiers, warehouse locations, pick confirmations, sales orders, shipment IDs, carriers, delivery destinations, and proof of delivery. With those links intact, a team can answer four questions quickly:

• Which finished lots contain the ingredient under review?
• Which inventory remains under company control?
• Which orders and customers received affected lots?
• Which apparently similar products can remain available because their genealogy is different?

Speed matters, but precision matters just as much. A broad hold protects consumers while facts are uncertain; a precise trace allows the business to narrow that hold safely as evidence improves.

Make quarantine and release rules executable

A specification has little value if a questionable result does not change inventory status. Quarantine rules should automatically block allocation, picking, loading, and shipment when a required certificate is missing, a result exceeds an applicable threshold, sample identity is uncertain, or two tests conflict.

The workflow should distinguish a pending result from a failed result. Pending material stays unavailable until an authorized release. A confirmed failure triggers an investigation and defined escalation. A conflicting result requires a documented resolution protocol—such as retained-sample testing by an approved laboratory—not an informal choice of the more convenient number.

Release authority should be role-based and separated from commercial pressure. The record needs the specification version, result, units, method, laboratory, reviewer, decision time, justification, and any deviation approval. If a threshold changes, the system should preserve the rule that governed the original decision while allowing teams to reassess inventory against the new standard.

These controls should also account for the natural variability of agricultural ingredients. Risk-based sampling may vary by commodity, geography, supplier history, season, and prior results. That flexibility is defensible only when the sampling rule and any exception are visible in the same audit trail.

Turn chain of custody into response capability

When an alert arrives, CXTMS should help translate quality scope into logistics action. A lot-level hold can stop an uncollected load, notify a warehouse to segregate pallets, flag an in-transit shipment for controlled disposition, and identify delivered orders requiring customer outreach. Every action should retain who initiated it, when the message was sent, who acknowledged it, and what happened next.

A defensible event file should combine the supplier certificate, receiving and seal records, sample custody, laboratory results, batch genealogy, inventory moves, hold and release decisions, shipment milestones, customer notifications, returns, and destruction or rework evidence. That creates one chronology for quality, legal, customer service, and operations instead of competing reconstructions.

Teams should test the process before a real event. Choose a finished lot and trace backward to every input, then choose an ingredient lot and trace forward to every pallet and customer. Measure time to identify scope, percentage of records retrieved automatically, inventory-location accuracy, customer-contact completeness, and time to enforce holds across facilities. A nominal traceability program that needs days of manual reconciliation is not operationally ready.

The lesson from the Gerber dispute is not that software decides whether a product is safe. Qualified people, validated methods, and applicable standards do that. The system’s job is to preserve the evidence and ensure each decision reaches the physical supply chain before questionable goods move.

Ready to connect supplier evidence, lot genealogy, shipment execution, and exception controls? Request a CXTMS demo to build a faster, more defensible traceability workflow.