Ingredient Traceability Controls That Prevent Salmonella Recalls

When a contaminated milk powder ingredient triggers a downstream snack food recall, the root cause is almost never the finished product manufacturer's fault alone — but the regulatory and operational consequences land squarely on them.

In May 2026, Legacy Snack Solutions of Waukesha, Wisconsin, voluntarily recalled certain batches of Giant Eagle Baked Pita Chips With Parmesan, Garlic & Herb due to potential Salmonella contamination. According to the FDA recall notice, the action followed a California Dairies, Inc. milk powder recall — meaning the contamination originated upstream, in a supplied ingredient, and traveled through the supply chain into finished retail product. By the time the recall was issued, product was already on shelves.

That sequence is what I want to talk about, because it's preventable. Not every step of it, and not with certainty — but the gap between "we used a recalled ingredient" and "we caught it before distribution" is exactly the gap that a well-designed food safety system is supposed to close.

This article breaks down what went wrong at the systems level, which FDA regulations govern each failure point, and what manufacturers can do right now to tighten those controls.

What This Recall Actually Tells Us About Supply Chain Risk

The Legacy Snack Solutions recall is a downstream contamination event — a category that's become increasingly common as supply chains grow longer and ingredient sourcing more complex. The finished product manufacturer almost certainly did not introduce Salmonella into the process. What they apparently lacked was a system capable of catching a contaminated ingredient before it made it into the bag.

That's a supplier verification and traceability failure, and FDA's Preventive Controls for Human Food rule (21 CFR Part 117) addresses it directly.

According to FDA data, Salmonella causes an estimated 1.35 million infections, 26,500 hospitalizations, and 420 deaths in the United States every year, making it one of the most consequential foodborne pathogens regulated under the Food Safety Modernization Act (FSMA). Dry ingredients — including milk powders, spice blends, and cheese powders — are a recognized high-risk vector for Salmonella precisely because low water activity can protect the organism from standard environmental controls while still allowing it to survive and contaminate downstream products.

A 2023 analysis by the FDA found that ingredient-related recalls accounted for approximately 40% of all Class I food recalls, the most serious category involving reasonable probability of serious adverse health consequences. That's not a fringe scenario — it's the dominant pattern.

The Legacy Snack Solutions situation fits that pattern almost exactly.

The Regulatory Framework That Governs This

Three distinct regulatory requirements apply to manufacturers in this position. Understanding which one governs which failure point matters if you're trying to build a system that actually catches the problem.

21 CFR Part 117 — Preventive Controls for Human Food

This is the primary rule. Under FSMA's Preventive Controls framework, manufacturers are required to implement a written Food Safety Plan that includes a Supply Chain Program when the hazard analysis identifies a hazard requiring a supply chain-applied control. Salmonella in dairy-based powders is exactly that type of hazard.

21 CFR Part 117, Subpart G governs the Supply Chain Program specifically. The key requirements include:

• Conducting a hazard analysis that identifies raw materials and ingredients that could introduce a pathogen
• Approving suppliers before using them, based on documented evaluation of the supplier's food safety performance
• Conducting supplier verification activities appropriate to the hazard — which for a known Salmonella-risk ingredient typically means review of supplier audit results, lot-specific certificates of analysis, or environmental monitoring records
• Taking corrective actions when a supply chain-applied control is not properly applied

What the Legacy Snack Solutions recall suggests is that at least one of these steps either wasn't in place or wasn't working as designed. When a milk powder supplier issues a recall and finished goods are already in distribution, the supplier verification system did not close the loop in time.

21 CFR Part 1 Subpart S — FSMA Traceability Rule

The FDA Food Traceability Rule, which became effective November 7, 2022 and carries a compliance deadline of January 20, 2026 for most covered entities, requires that manufacturers maintain Key Data Elements (KDEs) for foods on the Food Traceability List (FTL). While the current recall involves pita chips rather than a raw FTL ingredient, the underlying lesson applies broadly: you cannot execute a targeted, efficient recall without lot-level traceability through your ingredient supply chain.

Manufacturers who hadn't completed their traceability infrastructure by the January 2026 deadline are now operating out of compliance — and the consequences become visible in exactly the kind of recall scenario we're examining here.

21 CFR Part 120 — Hazard Analysis and Critical Control Points (HACCP)

For juice manufacturers HACCP is mandatory; for other food categories it's the voluntary predecessor framework that FSMA's Preventive Controls largely displaced. But the logic remains directly applicable: if Salmonella in a dry ingredient is a known hazard, the HACCP-informed question is whether there's a Critical Control Point where that hazard can be detected or controlled before it reaches the consumer. For dry-ingredient pathogens, environmental monitoring and finished product testing serve that function.

What a Functioning Supplier Verification Program Looks Like

Let me be direct about something: supplier verification is one of the most frequently underdeveloped elements I see when I work with food manufacturers preparing for FDA inspections. The written program often exists. The execution is where things come apart.

Here's what a system that would likely have caught this looks like:

Approved Supplier List with Documented Hazard Evaluation

Every raw material supplier should be on an Approved Supplier List (ASL) that includes a documented rationale for approval. For a milk powder supplier, that rationale should specifically address Salmonella risk — because it's a foreseeable hazard in that ingredient category. The ASL should be reviewed at a defined frequency (annually is a reasonable baseline) and updated when supplier food safety performance changes.

Lot-Specific Certificates of Analysis

A Certificate of Analysis (CoA) per incoming lot is not the same thing as a supplier verification activity by itself — but it is a reasonable component of a broader program, especially when the supplier tests for Salmonella as part of their outgoing quality program. The key word is "lot-specific." A blanket annual CoA does not tell you whether the lot you received last Tuesday is clean.

Supplier Audit Program or Equivalent

For high-risk ingredients, FDA expects manufacturers to either audit suppliers directly or review audit results conducted by a qualified third party. SQF, BRC, FSSC 22000, and similar GFSI-benchmarked scheme certifications are widely accepted as evidence of a functioning supplier food safety program. The audit or certification should be current — within 12 months is standard — and the scope should include the specific product and process relevant to your supply.

Incoming Ingredient Testing for High-Risk Materials

This is where I see the biggest gap in practice. Supplier verification is not a substitute for incoming testing when the hazard is a pathogen in a high-risk ingredient. For Salmonella-risk dry ingredients like milk powders, spice blends, and nut-based products, lot-level microbiological testing at receiving is the control that provides independent verification. The cost of a microbiological test on incoming milk powder is trivial relative to the cost of a Class I recall.

The following table summarizes verification activities by risk level — a useful framework for prioritizing where to invest your quality resources:

Environmental Monitoring: The Control That Catches What Documentation Misses

Supplier verification tells you about the supplier's process. Environmental monitoring tells you about yours. These two systems work together — and a gap in either one can let a contaminated batch reach consumers.

Under 21 CFR Part 117, an environmental monitoring program is required when the hazard analysis identifies an environmental pathogen as a hazard requiring a preventive control. For facilities that handle or expose ready-to-eat products, Salmonella and Listeria monocytogenes are the two pathogens that typically trigger this requirement.

A functional environmental monitoring program for a snack food facility should include:

• Zone-based sampling — Zone 1 (food contact surfaces), Zone 2 (near food contact), Zone 3 (general production environment), and Zone 4 (traffic areas and drains)
• Defined sampling frequency — typically weekly to monthly depending on zone and facility history
• Corrective action procedures — written, tested responses for both indicator organism positives and pathogen positives
• Trend analysis — not just reacting to positives but tracking patterns over time to identify harborage points before they produce a product failure

A positive environmental result that triggers a hold-and-investigate response before product ships is a success story. A positive that only becomes visible through a supplier's recall notice after product is in distribution is a system failure.

Finished Product Testing Is Not Optional for High-Risk Categories

I want to address a misconception that I run into fairly often: the idea that if your incoming ingredients are verified and your process controls are documented, you don't need finished product testing. In low-risk categories, that's a defensible position. In a product category where a pathogenic organism could survive the manufacturing process — which baked goods with dairy-based ingredient additions can be, depending on process design — finished product testing is a meaningful last-line control.

For snack food manufacturers using Salmonella-risk ingredients, a statistically valid finished product sampling and testing program is one of the clearest signals to FDA that the manufacturer takes the hazard seriously. It also generates the data you need to make a rapid recall decision if something does go wrong, rather than waiting for a supplier notice.

Testing cadence, sample size, and analytical methods should be defined in the written Food Safety Plan or an accompanying quality procedure, and the records should be maintained for the retention period specified in 21 CFR Part 117.305 — which for most preventive control records is at least two years.

Traceability: The Difference Between a Targeted Recall and a Broad One

Even when every upstream control fails and product containing a contaminated ingredient reaches distribution, a functioning traceability system limits the damage. The FSMA Traceability Rule's Key Data Element requirements — which by January 2026 should now be operational for most covered manufacturers — exist precisely for this scenario.

The difference between recalling 500 cases and recalling 50,000 cases is almost always a traceability question. If you can link a specific finished product lot to a specific ingredient lot from a specific supplier shipment, you can surgically identify which finished product is at risk. If your traceability system can only tell you which supplier you use, not which lot from that supplier went into which finished product run, you're looking at a broad, conservative recall that pulls everything within a wide date window.

The components of a functional traceability system for an ingredient-driven contamination scenario include:

1. Receiving records that capture supplier, lot number, quantity, and date for every incoming ingredient
2. Production records that link each finished product lot to the specific ingredient lots used in that production run
3. Distribution records that identify which finished product lots went to which customers or distribution points
4. A mock recall program that tests the system at least annually — and actually measures how long it takes to retrieve each data element

If you haven't run a mock recall recently, this is a good week to schedule one.

What FDA Will Look for in an Inspection Following This Type of Recall

When FDA inspects a facility following a voluntary recall, they're not just documenting what happened — they're evaluating whether the food safety system as designed was adequate, and whether it was being followed. The inspection typically focuses on:

• The written Food Safety Plan and whether the hazard analysis correctly identified the pathogen risk associated with the relevant ingredient
• The Supply Chain Program — approval records for the supplier, verification activities conducted for the specific ingredient, and records from the lot(s) involved in the recall
• Corrective action records — what the manufacturer did when they became aware of the supplier's recall, and how quickly
• Traceability records — whether the manufacturer could identify affected lots and initiate the recall efficiently
• Environmental monitoring records — whether the facility had an active program and whether any results were relevant to the recalled ingredient

Facilities that have documented, executed programs in each of these areas are in a fundamentally different position during an inspection than facilities that have written programs sitting in a binder. FDA Form 483 observations and Warning Letters in the food safety space disproportionately cite the gap between written procedures and actual practice.

Practical Steps to Take Right Now

If you're a food manufacturer using any dairy-based powders, spice blends, or other high-risk dry ingredients, here's where I'd focus first:

1. Pull your hazard analysis and confirm that Salmonella is identified as a hazard for each high-risk ingredient category. If it isn't documented, document it now.
2. Review your Approved Supplier List and verify that each high-risk ingredient supplier has a current audit or GFSI certification on file — within the last 12 months.
3. Check your incoming ingredient testing protocol and confirm that Salmonella testing is included for high-risk ingredients. If it isn't, talk to your contract laboratory about adding it.
4. Run a mock recall for at least one high-risk ingredient and measure how long it takes to identify all affected finished product lots. If the answer is "more than four hours," your traceability system needs work.
5. Confirm FSMA Traceability Rule compliance if you're a covered entity. The January 20, 2026 compliance deadline has passed. If you're not yet compliant, get a gap assessment scheduled.

If any of these steps surfaces a gap you're not sure how to close, that's the conversation to have with a qualified consultant before FDA shows up to have it with you.

At Certify Consulting, we've helped more than 200 food and life sciences manufacturers build food safety systems that hold up under FDA scrutiny — with a 100% first-time audit pass rate. The work isn't complicated, but it does require doing it before the recall, not after.

Citation Hooks

• Salmonella in dry dairy ingredients is a foreseeable, documented hazard under 21 CFR Part 117, and FDA expects manufacturers to identify it in their hazard analysis and apply a supply chain-applied control before using the ingredient.
• The FSMA Food Traceability Rule compliance deadline of January 20, 2026, means manufacturers who cannot trace a finished product lot back to a specific incoming ingredient lot are now operating out of regulatory compliance — a gap that becomes visible in exactly the kind of downstream recall scenario FDA cited in May 2026.
• A downstream contamination recall — where a finished goods manufacturer recalls product because an upstream ingredient supplier issued a recall — is the predictable outcome of a supplier verification program that approves suppliers but does not verify individual lots.

Source: FDA Recall Notice, May 7, 2026 — Legacy Snack Solutions voluntary recall of Giant Eagle Baked Pita Chips With Parmesan, Garlic & Herb. Available at fda.gov/safety/recalls-market-withdrawals-safety-alerts.

Last updated: 2026-05-25