RecallMatching

Evidence-first recall review

Recall candidates.Human decisions.

Match catalog records to official notices, inspect field-level evidence, and record every decision.

RecallMatching review workspace comparing a catalog item with an official CPSC recall notice

Catalog CSV and API inputs

Supported CPSC and openFDA sources

Field-level evidence

Documented review decisions

From catalog row to reviewed decision

RecallMatching organizes the evidence around a possible match so your team can make a traceable decision.

  1. Send product records

    Submit a CSV or structured API request with the identifiers your catalog already has.

  2. Surface recall candidates

    RecallMatching compares those fields with supported CPSC and openFDA recall records.

  3. Inspect the evidence

    Review exact matches, missing identifiers, source freshness, and the official notice.

  4. Record a human decision

    A reviewer decides whether to match, reject, or escalate the candidate and leaves an audit trail.

The review boundary

The system finds evidence. A person makes the decision.

RecallMatching does not determine whether a product is safe. It surfaces possible matches, shows why they appeared, and gives your reviewer a controlled place to decide what happens next.

Every candidate keeps the context visible

  • Submitted and official values shown side by side
  • Missing identifiers called out before a decision
  • Direct links to the official recall source
  • Reviewer, timestamp, note, and outcome preserved

Built for catalog teams that need a defensible process

Start with a real, non-sensitive workflow and help shape the product around the records, volume, and review controls your team needs.

Early access