Amazon Compliance & Account Health — Navigate Amazon's Rules

Most brands start searching for an Amazon compliance agency the week something breaks — an account deactivation email at 6 a.m., an ASIN pulled in the middle of Q4, a restricted products flag on a listing that sold cleanly for three years. By then the conversation is about damage control. The better conversation happens earlier, because Amazon compliance is not one problem. It is four distinct risk categories — account-level, ASIN-level, product-level, and 1P vendor risk — each with its own enforcement mechanism, its own appeal path, and its own documentation requirements. This hub maps the whole landscape: what triggers each enforcement type, what prevention actually looks like compared to reactive appeals, the documentation infrastructure every brand should build before anything goes wrong, and the escalation paths that exist when the standard process fails.

The Four Risk Categories in Amazon Compliance

Sellers talk about “getting suspended” as if it were one event. It isn’t. Amazon enforces at four different levels, and the level determines everything: who reviews your case, what evidence they expect, how long resolution takes, and how much revenue bleeds out while you wait. Misdiagnose the level and you send the right appeal to the wrong team.

Account-level risk: suspension and Account Health

Account-level enforcement is the one that stops all revenue at once. Amazon’s Account Health Rating scores your account from 0 to 1,000. Healthy is 200 and above, “At Risk” is 100 to 199, and below 100 you are in deactivation territory. The rating moves based on unresolved policy violations weighted by severity and recency — a single critical violation (counterfeit, safety, fraud) can drop you from green to deactivated overnight, while a stack of minor listing violations erodes the score gradually.

Behind the rating sit hard performance thresholds: Order Defect Rate under 1%, late shipment rate under 4%, pre-fulfillment cancel rate under 2.5%, valid tracking rate above 95% for seller-fulfilled orders. Breach those for long enough and you get a performance suspension. Separately, Section 3 of the Business Solutions Agreement covers conduct violations — review manipulation, related accounts, dropshipping violations — and Section 3 deactivations arrive with no warning and hold your funds for 90 days by default.

One program changes the calculus here: Account Health Assurance. Accounts that hold an AHR of 250 or higher for six months (with a valid emergency contact on file) get a call from Amazon before deactivation instead of after it — a chance to fix the problem while still selling. That single benefit is worth more than most compliance tooling, and it is earned entirely through the weekly hygiene described later on this page.

The appeal vehicle at this level is the Plan of Action, and it has a specific anatomy that Seller Performance expects. We break down the full POA framework in our guide to the Amazon account suspension appeal process. If your account is deactivated right now and every hour matters, skip the education and go straight to our emergency response page for suspended accounts.

ASIN-level risk: suppression and removal

One tier down, Amazon enforces against individual listings. There are two distinct states here and sellers constantly confuse them.

Suppression means the listing exists but is hidden from search — usually a detail page quality issue: missing main image, title over the category character limit, missing required attributes. Suppressions show in the “Fix Your Products” queue, they are self-serve fixes, and no appeal is required. If your catalog throws frequent suppressions, that is an operations problem, not a compliance problem.

Removal means Amazon pulled the ASIN for a policy reason and it appears in your Account Health dashboard under Product Policy Compliance. Removals require an appeal with evidence, and the evidence package differs completely depending on whether the trigger was a restricted product flag, a pesticide claim, a buyer safety complaint, or an IP notice. Our ASIN reinstatement guide maps each removal reason to its reinstatement path. The stakes compound daily: a removed ASIN loses keyword rank every week it stays down, and a listing that took two years to build page-one positions can fall off page three in a month.

ASIN-level enforcement also has a quieter cousin: ranking loss without removal. If sales dropped but the listing is technically live, start with our diagnostic for a sudden Amazon ranking drop before assuming enforcement.

Product-level risk: restricted categories, hazmat, IP, and authenticity

Product-level risk is about what you sell rather than how you sell it, and it splits into four families.

Restricted products. Amazon gates entire categories and product types — supplements, topicals, medical devices, pesticides, children’s products — and the restricted list changes without much announcement. The most common trap is keyword-triggered flagging: use “antibacterial,” “kills germs,” or “repels insects” anywhere in a listing and Amazon’s automated systems classify the product as a pesticide requiring EPA registration, regardless of what the product actually is. Ungating and approval workflows are covered in our restricted products guide.

Hazmat. Anything with lithium batteries, aerosols, flammables, or certain chemicals gets routed through FBA’s dangerous goods review. Without a compliant Safety Data Sheet on file — GHS 16-section format, less than five years old — inventory gets stranded in “hazmat review” limbo for weeks. Our Amazon hazmat guide covers the SDS requirements and the exemption sheet process for products that are not actually dangerous goods.

Intellectual property. IP complaints come in three flavors — trademark, copyright, patent — plus the counterfeit accusation, which is its own escalation tier. A single rights-owner complaint can remove an ASIN; repeated complaints threaten the account. The response strategy differs sharply depending on whether the complaint is legitimate, mistaken, or a competitor weaponizing the notice system, and we walk through all three in our IP violations guide.

Authenticity. Inauthentic complaints are invoice cases. Amazon does not need proof your product is fake — a buyer complaint plus your inability to produce clean supplier invoices is enough. Resellers get hit hardest, but private label brands see these too when supply chains run through trading companies. The invoice standards that actually pass review are detailed in our inauthentic complaints guide, and the broader regulatory documentation layer — CPC test reports, FDA registrations, COAs — is covered under product compliance.

There is also the offense side of this coin. If you own a brand, the same IP and authenticity systems become your enforcement tools against counterfeiters and unauthorized resellers — Brand Registry, Project Zero, Transparency. That playbook lives in our brand protection guide.

1P risk: Vendor Central chargebacks

Brands selling wholesale to Amazon face a completely different compliance regime. Vendor Central enforcement is financial, not access-based: Amazon deducts chargebacks for purchase order defects — late ASN transmission, carton label errors, prep noncompliance, on-time delivery misses — plus shortage claims and price claims that quietly shave 2% to 8% off invoiced revenue. Most vendors never dispute them because each individual deduction looks small. In aggregate they are not; we recovered $180K in Vendor Central chargebacks for one client by systematically disputing deductions the brand had been absorbing for years. The dispute mechanics and deadlines are in our chargeback disputes guide.

Prevention Systems vs. Reactive Appeals

Every compliance engagement falls on one side of a line: you are either building systems that stop violations from happening, or you are writing appeals after they happen. The economics are not close.

A functioning prevention system has four moving parts:

1. Weekly Account Health review. Someone opens the Account Health dashboard every week, triages new violations within 48 hours, and acknowledges or disputes each one before it ages into a rating problem. Violations left unaddressed hurt twice — once in the rating, and again as prior history when a future appeal is reviewed.
2. Policy change tracking. Amazon updates restricted product policies, category requirements, and compliance documentation rules continuously. The brands that get blindsided are the ones who learn about a policy from an enforcement email. Track the news feeds, but more importantly track your own category’s requirement pages monthly.
3. Pre-listing compliance screening. Before any new ASIN goes live: check the copy for pesticide-trigger and medical-claim language, confirm category gating status, verify whether the product profile hits hazmat criteria, and confirm the certification file is complete. Fifteen minutes per launch prevents the majority of product-level enforcement we see.
4. Voice of the Customer monitoring. VOC flags “CX Health” issues — the buyer complaints that eventually become safety investigations and authenticity flags. A SKU sliding into “Poor” CX Health is a leading indicator that enforcement is coming. Read the actual buyer comments, not just the status: three separate buyers mentioning a leaking cap is a product safety case forming in slow motion, and pulling the lot from FBA now costs a removal order instead of an ASIN.

On top of the weekly cadence, a quarterly compliance audit catches what weekly triage misses: listing copy that has drifted into claim territory through incremental edits, backend keywords added by a VA eighteen months ago, expired test reports, invoice coverage gaps from a supplier switch, and new gating requirements applied to your category since the last review. Two to four hours per quarter for a mid-size catalog; the output is a punch list, and most items take minutes to fix while the listing is still live.

Reactive appeals will always exist — no prevention system stops a competitor from filing a bogus IP complaint. But brands running the four systems above appeal a fraction as often, and when they do appeal, they win faster, because the documentation is already sitting in a folder instead of being chased across three suppliers in two time zones while revenue is stopped.

The Documentation Infrastructure Every Brand Should Maintain

Appeals are decided on documents. Amazon’s investigators do not take your word for anything; they cross-reference paper. The time to assemble that paper is now, not during a suspension. Four categories, kept current:

Supplier invoices. Real invoices — not pro formas, not order confirmations, not screenshots — covering at least the last 365 days of purchases. Each invoice needs the supplier’s name, address, phone number, and website; your business name and address exactly as registered in Seller Central; item descriptions and quantities that plausibly cover your Amazon sales volume for the period; and dates. Amazon calls suppliers and checks websites. An invoice from a supplier who cannot be verified is worse than no invoice.

Supply chain documentation. Purchase orders, packing lists, bills of lading, and freight documents that connect your invoices to physical inventory movement. For resellers, a letter of authorization from the brand or distribution agreement showing an authorized chain. When an inauthentic case escalates, Amazon increasingly asks for the full chain, not just the last invoice.

Safety Data Sheets. For anything containing liquids, powders, batteries, or chemicals — even products you are sure are not hazmat — hold a current SDS in GHS 16-section format from the manufacturer. FBA hazmat reviews are triggered by keywords and category, not by actual danger, and the review clock does not start until you upload the document.

Certifications and test reports. Category-dependent: Children’s Product Certificates backed by CPSC-accepted lab testing for anything a child might use, FDA facility registrations for supplements, EPA registration or establishment numbers for pesticides and pesticide devices, FCC and UL documentation for electronics, Certificates of Analysis for ingestibles. Keep them as clean PDFs, on letterhead, unedited — investigators reject documents that look modified, including ones that were merely cropped.

Organization matters nearly as much as possession. The working structure we set up for clients is one shared-drive folder per ASIN family containing invoices, supply chain docs, SDS, and certifications, with expiry dates in the filenames. The test is simple: could someone who is not you assemble a complete evidence package for any ASIN in under an hour? During a suspension, that hour is the difference between appealing on day one and appealing on day four.

We keep a complete, category-by-category checklist in our Amazon compliance documentation resource. The operational habit that matters: audit the folder quarterly. Documents age out — invoices roll past 365 days, SDS sheets pass five years, test reports lapse against new CPSC rules — and an expired document discovered mid-appeal costs you a week.

Escalation Paths When the Standard Process Fails

The published appeal path — submit through Account Health, wait — resolves most cases. When it does not, there is a ladder, and knowing the rungs matters because each one has a cost.

Rung 1: Account Health Support call. For account-level issues you can request a call from the Account Health team directly in the dashboard. They cannot reinstate you, but they can often tell you what the reviewing team found deficient in your last submission — intelligence that turns a blind rewrite into a targeted one.

Rung 2: Revised POA to the same queue. Most first denials are really requests for a better appeal. Rewrite against the specific deficiency, do not resubmit the same document. Repeated identical submissions get your case flagged and slow everything down.

Rung 3: Seller Performance escalation. A concise, evidence-forward escalation to Seller Performance leadership channels. This is where tone discipline matters most — escalations that read as angry or legalistic get routed back into the standard queue.

Rung 4: Executive escalation. The managing director escalation path (the successor to the old jeff@amazon.com route) puts your case in front of Executive Seller Relations. It works, but you get one credible shot; a sloppy executive escalation burns the channel.

Rung 5: Arbitration. The Business Solutions Agreement provides for arbitration. Real money, real timelines, and worth it only when the stranded funds or business value justify legal costs — typically six-figure situations.

Timing between rungs is a judgment call with a rule of thumb: give each rung one full response cycle — typically five to seven business days — before moving up, unless the response you received misstates your case entirely. Skipping rungs backfires; an executive escalation on day three, before a second POA was even attempted, reads as impatience rather than process failure and usually gets bounced back down to the standard queue with nothing gained.

For IP matters the ladder is different: retraction requests to the complainant, counter-notices for copyright, and Brand Registry escalations run parallel to the standard path. Sequencing them wrong can convert a solvable complaint into a permanent block.

What to Look For in an Amazon Compliance Agency

If you decide to bring in help, evaluate on three axes. First, violation-type depth: ask specifically about cases like yours — pesticide flags are not IP complaints are not verification suspensions, and an agency that treats them interchangeably will send generic appeals. Second, documentation fluency: the agency should be asking you for invoices, SDS files, and supply chain records in the first conversation, because that is what the appeal will be built from. Third, honesty about odds: some ASINs are not coming back, some suspensions take six weeks no matter who writes the POA, and an agency that guarantees reinstatement is telling you what you want to hear.

Two questions cut through most sales pitches. Ask what percentage of their reinstatement cases succeed on the first submission versus requiring escalation — a firm that tracks this will answer with a number and a caveat; a firm that does not track it will answer with confidence. And ask what they need from you in the first 24 hours — the right answer is a specific document list, because an agency that can start without your suspension notice, invoices, and Account Health screenshots is planning to send a template.

Pricing in this space typically runs $500 to $2,500 for single ASIN reinstatements, $2,500 to $7,500 for account-level suspension appeals, and $1,000 to $3,000 monthly for ongoing monitoring retainers. Cheaper usually means templates, and templates are precisely what Amazon’s reviewers are trained to reject — a failed template appeal does not just waste a week, it goes on the record every subsequent appeal is judged against.

Our own compliance practice covers both sides of the line described on this page: emergency reinstatement work with same-day case intake, and ongoing monitoring that keeps the Account Health dashboard boring. If you are evaluating whether that is worth it for your catalog, the compliance and reinstatement service page lays out exactly what is included, and our account suspension recovery case study shows what the reactive side looks like when it is done right — a full account deactivation reversed in 14 days. Whether you arrive with an active emergency or a healthy account you would like to keep that way, the starting point is the same: a clear read on which of the four risk categories applies to you, and what your documentation folder looks like today.