Lay’s Classic Potato Chips Recalled Over Undeclared Allergen
Attention, snack lovers! Frito-Lay has issued a limited recall on their popular Lay’s Classic Potato Chips due to an undeclared milk allergen, as announced by the FDA. This recall affects specific 13-ounce bags distributed in Oregon and Washington. If you’re in these areas and love your chips, here’s what you need to know to stay safe.
Also Read:- Zimbabwe vs Afghanistan Second ODI: All Eyes on Harare Sports Club as Teams Face Off for Series Lead
- U.S. Faces First Severe Bird Flu Case as California Declares Emergency
The issue came to light through a consumer report, prompting Frito-Lay to investigate. The affected bags are marked with a "Guaranteed Fresh" date of 11 FEB 2025 and manufacturing codes 6462307xx or 6463307xx . If you have a bag matching these details, especially if you or someone in your household has a milk allergy, discard it immediately. Consuming these chips could pose a serious or life-threatening allergic reaction for those sensitive to milk. However, the company assures that no allergic reactions have been reported so far.
In total, 6,344 bags of Lay’s Classic Potato Chips are impacted by this recall. These were available for purchase as early as November 3, 2024, in select retail stores and through online distributors. Importantly, no other Lay’s products, flavors, sizes, or variety packs are affected, so you can continue to enjoy the rest of your favorite snacks without worry.
Undeclared allergens are not uncommon in food recalls. Just last month, over 79,000 pounds of butter from a well-known retailer faced a recall for similar labeling issues. While Lay’s chips are a household favorite, this incident underscores the importance of vigilance when checking packaging, particularly for those with dietary restrictions.
If you suspect your chips are part of the recall, Frito-Lay encourages you to contact their Consumer Relations team at 1-800-352-4477 . Stay safe, and always double-check your snacks for any updates on recalls!
Read More:
0 Comments