United States / Amazon Compliance / CPSC Recall Coverage
Amazon Matched Your ASIN to a CPSC Recall—Does It Cover Your Inventory?
Amazon restricts an ASIN. A CPSC recall notice defines a population of physical products. Those are not the same thing.
Before arguing that an Amazon ASIN was incorrectly matched to a CPSC recall, prove two facts: the product in hand is outside the recall criteria, and the same conclusion applies to all stock under restriction.
An ASIN may resemble a recalled product in Amazon’s catalog while the seller’s actual units fall outside the affected model, lot, serial range, package configuration, or country of manufacture. That possibility is not enough to challenge the restriction.
If a unit matches, stop selling and shipping it and follow the recall remedy. If a decisive identifier is missing, unreadable, or mixed across receipts, place the stock on safety hold. A defensible mismatch case begins with the live recall notice, same-unit photographs, and inventory records—not a catalog screenshot alone.
Amazon restricts a catalog record. A CPSC recall notice defines a population of physical products. Proving the second is outside the first takes two separate findings: what the unit in hand is, and what every restricted unit is.
This guide is a coverage audit. It does not replace Amazon’s case-specific instructions, the recalling firm’s determinations, or legal advice, and none of the steps below guarantees reinstatement.
- ASIN scope is not recall scopeAn ASIN-level restriction may be broader than the unit-level scope of a CPSC recall. That does not expand the federal recalled population.
- “Voluntary” is not optionalFederal law generally prohibits selling a product subject to a voluntary corrective action once CPSC has notified the public or the seller knew or should have known.
- Unknown is not outsideA missing or unreadable code is unknown, not outside the recall. An unresolved identifier is a safety hold, not a mismatch theory.
Separate the four records before arguing about a mismatch
Four records are involved, and they are owned by different parties. Confusing any two of them produces an argument Amazon cannot act on.
- The Amazon actionThe notification, safety classification, cited recall, required response, and deadline.
- The catalog identityThe child ASIN and the brand, model, GTIN, variation, and pack data attached to it.
- Your offer and stockThe seller SKU/FNSKU, fulfillment channel, receipts, locations, lots, and physical units you can document.
- The recalled populationThe products the controlling notice includes by model, UPC, serial, lot, date, configuration, origin, or other criteria.
An ASIN-level restriction may be broader than the unit-level scope of a CPSC recall. That does not expand the federal recalled population. Proving your stock is outside the federal scope, however, neither reveals what other sellers hold nor waives a removal instruction. It supports review of the offer and inventory you can prove; it does not establish what Amazon should do with the catalog record as a whole.
Preserve the case before changing the catalog
Do not start by editing the brand, model, UPC, variation, or package count.
A legitimate catalog correction may eventually be necessary, but a post-restriction edit can obscure the historical record or create a new contradiction between the listing and the product. Save the following first.
Nothing preserved yet. Capture the original state before any edit.
A parent ASIN, an approved sibling variation, or another seller’s active offer is context, not proof of the identity of the targeted child ASIN.
Find the exact safety action Amazon is relying on
Everything downstream depends on identifying the controlling notice and reading it in its current form.
- Search the official databaseStart with the CPSC Recalls and Product Safety Warnings database. Search the number in Amazon’s notice, then search the product, manufacturer, brand owner, model, and distinctive identifiers. Open the individual notice; do not rely on a search-result excerpt.
- Record what the notice actually saysRecord the notice number, publication date, affected-product description, code locations, remedy, and access date.
- Check what the notice does not show on its faceAn expansion can reverse an earlier conclusion. The 2024 BLACK+DECKER garment-steamer expansion, for example, included units repaired under the earlier recall. The old green-dot or notch marking therefore stopped proving exclusion.
- related and expanded recalls;
- the recalling firm’s official list or eligibility checker;
- tables, photographs, captions, and code-location instructions;
- whether the action is a Recall, Product Safety Warning, market withdrawal, or another safety measure.
- Use the API for discovery, never as negative proofUse the CPSC Recall API for discovery, not as negative proof: lot, date, and serial criteria may appear only in the live notice, an image, or the manufacturer’s page.
- Resolve conflicts instead of choosing the narrowest wordingIf the CPSC description, remedy section, images, and official manufacturer page conflict, do not select the narrowest wording to manufacture an exclusion. Keep the stock on hold and ask the recalling firm or CPSC to clarify which identifiers control.
Ask Amazon to identify the specific action. Also check manufacturer recalls, Product Safety Warnings, market withdrawals, other regulators or jurisdictions, and the policy category named in the Amazon notification. One empty CPSC search is not evidence of a mismatch.
Read the notice as a coverage test, not a product name
The title of a recall identifies a product family. The body defines the affected population.
16 CFR §1115.27 formally addresses identification in mandatory recall notices. Its list of model and serial numbers, date codes, label locations, and photographs is a useful evidence benchmark, but it does not define the scope of a voluntary recall. The current individual notice controls this comparison.
Do not infer AND or OR merely from table layout. Reconstruct each inclusion path from the notice’s wording. Treat fields as conjunctive only when the notice makes them part of the same required combination; treat alternatives as separate paths, and attach exclusions only where the notice applies them. A unit is outside the recall only when every applicable path is defeated or an express exclusion applies.
This matters because no universal identifier wins every time. A Star Water sump-pump recall used exact brand, model, manufacture-date, and UPC combinations. A GE cooktop recall used model-specific UPC and serial combinations. Fabuloso Recall 23-115 uses UPC, lot code, product variant, and country-related exclusions.
What can decide it
- A mandatory identifier that differs. If every route into the recall requires a particular UPC, and the UPC on the product is different, that one fact may be enough to exclude the unit.
- A single defeated field. You do not have to prove that every field differs.
- The right reading of the right object. The hard part is showing that you read the right identifier from the right object — and that the same conclusion applies to all restricted stock.
What cannot
- An outer multipack UPC, which may not identify the retail products inside.
- A package change, unless the notice makes package or configuration part of the scope.
- A purchase date, which is not automatically a manufacturing date.
- A missing or unreadable code, which is unknown rather than outside the recall.
Catalog differences are weaker than physical readings throughout. The comparison that counts runs from the notice to the unit in hand, not from the notice to the listing.
The Fabuloso case: a plausible mismatch with missing proof
The January 2026 Seller Forums thread “ASIN Removed Under CPSC Recall That Does Not Apply to My Inventory” shows exactly where a potentially valid argument can become an incomplete case.
Case 01The UPC theory: a real lead without physical proof
- Facts
- The seller said Amazon had associated ASIN B0FSLM7P8L with CPSC Recall 23-115. The seller identified the ASIN’s UPC as 035000800015, said it was absent from the affected list, and described the recall as UPC-specific.
- Official scope
- The current official Fabuloso recall page lists 17 affected U.S. UPCs and two ranges for the first eight lot-code characters: 2348US78–2365US78 and 3001US78–3023US78. It also excludes products marked Made in Mexico or carrying MX in the lot code. The seller-stated UPC does not appear in the 17-item list.
- Further exclusions
- The manufacturer page also excludes all Fabuloso Antibacterial scents; the named Baking Soda and Tropical Spring variants; Fabuloso Original Apple with Vinegar; and products purchased before December 16, 2022. That purchase-date statement belongs to this recall. It is not a general rule that purchase date equals manufacturing date.
- Why it is a lead
- Because a listed UPC is required for coverage, a verified UPC outside the list could exclude that bottle from the recall; the seller would not need a second identifier to differ.
- What is missing
- The public thread does not show an unedited photograph of that UPC on the relevant retail unit, the outer-to-inner pack relationship, or records proving that all restricted inventory carries the same physical identity.
- The other direction
- The phrase “UPC-specific” is also incomplete in the other direction. A matching UPC alone would not establish coverage without the applicable lot and exclusion checks.
- Status
- Amazon moderator Manny said only that the issue had been sent to a partner team. No final decision or reinstatement is published. This is an unresolved case, not a success precedent.
Case 02The lot-code theory: the right field, an untraced population
- Facts
- A second thread from the same seller illustrates a different theory. In December 2025, the seller reported lot code 5270US781L; its first eight characters, 5270US78, fall outside both published ranges.
- Why it could work
- That could exclude units carrying the code even if their product and UPC matched.
- What is missing
- The public lot-code thread does not show that every restricted unit came from that lot. The seller reported photographs, invoices, and manufacturer confirmation, but the attachments are not public.
- Amazon’s request
- Amazon’s moderator requested an authorized signature and fulfillment-center inventory removal.
- Status
- The final outcome is unknown.
Together, the two cases show why “wrong product” and “same product, unaffected lot” require different evidence. The first turns on physical identity. The second turns on production code and stock-wide traceability.
The correct conclusion is therefore narrow: the stated UPC supports investigating a mismatch, but the published record does not prove that Amazon made an error.
How to verify whether an Amazon ASIN was incorrectly matched to a CPSC recall
Complete the crosswalk from records and physical evidence. Use matches, proves exclusion, different but not decisive, contradiction, unverified, or not used by this recall. For the inventory row, use complete, mixed, or unverified.
One row per identity field, one finding per row
| Identity field | Catalog record / seller offer | Physical evidence | Official recall test | Defensible finding |
|---|---|---|---|---|
| Brand and product type | Child-ASIN title and brand | Full product and permanent branding | Named product family | Match, contradiction, or unverified |
| Model or variant | Model, scent, size, color, configuration | Permanent model or variant mark | Listed model, variant, or row | Match, exclusion, or non-decisive difference |
| UPC/GTIN | Catalog GTIN and pack count | Retail-unit barcode; outer and inner codes separated | Listed UPC, if material | Match, exclusion, contradiction, or unverified |
| Serial, lot, or date code | Often absent from catalog | Full code and its location on the same unit | Range, prefix, or manufacturing window | Match, exclusion, contradiction, or unverified |
| Package/configuration | Offer and fulfillment configuration | Product and package shown together | Material only when the notice says so | Match, exclusion, or supporting difference |
| Official repair/exclusion mark | Catalog claim, if any | Recognized mark plus authorized record | Current notice still recognizes it | Exclusion, contradiction, or unverified |
| Inventory population | Quantities, receipts, locations | Unit census or documented homogeneous batches | Scope applied to every unit or valid batch | Complete, mixed, or unverified |
Table scrolls horizontally on narrow screens. The inventory row is where many otherwise strong cases break.
Start by separating stock by child ASIN and seller SKU/FNSKU, then by receipt or inbound shipment, supplier, fulfillment location, and every variable lot or serial code. Reconcile those groups to the restricted quantity.
- Child ASIN
- Seller SKU/FNSKU
- Receipt or inbound shipment
- Supplier
- Fulfillment location
- Lot or serial code
- Restricted quantity
Use a 100% census when codes vary by unit or when receipts may contain different production runs. Treat a batch as uniform only when lot-specific manufacturer, packing, shipment, or receiving records connect every unit in the group to the same decisive identifiers. There is no universal safe sample size. If FBA units are inaccessible and the available inbound records cannot establish identity, the result remains unresolved.
Diagnose the type of mismatch before choosing evidence
Four fact patterns require different proof. Name the one in front of you before assembling anything — the evidence for one theory does nothing for another.
Find the theory the evidence actually supports
Pattern one — wrong product
The patternThe physical brand, model, product type, or defining feature does not satisfy any listed product path.
What makes it decisiveDefeating every listed product path — not merely showing a different title.
Evidence it needsA complete identity chain, from the full product to its permanent branding, on the units under restriction.
Pattern two — wrong variant or package
The patternThe size, scent, configuration, or packaging differs from the named variant.
What makes it decisiveThat difference is decisive only when the official notice makes it a limiting criterion.
Evidence it needsThe notice wording that makes variant or configuration part of the scope, plus the product and package shown together.
Pattern three — same product, unaffected production
The patternThe model or UPC may match, but the serial, lot, or manufacturing date is outside the affected range.
What makes it decisiveA full code read from the location the notice states, with every expansion checked.
Evidence it needsReadable codes and inventory-wide traceability across every relevant unit or valid homogeneous batch.
Pattern four — officially corrected or reworked unit
The patternThe unit carries an official repair or rework mark.
What makes it decisiveExclusion requires the authorized record and the distinguishing mark recognized by the current notice.
Evidence it needsThe authorized repair record and the recognized mark. An old mark cannot be treated as permanent; a later expansion may include repaired units.
This diagnostic narrows the theory the evidence can carry. It is not a legal determination, a CPSC finding, or a guarantee of Amazon acceptance.
An unreadable code, conflicting sources, or mixed inventory is not a fifth mismatch theory. It is an unresolved safety result.
Decide the safety outcome before submitting anything
Federal law generally prohibits selling, offering for sale, or distributing a consumer product subject to a voluntary corrective action taken by the manufacturer in consultation with CPSC when CPSC has notified the public or the seller knew or should have known of the action, subject to the statutory exceptions in 15 U.S.C. §2068(b).
CPSC also instructs online sellers to stop the sale of recalled products. “Voluntary recall” does not mean optional resale.
Every finding read across four columns at once
| Finding | Sale and inventory status | Correct next step | Stop condition |
|---|---|---|---|
| Physical unit is covered | Stop sale and shipment; isolate inventory | Follow the official remedy and Amazon instructions | Never use a mismatch submission to bypass coverage |
| All relevant units are provably outside this recall | Do not resume the offer or ship the stock; comply with the active restriction during review | Submit the traceable non-coverage case through the exact Amazon notification | Any unresolved path, conflicting identifier, or untraced stock |
| Inventory is mixed or coverage is unresolved | Safety hold; no sale or shipment | Rebuild traceability and obtain identifier-specific manufacturer clarification | Do not claim exclusion while a relevant unit remains unknown |
| Unit was officially repaired or reworked | Do not resume sale without current proof | Provide the authorized repair record and recognized mark | Seller-created mark, undocumented repair, or later expansion |
Table scrolls horizontally on narrow screens.
The unresolved hold is a prudent safety-control measure, not a claim that federal law contains a universal unreadable-code rule.
Exclusion from one recall does not prove that the product is generally safe or compliant. If the review uncovers a separate defect, noncompliance, or unreasonable risk of serious injury or death, the reporting analysis under 15 U.S.C. §2064(b) is a separate question.
Rank the evidence by what it can prove
A large packet is not necessarily a strong packet. Evidence becomes persuasive when each item answers a defined question.
- Authoritative scope comes firstUse the current CPSC notice, every relevant expansion, and the official manufacturer list, checker, or identifier explanation. These sources define the population; they do not prove which units you own.
- Direct unit identity comes nextUse unedited, contextual photographs that move from the full product to the permanent label, code location, UPC, lot/date/serial, origin, and package. These prove visible values for the photographed unit only.
- Population and traceability extend the conclusionLot-specific invoices, packing lists, production or shipment records, receiving logs, FNSKU/SKU mapping, and a unit census or documented homogeneous-batch control connect the photographed identity to the restricted stock.
- Manufacturer and Amazon documents establish authorityA strong Letter of Compliance uses official letterhead and an authorized signature and names the product, ASIN, recall, decisive identifiers, and reason for exclusion. A generic letter cannot cure an unreadable or untraced code. An identifier-specific manufacturer determination helps only when it explains how the stock is tied to the unit or uniform batch.
- Context supports but rarely decidesCatalog history, GS1 records, purchase dates, generic invoices, specifications, test reports, CPCs, and prior forum cases can support consistency. A GS1 record proves GTIN allocation, not a production lot; a generic invoice proves a purchase, not inventory homogeneity.
Build the submission in the same order as the proof
- Cover pageOne page naming the child ASIN, recall number, exact Amazon notification, and case ID.
- Authoritative scopeThe current notice, expansions, and official manufacturer scope source.
- Identity crosswalkA one-page crosswalk identifying the decisive field.
- Same-unit photographsA clear sequence from the full product to the decisive code.
- Population recordsInventory census or batch-level traceability records.
- Requested manufacturer documentThe document Amazon actually requested, if applicable.
- Case historyThe notification, inventory actions, deadlines, and submission history.
- The single contradictionA short explanation of the one contradiction the evidence resolves.
Follow the current Amazon notification—not a forum workaround
The Seller Central Help references for Recalled products information and product-safety alerts, recalls, stop sales, and market withdrawals may require authentication to show their complete workflows.
In the restricted account, confirm how Amazon classified the action, then use the review, upload, or case control actually displayed in the notification and answer its current document request.
Keep factual CPSC coverage separate from Amazon’s operational conditions. If Amazon instructs you to remove all FBA inventory or obtain a signed manufacturer letter even though you believe your lot is unaffected, proof of non-coverage does not authorize you to ignore that instruction. Document compliance and request review through the control or case channel actually provided.
Dated first-party statements are useful but limited. A June 2025 moderator post separated Product Safety Issue evidence from the manufacturer-letter and inventory process for Product Recall or Market Withdrawal. The December Fabuloso case discussed above adds case-specific signature and fulfillment-center removal requirements.
Neither statement creates a universal wrong-match route, review deadline, or reinstatement guarantee. If the notification gives a removal or disposal deadline, do not assume that opening a case pauses it. Obtain written clarification and preserve the response.
Six gaps that leave a mismatch unproved
A mismatch case remains incomplete when any essential link is missing.
- The barcode is not tied to the unitA catalog or outer-package UPC is not tied to the physical retail unit.
- One sample stands in for many receiptsOne unaffected sample is used to represent mixed receipts or lots.
- A substitute criterion replaces the real oneA purchase date, package appearance, or general test replaces a criterion the notice actually uses.
- The manufacturer letter is incompleteA manufacturer letter omits the recall number, decisive identifiers, or an authorized signature.
- The evidence belongs to something elseThe evidence concerns another child ASIN, seller, batch, or an outdated notice.
- The resubmission answers nothing newThe resubmission repeats the same documents without resolving Amazon’s stated contradiction.
- Create a replacement ASIN.
- Change identifiers.
- Relabel the product.
- Invent a repair mark.
- Use photographs from another batch.
- Continue FBM shipping to bypass the restriction.
A legitimate documented catalog correction may be appropriate through Amazon’s process, but changing the catalog does not prove that the physical inventory is outside the recall.
Focused FAQ
Does a different UPC prove that my product is not recalled?
It can, when the current notice makes UPC mandatory in every applicable inclusion path and the different value is verified on the relevant physical retail units. A catalog-only or outer multipack UPC is not enough.
What if the lot code is outside the recalled range?
An outside lot may be decisive when the notice uses that range, the full code is read from the stated location, all expansions are checked, and records show that every relevant unit or valid homogeneous batch carries that lot.
What if Amazon does not provide a recall number?
Ask Amazon to identify the safety action. Search CPSC by product and manufacturer, then check manufacturer actions, Product Safety Warnings, market withdrawals, other regulators or jurisdictions, and the policy classification in the notification. Do not infer an error from one negative search.
Can a manufacturer letter remove the recall flag?
It may satisfy a requested Amazon document and provide strong authority, but it does not guarantee removal. It must be specific to the product, recall, identifiers, and inventory, and it cannot override the official notice.
What if only another seller’s units under the ASIN are affected?
Prove the identity and traceability of your own units, but do not claim to know another seller’s stock or Amazon’s backend match. Amazon may keep an ASIN-level control in place even when seller-specific evidence is strong.
Can I continue selling while Amazon reviews the mismatch?
Do not bypass an active restriction. If any material identifier or inventory segment remains unresolved, keep the product on hold and do not ship it. If the units match, follow the recall remedy instead of pursuing a mismatch theory.
Does absence from the CPSC database prove the product was never subject to a safety action?
No. The relevant identifier may appear only in the notice narrative or manufacturer materials, and the action may come from a manufacturer, another regulator, another country, or a different Amazon safety policy.
Sources and claim audit
- 15 U.S.C. §2068Sale, offer for sale, or distribution of products subject to a voluntary corrective action taken in consultation with CPSC is generally prohibited once CPSC has notified the public or the seller knew or should have known. Establishes the confirmed-match stop-sale boundary.Checked 15 Aug 2026
- 15 U.S.C. §2064(b)A separate defect, noncompliance, or serious-injury risk can create an independent reporting question. Limits the meaning of exclusion to one specific recall.Checked 15 Aug 2026
- 16 CFR §1115.27Official identification can use models, serials, date codes, SKUs, tracking labels, code locations, and photographs. Used as an identification benchmark with an express mandatory-notice caveat.eCFR, 15 Aug 2026
- CPSC Recalls database and Recall APISearch and API data are discovery tools; the live notice controls the final identifier comparison. Supports the warning against treating one negative search as proof of non-coverage.Checked 15 Aug 2026
- CPSC: stop the online sale of recalled productsInstruction to online sellers, used alongside the statutory prohibition rather than in place of it.Checked 15 Aug 2026
- CPSC Recall 23-115 and the official Fabuloso recall pageNamed product variants, 17 U.S. UPCs, two first-eight lot-code ranges, and Mexico exclusions. Corrects the seller’s UPC-only description while recognizing that a verified false mandatory UPC condition can exclude a unit.Checked 15 Aug 2026
- Seller Forums: main Fabuloso ASIN caseThe seller-stated UPC is absent from the published U.S. list, but the thread publishes no physical or inventory-wide proof, and no final decision or reinstatement. Supports a mismatch hypothesis without declaring Amazon error.Thread, 15 Aug 2026
- Seller Forums: lot-code thread (December 2025)Amazon moderator response requiring an authorized manufacturer signature and fulfillment-center inventory removal. Used only as dated, case-specific operational guidance.Thread, 15 Aug 2026
- Recalled products information and product-safety actionsSeparate Amazon Help references whose complete workflow may require authentication. Procedural instructions are deferred to the classification and control shown in the seller’s current account notification.Checked 15 Aug 2026
- Amazon moderator guidance, June 2025Distinguishes safety-issue evidence from recall and market-withdrawal handling. Supports action-type diagnosis while deferring to the current account notification.12 Jun 2025 · checked 15 Aug 2026
- BLACK+DECKER expansion 24-181A later expansion can invalidate an earlier repair or rework exclusion. Demonstrates why current expansions must be checked before relying on an old mark.4 Apr 2024 · checked 15 Aug 2026
How the sources are used. Federal requirements come from the U.S. Code and the eCFR. Recall scope comes from the individual CPSC notice and the recalling firm’s own page, which control over any search result or API record. Marketplace requirements come from Amazon’s public pages, which may be superseded by ASIN-, category-, account- or case-specific instructions inside Seller Central. Seller-reported forum cases are used only to show recurring operational patterns — never as federal law, statistical evidence, or universal Amazon policy. The identity crosswalk, the four mismatch patterns, and the evidence ranking are derived analytical methods, not official Amazon or CPSC procedures. Two further recalls (Star Water sump pumps, GE cooktops) are cited only to show that different notices use different decisive identifier combinations.
Bottom line
Before asking Amazon to correct the recall match, answer four questions:
- Which child ASIN or seller offer did Amazon restrict, and which seller-owned units does that action affect?
- What affected population does the current official notice define?
- Which physical identifier proves inclusion or exclusion?
- Can that conclusion be traced across every relevant unit or valid homogeneous batch?
Request clarification from Amazon as soon as the cited action or required process is unclear. Submit a non-coverage claim only after the relevant seller-owned inventory is proved outside the recall. Ask Amazon to review the ASIN-to-recall association only when the catalog product itself—not merely one seller’s lot—is demonstrably outside the official product identity. Use the control in the exact notification.
For related platform-specific guidance, see the Amazon Marketplace Compliance Guides.
If any unit is covered — or material coverage remains unresolved — do not sell or ship it.
Editorial notice: This material is an independent, source-led explanation for commercial and compliance operations, stated as of August 15, 2026. Registry Intelligence is not affiliated with Amazon, Colgate-Palmolive, or the U.S. Consumer Product Safety Commission. Recall scopes are amended and expanded: the current official notice, the recalling firm’s own materials, and the exact notification in the affected account control every conclusion drawn here. This page is informational only — it is not legal advice, a CPSC determination, or an official Amazon decision, and it does not guarantee marketplace approval or reinstatement.