First 24 hours: stabilize, do not panic-spam
Read the performance notification carefully. Amazon suspensions are typed: policy violation, authenticity, related accounts, shipping performance, and others. The fix depends on the type.
Do not open multiple cases with conflicting stories. Do not admit to policy violations you did not commit. Gather facts first: which ASINs, which orders, which metrics triggered the action.
- Screenshot the notification and note the exact policy cited
- Pull all affected order IDs and ASINs into one sheet
- Pause ads and inbound shipments until you understand scope
- Assign one person to own communication with Amazon
- Preserve invoices, labels, and tracking before records age out
Diagnose the root cause
Amazon reviewers respond to root cause, corrective actions, and preventive controls. Surface-level apologies fail. Map the failure mode to operational reality: supplier change, listing edit, unauthorized seller, or metric drift.
- Authenticity: trace lot codes to supplier invoices
- Condition complaints: compare pick/pack photos to buyer claims
- Related accounts: document legal separation and shared assets
- IP complaints: identify complainant and listing edit history
- Performance metrics: export defect reports for the cited window
Build the appeal document
Write in plain language with numbered sections. Lead with what happened, why it happened, what you fixed, and how you prevent recurrence. Attach only relevant evidence; volume is not credibility.
- Section 1: Acknowledge the issue in Amazon's terms
- Section 2: Root cause (specific, not generic)
- Section 3: Immediate corrective actions already taken
- Section 4: Long-term preventive controls and owners
- Section 5: Evidence index with file names described
Evidence that reviewers actually use
Invoices should show supplier name, your entity, quantities, dates, and ASIN-relevant identifiers. Tracking should match carrier events. Photos should be dated when possible.
- Supplier invoices with matching UPC/EAN/SKU where applicable
- Authorization letters for distributorship or brand ownership
- Packing station photos and QC checklists
- Carrier tracking screenshots tied to complaint order IDs
- Return and refund logs showing good-faith resolution
If the first appeal fails
Read the denial reason. Add net-new information; do not resubmit the same PDF with a new cover letter. Escalate through Account Health with factual updates, not emotional appeals.
For complex IP or authenticity cases, consult counsel early. Some fixes are legal structure and authorization, not better bullet points.
Operating during suspension
If FBA inventory is stranded, understand removal vs disposal costs. Communicate with retail partners and DTC customers if Amazon was a major revenue channel. Cash flow planning matters while appeals run.
- Model cash impact weekly while account is down
- Redirect fulfillable inventory to other channels if legally allowed
- Pause purchase orders tied to Amazon-only SKUs
- Document lost revenue for internal planning, not for reviewer drama
Prevention systems worth installing now
Most suspensions are repeat failure modes. Build lightweight controls before you need them: metric alerts, invoice retention policy, listing change approvals, and MAP enforcement basics.
- Weekly Account Health review with assigned owner
- Invoice and lot traceability retained minimum 24 months
- Listing edit approval for title, ingredients, and compatibility claims
- Supplier change checklist triggers re-verification
- Unauthorized seller monitoring on hero ASINs
- Quarterly mock appeal drill on your highest-risk SKU class