TRANSPARENCY, BUILT IN
What’s here.
What may be missing.
RecallMenu brings source records together. It cannot guarantee every recall, every product, or every affected store.
You are viewing the configured recall database. Freshness depends on successful ingestion jobs. A successful fetch does not mean an agency published new information today.
FDA enforcement
Import status: Last attempt succeeded
Last successful retrieval: Sep 28, 2026
Last attempt: Sep 28, 2026 · Records processed: 29,415
Agency dataset date: Sep 25, 2026
Complete export processed; records are not unique recall events.
FDA public notice
Import status: Last attempt succeeded
Last successful retrieval: Sep 28, 2026
Last attempt: Sep 28, 2026 · Records processed: 16
Current RSS window processed; not an all-time public-notice archive. Distribution evidence: 1 notice(s) have an unavailable or unreadable page/attachment; retained record-level status.
USDA FSIS
Import status: Last attempt succeeded
Last successful retrieval: Sep 28, 2026
Last attempt: Sep 28, 2026 · Records processed: 1,239
Returned API dataset processed; translations consolidated by recall identity, preferring English. Historical availability is defined by FSIS. Distribution evidence: 1 notice(s) have an unavailable or unreadable page/attachment; retained record-level status.
Three distinct sources
| Source | What it provides | Limits |
|---|---|---|
| FDA enforcement archive | Publicly releasable food enforcement records from 2004 onward; imported using the full export. | Updated weekly. Not a live alert feed or a reliable tracker of current recall status. |
| FDA public notices | Food-related entries verified against the agency’s public notice pages. | The RSS feed is a rolling window. Older notices are retained after import, but the initial feed does not provide an all-time archive. |
| USDA FSIS API | Meat, poultry and egg-product recalls and public health alerts. | Availability depends on the agency endpoint. A public health alert is not necessarily a recall. |
How to read these records
- Records are not unique recall events. One FDA event can contain many product records. A press notice may describe the same event. We preserve separate source identifiers instead of automatically merging uncertain matches.
- Dates have names. “Latest” sorts by publication or report date, falling back to initiation date. A newly published record can describe an older recall.
- Locations have roles. The recalling firm’s address, product origin and distribution are different facts. Unknown origin is not inferred from the firm’s address.
- Categories and hazards are browsing aids. They are inferred from text. Agency classification is displayed separately and is never guessed.
- State filters are incomplete. They use distribution statements and captured official location evidence, including supported retailer lists and attachments. The importer separates company addresses from distribution and attempts to exclude states explicitly named as unaffected. Nationwide wording is handled separately; ambiguous or unparsed text may remain unknown. Read the original distribution statement; missing states do not rule out exposure.
- Missing fields stay missing. UPCs, lot codes, retailers, dates and origin countries are not universally available. A product with the same brand name is not automatically an affected lot.
Coverage boundaries
“Distribution: see source” means the stored record has no usable distribution location summary. It does not mean the product had no affected locations. Check the official notice and its attachments; extraction and agency publication can both be incomplete.
State-only, retailer-only and manufacturer-only notices may not appear. Historical public-notice coverage is limited to notices imported since collection began. This is a recall index, not a catalog of every food sold in the United States.
FDA cautions against using its enforcement data to issue public alerts or track recall lifecycles. RecallMenu uses it as a searchable reference archive and separates optional enforcement archive additions from current public-notice updates in subscriber digests. Archive additions are not presented as newly initiated recalls or live status alerts.
Read the FDA source guidance, bulk-download guidance and current FSIS notices.
Sales descriptions and recall comparisons
When a matching sales description is found, we compare its claims against the official recall reason. Each published comparison links both sources and shows when it was checked. Automated matching and explanations can be wrong; verify the source text. A matching product listing does not show whether that seller has recalled lots, and we do not infer intent. Where no verified comparison is available, we show the recall-source reason instead.