Direct answer: Seller account health rests on a handful of metrics that platforms publish and sellers ignore until a warning arrives: order defect rate, late shipment rate, valid tracking rate, cancellation rate, and policy violation notices. Each has a threshold, and drifting toward one is visible weeks before enforcement if anyone is looking. A weekly fifteen minute review of the health dashboard, with an owner and a simple log, catches the drift while it is still a process fix rather than an appeal. Suspensions are usually the last step of a story the dashboard told in advance.
Ask a suspended seller when the trouble started and they will name the email. Ask their dashboard and it will name a date six weeks earlier, when a metric crossed a line nobody was assigned to watch.
This guide covers the account health metrics that matter, how to read drift before it becomes enforcement, and the small weekly discipline that keeps a selling account boring in the best way.
Order defect rate bundles negative feedback, claims, and chargebacks into the number platforms guard most closely. Late shipment, valid tracking, and pre fulfillment cancellation rates cover the operational promises. Each platform publishes its thresholds; print them where the team works, because a metric without its line is just a number.
Policy violations sit outside the percentages and matter as much. A listing flagged for a restricted claim or an IP complaint is a health event even at perfect shipping numbers, and repeat flags in a category compound toward enforcement faster than sellers expect.
A metric inside its threshold but climbing for three straight weeks is a warning with lead time attached. The causes are usually mundane and fixable: a carrier lane degrading, a warehouse backlog day, a listing whose description is generating mismatch claims. Trend watching finds them at the process stage.
Keep a one line weekly log: each core metric, its direction, and any notice received. The log takes minutes and does two jobs, it forces the look, and it becomes the evidence of active management that an appeal, if one is ever needed, is built from.
Health dashboards fail socially before they fail numerically: everyone can see them, so no one does. Name the owner, set the weekly check, and write the first responses in advance: which listings get paused on a defect spike, who contacts the carrier on a tracking dip, what gets documented when a policy notice lands.
Speed of response is itself a health factor. Platforms weigh how a seller handles a notice, a buyer message backlog, or a defect cluster. A same day, documented response pattern is visible in the account record and separates managed accounts from abandoned ones at review time.
A warning email is the platform selling you information at the lowest price it will ever offer. The correct response is a root cause note in the log and a process change, not relief that nothing worse happened. Accounts are rarely suspended for the thing that was warned about once; they are suspended for the pattern of warnings absorbed without changes.
Once a quarter, audit the catalog against current policy as well: claims in copy, image rules, and category requirements shift, and yesterday compliant listings drift into violation standing still. Prevention here is an afternoon; the appeal version is measured in weeks of lost sales.
Related reading: Marketplace Test Buys: Turning a Purchase Into Takedown Evidence, Counterfeit Monitoring for the Holiday Surge: A Brand Playbook, and Counterfeits in Social Commerce: Finding and Reporting Fakes in Feeds.
Order defect rate is usually the most consequential, because it combines buyer reported failures into one closely enforced number. But any single metric crossing its threshold can trigger enforcement, and policy violations operate outside the rates entirely. Watch the full set.
Weekly is the rhythm that catches drift while it is still cheap, with an immediate check whenever a platform notice arrives. The review takes about fifteen minutes when the metrics are calm, which is exactly when the habit needs to hold.
Find the operational cause in the underlying orders: a carrier, a listing, a processing day, a product with rising claims. Fix the cause, document what you found and changed in your health log, and watch the next cycle. Appeals and explanations come second to evidence of a fixed process.
Often, with a plan of action that names the root cause, the corrective steps already taken, and the preventive measures in place. Vague apologies fail; specific, evidence backed plans succeed more often. The weekly log and documented fixes from before the suspension are the strongest material an appeal can include.