Skip to main content
Thirdwatchthirdwatch
E-commerce & products

Compare CPSC, FDA, and NHTSA Recall Data

Choose the correct US recall source for consumer products, regulated health products, and motor vehicles.

Jul 21, 2026 · 2 min read · 316 words
See the scraper →

“Recall data” is not one uniform US dataset. Consumer products, foods and regulated health products, and motor vehicles sit in different systems with different identifiers, terminology, and decision contexts. The CPSC Product Recalls Scraper covers CPSC consumer product notices; a complete compliance architecture must route other products to their proper authority.

Understand the boundaries

CPSC notices commonly describe consumer products, hazards, remedies, incidents, companies, countries, and images. They are well suited to retail and marketplace screening for goods such as furniture, appliances, toys, and tools.

FDA recall and enforcement records cover areas including food, drugs, medical devices, cosmetics, and related regulated products. Their fields often emphasize classification, recalling firm, distribution pattern, reason, product description, and status. Teams handling supplements, packaged food, or devices should use the applicable FDA source rather than assuming a CPSC keyword search is complete.

NHTSA vehicle recalls center on campaign numbers, manufacturers, components, consequences, remedies, affected units, and vehicle configurations. Model-level searches can support fleet or catalog research, while a specific vehicle requires an official VIN-level check.

For a combined warehouse, create a common envelope containing source agency, source record ID, record type, publication date, title, description, canonical URL, collection time, and raw-source reference. Then retain agency-specific tables for products, firms, hazards, classifications, campaigns, vehicles, and remedies. Do not map unlike fields into a generic “severity” value unless a documented methodology supports it.

Route catalog items by jurisdiction and allow overlap where product boundaries are genuinely uncertain. Preserve the authoritative link and show users which agency produced each record. Deduplicate only within an agency identifier unless there is explicit evidence that two notices describe the same event.

The goal is not one cosmetically uniform recall table. It is a traceable system that sends each product to the right source, retains the details needed for confirmation, and avoids dangerous gaps created by treating CPSC, FDA, and NHTSA as interchangeable feeds.

Frequently asked questions

Does one US database contain every recall?

No. Product jurisdiction and record structure differ across CPSC, FDA, and NHTSA.

Can records from all three sources share one schema?

Use a common envelope, but preserve source-specific fields and identifiers instead of forcing false equivalence.

Related

Try it yourself

100 free credits, no credit card.

About 30 real searches. Add the MCP to Claude or Cursor in two minutes.