Upload your purchase history. ReCheck matches it against 68,580+ FDA recall records and shows you exactly which products need attention — and why.
Every recalled device that goes undetected in a hospital is a risk to someone's life. ReCheck exists to close the gap between an FDA recall announcement and the moment a clinician stops using that device.
Hospitals manage tens of thousands of unique products across departments, warehouses, and surgical trays. Manually cross-referencing each one against FDA recalls is slow, error-prone, and often happens too late. We built ReCheck so that no patient is ever exposed to a recalled device because the paperwork didn't keep up.
The average hospital uses 5,000 to 10,000 unique medical devices. When a recall hits, the question isn't whether you have it — it's how fast you can find out.
The problem ReCheck was built to solveUpload your data, let ReCheck cross-reference it against the FDA recall database, and review a single sortable report that tells you which devices need attention first.
Drop in an Excel or CSV of purchase history. ReCheck auto-detects your columns or lets you map them. A downloadable template with the required layout is available on the upload page.
Catalog numbers are normalized and checked against labeled REF, CAT, UPN, and model codes in every FDA recall. Manufacturer names and product descriptions are scored to boost confidence and reject false positives.
An Excel workbook grouped by urgency, with recall class, match score, a plain-English recommendation, and a direct link to the FDA record. Stored inventories are also re-checked automatically when new recalls post.
Results are grouped first by FDA recall class — the severity level FDA assigns to each recall — then within each class, sorted by match confidence. Class I always sits at the top of the report.
Reasonable probability of serious adverse health consequences or death. Always appears at the top of the report. A Class I match with strong confidence triggers a "Stop Use" recommendation and a push notification.
May cause temporary or medically reversible adverse health consequences. Remote probability of serious consequences. Reviewed after Class I; handle according to the recommended action on each line.
Unlikely to cause adverse health consequences but violates FDA law or regulation. Usually labeling or documentation issues. Lowest priority on the report but still worth tracking for compliance records.
Every matched line gets a score from 0 to 1 based on how well your catalog number, manufacturer, and description line up with the recall. Within each class group, higher-confidence matches appear first.
Two columns are required to run a match. The rest are optional but make the report more useful — more detail per line means better scoring and clearer triage.
| Column | Status | What it's used for |
|---|---|---|
| Catalog Number | Required | Primary identifier matched against labeled codes in each FDA recall. The match will not run without it. |
| Manufacturer Name | Required | Used to confirm matches and suppress false positives when the same catalog number shows up across unrelated vendors. |
| Mfr Catalog Number | Recommended | Secondary catalog number (manufacturer's own code vs. your internal SKU). Widens the match surface so more recalls are caught. |
| Product Description | Recommended | Text from your line item. Used for description similarity scoring and to display human-readable context in the report. |
| PO Number | Recommended | Grouping key in the report so you can trace each match back to the purchase that brought it in. |
| PO Date | Recommended | Used in the timeline view to show when affected devices entered your inventory. |
| Unit Price | Recommended | Rolled into the financial impact summary on the report. |
| Vendor Name | Recommended | Distributor or supplier. Helps distinguish manufacturer from reseller when issuing recall notices to your supply team. |
Export from your ERP, your spend analytics tool, or any spreadsheet. As long as the required columns are present, ReCheck will read it.
First sheet is read. Headers on the first row. Multi-row header exports are supported via the column mapper.
Comma-separated values with a header row. Common delimiters and BOM encodings are auto-detected.
Positional item-master files (one record per row, pipe-separated) are supported for bulk catalog imports.
Upload your file and get a prioritized recall report in under two minutes.
Start Recall ScreeningAI-powered recall & compliance help