Amazon Restricted Products

Amazon restricted products generate more preventable suspensions than almost any other policy area on the platform. The rules aren’t hidden — Amazon publishes its Restricted Products policy pages — but the enforcement is automated, aggressive, and frequently wrong. A supplement seller with clean FDA facility registration can wake up to a blocked ASIN because a bullet point contained the word “cure.” A cutting board can get flagged as a pesticide because the listing mentioned “antimicrobial.” If you sell anywhere near supplements, topicals, food, toys, electronics, or anything that touches a federal regulatory framework, you need to understand three things: how Amazon classifies restrictions, how its detection systems actually work, and what to do when the system flags a product that’s fully compliant. This guide covers all three, at the level of detail you need to act.

Restricted vs. Gated vs. Prohibited: Three Different Problems

Sellers use these terms interchangeably. Amazon doesn’t, and the distinction determines your path forward.

Gated means you need approval before listing. Gating exists at two levels. Category gating covers entire departments — Fine Jewelry, Watches, Collectible Coins. ASIN-level gating covers specific brands and products, which is why you can be approved for Grocery as a category but still blocked from listing a specific brand of protein powder. Gating is a sales channel problem, not a legal one. The product is fine; you just haven’t proven you should sell it.

Restricted means the product can be sold, but only under conditions: documentation on file, specific claim limitations, labeling requirements, or seller qualifications. Dietary supplements are the classic example — sellable by anyone, but subject to Amazon’s supplement policy requiring a Certificate of Analysis (COA) from an ISO 17025-accredited lab on request, and strict limits on disease claims.

Prohibited means never sellable on Amazon, period. CBD (as of current US policy), prescription drugs, weapons parts, recalled products. Listing a prohibited product doesn’t get you a documentation request. It gets you a listing removal at best and an account deactivation at worst, because Amazon treats it as a deliberate policy violation rather than a paperwork gap.

Diagnose which bucket you’re in before responding to anything. A gating rejection needs a better application. A restriction violation needs documentation. A prohibited-product flag needs either a successful argument that Amazon misclassified you — common — or a fast, clean removal of the product with an acknowledgment in your Plan of Action.

The Categories That Trip Sellers Most

Five product areas account for the bulk of restricted product enforcement we see:

Dietary supplements. Amazon’s supplement policy now requires third-party testing verification through programs like NSF or USP, or COA submission via manage-your-compliance workflows. The enforcement trigger is almost always claims language: “treats,” “cures,” “prevents,” “anti-inflammatory,” “immune defense against illness.” The FDA’s structure/function claim rules apply, and Amazon enforces a stricter version of them by bot.

Pesticides and FIFRA. This is the category that catches sellers who don’t think they sell pesticides. Under FIFRA, anything making a pesticidal claim — kills germs, repels insects, antimicrobial, antifungal, mold-resistant — is a pesticide. Amazon requires an EPA registration number, a FIFRA 25(b) minimum-risk exemption, or a “treated article” exemption, plus a completed pesticide training certification in Seller Central. Sellers of soap dispensers, cutting boards, and phone cases get swept up constantly because of a single bullet point.

Medical devices. Anything the FDA classifies as a device — pulse oximeters, TENS units, orthodontic products, even some massage guns — can require FDA establishment registration, 510(k) documentation, or listing numbers. Class II devices draw the most document requests.

Toys and children’s products. CPSIA applies to anything designed or intended primarily for children 12 and under. Amazon requires a Children’s Product Certificate (CPC) backed by testing from a CPSC-accepted lab, and it asks proactively, especially in Q4. No CPC, no listing.

Food and grocery. FDA facility registration, expiration date requirements, temperature-control declarations, and country-specific labeling. Meltable inventory restrictions (roughly mid-April through mid-October for FBA) compound the compliance picture.

If most of your catalog lives in these categories, the broader documentation strategy in our guide to Amazon product compliance matters as much as any single ungating application, and our regulated products practice exists specifically for this catalog profile.

How Amazon’s Automated Flagging Actually Works

Understanding the detection mechanism explains 80% of “why did this happen to me.”

Amazon’s compliance systems continuously scrape listing content — titles, bullets, descriptions, A+ Content, backend keywords, even customer Q&A and reviews — against keyword blocklists mapped to policy categories. The word “pesticide-free” can trigger the pesticide workflow. “FDA approved” triggers medical claims review. “Flammable” can route a product into hazmat review. The system doesn’t evaluate context; it matches strings and applies the associated restriction.

Three other inputs feed the system. Browse node classification: if your product sits in a node associated with a restricted category, it inherits that node’s scrutiny. Catalog attributes: an incorrect item_type_keyword or a battery attribute set to “yes” on a battery-free product creates flags. And contribution conflicts: on multi-seller ASINs, another seller’s content edits can inject trigger words into a listing you built clean.

Practical consequence: audit your own listings for trigger language before Amazon does. Search your catalog exports for high-risk terms — sanitize, disinfect, kill, cure, treat, FDA, antibacterial, repellent, pesticide — and rewrite anything that isn’t essential and defensible. This is the cheapest compliance work you’ll ever do.

Ungating and Approval Workflows That Actually Get Approved

The application path runs through Seller Central: Catalog → Add Products → search the ASIN → “Apply to sell.” What happens next depends on your account profile. Established accounts with strong metrics frequently get auto-approved — the fabled instant ungating. Everyone else enters manual review.

For manual review, the document Amazon almost always wants is an invoice, and this is where most applications die. The requirements are specific: an invoice (not a receipt, not a pro forma, not a packing slip) dated within 180 days, from a distributor or manufacturer — not a retailer — showing purchase of at least 10 units, with your name and address matching your Seller Central details exactly. Prices can be redacted; quantities and product identifiers cannot. Amazon verifies suppliers, so the distributor needs a real commercial footprint: a website, a business address, a phone number that answers.

For regulated categories, layer on the compliance documents: COA for supplements, CPC and test reports for children’s products, EPA registration for pesticides, FDA registration for devices and food. Submit them as clean, legible PDFs with the ASIN referenced. Blurry phone photos of documents are a leading cause of rejection.

If you’re rejected, don’t immediately resubmit the same package — repeated identical submissions train the system to auto-deny you. Fix the actual deficiency first. Our compliance documentation resource covers formatting requirements document by document.

When a Compliant Product Gets Flagged Anyway

This is the scenario that fills our intake queue: your product is legal, tested, and documented, and Amazon blocked it anyway. Here’s the working sequence.

First, identify the trigger. Read the enforcement notice in Account Health for the specific policy cited. Then diff your listing against that policy. Nine times out of ten you’ll find the trigger word or the miscategorized attribute. If the notice cites “restricted products — pesticides” on a kitchen product, search your listing for antimicrobial-adjacent language.

Second, fix the listing before you appeal. Amazon’s reviewers check whether the trigger is still live. An appeal that says “this isn’t a pesticide” while the bullet still says “kills 99.9% of bacteria” gets auto-denied.

Third, submit documentation, not arguments. Reviewers act on documents. A one-page appeal attaching your EPA exemption rationale, lab results, or FDA registration outperforms three paragraphs of reasoning. Reference the ASIN, cite the policy, attach the proof.

Fourth, escalate on a schedule. No movement in 72 hours: open a case and reference the original submission ID. Denied twice with valid documentation: escalate to seller-performance escalation channels or, for Brand Registry brands, through your brand support contacts. Track every case ID — the paper trail matters when a full ASIN reinstatement becomes necessary.

We’ve run this playbook on genuinely hard cases; the regulated-product ASIN reinstatement case study shows what the full sequence looks like when Amazon initially refuses to budge.

Building a Restriction-Proof Catalog

Prevention is unglamorous and dramatically cheaper than reinstatement. Four habits separate sellers who rarely see restriction flags from sellers who see them quarterly.

Keep a live compliance file per ASIN — invoices under 180 days old refreshed on a rolling basis, current COAs and test reports, registration numbers — so any documentation request is a same-day response instead of a two-week scramble. Audit listing copy for trigger language every time you or an agency touches the content. Monitor Account Health daily, because restricted-product warnings escalate to removals fast, and repeated violations degrade your Account Health Rating. And re-check Amazon’s category policy pages quarterly; supplement and pesticide policy language has shifted multiple times in recent years, and grandfathered listings do not stay grandfathered.

The whole enforcement landscape — restrictions, suspensions, IP claims, documentation demands — is mapped in our Amazon compliance hub if you’re building out this capability internally.

If you’d rather not build it internally, this is exactly what a compliance engagement covers: catalog risk audits, trigger-language sweeps, documentation prep formatted to Amazon’s requirements, ungating applications, and appeals when the bots get it wrong. Our compliance and reinstatement service handles restricted product cases daily, and the fastest resolutions are always the ones where the documentation was ready before Amazon asked.