Recall Forensics

Recall Forensics: The Viva Raw Warning Letter — the validation failure behind it

Team ValidLeaf · October 2026 · 6 min read

Recall Forensics is our series tracing real product recalls and enforcement actions to the specific validation gap behind them. Every fact comes from public regulator records or reporting of those records — no speculation, no invented causes. This case is not a new recall. It is something quieter and, for quality teams, more useful: a warning letter about a fix that was promised after a recall, then never shown to have happened. The gap was not a missing idea. It was missing evidence.

What happened

On September 22, 2026, the U.S. Food and Drug Administration posted a warning letter to Viva Raw LLC of Charlotte, North Carolina. The letter itself is dated August 5, 2026. It concerns raw pet food the company sold in the summer of 2025, and it states that the product was adulterated within the meaning of the federal food law (Food Poison Journal / LexBlog, reporting the FDA letter; Cats.com, updated October 11, 2026).

The underlying recall dates to August 25, 2025. Viva Raw recalled two lots — 21495 and 21975 — covering six frozen raw products: Viva Ground Beef for Dogs, Viva Beef & Turkey for Puppies, Viva Ground Chicken for Dogs, Viva Chunked Chicken for Dogs, Viva Chicken for Cats, and Viva Pure Chicken. The lots were sold from July 2 to August 21, 2025, shipped directly to customers nationwide and supplied to retail stores in seven states: New York, Illinois, South Carolina, Florida, Kansas, California, and Arizona. No illnesses in people or pets were reported in connection with the recalled lots (LexBlog; Cats.com).

The contamination was not found by the company first. Routine testing by the North Carolina Department of Agriculture and Consumer Services identified it. FDA then inspected the contract manufacturer that made the food from August 25 to 29, 2025, and its own samples matched the state findings: Salmonella Enteritidis in two chicken products from lot 21975, and Listeria monocytogenes in the turkey-and-beef puppy food from lot 21495 (LexBlog; Cats.com).

What happened next is the heart of the case. The company initiated a Class I recall and submitted a corrective action report in October 2025. As part of its response, it told FDA it would move to high-pressure processing of its packaged products — a non-thermal step used to reduce Salmonella and Listeria without cooking the food. In the August 2026 letter, FDA said it could not fully evaluate whether the corrective actions were adequate, because the company had not provided documentation demonstrating that high-pressure processing had been implemented as a preventive control. The letter did not announce an additional recall (Cats.com; LexBlog).

An honesty note, because we hold ourselves to it: the public reporting summarized here does not say where in the contract manufacturer’s process the organisms entered the food, and it does not say whether high-pressure processing was adopted at some later point after the letter was written. It also does not resolve every product-name variation between secondary summaries, so this article uses the product names and lot numbers on which both sources agree. The lesson does not depend on the missing details: a regulator asked for proof of a named preventive control, and the file did not contain it.

The validation gap: a preventive control with no evidence behind it

Raw pet food has no cook step. If a manufacturer adopts a kill step such as high-pressure processing, that step becomes the centre of the quality system — and it has to be proved, not announced.

That distinction separates this case from the other pet-food cases we have traced. In the Raaw Energy teardown, the centre of gravity was a contaminated plant environment and an inspection response that never arrived in writing. In the Darwin’s teardown, it was a recall recommendation that was never carried out. Here, a recall was carried out and a corrective plan was submitted. The failure sits one step later, in the space between a commitment and a validated control:

• A preventive control needs validation, not intention. For a processing step relied on to reduce pathogens, the evidence package should show the operating parameters that were studied, the organisms or surrogates used, the log reduction or other acceptance criterion that was set in advance, and results from production-representative product. A sentence in a corrective action report is a plan. Validation data are a control.
• Implementation needs records that a third party can audit. Equipment qualification, a written procedure, training records, batch records showing the step was applied lot by lot, and deviation handling when parameters fall outside limits — that chain is what lets an inspector, a customer, or the brand owner verify the step months later without taking anyone’s word for it.
• A contract manufacturer does not transfer the responsibility. The food in this case was made by a contract manufacturer, and FDA inspected that site. The brand whose name is on the package still owns the preventive-control decision and its documentation. A quality agreement should name who validates the kill step, who holds the data, who reviews batch evidence, and how quickly the brand can obtain the complete file when a regulator asks.
• Test-and-hold is not a substitute for a working control. In this case, routine state testing found the contamination. External sampling is a valuable safety net, but it samples a fraction of production and reports after product exists. A manufacturer of pet food who relies on someone else’s testing to discover positives has detection, not prevention — and detection after distribution is the most expensive form of quality control there is.
• Corrective action closes on evidence, not on submission. Submitting a report starts the closure conversation; it does not finish it. An effectiveness check — predefined evidence, reviewed after implementation, showing the control is operating as validated — is the step that turns corrective action from correspondence into a closed loop. FDA’s position in this letter is a textbook illustration of a loop left open.

The documented point is general: when a high-risk product depends on a named intervention, that intervention has to exist in three places at once — in the process, in the validation file, and in the batch record. If it exists in only one, a regulator will treat it as unproven.

How a GMP Readiness Assessment catches it

This is exactly the kind of gap a GMP Readiness Assessment is built to find while it is still a documentation problem. Over four weeks, it reviews:

• Preventive-control evidence — for each control your food safety plan relies on, is there a validation study with preset acceptance criteria, or only a description of intent?
• Corrective action closure — do past recalls and deviations close with an effectiveness check supported by records, or with a submitted report and no follow-up evidence?
• Contract-manufacturer oversight — do quality agreements assign validation, data ownership, batch review, and file-access duties clearly enough to answer a regulator within days?
• Detection versus prevention balance — how much of your pathogen assurance comes from your own validated controls, and how much depends on outside sampling finding a problem first?
• Batch-level traceability of controls — can you show, for any given lot, that every preventive control claimed for it was actually applied and stayed within limits?

It closes with a gap assessment, a remediation roadmap, and starter IQ/OQ/PQ templates — so the evidence file is built before the warning letter, not after it.