What each seal saw for the first time

260 recalls across 45 seals.

This is an additions ledger and nothing else. It deliberately has no departures column: a recall leaving our snapshots means newer reports pushed it past the hundredth row of the window we fetch, not that FDA removed it. Publishing that as a removal would turn our own coverage limit into a market event.

What this archive is, exactly. Once a day we seal one copy of a single openFDA request: the 100 most recently reported food enforcement records. That is a rolling window, not the enforcement database. A recall that entered and left the window between two of our seals is not here at all, and a recall missing from the newest seal was pushed out by newer reports — it was not withdrawn by FDA. These pages are a record of what openFDA served us on each date. They are not a complete list of food recalls and must not be read as one.

Days we did not seal. 45 seals span 47 calendar days, so these days inside the span have no sealed copy: 2026-07-04, 2026-07-15. A missing day means we did not read the API. It does not mean nothing changed, and a change that landed and was superseded across one of those gaps is not in this archive.

How often the source actually moves. Our 45 fetches returned only 7 distinct payloads — openFDA refreshes this endpoint roughly weekly, so most daily seals record an unchanged file. A change can only be witnessed between two seals that straddle a refresh.

Seal	Recalls seen for the first time
2026-08-04	11
2026-07-28	26
2026-07-22	15
2026-07-14	9
2026-07-07	45
2026-06-30	55
2026-06-23	99

A large first-seal number is an artefact of the archive opening, not a busy week: everything in the window on day one was new to us.

Get told the day a recall status moves for your suppliers

openFDA serves the current status and nothing else, and the field that marks a termination only shows up once the termination has already happened — so an imminent change is invisible in a single fetch. We seal a dated copy every day and can see the move the day it lands. Leave your email and we'll tell you when a recall in your suppliers changes, with what it said before.

Email me recall status changes →

Work email only. No newsletter, no obligation.

Prefer to just buy it? See what we sell off this archive, priced, with a sample of what changed.

Compiled from dated copies of the U.S. Food and Drug Administration's public openFDA food enforcement API (public domain, CC0 1.0). Data provided by the U.S. Food and Drug Administration. Values are reproduced exactly as openFDA served them on the date shown and may since have changed; FDA is the authority on the current status of any recall. openFDA data is provided as-is with no warranty, is not a certified regulatory record, does not represent FDA's official position, and must not be used as the sole basis for a compliance decision. Always verify against the FDA enforcement report before acting.

Food recall record home · Status changes we witnessed · How this is collected · FDA recalls · US Tech Automations.