Product Recall Checker

A recall can cover one model or production batch within a familiar brand. The identifying details in the notice determine which products need action, so checking a household item or stock for resale involves comparing the physical product with the full recall description. A matching brand name alone cannot establish that a particular item is affected.

The U.S. Consumer Product Safety Commission (CPSC) publishes recalls involving consumer products that may have a safety defect or violate a mandatory safety standard. A notice explains the affected products, the hazard and the remedy. The remedy may involve a repair, replacement or refund, with specific instructions and a contact for the responsible company. The appropriate action comes from that particular notice.

Several kinds of identification may help distinguish similar products. Each answers a different part of the comparison.

Brand and model

The brand and model identify the product described. A similar name or appearance does not establish the same model or variant.

Universal Product Code (UPC)

A UPC is a retail product code that may appear with a barcode. It helps compare products when the notice supplies one, but does not identify an individual unit.

Serial, batch or date code

These details can distinguish individual units or production groups. A notice may limit the recall to particular codes or manufacturing periods.

For a secondhand purchase, the seller's description may omit the model label or production code. Packaging, labels and the notice's description can provide the missing comparison. Sale periods, retailers, sizes and other distinguishing features also matter when the notice uses them to describe the affected products. Missing identification leaves applicability unresolved.

A hazard describes what could go wrong. Incident and injury information describes what was reported in that notice. A recall can carry a serious hazard even when no injuries have been reported. Likewise, an older announcement can still matter because recalls usually have no end date.

CPSC recall information covers U.S. consumer products within the agency's authority. It does not combine the separate recall databases for road vehicles, food or medicines, and it is not a worldwide register of every product-safety incident. A search with no matching notice therefore cannot certify safety, permission to resell, legal compliance or absence of a recall. Search wording, missing identifiers, date restrictions and the responsible authority can all affect what is found.

How to Use This Tool:

Start with the product label or a published CPSC recall number. The prefilled product name is Lolanta; opening the page does not run a search.

1. Enter a Product name or Recall number. Replace the example product name with your own search, or clear it when searching by recall number alone. Recall numbers must contain 2 to 20 digits, without a hyphen.
2. Open Advanced if you need to narrow the search by Manufacturer, First recall date or Last recall date. All supplied fields narrow the same search, and the dates refer to the original recall announcement. Leave a date boundary blank if it is not known.
3. Select Search recalls and wait for Candidate notices or an explanation of why the search could not finish.
   If Check search inputs appears, enter at least a product name or recall number, use a real calendar date and put the first date on or before the last. A manufacturer or date range alone is insufficient.
4. Select a candidate's recall number and title in Recall notices to open Notice details. Check the product description and available model, UPC, manufacturer and sale information. The first returned notice is selected initially.
5. Open the official CPSC notice and compare its complete identifying details with the item. Read its hazard, remedy and consumer contact before deciding what action applies. If the details are insufficient to identify the product, use the contact in the official notice to resolve the uncertainty.

Interpreting Results:

Candidate notices counts the notices accepted from the current response. One notice can describe several products or many affected units. The count is neither the number of matching physical items nor a total for the CPSC database.

• One or more notices: inspect the full recall number and product identification. Substring matches can include another product, and the first returned notice is not a relevance or safety recommendation.
• Zero notices: a complete accepted response contained no candidates for those filters. Check the product wording and any manufacturer or date restriction, then consult CPSC's official search if identification remains uncertain.
• Search incomplete, Search timed out or Search cancelled: there is no usable search result. These outcomes do not mean that zero notices matched.
• Not supplied: CPSC did not provide that detail in the returned record. A missing model, UPC, remedy or incident entry must not be interpreted as a negative finding.

Only supplied addresses that pass the check for an official HTTPS CPSC recall link become clickable notice links. Other addresses remain visible as text, and absent addresses are identified as missing. An accepted address does not establish that the page is reachable or that the notice applies to the item; use CPSC's official search if the link cannot be followed.

For a comparison record, the notice table can be copied or downloaded as CSV, exported as DOCX, or copied one row at a time. CSV and row copies retain complete recall numbers, CPSC IDs and supplied official URLs alongside the table's product and date information. DOCX adds CPSC attribution, retrieval time and search information. These table summaries do not replace the full hazard and remedy text.

Copy notice details preserves the selected notice's supplied identification, descriptions, hazards, reported incidents, remedy, contact and sale or supply details, together with its identifiers, dates, retrieval time and official URL. This is the more complete handoff when another person needs to inspect that notice.

CSV and row copies prefix potentially executable spreadsheet cells with an apostrophe. The check looks past leading whitespace and control characters before testing for =, +, - or @. The displayed facts and copied notice-detail text retain the source text without that spreadsheet-only prefix.

The Recall date distribution summarizes the same returned candidates. Its PNG, WebP and JPEG images preserve the chart, search terms and returned-candidate scope, while its CSV contains recall-year counts. A chart image or year-count file does not carry the full product identification and remedy needed to assess an item. If the chart is unavailable, the notice details remain usable and Retry chart can try drawing it again.

Technical Details:

Recall searching compares text and dates in published records. CPSC provides the matching notices; the returned product descriptions then support a separate comparison with the physical item. There is no automatic decision that a model, barcode or serial number belongs to the recall.

Lookup Core

Product and manufacturer searches are case-insensitive substring searches. A match can occur within a longer word, and a recall-number search can match digits within a longer recall number. Supplying several fields requires the corresponding conditions together.

Leading and trailing spaces are removed before the search. Embedded control characters are rejected. Calendar checks include leap days, and the first recall date cannot be later than the last. Model, UPC, serial number and product category are information to inspect in a notice, rather than separate search fields here.

The search sends one combined request. The complete response is checked for required notice identifiers and readable supplied details. Product identity is not independently confirmed, and the returned text is not re-matched locally to produce an exact-match verdict. No additional pages are fetched automatically, and a successful response does not independently establish that CPSC returned every potentially relevant notice.

Complete-response limits

A result must fit all of the following boundaries. Exceeding a limit rejects the response instead of displaying a shortened list.

Every notice must have a positive whole-number CPSC notice ID, a nonblank published recall number and a nonblank title. Duplicate notice IDs, unreadable responses or malformed supplied details reject the complete result. Missing optional details are allowed and remain explicitly unsupplied. An invalid source date has its own treatment below and does not by itself reject an otherwise valid notice.

If the response is too broad or too large, add a manufacturer, a more specific recall number or an original-recall date range. A malformed or incomplete response requires a fresh search or inspection through CPSC directly. Neither case produces a partial table that can be mistaken for a complete result.

Notice identity and source dates

The published Recall number identifies the recall announcement. The CPSC ID, also shown as Notice ID in the details, identifies its database record. These are distinct values. The recall-number search uses the published number, not the CPSC ID, and neither value is a product model or serial number.

Three dates describe different events. Keeping them separate prevents an updated older recall from being counted as a new recall.

Source dates remain visible as supplied. Valid calendar dates, including accepted date-and-time forms, use their written calendar day without conversion to the viewer's timezone. Missing dates show Not supplied. Invalid date text is retained with Invalid date supplied, so an impossible date is not silently repaired or replaced by the publication date.

Each accepted notice contributes once to the recall-year counts. A missing or invalid original recall date contributes to Date unavailable, shortened to No date on the chart. Thus the year counts, including unavailable dates, add up to the returned notice count. They do not measure affected units, incident frequency or relative danger. A newer retrieval can produce different candidates or details, so comparisons need the same search terms and date restrictions as well as the recorded retrieval times.

Privacy Notes:

Selecting Search sends the nonblank product name, recall number, manufacturer and date filters directly from your browser to CPSC. This requires a network connection. The lookup request omits browser login credentials and the referring page address, but CPSC still receives the search and may keep its own request records.

• Changes to search fields are reflected in the page address. Copying that address can reveal those values and restore the fields for another visitor. Returned notices, the selected notice and retrieval time are temporary and are not restored as a completed search.
• Loading or restoring search fields does not contact CPSC until Search is selected. There is no automatic retry. If CPSC is busy or limiting requests, wait before choosing Retry search.
• Editing any search field clears previous results and cancels a pending search. Starting another search also clears the previous result. A late response cannot replace results for the current search.
• Cancel stops waiting and keeps no result from that search. It cannot withdraw search values already sent to CPSC.
• Copied text and downloaded files remain wherever you save or paste them. They are records of the retrieved information and do not update automatically when CPSC changes a notice.

Worked Examples:

These cases explain a published recall and the treatment of source dates. They do not report a new live lookup or promise a fixed number of search results.

References:

• About Us FAQ, U.S. Consumer Product Safety Commission.
• Products Under the Jurisdiction of Other Federal Agencies and Federal Links, U.S. Consumer Product Safety Commission.
• CPSC Recalls Retrieval Web Services Programmer's Guide, version 1.2, U.S. Consumer Product Safety Commission, March 11, 2016.
• Children's Bathrobes Recalled Due to Burn Hazard and Violation of Flammability Regulations, U.S. Consumer Product Safety Commission, February 8, 2024.