FDA warns top U.S. bakery not to claim foods contain allergens when they don't

Regulatory change & unintended consequences

  • Many see this as a classic “unintended consequences” case: stricter allergen rules (esp. for sesame) created incentives to over‑label or deliberately add allergens.
  • Several argue the FDA designed a system that ignores real‑world manufacturing limits and thus pushed firms into perverse but legally safer behavior.

Sesame-specific issues

  • New law made sesame a “major allergen” like peanuts or dairy.
  • Some bakeries reportedly responded by:
    • Slapping sesame warnings on almost everything, or
    • Intentionally adding small amounts of sesame so labels could truthfully say “contains sesame” instead of managing cross‑contamination.
  • This is described as following the letter but not the spirit of the law, and as materially reducing safe options for sesame‑allergic people.

“May contain” vs “contains”

  • In Europe/UK, “may contain” and “made in a facility that also processes X” are common; people note this had also been common in the US.
  • FDA guidance is seen as treating “may contain” as insufficient if major allergen cross‑contact is possible, pushing companies toward either:
    • Expensive segregation/cleaning, or
    • Intentionally adding the allergen.
  • Disagreement over harm:
    • Some say “if the label says it, you just don’t eat it; no harm.”
    • Others say blanket “may contain” or “contains” on everything makes life impossible and encourages people to ignore warnings.

Practicality of controlling cross‑contamination

  • Multiple commenters with factory experience claim zero cross‑contamination is effectively impossible without separate facilities or clean‑room‑like setups, which would make basic bread very expensive.
  • Others counter that better practices and separate lines are feasible and already done for gluten‑free or allergen‑free products, albeit at higher cost and narrower availability.

Market incentives and ethics

  • Repeated theme: each individual decision (avoid liability, minimize cost, follow letter of law) is “rational,” but the system outcome is bad.
  • Debate over whether this is “evil,” just efficiency, or a coordination problem/regulatory design failure.
  • Some say large firms will abandon tiny high‑cost segments (e.g., severe sesame‑allergic consumers), leaving space for niche or artisanal providers; others think the market is too small to support that.

Impact on allergic consumers

  • People with severe allergies describe losing access to previously safe products and having to bake their own bread or rely on rare, carefully chosen brands.
  • For milder allergies, the shift from “may contain” to “definitely contains” removes products they previously tolerated.

Comparisons to other regulations

  • Frequent analogy to California’s Prop 65: over‑broad warnings on “everything” dilute meaning.
  • ADA and disability accommodations raised as a parallel: should the majority bear higher costs to include a small minority?

Proposed alternatives

  • Allergen‑free positive labels (“sesame‑free certified”), with default assumption that unlabeled items may contain allergens.
  • Clear separation between:
    • “Ingredient” allergen (known quantity), and
    • “Trace/cross‑contact” allergen with standardized thresholds (e.g., ppm limits).
  • Use “may contain” explicitly for controlled, low‑level cross‑contact, not as a catch‑all liability shield.
  • Stronger FDA ability to sanction “malicious compliance” (adding allergens solely to dodge cross‑contact requirements), though feasibility is debated.