Your Recall Can't Hinge on a Single Test Result

FDA reported a positive cyclospora result on Taylor Farms iceberg lettuce. The company recalled. A day later, FDA re-reviewed the sample and called that result a false positive. The recall stood anyway, because the outbreak was already tied to that lettuce by patient interviews and traceback, not by the test. If your recall decision hangs on a single lab result, you're building on the weakest evidence in the room.

What actually happened

A cyclosporiasis outbreak sickened more than 1,600 people across five states, by laboratory-confirmed count, before anyone named a product. CDC and state health departments linked the illnesses through interviews. About 90 percent of the people they talked to had eaten iceberg lettuce at the same restaurant chain. FDA's traceback pointed to iceberg lettuce grown on a single farm in Mexico and supplied through Taylor Farms. FDA said the implicated farm represents less than one percent of the U.S. iceberg supply.

FDA then reported a positive cyclospora result on the lettuce itself. Taylor Farms recalled shredded iceberg and salad sold through Walmart and foodservice.

The next day, FDA pulled the result back. Its lab experts re-reviewed the sample and concluded the finding "does not represent true amplification" and should be treated as a false positive. Cyclospora is hard to detect, and the molecular test that flagged the sample could not be confirmed.

The recall did not get reversed. The outbreak investigation still pointed at the same lettuce, with more than 90 hospitalizations and thousands of additional suspected illnesses under review across dozens of states.

The test was never the case

The evidence that implicated the lettuce was the outbreak investigation, not the sample. Patient interviews and traceback did the work. The positive result arrived late and left early, and the conclusion didn't move when it disappeared.

This is the part operators get backwards. A single positive feels like proof, so a single negative feels like a clearance. Neither is true. A lot can test negative and still be the vehicle, because contamination is rarely uniform and a sample plan catches a fraction of a fraction. A lot can throw a positive that a second method can't confirm, the way this one did.

Your incoming COA works the same way. A negative result on a sampling plan you didn't design and can't see is not the same thing as a clean lot.

Where the 2 a.m. decision goes wrong

Most recall decisions get made under time pressure with incomplete data, and most facilities improvise them. Someone forwards a positive from a customer, a third-party lab, or a regulator, and the room argues about whether to pull product while the clock runs. That argument should have happened months earlier, on paper. We've written before about the first 24 hours after a supplier causes a recall, and the pattern is always the same: the facilities that move cleanly already decided how they'd move.

Write the decision rule before you need it. What triggers a hold. What triggers a market recall. What a single presumptive or molecular positive means versus a confirmed one. Who has the authority to pull the trigger at midnight without waiting for a callback. If those answers live in someone's head, they change every time the pressure changes.

Taylor Farms moved fast on a regulator's positive during an active outbreak. That was the right call, and the later retraction doesn't make it wrong. Fast was correct because the epidemiology already existed. The mistake would have been waiting for a confirmatory test that, as it turned out, would have pointed the wrong way.

What to check this week

Pull your recall plan and find the sentence that tells you what to do with a single unconfirmed positive. Most plans don't have it.

Then run this drill. A customer emails you a molecular positive on a lot you shipped three weeks ago. Their retest is pending. Walk it through. Do you notify? Do you hold your remaining inventory? Do you initiate a recall now or wait for confirmation? Who signs off? Time the decision. If it takes more than an hour, or the answer depends on who's in the room, your plan has a gap a real event will find.

Do the same for the inverse. A lot you were worried about comes back negative. Does that close the file, or do you still hold on the epidemiology? If negative auto-closes, you've built the same single-result trap in reverse.

A recall program isn't the plan document. It's whether the decision is already made when the positive lands. Beacon keeps the recall decision tree, the traceability records, and the hold authority in one place, so the call at midnight follows the rule you wrote at noon. If your recall plan still lives in a binder, see how it works.