Allergen Controls That Prevent Undeclared Tree Nut Recalls

The George J. Howe Co. recall of 13,619 pounds of sunflower seeds — pulled from distribution in June 2026 because the product may contain undeclared cashew allergens — is worth paying attention to, not because it's unusual, but because it's so familiar. According to the FDA recall notice, individuals with an allergy or severe sensitivity to tree nuts face a risk of serious or life-threatening allergic reaction from consuming the affected product. Tree nut allergies, cashew allergy in particular, are among the most common causes of anaphylaxis requiring emergency care.

And yet, undeclared allergens are consistently the leading cause of FDA food recalls year after year — a fact that hasn't changed much since FALCPA took effect in January 2006. The regulations are clear. The stakes are obvious. And the recalls keep happening.

In my experience working with 200+ food manufacturers at Certify Consulting, the allergen incident almost never traces back to bad intentions. It traces back to a gap in the allergen control program — a gap that a well-designed food safety system would have closed before product ever left the facility. That's what this article is about: building the system that prevents the gap.

Why Allergen Recalls Keep Happening

Food Allergy Research & Education estimates that 32 million Americans live with food allergies, and food allergic reactions send approximately 200,000 people to emergency rooms every year. The business case for getting this right is obvious, and so is the regulatory obligation. What's less obvious is why the failure rate remains so stubbornly high.

The honest answer is that most allergen incidents aren't labeling failures in the narrow sense — somebody forgetting to type "cashews" on a label. They're systems failures. The label was wrong because the process that should have verified it was absent or broken. The allergen showed up in the product because a shared piece of equipment wasn't validated clean, or because a supplier changed a formulation without triggering a review, or because a rework batch got absorbed back into production without proper allergen evaluation.

Undeclared allergens are the leading cause of FDA food recalls, and the root cause in nearly every case is a systems gap — not a labeling error in isolation, but a failure somewhere in the chain of controls that should have verified the label before the product shipped.

A sunflower seed facility that also handles cashews in any part of its operation has a known cross-contact risk. Whether that risk is controlled depends entirely on what the allergen program looks like — and whether it was designed to find gaps or designed to check boxes.

The Regulatory Framework You're Working Under

Before getting into controls, it's worth grounding this in the specific rules at play.

FALCPA (21 U.S.C. § 343(w)) requires that any food containing a major food allergen declare it clearly on the label, either in the ingredient list using the common name of the food source or immediately after in a "Contains" statement. Tree nuts — including cashews specifically — are one of the nine major allergens as of January 1, 2023.

The FASTER Act (signed April 23, 2021, effective January 1, 2023) expanded the FALCPA major allergen list to include sesame as the ninth allergen. That addition is a useful reminder: the allergen landscape can shift by statute, and your allergen control program needs to be built to respond to those shifts systematically, not just to whatever was on the list when you last reviewed your labels.

21 CFR Part 117, Subpart C — the FSMA Preventive Controls rule — goes significantly further than FALCPA. It requires your food safety plan to include a hazard analysis that evaluates allergen cross-contact and allergen labeling as potential hazards, and to establish preventive controls when those hazards are reasonably likely to occur. Under 21 CFR Part 117 Subpart C, allergen cross-contact is explicitly a hazard requiring a preventive control, with monitoring, corrective action, and verification requirements — a significantly higher bar than the pre-FSMA expectation of good allergen labeling practices.

21 CFR § 101.4 governs ingredient declaration more broadly, and combined with FALCPA, there's essentially no room for ambiguity: if your product contains a major allergen, or is processed on shared equipment with one, the label has to say so.

What a Real Allergen Control Program Looks Like

Most allergen programs fall short because they're built to address allergen labeling as a documentation problem. They're not built to address the actual routes by which an allergen ends up in a product it doesn't belong in. A program designed to prevent undeclared allergen incidents has six distinct layers — and a recall is almost always traceable to a gap in one of them.

Layer 1: Allergen Hazard Analysis

Your food safety plan under 21 CFR Part 117 must include a written hazard analysis that evaluates allergen cross-contact — not just allergen labeling — as a potential hazard. In practical terms, this means mapping every allergen present in your facility (in ingredients, in rework, in shared equipment, in employee food brought on-site) against every product you produce, and asking honestly: could this allergen reach that product without appearing on the label?

For a facility that handles cashews in any capacity — even in a different product line run on shared equipment — the answer for products like sunflower seeds is "yes, it's possible," and the hazard analysis needs to document that evaluation. A good hazard analysis doesn't assume controls are working. It asks what happens if they're not, and it requires the controls to be in place before drawing the conclusion that a hazard is adequately managed.

Layer 2: Physical and Scheduling Controls

The most reliable allergen control is physical separation — dedicated equipment, dedicated production lines, and where practical, dedicated areas for allergen-containing products. When dedicated equipment isn't feasible, scheduling controls become the primary tool: run allergen-free products first in the production day, after thorough cleaning and verification, so any residual allergen from prior runs has been removed before clean product is processed.

The limitation of scheduling controls is that they require consistent discipline across multiple people, multiple shifts, and competing production pressures. They're easily disrupted by equipment breakdowns, urgent orders, and schedule changes. That's why scheduling alone is almost never sufficient — it works best as one layer in a system, not as the system itself.

Layer 3: Cleaning and Sanitation Validation

This is the layer that fails most often and costs the most when it does. If your facility uses shared equipment for allergen-containing and allergen-free products, you need to know — not assume, not hope — that your cleaning procedures actually remove allergen residues to safe levels.

Cleaning validation for allergen control means establishing your written cleaning procedure, then testing cleaned equipment surfaces and first-production samples to verify that allergen levels fall below your action threshold. A common mistake here is relying solely on ATP testing for allergen verification. ATP measures organic load broadly but doesn't detect specific allergens — you need allergen-specific testing, typically ELISA-based lateral flow strips or laboratory kits validated for the specific allergen of concern.

Validation isn't a one-time exercise, either. It should be repeated when cleaning procedures change, when equipment is modified or replaced, and on a periodic schedule as part of your preventive control verification activities under 21 CFR § 117.165.

Layer 4: Supplier Verification Program

Undeclared allergens frequently enter through the supply chain rather than through an error in production. A supplier may reformulate an ingredient without notifying customers. They may start running your ingredient on shared equipment that wasn't shared when you approved them. The FSMA Supply Chain Program requirements at 21 CFR Part 117, Subpart G require procedures to verify that your raw material suppliers are controlling allergen hazards effectively.

At minimum, an effective supplier allergen program includes: collecting and reviewing supplier specifications and allergen declarations at least annually and whenever formulations change; requiring contractual notification from suppliers when formulations, ingredient sources, or processing equipment are modified; conducting supplier audits or reviewing third-party audit reports for suppliers who pose allergen risk; and maintaining a supplier approval list that includes allergen risk designation for each ingredient and supplier.

The George J. Howe recall is a useful prompt for a practical question: do you know, right now, every supplier in your system who handles cashews or other tree nuts? And do they have an obligation to tell you if that changes?

Layer 5: Label Control Program

This layer is about ensuring that what's in your product matches what's on your label — and that any change to either one triggers a formal review before that label goes to print or to press.

A functional label control program includes: a master allergen matrix that maps every product against every allergen present in each formulation, updated when anything changes; a label approval workflow with allergen verification as a required sign-off step; a change control procedure that routes ingredient and supplier changes through label review; and pre-production label verification — confirming that the label in use matches the current approved specification before every production run, not just at launch.

That last element is easy to undervalue and frequently skipped. Labels get reprinted, versions get mixed up in storage, someone grabs the wrong roll. A pre-production label check adds very little time and catches the version-control errors that otherwise sail through undetected.

Layer 6: Finished Product Testing

Finished product allergen testing is the final net in the system — the control that catches what everything else missed. It doesn't substitute for the upstream layers, but it provides independent verification that the system is working and gives you the ability to detect problems before products reach consumers.

A complete allergen control program covers at least six layers: hazard analysis, physical and scheduling controls, cleaning validation with allergen-specific testing, supplier verification, label control, and finished product testing — and a recall is almost always traceable to a gap in one of them.

For facilities with shared equipment or complex allergen matrices, routine finished product allergen testing is a defensible and often necessary verification activity under 21 CFR § 117.165. The right testing frequency depends on your risk profile — some facilities test every lot, others run a statistically-based sampling plan — but having no finished product testing program is difficult to justify in a recall investigation.

The Gap That Gets Companies

Here's what the difference typically looks like between a facility that has experienced an allergen recall and one that hasn't:

Companies that recall products aren't usually doing none of these things. They're typically doing most of them — but with a meaningful gap in one area, and that's the gap the incident runs through.

What FDA Auditors Are Looking For

Under FSMA, allergen controls are preventive controls, which means an FDA investigator during a routine inspection can ask to see your hazard analysis, your monitoring records, your corrective action procedures, and your verification records — including any allergen testing results. This is a different posture than the pre-FSMA world, where allergen compliance was primarily evaluated through label review.

In my experience preparing clients for FSMA inspections, the most common observation-triggering gaps are: hazard analyses that don't document the rationale for allergen cross-contact evaluations, cleaning validation records that don't include allergen-specific testing results, and label control procedures that exist in the SOP binder but have no records demonstrating they're being followed at the floor level.

When FDA describes a recall as involving "undeclared tree nut (cashews)" in a product that shouldn't contain them, the question an investigator asks next is which preventive control failed to catch it. The absence of clear documentation in your records is itself a finding — and it tends to expand the scope of an inspection significantly.

Where to Start If Your Program Has Gaps

If you're reading about this recall and wondering whether your allergen program would have caught the same issue, the honest starting point is your hazard analysis. Pull it out and ask: does it specifically evaluate allergen cross-contact, not just labeling? Does it account for every allergen present in your facility, including those used in different product lines? Does it reflect your current supplier list and your current equipment configuration?

If the answer to any of those is no, that's where to begin — because every downstream control (monitoring, verification, corrective action) is only as complete as the hazard identification that drove it.

From there, the sequence I typically recommend to clients is: fix the hazard analysis first, then audit your cleaning validation documentation to confirm allergen-specific testing is included, then stress-test your label control workflow by tracing a hypothetical supplier change through the system and seeing whether it would actually trigger a label review — or whether it would just flow through.

If you want an experienced second set of eyes on where the gaps are, Certify Consulting's food safety and FSMA compliance services can usually provide a clear picture in a single focused audit session. Our 100% first-time audit pass rate reflects what happens when you build the program correctly before the auditor arrives, not in response to them.

The Lesson from This Recall

Every undeclared allergen recall is, at some level, a story about a control that didn't exist or a verification that didn't happen. The product in question — sunflower seeds — is inherently tree nut-free. The cashew allergen arrived through the process, not the formulation. That's a cross-contact problem, and cross-contact problems have known, manageable solutions.

The question worth asking isn't whether this was negligent. It's whether the system was built to find and close that kind of gap before product shipped. In most cases where recalls happen, it wasn't — and in most cases where they don't, it was.

That's the whole argument for investing in this program now, before you need it.

Last updated: 2026-06-09