ConAgra Beef Recall 2016: Worcestershire Sauce Fish Mix-Up

The ConAgra Beef Recall (2016): When Worcestershire Sauce Became “Rochester Sauce”

On 19 May 2016, ConAgra Foods recalled 84,340 pounds of frozen beef products — Marie Callender’s Salisbury Steak meals and Molly’s Kitchen Macaroni & Beef — because they contained undeclared fish. The fish was anchovy, via Worcestershire sauce. The Worcestershire sauce had been miscoded in the company’s systems as “Rochester sauce” — a product that presumably contained no fish — and the miscoded ingredient flowed straight into production. It is one of the most vivid examples on record of how a data-entry error becomes a food safety incident.

The product and the people affected

The recalled products were 14-oz. boxes of Marie Callender’s Salisbury Steak with Roasted Potatoes and Home-Style Gravy (package code 5014610500, produced 14 April 2016), shipped to retail distribution centers nationwide, and 76-oz. institutional packages of Molly’s Kitchen Macaroni & Beef with Tomato Sauce (package code 5014610400, produced 13 April 2016), shipped to an institutional customer nationwide. Both bore establishment number EST. 1058.

At a glance:

What happened

ConAgra discovered the problem when it became aware of an error associated with a shipment of Worcestershire sauce: the sauce had been miscoded in the company’s ingredient system as “Rochester sauce.” Because the system believed the ingredient was Rochester sauce — with Rochester sauce’s allergen profile, which did not include fish — the production system raised no flag when the sauce went into the beef products. The labels, generated from the system’s (wrong) ingredient data, declared no fish.

Worcestershire sauce is made with anchovies — one of the nine major U.S. allergens, and one of the least expected in a beef gravy. Fish-allergic consumers eating Salisbury steak would have no reason to suspect anchovy in the gravy; the undeclared allergen was effectively invisible.

The USDA’s Food Safety and Inspection Service announced the recall on 19 May 2016. No confirmed adverse reactions were reported — fortunate, given the nationwide distribution across both retail and institutional channels (the institutional product, served in settings like schools or cafeterias, could have reached consumers with no access to the original packaging at all).

Ingredient master-data governance sounds like an IT concern; the ConAgra case proves it is a food safety discipline. In a modern food plant, the ingredient database drives everything: formulation, allergen declarations, label generation, and traceability. A single wrong record propagates automatically into labels, production orders, and shipping documents, with no human ever re-examining the allergen implications. Food safety plans increasingly treat master-data accuracy as a preventive control, with verification steps at ingredient receipt and periodic database audits.

Timeline

• 13–14 April 2016 — Affected products manufactured with miscoded Worcestershire sauce.
• May 2016 — Company discovers the coding error.
• 19 May 2016 — FSIS announces recall of 84,340 pounds.
• 2016 — Ingredient-coding and verification controls corrected.

Root cause

The company’s investigation found that a shipment of Worcestershire sauce was miscoded as “Rochester sauce” in the ingredient management system. The root cause was an ingredient master-data failure compounded by absent verification: the wrong allergen profile was attached to a physical ingredient, and no check — receiving verification, label-to-formulation reconciliation, or production-line confirmation — caught the mismatch before 84,340 pounds of finished product shipped. The system trusted its own data, and its data was wrong.

Regulatory and business outcome

The FSIS Class recall resolved the immediate risk. No enforcement action beyond the recall is documented. For ConAgra, the incident became an internal case study in master-data governance: ingredient coding errors are food safety hazards, not just procurement annoyances, and the corrective action focused on verification controls around ingredient receipt and system coding.

The look-alike name problem has parallels across the industry: coconut (a tree nut for labelling purposes) versus coconut flavouring, “natural flavours” that contain milk or egg, whey versus whey protein concentrate. Receiving procedures at well-run plants now include explicit checks for sound-alike and look-alike ingredients, and supplier agreements require notification of any ingredient whose name could be confused with another. The cheapest control in food safety may be reading the drum before trusting the database.

Lessons for food businesses

1. Ingredient master data is a food safety control. A miscoded ingredient carries the wrong allergen profile into every product, every label, and every shipment. Govern your ingredient database with the rigour of a CCP.
2. Verify receipts against physical reality. When a shipment arrives, confirm it is what the system says it is — product identity, not just quantity. “Rochester sauce” on the system and Worcestershire in the drum should never coexist.
3. Hidden allergens need explicit mapping. Anchovy in Worcestershire sauce, milk in “natural flavours,” egg in some pasta — maintain a hidden-allergen reference for every ingredient and check formulations against it.
4. Institutional distribution amplifies the risk. The Molly’s Kitchen product went to institutional customers where end consumers never see the package. Undeclared allergens in foodservice products are uniquely dangerous — verify twice.
5. Labels generated from wrong data are wrong labels. Automated label generation is only as reliable as its source data. Build reconciliation checks between the physical ingredient, the system record, and the printed label.
6. No illnesses is luck, not validation. Nationwide distribution of undeclared fish with zero confirmed reactions reflects the low prevalence of fish allergy and consumer vigilance — not adequate controls.
7. Name confusion is a foreseeable hazard. “Worcestershire” vs. “Rochester” — similar names, different allergen profiles. Flag look-alike and sound-alike ingredient names in your receiving procedures.

Sources

• “ConAgra Foods Packaged Foods, LLC Recalls Two Beef Products Due to Misbranding and an Undeclared Allergen” — USDA Food Safety and Inspection Service (via Manufacturing.net), 19 May 2016. https://www.manufacturing.net/safety/news/13163300/conagra-foods-packaged-foods-llc-recalls-two-beef-products-due-to-misbranding-and-an-undeclared-allergen