Kettle Cuisine Recalls Marketside Tomato Bisque Soup Kits Over Listeria Risk
Kettle Cuisine LLC has recalled Marketside Tomato Bisque Soup Kits following routine testing that indicated potential Listeria monocytogenes contamination.
3 reports on this incident · first at Aug 18, 2026, 9:40 p.m. ET
Earlier reports
Aug 18, 2026, 9:54 p.m. ET
Kettle Cuisine Recalls Marketside Tomato Bisque Soup Kit Over Listeria Risk
On August 14, 2026, Kettle Cuisine LLC of Savage, MD, recalled its Marketside Tomato Bisque Soup Kit – 14oz (397g) due to potential contamination with Listeria monocytogenes, according to Food Safety News reporting on FDA records. Routine testing conducted by the company produced a presumptive positive result for Listeria monocytogenes, which can cause serious and sometimes life-threatening infections.
The product is packaged in a wrapped tray and marked with product description labels and printed use-by code identifiers. According to Food Safety News, the company has received no confirmed reports of illnesses associated with this product.
Aug 18, 2026, 9:40 p.m. ETFirst report
Kettle Cuisine Recalls Marketside Tomato Bisque Soup Kits Over Listeria Risk
On August 14, 2026, Kettle Cuisine LLC of Savage, MD initiated a recall for soup kits in an open and developing situation reported by Food Safety News and the FDA.
The recall affects the Marketside Tomato Bisque Soup Kit – 14oz (397g), packaged in a wrapped tray and marked with product description labels and printed use-by code identifiers. Routine testing conducted by the company produced a presumptive positive result for Listeria monocytogenes, creating a potential contamination hazard.
Listeria monocytogenes can cause serious and sometimes life-threatening infections. The company has received no confirmed reports of illnesses associated with this product, according to Food Safety News.
Was this report accurate and useful?
Sources
- Walmart Marketside tomato soup mix recalled because of Listeriafoodsafetynews.com
Revision history
- Version 119 Aug 2026, 01:55current
First published.
- Version 119 Aug 2026, 01:40current
First published.
- Version 119 Aug 2026, 01: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.