Strategy
A written plan built for your notice and your case history, not a template.
Founder-led since 2016. If the odds are not there, we tell you in writing instead.
Answer the questionnaire and a real person reads it. You get our read on the case, what we would argue, and the fee, before you pay anything.
ASA Compliance Group handles Amazon enforcement end to end: account and listing reinstatement, regulatory and legal support, run by the same team that writes the appeal and answers Amazon's replies.
Amazon has concluded that reviews on your listings were influenced rather than earned. The trigger is often indirect: a package insert, a third-party service you used, a review-gating message, or a pattern its systems associate with incentivised reviews.
You will usually not be told which reviews or which behaviour caused it. Sellers who did nothing deliberate still get these notices, frequently through an agency or software vendor acting on their behalf.
Amazon is judging the mechanism that produced the reviews: the insert, the message, the vendor, the incentive. The reviews themselves are the symptom it noticed.
An agency, a launch service or a virtual assistant acting on your account is treated as you acting. Whether you knew is not the question Amazon is deciding.
Every message you send becomes part of the case log. A rushed denial in the first hour is the thing a later, accurate submission has to work around.
A large share of the cases we take start here. A rejection is not the end of the case, but it does change the job: the next submission has to account for what you already said.
Amazon is reading your submissions against each other. Before anything new goes in, the contradictions between them have to be resolved deliberately, not quietly dropped.
Resending a similar appeal with stronger wording signals that nothing operational happened. The second submission has to contain something the first did not.
There is a difference between escalating with new verifiable facts and escalating by volume. The second one shortens the runway on the account.
We have reviewed your submission and do not have enough information to reactivate your account at this time.
Typical rejection wording, paraphrased
Amazon reinstates when it can see that the behaviour is identified, ended, and structurally prevented. Every item below is something a reviewer can check outside your own account.
What does not carry this case:
One owner on the Seller Central thread, from the notice through to resolution.
A written plan built for your notice and your case history, not a template.
Plan of Action, evidence package, and the submission itself, placed in the queue Amazon can act on.
Follow-ups and escalation are ours. If Amazon needs several cycles, we run several cycles.
You see the strategy and the fees first. If the odds are not there, you get that in writing instead.
ASA Compliance Group has been founder-led since 2016. Or Shamosh builds the strategy on every case we accept.
Most of these cases are not deliberate. Insert cards asking for honest reviews, review-gating flows, and third-party tools all produce the same signal. The response has to identify the actual mechanism rather than deny intent.
Yes, Amazon holds the account owner responsible for anything done on the account. It is still worth stating plainly, because the corrective action is credible when it names what changed.
Usually yes. Amazon strips the reviews it associates with the pattern as part of the same enforcement. That is its action, not something you are asked to do, and it is not what the appeal is judged on. The appeal is judged on the mechanism you identify and the control you put in its place.
Often, yes. We start by stabilising the case log, resolving contradictions between what you have already sent, and then rebuilding the submission around evidence Amazon can verify.
The exact notice text, every appeal you have submitted, Amazon's replies, and an honest account of any review-related tooling or inserts you have used.
Different notices need different evidence. If your case is not the one on this page, start here.