Undeclared allergen recalls are among the most preventable failures in food manufacturing — and among the most common. The FDA's recall database is full of them, and every single one follows a pattern that an effective quality system should have caught before the product ever reached a shelf.
The most recent example worth studying: Fayus Inc., doing business as Yusol International Foods out of Sacramento, CA, expanded a recall of its OLA-OLA POUNDED YAM product across four package sizes — 2 lbs, 4 lbs, 5 lbs, and 10 lbs — because the label failed to declare sodium caseinate, a milk derivative, as an allergen. According to the FDA recall notice, consumers with milk allergies or sensitivities face a real health risk from this product. The fact that this was an expansion of the recall — meaning it grew after the initial action — suggests the problem wasn't caught all at once, which is itself a signal about where the quality system broke down.
I want to be clear about what this article is and isn't. This isn't a story about one company. It's a case study in how undeclared allergen failures happen across the food industry, and what a well-designed quality system would have done differently. If you're a food manufacturer, a quality director, or a compliance consultant, the patterns here are worth understanding — because the next recall in that database could be yours.
Why Sodium Caseinate Is an Especially Common Blind Spot
Sodium caseinate is a milk protein derived from casein. It's used as a functional ingredient in a surprising range of products — emulsifiers, texture enhancers, whitening agents in powdered formulations. It shows up in products where consumers would never think to look for milk.
That's the core of the problem. When an ingredient functions as a processing aid or a minor additive rather than a primary ingredient, it tends to get under-scrutinized in the labeling review process. A product team focused on the main ingredient — pounded yam, in this case — may not apply the same allergen lens to every additive in the formulation.
Under 21 CFR Part 101.4 and the Food Allergen Labeling and Consumer Protection Act (FALCPA), milk is one of the eight major food allergens (now nine, with sesame added by FASTER Act, effective January 1, 2023) that must be declared on the label. That declaration applies regardless of whether milk is a primary ingredient or a trace derivative like sodium caseinate. There is no threshold. There is no "small amount" exception. If it's in the product, it has to be on the label.
This is a regulatory bright line — and it's been a regulatory bright line since 2006. An undeclared milk derivative in 2025 is not a gray area. It's a documentation and process failure.
The Four Places a Quality System Should Have Caught This
If you want to understand where allergen recalls come from, it helps to think about the system as a set of control points, each of which had an opportunity to prevent the problem. Here's where the breakdown typically happens.
1. Ingredient-Level Allergen Documentation
Every ingredient that enters a manufacturing facility should come with an allergen declaration from the supplier — and that declaration should be reviewed and reconciled against the finished product label before production begins. This is sometimes called an allergen profile or allergen impact assessment, and it should be a living document that gets updated every time a formulation changes or a supplier substitutes an ingredient.
Sodium caseinate is not a secret. Any competent review of a formulation containing it would surface milk as an allergen. The failure to declare it on the label suggests either that the allergen profile was never completed, that it wasn't reconciled against the label, or that the formulation changed after the label was approved and no one triggered a re-review.
That last scenario — formulation changes without label review — is more common than it should be. Suppliers reformulate. Procurement teams source alternative ingredients. And unless the quality system explicitly requires an allergen impact assessment every time an ingredient is modified, those changes can slip through.
2. Label Review and Approval Process
A robust label review process is one of the cheapest insurance policies in food manufacturing. It involves a structured comparison between the formulation's allergen profile and the label's allergen declarations — not just a proofreading pass, but a systematic cross-reference.
Under 21 CFR Part 117 (the Current Good Manufacturing Practice, Hazard Analysis, and Risk-Based Preventive Controls rule for Human Food), allergen labeling is a required component of a food safety plan. Specifically, 21 CFR 117.135(c)(2) identifies allergen preventive controls as a category that must be addressed when allergens are a significant hazard. Undeclared allergens qualify. That means a food safety plan that doesn't include a label review as part of its allergen controls is almost certainly out of compliance with the regulation, not just out of best practice.
The practical question is: who owns the label review, and what are they checking against? If the answer is "the marketing team checks it for visual accuracy," that's not a food safety control. It's a layout review. Those are different things.
3. Change Control Procedures
Change control is where allergen failures most often sneak through. A formulation that was once fully compliant can become non-compliant the moment a supplier changes an ingredient sub-component — and that change may never trigger a label review if the change control procedure doesn't require it.
Effective change control for allergen management requires that any change to a formulation, an ingredient source, or a supplier's specifications automatically triggers a review of:
- The allergen profile for the finished product
- The current label's allergen declarations
- Any co-manufacturing or contract production agreements that reference the formulation
This sounds obvious when stated plainly. In practice, it requires a quality management system (QMS) with documented workflows that route formulation changes through the food safety team before production approval — not after. A QMS that only reviews finished products for compliance, without catching upstream formulation changes, is solving the wrong problem.
4. Pre-Market Verification and Periodic Label Audits
Even a well-designed system can drift. Periodic label audits — where a quality team pulls current labels and runs them against current formulations — are a simple, low-cost way to catch drift before a regulatory agency or a consumer complaint does it for you.
The fact that this recall was expanded to include multiple package sizes suggests that the label error was consistent across the product line, not isolated to one SKU. That's a signal of a systemic labeling process failure, not a one-time typo. A periodic audit across all SKUs in a product family would likely have caught this at the same time.
What the FASTER Act Changed — and What It Means for Your Labels
The Food Allergy Safety, Treatment, Education, and Research (FASTER) Act added sesame as a ninth major allergen, effective January 1, 2023. This is worth raising here because it's the most recent change to the federal allergen labeling framework, and it exposed a lot of the same labeling process gaps that the OLA-OLA recall illustrates.
Companies that scrambled to add sesame declarations in 2022 were, in many cases, discovering for the first time that their label review process wasn't systematic enough to have caught the gap if a regulatory deadline hadn't forced the review. If your team did a full allergen audit in 2022 to comply with the FASTER Act, that's the same audit methodology that would have caught an undeclared milk derivative in any other product line.
If you didn't do a systematic audit then — or if your team has changed since — now is a reasonable time to run one.
Allergen Control: A Comparison of System Maturity Levels
One of the most useful frameworks for assessing allergen risk in a manufacturing operation is to evaluate system maturity across the key control points. Here's how I'd describe the difference between a reactive, basic, and proactive allergen program:
| Control Area | Reactive (High Risk) | Basic (Moderate Risk) | Proactive (Low Risk) |
|---|---|---|---|
| Supplier Allergen Documentation | Collected at onboarding only | Reviewed annually | Reviewed at onboarding, with every ingredient change, and on annual cadence |
| Formulation Allergen Profile | Not formally documented | Documented at launch | Living document updated with every formulation or supplier change |
| Label Review Process | Visual/layout review only | Cross-referenced against ingredient list | Systematic cross-reference against allergen profile with sign-off required |
| Change Control Triggers | No allergen-specific triggers | Major formulation changes trigger review | Any ingredient or supplier change triggers allergen impact assessment |
| Periodic Audits | No scheduled audits | Annual label audit | Quarterly audits + triggered audits after any supply chain change |
| Regulatory Currency | Labels updated reactively | Updates tracked by QA | Regulatory watch process with scheduled label review cycle |
Most companies that end up in an allergen recall are operating somewhere in the "Reactive" or "Basic" columns. The gap between "Basic" and "Proactive" is not primarily a budget issue — it's a documentation and workflow design issue. The proactive approach requires more structured procedures, but not necessarily more labor.
The Expanded Recall Signal: What It Tells Us About Process
I want to come back to the expansion aspect of this recall, because it's diagnostically interesting. When a recall expands from one SKU to multiple SKUs, it usually means one of two things: either the problem was initially scoped too narrowly, or additional sizes and lots were reviewed after the first recall and found to have the same issue.
Either way, it points to a gap in the initial investigation. A well-executed allergen recall investigation should include a root cause analysis that immediately asks: if this label error exists in this SKU, where else might it exist? That question should drive a rapid review of all related products before the recall scope is determined, not after.
In practice, this kind of cross-SKU root cause analysis requires that your QMS can quickly surface all products that share a formulation, an ingredient, or a label template. If that information lives in disconnected spreadsheets or tribal knowledge, the investigation will be slow and the recall scope will be underestimated — which is exactly what an expansion indicates.
Practical Steps to Take Right Now
If you're a food manufacturer reading this, here are the immediate actions worth considering — not as a comprehensive program, but as a triage for the most common gaps:
Pull your current allergen profiles. For every active SKU, confirm you have a documented allergen profile that reflects your current formulation and current ingredient suppliers. If you can't produce that document in under 10 minutes, you have a documentation gap.
Run a formulation-to-label cross-check. Take your current ingredient specifications and compare them against your current labels. Pay particular attention to ingredients that function as additives, emulsifiers, or processing aids — those are where hidden allergens tend to live. Sodium caseinate, whey protein, lactylate-based emulsifiers, and casein are all milk derivatives that can appear under non-obvious names.
Review your change control procedure. Confirm that any change to a formulation or an ingredient source triggers an allergen impact assessment and a label review before the change is approved for production. If that workflow doesn't exist in writing, it doesn't exist as a control.
Check your labels against current federal requirements. The nine major allergens under federal law are: milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soybeans, and sesame. Every one of these — including all derivatives — must be declared. If your labels were last reviewed before January 1, 2023, they may be missing sesame declarations as well.
How Certify Consulting Approaches Allergen Label Compliance
At Certify Consulting, allergen labeling is one of the first things I look at during a food safety gap assessment — and it's one of the areas where I most consistently find undocumented processes. Companies often have good intentions and experienced teams, but the procedures that translate those intentions into reliable label accuracy aren't always written down in a way that survives staff turnover or a supplier change.
Across 200+ clients and eight-plus years of compliance work, I've seen the same pattern repeat: the label was approved once, it was accurate at the time, and then the formulation quietly drifted without triggering a re-review. The product that gets recalled isn't the product that was approved. It's the product as it's currently made — and the label never caught up.
That's a solvable problem. It requires a QMS with clear change control triggers, a documented allergen profile for each SKU, and a periodic audit process that checks labels against current formulations on a scheduled basis. None of that is exotic. It's basic quality infrastructure, and it's the kind of thing we help companies build and maintain at Certify Consulting.
If you're not sure whether your allergen controls are where they need to be, that uncertainty is itself worth acting on. An allergen recall is expensive, damaging to consumer trust, and entirely preventable. The controls exist. The regulations are clear. The question is whether your quality system is actually executing them.
If you'd like to talk through where your program stands, I'm happy to start with a conversation. You can learn more about how we work with food manufacturers at certify.consulting.
Summary: The Controls That Prevent This
To close the loop on what went wrong in the OLA-OLA recall and how it gets prevented: the failure was an undeclared milk derivative (sodium caseinate) on a product label, discovered broadly enough that the recall had to be expanded across multiple package sizes. The root cause, almost certainly, was one or more of the following: an incomplete allergen profile, a label review that didn't cross-reference against allergen declarations, a change control process that didn't require allergen re-review when the formulation or ingredient sources changed, or a lack of periodic audits that would have caught drift before a recall did.
Every one of those is a documented quality system gap. Every one of them has a known prevention. The regulation requiring the declaration — FALCPA, codified under 21 CFR Part 101 — has been in effect since 2006. This is not a new requirement or an ambiguous standard. It's a bright line that a functional quality system should make nearly impossible to miss.
The recalls keep happening because quality systems are often built to meet the letter of the regulation at the moment of launch, not to sustain compliance across the product lifecycle. That's the gap worth closing.
Last updated: 2026-07-26
Jared Clark
Principal Consultant, Certify Consulting
Jared Clark is the founder of Certify Consulting, helping organizations achieve and maintain compliance with international standards and regulatory requirements.