The notice names a policy family. It rarely names the rule, and the rule decides everything.
For cases we accept: the precise restriction and marketplace, the product facts that engage it, and the route that rule actually permits.
A real person reads your case and replies within about an hour.
ASA Compliance Group operates Amazon Sellers Appeal. On restricted-product files we identify the governing rule and run the route it allows in Seller Central.
Include the policy Amazon named, what the product is and is made of, and any documents already rejected. Four short steps. Or Shamosh reads every intake.
Or Shamosh · Founder and lead strategist
5,500+ enforcement cases since 2016. Every intake is personally assessed before acceptance.
Send what you have, including prior DIY or agency appeals. We say what is viable in writing before you commit.
Questionnaire
If the questionnaire does not load, open intake on the account page.
* Across ASA’s accepted and fully managed enforcement cases (all notice types we take on), not restricted product matters alone. Details under Proof.
The heading covers several unrelated findings. The product may be prohibited outright, allowed only under conditions, missing an approval or document, listed in the wrong category, or presented with claims that placed it into a restricted class. The notice normally names the listing and the policy family, and often not the rule itself.
So the first work is locating the precise restriction, the marketplace it applies in, the product characteristic it turns on, and the route it allows. Everything downstream depends on that, and a response written before it is known cannot be aimed at anything.
Three honest outcomes, and a good file can end at any of them:
A misclassification, a claim, a category or a missing document. The product can be offered once the specific thing is fixed.
Allowed with approval, documentation or seller eligibility. The work is obtaining and mapping the right evidence.
The product cannot be sold on that marketplace. Withdrawal and truthful acknowledgement is the correct response, not a failure of the appeal.
One distinction does most of the damage when it is missed: lawful to sell is not the same as eligible on Amazon. Amazon's restricted products policy applies its own category rules, and a product can be entirely legal and still ineligible. Arguing legality at a policy question answers nothing.
These need different evidence and lead to different outcomes. The notice usually distinguishes them less than the product does.
It cannot be offered on that marketplace at all. This is the branch where the honest answer is withdrawal, inventory disposition and a truthful acknowledgement, and where pressing an appeal makes the account position worse rather than better.
Establishing it early is a service to the seller. The alternative is months of submissions against a rule that has no route through it.
The product is permitted with approval, documentation, category eligibility or a marketplace-specific registration. The work is identifying exactly which condition applies and obtaining evidence that maps to this product.
The product sits in a class that carries restrictions it should not attract. This is genuinely correctable and it has to be done transparently: showing the physical facts and removing the catalog signals that produced the wrong class.
What is not available is changing wording or category to avoid detection. That converts a classification question into a circumvention finding, and the second is much harder to answer than the first.
The listing said something that placed the product into a restricted class: a pesticidal claim, a medical purpose, a weapon capability, a surveillance function. The product may be ordinary and its description was not.
Which restricted class it landed in decides the lane. A medical purpose is medical claims or FDA compliance; a pest or microbe claim is pesticide compliance. Each has its own evidence and its own vocabulary.
Certificates or supplier declarations that do not correspond to the product, manufacturer, model, marketplace or requested document type. A genuine document for a neighbouring product is still the wrong document.
Reviewers are applying one specific rule. Most rejected responses never establish which rule they are answering.
A general plan of action that never identifies the restriction or the product characteristic it turns on.
The product is lawful to sell. True and beside the point, because eligibility is a separate question with its own rules.
The offer removed on the assumption the violation goes with it. It usually does not, and the evidence goes instead.
Category or wording changed to avoid detection rather than to describe the product correctly. That is a worse finding than the original.
Certificates and invoices sent as a set, none of them matching the product, model, marketplace or the document type actually requested.
Corrections described as live when the listing is suppressed and the customer-facing state cannot be checked.
There is no universal checklist here, and offering one would be the mistake. The rule decides the evidence.
Record the notice, the policy name, the listing, the marketplace, the appeal options offered and any rejection reasons. Then establish the product facts: what it is made of, what it does, how it works, its intended use, model, manufacturer or importer, and what its label and instructions say.
Only then look for the rule. Working from the product to the restriction is reliable; working from a guessed restriction back to the product produces confident answers to questions nobody asked.
State it explicitly, because it determines everything after it and because an unstated assumption here is what produces months of misdirected submissions:
A file that names its branch and is wrong is correctable. A file that never names one cannot be assessed by anyone, including the person writing it.
Category-specific legal or regulatory evidence, approvals, registrations, test reports, certificates or an exemption analysis, each mapped to the exact product, model, manufacturer and marketplace. Amazon's document requirements decide whether what you send is usable before anyone considers whether it is persuasive. Where the requirement is testing or certification, the matching rules are the same ones that govern product safety compliance.
Send what the notice asked for. A larger bundle does not improve the odds and slows the review, and it signals that the requirement was not identified.
For covered categories Amazon requires testing, inspection, certification or document validation through an authorized TIC provider. Where suitable reports already exist, the provider may validate them. Where new work is required, the provider performs the applicable service and submits the compliance result directly to Amazon under the updated process. A seller-supplied report can be genuine and technically correct and still be unusable, because the submission has to come from the provider. Check which route the request names before commissioning anything.
Where correction is the route, catalog work runs through prepared, uploaded, processed and live-verified. A suppressed listing makes the last one impossible, and the honest response says what processed, what cannot be seen, and what route is needed after restoration.
Where withdrawal is the route, the file is the inventory disposition, the removal records and a truthful acknowledgement. Amazon's compliance and appeal route is where either is submitted.
If a document was rejected and the reason was not explained, include it anyway. The mismatch is usually visible on comparison even when the rejection message is not specific.
Scoped historical outcomes on cases we accepted and fully managed. One seller voice below; deeper galleries live on account reinstatement.
Population: historical cases ASA accepted and fully managed (we prepared the compliance response and ran follow-ups in Seller Central). The figure combines reinstatement and restoration work across notice types in that managed population, not restricted product matters alone. Declined intakes and self-serve template buyers are not in the rate.
Success: reinstatement or restoration of the privileges Amazon had restricted for that file (account, listing, verification, funds, or related, depending on the case). Amazon decides every outcome; the rate is not a guarantee for future cases.
Review: the underlying records were independently reviewed. Verified as of .
More methodology context and galleries: account reinstatement proof.
“In less than 24 hours after the appeal, my account was reactivated with all products available for sale.”
More outcomes and video proof: account reinstatement proof.
For sellers who already have the Performance Notification. Broader questions: full FAQ library.
If Amazon removed a product as restricted, start with the questionnaire.
Listing removed rather than mis-described: listing reinstatement. Other notice names: all suspension types.
