- Read the exact notice before drafting any response.
- Identify the specific policy, transaction, ASIN or behaviour Amazon is asking about.
- Collect evidence before making unsupported explanations.
- Do not submit repeated speculative appeals that contradict each other.
1. Preserve the exact notice
Save the complete Performance Notification or Account Health message, including the date, policy name, examples, ASINs and any requested documents. Small details in the notice often determine what evidence is relevant.
2. Separate facts from assumptions
List what you know from Seller Central records, invoices, account users, messages, product documentation and internal processes. Do not fill gaps with guesses. If a third party, employee or agency was involved, document the actual scope and timeline.
3. Stop the underlying risk before appealing
Where possible, correct the root issue first—for example, remove problematic inventory, end a non-compliant process, update listings or revoke unnecessary user access. Corrective actions should be real actions, not promises written only for the appeal.
4. Gather the evidence Amazon requested
Depending on the issue, this may include invoices, authorization letters, product photos, supply-chain records, compliance documents, account-user details or other records. The correct evidence depends on the notice; there is no universal suspension-document pack.
5. Respond once the case is coherent
A rushed response can introduce contradictions. Build a factual timeline, root cause, corrective actions and preventive controls where relevant, then answer the exact points Amazon asked for.