FDA Reports Class I Recall of Whole Foods Pomegranate Guacamole Dip Over Salmonella Risk
On August 26, 2026, the FDA reported a Class I recall of Whole Foods Pomegranate Guacamole Dip, initiated August 7, 2026, due to possible Salmonella contamination.
2 reports on this incident · first at Sep 7, 2026, 6:48 p.m. ET
This recall is open. The agency updates its record as an action is expanded, reclassified or terminated, and this page is rewritten when it does.
We last searched for new coverage of this at Sep 8, 2026, 4:10 a.m. ET — checked 3h ago.
Earlier reports
Sep 7, 2026, 6:48 p.m. ETFirst report
Whole Foods Pomegranate Guacamole Dip Recalled Over Possible Salmonella
WFM Purchasing, LP of Austin, Texas, has initiated a recall of Whole Foods Pomegranate Guacamole Dip, according to an FDA enforcement report dated August 26, 2026. The recall, numbered H-1250-2026, covers approximately 12,995 units distributed in AR, IA, IL, IN, KY, LA, MI, MN, MO, OH, OK, TX, and WI. The product is sold in various sized clear plastic containers with best before/by dates from 8/7/2026 to 8/12/2026, and includes PLU codes 27908100000 and 27908500000.
The FDA has classified this as a Class I recall, its most serious category, indicating a reasonable probability that use of the product could cause serious harm or death. The reason for the recall is that the salsa and guacamole products were made with jalapenos that may be contaminated with Salmonella. According to the FDA, Salmonella can cause diarrhoea, fever, and abdominal cramps within 12 to 72 hours, with illness typically lasting four to seven days, and may require hospitalization in some cases, especially for young children, older adults, and those with weakened immune systems.
The recall is ongoing. The FDA enforcement report lists 13 other actions by this firm, all dated August 26, 2026, involving similar guacamole products, but these are context and do not indicate fault in this specific action.
Was this report accurate and useful?
Sources
Revision history
- Version 17 Sept 2026, 22:48current
First published.
- Version 17 Sept 2026, 22:54current
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.