199 Recalls: Our First Monthly FDA Edition

This is the July 2026 edition of US Tech Automations' monthly FDA food recall tracker — the first dated entry in what will become a running monthly series, built from the same daily FDA-enforcement clock behind our evergreen recall tracker. As of this edition's snapshot date, July 13, 2026, that clock had captured 199 distinct food recalls.

This is the first dated edition in this series. There is no prior monthly edition to compare it against yet, so this report states only what this edition shows — it does not claim a trend, an increase, or a decrease relative to any earlier month.

TL;DR for This Edition

• 199 distinct food recalls on file as of July 13, 2026, the earliest dating back to an initiation of December 15, 2025.

• 75 recalls (37.7%) are Class I, the FDA's most serious tier.

• 187 recalls (94.0%) remain open in FDA paperwork terms.

• 152 recalls fall inside the trailing 90-day window ending on this edition's snapshot date.

• Idaho-based firms lead the state ranking with 41 recalls, a 20.6% share — a fact about company headquarters, not about food safety in Idaho.

Severity: Class I, II, and III This Month

Class II is the largest single tier this edition, at 47.2% of all 199 recalls. These are the FDA's own classifications, assigned by the agency at the time each recall was initiated — nothing here is a severity judgment made by US Tech Automations.

Status: How Much of This Month's Recall Activity Is Still Open

94.0% of this edition's recalls are still open, meaning the FDA has not formally closed its file on them. Open is a paperwork state — it does not mean any specific product is still available for purchase anywhere.

This Edition's State Ranking, by Recalling Firm

Idaho tops this edition's ranking at 41 recalls, a 20.6% share of all 199 captured. The state column names where a recalling company is legally headquartered, never where the food was sold, eaten, or where anyone got sick. A single Idaho-based firm's recalled products are routinely shipped and sold nationwide, in every state — the ranking above is a map of company addresses, not a map of contamination.

Reading this table as a food-safety ranking of states is the single most common misreading of recall data. Idaho's position at the top reflects where recalling firms are based, not a judgment about food produced, sold, or eaten anywhere in the state.

Why This Edition Doesn't Compare Itself to Anything Yet

Because this is the first dated monthly edition in the series, there is no earlier July, June, or any other prior month's edition of this specific dated series to measure against. A future edition of this series will be able to show whether Class I's 37.7% share moved, whether Idaho stays at the top of the state ranking, or whether the open-recall share shifts from 94.0% — but none of that comparison exists yet, and this edition does not manufacture one.

Only once a second dated edition exists will a month-over-month comparison have any meaning, and even then, this series will only ever compare consecutive dated editions on the same window definition, never mix a cumulative count against a narrower one.

What a Second Edition Will Be Able to Show

Once this series has run for a second month, a reader will finally be able to check whether Idaho's 41-recall lead in the state ranking is a persistent pattern or a one-month artifact, and whether the 94.0% open-recall share is typical or unusually high. Neither question can be answered from a single edition alone, no matter how the numbers are read.

The evergreen version of this report already updates continuously against the same underlying clock, if a reader wants the current picture rather than a fixed monthly snapshot while this dated series is still building its own history. The two are built from the same feed; they simply answer the "as of when" question differently — one is always current, the other is frozen to a stated date and never quietly redrawn.

A dated edition and an evergreen report drawn from the same clock will usually show close but not identical numbers, because the evergreen version keeps moving after a dated edition is sealed. Neither is more accurate than the other — they answer "how many recalls, as of what date" differently on purpose.

Method in Plain English

One recall is one FDA recall_number, and a single recall can cover anywhere from one product to dozens of related products sold under different labels or sizes — this report counts recalls, not products pulled from shelves.

Each recall is counted once, using its most recent observation in the feed, so a recall whose status updates daily is not double-counted. Every count in this edition is a verbatim count of distinct FDA recall_numbers our own clock actually captured; nothing is estimated, modeled, or inferred beyond the FDA's own class and status labels. This edition covers FDA-regulated food only — meat, poultry, and egg products sit under separate USDA/FSIS jurisdiction and are not part of this feed.

This edition re-shapes one already-sealed capture of the FDA-enforcement clock; nothing was fetched fresh to build this page. Our rates-and-labour report applies the same sealed-capture discipline to two different federal data series, if a second example of the method is useful.

A recall's class and status can both change between the moment it is first captured and the moment this edition is sealed — a Class II recall on file today can later be reclassified, and an ongoing recall can later be terminated. This edition freezes each recall's class and status exactly as they stood on July 13, 2026; a later edition reading the same recall_number could show a different value for either field, and that would reflect the FDA's own record changing, not an error in either edition.

This is also why a dated edition carries its own frozen sha, separate from the live clock's most recent read. Anyone comparing two editions of this series later can be confident each one describes exactly what the FDA's feed showed on its own stated date, rather than whatever the feed happens to show at the moment someone reads the page.

A reader checking this edition next year will see the same 199 recalls, the same 75 Class I count, and the same 41-recall Idaho lead that this edition shows today — none of that is meant to move after publication, even as the live, evergreen version of this report keeps updating in parallel.

Put the Recall Data to Work

A compliance lead or a regulatory-affairs manager tracking supply-chain exposure across food categories cannot get a monthly, dated, FDA-label-accurate count like this from the agency's own portal without building a scraper and a classification layer first. US Tech Automations runs the daily clock, keeps the FDA's own class and status labels intact, and republishes this dated edition every month on a fixed schedule instead of someone re-running a manual pull whenever the question comes up again. Our formation-index report applies the same dated-edition discipline to a different first-party dataset, if a second monthly series is useful context.

Frequently Asked Questions

Q: How many food recalls does the July 2026 edition track?
A: 199 distinct recalls, as captured by our FDA-enforcement clock as of this edition's July 13, 2026 snapshot date.

Q: Is this edition higher or lower than the previous month?
A: There is no previous dated edition of this monthly series to compare against — this is the first one. No trend, increase, or decrease is claimed anywhere in this report.

Q: What share of this edition's recalls are the most serious kind?
A: 75 recalls, or 37.7%, are Class I — the FDA's own most serious tier, defined as a reasonable probability of serious health consequences or death.

Q: Does Idaho's position at the top of the state table mean Idaho has a food-safety issue?
A: No. The state column reflects where the recalling company is legally headquartered, not where the food was sold or eaten. Idaho's 41 recalls in this edition almost certainly trace to a small number of firms based there whose products are shipped and sold nationwide.

Q: Will future editions of this series show a trend?
A: Only once at least two dated editions exist can a month-over-month comparison be shown, and even then only between editions using the same window definition — never a cumulative count compared against a narrower recent-window count.

Q: Can a recall's class or status change after this edition is sealed?
A: Yes. The FDA can reclassify a recall or move it from ongoing to terminated after this edition's July 13, 2026 snapshot date. This edition freezes each recall's class and status exactly as they stood on that date; a later edition reading the same recall could show a different value, reflecting the FDA's own record changing rather than an error here. That is a normal part of how a dated series works over time.

Method and Provenance

Every figure in this edition is read directly from our own sealed FDA-enforcement clock, re-shaped from an already-sealed edition dated July 13, 2026. This edition covers the U.S. FDA's openFDA food enforcement feed only, deduplicated to 199 distinct recall events — not USDA/FSIS meat, poultry, and egg recalls, and not drug or device recalls. Every count is a verbatim count of distinct FDA recall_numbers the clock actually captured; nothing is estimated, modeled, or inferred beyond the FDA's own class and status labels.

Source: US Tech Automations Research — FDA Food Recalls series, July 2026 edition, from our own FDA-enforcement clock (openFDA food enforcement feed).