Track Food Safety Recalls by Company

Class I is the FDA classification for the highest-risk recall situations. Query status:Ongoing, select Class I, and set a recent report-date floor. Then compare product codes and distribution details with your own catalog.

Use the FDA Recalls Scraper to make that search reproducible. Save the exact filters and result cap as a Task rather than editing a one-off query every time.

Turn the search into a decision

Match on product code, lot, model, or other identifiers in code_info before escalating. Company and product-description text are useful for discovery but can overmatch unrelated inventory.

Create explicit inclusion columns such as is_in_scope, owner, and review_reason. Keep them in a derived table, not in the raw source rows. This makes it possible to rerun qualification rules without losing the original evidence.

Sample ten included and ten excluded records. If exclusions are caused by missing upstream fields, do not silently treat those fields as false. Put them in a review queue or document the assumption.

Refresh without creating duplicates

The record key is product_type plus recall_number. Upsert on that key and record the collection timestamp separately. A recurring workflow should distinguish a newly published record from an older record whose metadata changed.

Enforcement records change during an investigation. Refresh ongoing recalls and retain code_info and distribution_pattern. A company-name match alone is not enough to decide whether inventory is affected.

The practical payoff is a smaller, explainable queue. The source query finds candidates; the qualification layer decides which candidates deserve attention. Mixing those two jobs into one opaque keyword search makes both harder to audit.