Account health, suspensions and the plan of action
- You know the metrics behind account status and their thresholds.
- You tell performance, policy and product violations apart — they have different consequences.
- You can build a plan of action that genuinely contains all three required parts.
- You have the emergency folder ready before you need it.
Account suspensions attract a lot of whispering and very little arithmetic. In fact account status is one of the few Amazon systems whose components are disclosed: there are measurable metrics with thresholds, violation types with different weights, and a procedure that runs predictably. Understand that and the fear goes — along with the carelessness. Getting started L3 introduced the metrics; this lesson is about diagnosis, procedure and preparation.
1The three pillars of account status
| Pillar | What counts | Metrics |
|---|---|---|
| Customer service performance | How satisfied buyers are with fulfilment | Order defect rate |
| Shipping performance | Only relevant for seller-fulfilled orders | Late shipments, valid tracking, pre-fulfilment cancellations |
| Policy compliance | Violations of rules and third-party rights | IP complaints, product authenticity, product safety, restricted products |
The reported thresholds (evidence level: practice — what counts is the display in your own account):
| Metric | Threshold | What it consists of |
|---|---|---|
| Order defect rate | below 1 %, rolling over 60 days | Negative feedback (1–2 stars), A-to-z guarantee claims, credit card chargebacks |
| Late shipment rate | below 4 % | Seller-fulfilled only — not relevant with FBA |
| Valid tracking rate | above 95 % | Since January 2025 for ALL carriers, not just integrated ones |
| Pre-fulfilment cancellation rate | below 2.5 % | Seller-fulfilled only; the usual cause is badly maintained stock data |
Think of account status as a driving licence with penalty points. The performance metrics are the minor offences: one alone does nothing, too many in a short time do. Policy violations are the serious ones — with some, the licence is gone immediately, regardless of your points. And as with a licence, what counts in the end is not what you can explain but what you can evidence.
2Why accounts really get suspended
The idea that “bad numbers lead to suspension” holds only for part of the cases — and the less likely part. The three cause groups and their typical dynamics:
- Performance metrics above threshold. Arrives gradually, is announced in the account health dashboard, can be averted by repair. This is the benign version — it gives you time.
- Policy violation. Arrives suddenly: IP complaint, product safety report, sale of a restricted product, review manipulation, catalog manipulation (lesson 4). A single serious violation can be enough.
- Account linking and identity. The most unpleasant case: your account is associated with another, suspended account — via address, bank details, device or tax data (Getting started L3). No behavioural plan of action helps here, only evidence that no link exists.
The key practical insight: your metrics can be flawless while your risk is high. An account with a 0.2 % defect rate and three open IP complaints is in greater danger than one at 0.9 % with a clean policy column.
3When it happens: the procedure
- Read what is actually there. The notice names the affected ASIN or order and the policy breached. Answer the wrong allegation and you get a standard rejection — which costs you an attempt.
- Do not delete anything hastily. A deleted offer does not remove the violation, only the evidence for your version.
- Gather facts before you write. Invoices, supplier evidence, photos, test reports, correspondence.
- Write the plan of action — the three required parts are in the next chapter.
- Submit once and watch deadlines. Answer follow-up questions promptly; let them lapse and the case may be closed.
- Do not escalate in parallel. Several simultaneous cases on the same matter slow processing down rather than speeding it up.
The emotional first draft: outrage, revenue history, a reference to years of loyalty. None of that is an argument — the allegation is not “unlikeable” but, say, “product authenticity not evidenced”. A plan of action that does not address the cited policy gets rejected, however justified the anger. Write the draft if you need to — and do not send it.
4The plan of action: three parts, no opinion
| Part | What belongs in it | Where it fails |
|---|---|---|
| 1. Root cause | What concretely happened, in your operation, with a date | Blaming outwards (“the supplier”), vagueness (“a misunderstanding”) |
| 2. Immediate action | What you have already done — past tense, verifiable | Announcements instead of completed steps |
| 3. Prevention | Which process prevents recurrence, with an owner and a cadence | “We will be more careful” — no process, no prevention |
Allegation: product authenticity on the AURELO set after a customer complaint. Root cause: 60 units of batch 2026-04 were sourced from an intermediary because the manufacturer could not deliver; no manufacturer invoice exists for that batch. Immediate action: the 41 remaining affected units were removed from inventory on 12 March, the intermediary's invoice including the supply chain is attached, and all buyers of that batch were contacted. Prevention: sourcing from now on exclusively direct from the manufacturer; since 15 March every goods-in booking requires a stored manufacturer invoice, checked by the purchasing lead on every delivery. Three paragraphs, no adjectives — and every sentence backed by a date or a document.
5Preparation: the emergency folder
The difference between a week and three months of suspension almost always lies in preparation. What belongs in the folder before anything happens:
- Manufacturer invoices per batch, with complete contact details of the issuer. Intermediary invoices are often not enough for authenticity allegations.
- Brand evidence: the certificate, licence agreements, letters of authorisation.
- Product conformity: declarations of conformity, test reports, safety data sheets (Listing L15).
- A contact route: a second, constantly monitored mailbox — miss the deadline mail and you lose the case regardless of the merits.
- A liquidity plan for 60 days without disbursement. Balances are usually withheld during a suspension. Being surprised by that turns one problem into two.
- Account health dashboard reviewed weekly, not only when something is wrong.
- Policy column assessed separately from performance metrics.
- Manufacturer invoices filed per batch, not just payment records.
- Second mailbox set up and actually read.
- Liquidity planned for 60 days without disbursement.
- Plan-of-action template with the three required parts ready to hand.
- No parallel cases on the same matter.
6Expert insight: the order defect rate is a small-numbers trap
The defect rate is shown as a percentage, and percentages suggest precision. In fact, at low order volumes it is one of the most volatile numbers in the whole account — with a consequence hardly anyone draws.
Do the maths: the threshold is 1 %. At 100 orders in the 60-day window, a single defect makes 1 % — one dissatisfied buyer puts you at the line. At 1,000 orders you need ten defects for the same figure. So the number measures something entirely different for small accounts than for large ones:
| Orders in 60 days | Defects to the 1 % line | What the number practically measures |
|---|---|---|
| 50 | 0 (one already makes 2 %) | Chance |
| 200 | 1 | Individual cases |
| 1,000 | 9 | A pattern |
| 5,000 | 49 | Your actual process quality |
Three rules follow, and they read differently at small scale than at large:
- Small accounts see every single case through. At 200 orders an unanswered customer question is not a statistic, it is half the threshold. The 24-hour response rule therefore matters more for small accounts than for large ones — not less, as many assume.
- Large accounts work on patterns. Above four-figure order counts an individual case is noise; what matters is whether the same cause recurs. That requires categorising defect reasons, not just counting them.
- Recovery takes 60 days. The window rolls: a defect only disappears when it rolls out. Fix something today and you see the result in two months — and you have to plan for the interval rather than lapse into frantic action.
A second point that is just as little known: the defect rate blends three very different events. Negative feedback is an opinion, a guarantee claim is a complaint about fulfilment, a chargeback is a payment event. Look only at the total and you treat three illnesses with one medicine. The breakdown sits in the account health dashboard and is the first thing to check after any deterioration — because the remedies have nothing in common: feedback needs product and expectation work, guarantee claims need communication and shipping quality, chargebacks need fraud prevention.
A widespread piece of advice is to “sell more so the rate dilutes” when a threshold looms. It works arithmetically and is still dangerous: more orders with an unchanged process bring proportionally more defects, just later. Dilution is not a fix but a bet that the cause will not grow with you. Fix the cause — the rate then follows on its own.
The pro track assumes the other three and repeats nothing from them. It opens once you have completed all three in full — every lesson quiz at 80 % or better, and every final quiz passed.
Not logged in? Your progress only counts with a free account.
Check yourself
6 quick questions — one at a time, instant feedback. With a free account your progress is saved.
Frequently asked
Are FBA orders exempt from the order defect rate?
No. Shipping metrics such as late shipments only concern seller-fulfilled orders, but the defect rate does not: negative feedback and guarantee claims also arise with FBA — because of the product itself, or a misleading listing claim. That is exactly why dimensions, contents and expectation management in the listing are an account health question too.
How long does a metric take to recover?
The 60-day window rolls: a defect only disappears when it rolls out. Fix the cause today and the full effect appears in two months. That interval belongs in the plan — otherwise repair is followed by frantic action, and that creates fresh errors.
Should I hire a service provider for a suspension?
For linking and identity cases, experience can be worth a lot, because what is disputed there is an association rather than behaviour. For performance and policy cases the plan of action is craft you handle better than any outsider: only you know the cause and the process. Even if someone else writes it, you still have to supply the facts.
The free Listing Check scores any ASIN from 0 to 100 in a minute — the fastest way to see whether the mechanics from this lesson actually hold on your own listing.
Go deeper: the complete guide to optimizing Amazon listings →
Everything in this academy comes from day-to-day selling practice — the same playbook behind Listimo, the tool that turns product photos into complete Amazon listings.