About FoodRecallWatch
What just got recalled?
What we do
FoodRecallWatch tracks every FDA recall as it is posted and explains who is affected, what to do, and why it matters.
We focus on U.S. FDA food, drug, and device recalls. Every page on foodrecallwatch.com is built from the FDA openFDA enforcement-report API, cited and linkable so readers can trace any number back to its source.
Who runs this
FoodRecallWatch is built and maintained by the FoodRecallWatch Team. We're a small group working on making public U.S. FDA food, drug, and device recalls data easier for non-specialists to read. If you have a correction, a data tip, or a question about how a number was derived, the contact email below reaches us directly.
Who this is for
FoodRecallWatch is built for parents, caregivers, grocery shoppers, reporters, and food-safety researchers.
Why this exists
Public data on U.S. FDA food, drug, and device recalls is technically free, but practically locked behind file formats, acronyms, and paywalled dashboards. FoodRecallWatchexists to close that gap: take the raw federal and public-sector data, and turn it into pages a normal person can read in thirty seconds.
How we work
- Primary source only. We pull from the FDA openFDA enforcement-report API and cite the exact dataset and version on every page.
- No invented numbers. If a figure is not in the underlying public data, it does not appear on foodrecallwatch.com. We never generate synthetic statistics to fill gaps.
- Methodology, in plain English. We poll the openFDA enforcement-report API for new food, drug, and device recalls, classify each by product type, hazard class (I, II, or III), distribution geography, and recall stage. Pages surface the full FDA enforcement-report text plus a short readable summary.
- Refreshed on a schedule. Refreshed daily; most newly posted FDA recalls appear on the site within 24 hours.
- Corrections welcome. Readers flag issues all the time. When the source fixes a record, FoodRecallWatch follows.
Known limitations
FDA posts many recalls days or weeks after the company initiated them voluntarily, so the date-posted is not the date the product actually left shelves. Local retailer-only recalls that do not cross state lines often never appear in the federal feed.
Why FDA recall data deserves a public-facing home
The FDA openFDA API publishes every recall the agency has overseen — food, drug, device, biologic, cosmetic. Each recall record includes the product, the manufacturer, the distribution geography, the hazard class (I, II, or III based on health consequence severity), the reason for recall, and the recall stage. The data is comprehensive and free.
The presentation problem is that the FDA’s own openFDA portal is built for regulators and researchers, not for parents, grocery shoppers, or food-safety reporters trying to know what was just recalled. FoodRecallWatch presents the same data in a public-facing format. Every recall has its own page; every brand has a brand page rolling up its recall history; every state page surfaces recalls with distribution into that state. The data is the FDA’s; the value the site adds is the navigation.
How the pipeline pulls FDA data
The pipeline polls the openFDA enforcement-report API on a daily cadence. Most newly posted FDA recalls appear on the site within 24 hours of FDA classification. The pull touches every active recall and merges historical data so brand and ingredient pages show the multi-year recall history. The methodology page describes the API endpoints and the refresh cadence.
A practical detail: FDA classification can lag the announcement. A company might announce a voluntary recall to the media days before FDA finalizes the classification and posts the record to openFDA. The site captures the FDA record once it appears; for media-announced recalls in the meantime, the company’s own website and the FDA recall page are the right interim references.
Where FDA recall data has caveats
Three things to know. First, openFDA covers recalls only — products that have been pulled or are being pulled from sale. Products that received a warning letter or were the subject of a 483 inspection finding without proceeding to recall are not in this dataset. For the full enforcement picture, the FDA inspection-results database is the additional reference.
Second, recall reason language is FDA’s classification of the specific health risk. The same underlying product issue (undeclared allergen, contamination, mislabeling) can produce very different classifications depending on the population at risk. The pages report the FDA classification verbatim and explain what each hazard class means.
Third, distribution geography reports where the product was distributed, not necessarily where it was sold. A recall covering retail distribution into 30 states may have actual at-risk inventory concentrated in a smaller number of stores. The state pages capture FDA’s reported distribution; for verification of whether your specific store carries the recalled product, the retailer’s own customer-service channel is the more reliable reference. For households reading the recall record after the fact, the FDA recall page is the authoritative reference; the site is the navigation layer that makes finding the relevant recall fast rather than the source of truth.
Independence
FoodRecallWatch is an independent publication. We are not funded, owned, or directed by any of the agencies, companies, or organizations that appear in our data. Hosting is paid for by advertising — see our Privacy Policy for details — and we do not take paid placements, sponsored rankings, or "remove-my-entry" fees.
History
FoodRecallWatch launched in 2025 as part of a small portfolio of independent public-data sites. It has been maintained and updated continuously since.
Contact
Tips, corrections, data-partnership questions, and press inquiries: hello@foodrecallwatch.com. More options on our contact page.