CPSC Recall Matcher: Check Seller Catalogs avatar

CPSC Recall Matcher: Check Seller Catalogs

Pricing

$200.00 / 1,000 completed catalog scans

Go to Apify Store
CPSC Recall Matcher: Check Seller Catalogs

CPSC Recall Matcher: Check Seller Catalogs

Compare up to 100 seller catalog items with recent U.S. CPSC recalls. Get source-linked possible matches by UPC or model, coverage counts and clear limits. No source credentials needed.

Pricing

$200.00 / 1,000 completed catalog scans

Rating

0.0

(0)

Developer

Althor Labs

Althor Labs

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

Seller catalog CPSC recall matching

Compare a catalog of up to 100 seller-owned products with recent U.S. Consumer Product Safety Commission (CPSC) recall notices. The Actor returns source-linked possible matches and the notice fields used to identify them.

Input

Provide inline JSON rows or choose a key-value store using the READ-only resource picker and name one JSON or CSV key. Each row needs a unique seller_sku; upc, brand, model, and product_name are optional. Catalog input is limited to 100 rows and 1 MiB. A rolling recent seven-day publication window is selected automatically. An explicit window may be supplied with both date bounds and must span no more than seven days.

The Actor queries the fixed CPSC Recalls API endpoint. It does not fetch URLs from catalog input or open recall notice URLs. One source response is limited to 2 MiB, 20 seconds and 500 notices. HTTP 403 and 429 end the scan. A server error may receive one retry after at least 60 seconds. The adapter honors Retry-After up to five minutes, then stops. A successful response is cached for up to 168 hours for the same date window in an Actor-owned key-value store. The cache best-effort spaces requests by at least 60 seconds in that Actor context. Concurrent runs can race, so this is not a cross-run or global request-spacing guarantee.

Output

One dataset item contains retrieval time, the queried window, coverage counts, identifier availability, per-SKU statuses and linked candidate notices. A possible match requires an exact 12 to 14 digit UPC or an exact model value. Model and official Description identifier matches also require a separate brand or full product-name context match. A product-name or generic-word overlap alone never creates a candidate. Description-based evidence includes its source field and a short excerpt.

Example from one cloud run

This excerpt is from an actual cloud run using the prefilled synthetic SKU EXAMPLE-001 and live CPSC notices in the 2026-10-14 through 2026-10-21 window. It returned no candidate; this does not determine product safety.

{
"queried_window": {
"LastPublishDateStart": "2026-10-14",
"LastPublishDateEnd": "2026-10-21"
},
"retrieval": {
"retrieved_at_utc": "2026-10-21T23:08:07.326108Z",
"earlier_recalls_omitted": true
},
"results": [
{
"seller_sku": "EXAMPLE-001",
"status": "no_candidates",
"matches": []
}
]
}

The output explicitly omits recalls published before the selected window. The scan does not cover historical recalls outside that window, promise a source update schedule, guarantee matching completeness, determine product safety, or provide legal advice. A no-match result does not establish that a product is safe. Confirm candidates against the official notice.

CPSC material is attributed. This product is not affiliated with or endorsed by CPSC. Notice photos and contact details are excluded.

Price

Pay-per-event pricing is active at $0.20 per completed catalog-window-scan. One event covers 1-100 seller-owned SKUs in one selected publication window, including scans with zero matches. There is no Actor-start or dataset-item fee; standard Apify platform usage is included in the event price.