By the Time FDA Names the Food, Your Lot Is Gone

FDA closed a 14-case E. coli O157:H7 investigation this summer. Its note says the product was already beyond shelf life by the time FDA identified romaine lettuce as the likely source. FDA named no grower or processor in its public table, and the row lists no recall. Eight more investigations are open right now with the food listed as Not Yet Identified. Nothing in that table promises you a phone call.

What the FDA table says this week

FDA's outbreak investigation table, current as of September 10, lists eight active investigations where the product is still Not Yet Identified. Together they carry 569 confirmed cases.

Salmonella Newport at 109 (ref 1403). Salmonella Oranienburg at 99 (ref 1387). Four separate Cyclospora investigations at 231, 38, 22 and 18 (refs 1392, 1385, 1398, 1384). Salmonella I 4,[5],12:i:- at 43 (ref 1402). Listeria monocytogenes at 9 (ref 1379). Traceback is underway on every one. None of them has a food. On ref 1384 the outbreak itself is already over and the investigation is still open with nothing named.

The romaine case is the one that closed. FDA posted ref 1382 on July 1, CDC declared the outbreak over on July 29, and FDA's note reads: "By the time romaine lettuce was identified as the likely source, product was beyond shelf life." Fourteen people and a commodity named. FDA did not name a grower or processor in its public table, and the row lists no recall or product-specific advisory.

That ending is normal. Of the 26 investigations FDA posted in 2025 and has since closed, twelve closed with the product listed as Not Identified, covering 286 confirmed cases. Nearly half.

A named source doesn't settle it either. CDC reported 19,595 laboratory-confirmed cyclosporiasis cases acquired in the United States between May 1 and September 8 of this year, against 1,180 between May 1 and August 31 of last year. The lettuce was named as an outbreak source, and CDC says that seasonal total includes both that outbreak, which recently ended, and cases not linked to it.

The read that gets you hurt

The easy read is that this is a produce problem. Farms, water, field-level contamination, a part of the chain you don't own.

That's the wrong lesson. The pattern in that table is about how much an investigation can settle before the trail goes cold. A closed row with no food named tells you what the investigation could establish, not what happened.

Now put your own plant in one of those rows. Nothing on the page promises a direct notification, and nothing in it would tell you that your product had been looked at and set aside. The outbreak can run its course and the file can close while you're reading the same table as everyone else.

The clock is the reason, and it varies by pathogen. CDC says it usually takes 3 to 4 weeks to determine whether a sick person is part of an outbreak, and its Cyclospora page puts about six weeks between the start of symptoms and CDC receiving the case information. Interviews and traceback both take time on top of that. In the romaine case, FDA said the product was beyond shelf life by the time it had a likely source.

Four signals that reach you before a phone call does

Four early signals you can control are already inside your own plant. Count how many of them you actually have.

Environmental monitoring positives you've trended. A site-level history you can read, so the third positive at the same drain reads as one pattern instead of three separate events. That pattern is the reason to investigate for harborage or a resident strain; WGS and the investigation are what establish whether the isolates are related. It's a warning you're already paying a lab for.

Complaint clusters you read weekly. Three "tasted off" calls on the same product in ten days is a signal. The same three complaints filed across three months in three folders is filing. Complaint handling only works as an early-warning system when someone reads the set instead of the ticket.

Supplier lots you can pull in an hour. One supplier lot code in, every finished lot it went into and every customer who received them out. Time that pull, because the elapsed time is what you're measuring.

Finished-product retains you kept past the code date. This is the one that decides whether you have anything left to test.

What "beyond shelf life" means for your retains

FDA's shelf-life sentence is the operator lesson in one line: the product that could have answered the question was gone before the question got asked.

An outbreak question arrives late on CDC's own intervals, weeks after illness onset at best. A retain program sized only to shelf life may discard the product before that question arrives.

So set the retain hold by the investigation clock instead of the consumer date. Shelf life plus the reporting lag, and hold longer on anything with a raw agricultural input or a shared line. If your retain schedule discards at the code date, then by the time anyone asks, you have a lot code and no product behind it.

21 CFR 117.315 requires records under the preventive controls rule to be retained for at least two years after preparation, and other than the food safety plan, those records may be stored offsite if they can be retrieved and provided onsite within 24 hours. For foods on the Food Traceability List, FSMA 204 requires two years of traceability records and availability to an authorized FDA representative within 24 hours of a request, or another reasonable time FDA agrees (21 CFR 1.1455(c) and (d)). FDA has proposed moving the compliance date to July 20, 2028, and Congress has directed FDA not to enforce the rule before that date. Two years of records against a retain program that ends at the code date is a gap you chose.

The horizon check

Run this today and time it. Three pulls and one question, one hour.

Pick one supplier lot received 90 days ago. List every finished lot that used it and every customer who got those lots. Time it.

Pick one environmental monitoring site. Pull its last 18 months of results as a series, not as individual reports. Can you see whether this year looks like last year?

Pick one product. Pull every complaint on it for the last 12 months in date order. Does a cluster show up, or do you get a folder?

Then the retain question. For a lot you shipped 60 days ago, is there still physical product on the shelf?

If the answers are "most of a day," "not as a series," "a folder," and "no," you have a horizon problem. Your ability to look backward is shorter than the time an investigation takes to develop, and that gap is the capability worth testing before one reaches you.

Go time the lot pull. An hour from now you'll know how long that one takes, and the retain and trend checks tell you the rest.

Beacon keeps environmental monitoring trends, complaint records and lot genealogy in one platform, so your team can read the signals together. If you want to see how that lines up against your own retain window, book a demo.