Skip to main content

SQF Edition 10 audits start January 2027. Is your program ready? Learn more →

The Brief archive

The Brief · Issue 14 · Jun 25, 2026 · 4 min read

The Soup Was Labeled Vegetarian. The Recall Was for Shrimp.

Kettle Cuisine recalled Whole Foods minestrone labeled Vegetarian because the cups contained shrimp. FDA called it Class I. The label was right. The contents weren't. A different soup got packed into the vegetarian cup, and a store inspection caught it, not the plant. That's not a labeling failure. It's line clearance, and the vegetarian claim is what made a product mix-up life-threatening.

SM
Steven Moussawer Founder

Kettle Cuisine recalled Whole Foods Market Kitchens Minestrone Soup for undeclared shrimp. The cups were labeled Vegetarian. The recall went out in May 2026. FDA's Class I classification, its most serious tier, posted in June. Nobody got sick. The label was correct. The contents weren't. A different soup ended up in the vegetarian cup, and a store inspection caught it, not the plant.

What actually happened

A shrimp-containing soup got packed into the minestrone cup. Minestrone is a vegetable soup. The product is sold as vegetarian, and the cup says so on the lid and the front.

The recall covered 4,496 units across 17 states and Washington, D.C., plus online orders through Whole Foods and Amazon. It's Class I because crustacean shellfish is one of the nine major allergens and a shrimp reaction can be life-threatening.

The part that should bother you: the mismatch turned up during an in-store inspection that found a single cup with the wrong product in it. Not at fill. Not at release. At the store.

This is a different failure than the label getting it wrong

Most undeclared-allergen recalls are label problems. The formula changed and the label didn't. The "Contains" statement missed an ingredient. The wrong label printed on the line. I've written about the label-to-product mismatch and the formulation change that outran the label before.

This one is the opposite. The label is right. It accurately describes a vegetarian minestrone. The contents are wrong. A whole different soup went into the package.

That's a product-identity failure. A line-clearance and changeover problem, not a labeling or cross-contact problem. Cross-contact is a trace amount from a shared surface. This was a full serving of the wrong soup. The fix lives on the production line, not in the label-approval workflow.

The Vegetarian claim is an allergen control, not marketing

A vegetarian or free-from claim is a control point. Treat it like one.

People with a shellfish allergy use that claim to screen. A shopper avoiding shrimp sees "Vegetarian Minestrone" and assumes no shellfish. That assumption is the whole reason a wrong-product mix-up became Class I instead of a quality complaint. The claim raised the stakes.

So the claim has to be backed by a controlled line, not just a correct recipe card. If you run an allergen-bearing SKU and a free-from SKU through the same filler, the claim is only as good as your changeover.

Where the control should have been

The question isn't how shrimp got into one company's soup. It's what stands between fill and ship in your plant.

Walk one changeover. Pick any allergen-bearing product that shares a line, a filler, or a packaging station with a free-from product. Then answer two questions.

What physically prevents product A from ending up in product B's labeled package? Documented, verified line clearance, or an operator who's supposed to remember.

What at the end would catch it if it happened anyway? A finished-goods check that the contents match the label, or just a check that the label printed correctly.

If your honest answer to the second one is "a customer would notice," your last line of defense is a store shelf. That's exactly what happened here.

The drill

Run a changeover audit on your highest-risk pair: the allergen-bearing SKU and the free-from SKU that sit closest together on the floor.

Document the line-clearance steps and make the verification a signature, not a habit. Add one finished-goods check that confirms the product in the package is the product on the label. By recipe, by appearance, by net weight, by whatever actually tells the two apart. Pull that sample at the start of every run after a changeover, not once a shift.

None of this is exotic. It's the difference between catching a wrong-product fill at your line and reading about it in a Class I recall notice.

Make the verification live on the line

This is the kind of control that's invisible on paper and obvious in software. The changeover record, the allergen matrix, and the label claim usually live in three different places, so nobody can see that a free-from cup just ran on a line that handled shellfish an hour earlier.

Beacon keeps them connected. The allergen rules and the changeover verification sit on the line, where the check has to happen, instead of waiting for a store inspection to find the one cup that's wrong.

If you want to see how that works, book a call.

Run a food safety program? See how Beacon keeps it audit-ready.

See Beacon in 20 minutes