Understand what kind of Amazon suspension, deactivation, or block you are facing.
Amazon does not review identity checks, related accounts, authenticity complaints, review abuse, performance failures, and payout holds in the same way. This page helps you tell those case types apart so you can see what Amazon is likely reviewing and what kind of response usually fits.
Amazon case types, grouped by how Amazon usually reviews them
These case types are grouped by the questions Amazon usually asks in practice. Use the summaries below to understand what each category means, what Amazon is typically checking, and how it differs from similar notices.
Verification & Payments
These cases are usually about identity, business records, banking details, cards, and document consistency. Amazon is typically checking whether the account can be verified cleanly, not whether the seller can write a persuasive appeal.
Banking Details
Amazon cannot verify the bank account receiving disbursements because the holder name, account details, or bank proof do not match the seller record.
Amazon is usually looking for
Updated deposit-method details and a recent bank document that exactly matches the account holder, account number, and bank name in Seller Central.
How this differs
This is usually narrower than a full identity review. Amazon is often focused on bank ownership and exact-match proof, not a wider misconduct accusation.
Adjacent scenarios
This case already has a dedicated guidance page.
Credit or Debit Card Information Verification
Amazon cannot validate the credit or debit card on file for charges, verification, or account maintenance.
Amazon is usually looking for
A chargeable card with the correct billing details, available authorization, and cardholder information that matches the account.
How this differs
This is usually a billing or verification issue, not a related-accounts, authenticity, or policy-abuse case.
Adjacent scenarios
This case already has a dedicated guidance page.
Documentation Verification
Amazon is rejecting uploaded documents because they are unreadable, outdated, incomplete, or inconsistent, and the safest live route is still the broader verification umbrella rather than a narrower child page.
Amazon is usually looking for
The exact documents Amazon requested, submitted in the right format, with clear scans and details that match the seller record.
How this differs
This usually stays on the umbrella verification route until the record points more honestly to banking details, identity verification, legal-entity issues, or a required-information wrapper.
Adjacent scenarios
This case already has a dedicated guidance page.
Failure to Provide the Required Information
Amazon asked for specific documents or answers and believes the response did not address what was requested.
Amazon is usually looking for
A direct response to each request, backed by the exact documents or facts Amazon asked for.
How this differs
This usually means the response missed the request, not that the seller necessarily has a separate policy violation.
Adjacent scenarios
This case already has a dedicated guidance page.
Identity Verification
Amazon is trying to confirm the real person or business behind the account, and sometimes the beneficial owners behind it.
Amazon is usually looking for
A complete identity-verification record with matching personal, business, and ownership documents in the sequence Amazon can check.
How this differs
This is broader than a simple document re-upload because Amazon may be checking the full ownership and business record.
Adjacent scenarios
This case already has a dedicated guidance page.
Legal Entity Information Update
Amazon found a mismatch or outdated information in the legal business name, entity type, registration details, or tax identity tied to the account.
Amazon is usually looking for
A corrected legal-entity record supported by business documents that match the updated information.
How this differs
These cases often look like bank or document problems at first, but the real issue is the business record Amazon is trying to verify.
Adjacent scenarios
This case already has a dedicated guidance page.
Account Access & Related Accounts
These cases focus on who controls the account, whether another seller account is connected, or whether a security problem is masking the real issue.
Related Accounts
Amazon believes this seller account is connected to another account through ownership, operators, devices, payment details, access history, or other shared signals.
Amazon is usually looking for
Proof that explains the connection: reactivation of the linked account, evidence of genuine separation, or evidence that the link came from past access or compromise rather than shared control.
How this differs
The key issue is not just that two accounts touched the same details. Amazon is usually trying to decide whether there is real current control.
Adjacent scenarios
This case already has a dedicated guidance page.
Hacked Account
Unauthorized access changed the account, exposed sensitive details, or created activity Amazon now treats as a risk.
Amazon is usually looking for
Evidence the account is secure again, access was reset, unauthorized changes were identified, and any resulting order or account issues were addressed.
How this differs
A hack is not automatically a related-accounts case, but it can become one if the breach created links to another seller account.
Adjacent scenarios
This case already has a dedicated guidance page.
Generic Blocking Notice
The current notice is too vague to identify the real problem, often because Amazon is now showing only a generic rejection or blocking message.
Amazon is usually looking for
A reconstruction of the notice history and account events so the real underlying case type can be identified before sending another submission.
How this differs
This is not a case type in the same sense as related accounts or counterfeit. It is a warning that the visible message may no longer show the root cause.
Adjacent scenarios
This case already has a dedicated guidance page.
Authenticity & Supply Chain
These are trust and sourcing cases. Amazon is usually testing whether the products are genuine, whether the invoices are reliable, and whether the supply chain can be traced.
Counterfeit Products / Inauthenticity
Amazon believes the products may be inauthentic and wants credible proof of origin for the cited ASINs.
Amazon is usually looking for
Supplier invoices, traceability records, and an explanation that shows where the products came from and why the documents can be trusted.
How this differs
This is different from IP complaints or listing mismatch. The central issue is whether Amazon believes the goods are genuine and traceable.
Adjacent scenarios
This case already has a dedicated guidance page.
Unsupported Sales
Amazon believes the products sold on the account are not supported by reliable sourcing or traceability records, even if the seller says the goods are genuine.
Amazon is usually looking for
Recent sourcing records, supplier details, and a clear explanation of how the cited sales can be verified.
How this differs
Unsupported sales overlaps with inauthenticity, but the problem is often incomplete traceability rather than a direct counterfeit allegation.
Adjacent scenarios
This case already has a dedicated guidance page.
Manipulated Invoices
Amazon believes the invoices or supporting documents were altered, fabricated, or otherwise unreliable.
Amazon is usually looking for
A direct explanation for the concern and, where possible, independent proof from the issuer or supplier that confirms the documents are genuine.
How this differs
Once Amazon suspects document manipulation, the case is more serious than an ordinary document-quality problem.
Adjacent scenarios
This case already has a dedicated guidance page.
Intellectual Property
These cases are driven by rights-owner complaints or alleged misuse of protected content. They need different evidence from authenticity or listing-fit disputes.
Intellectual Property Violation
Amazon received or identified a trademark, copyright, patent, or other rights complaint connected to the listing or product.
Amazon is usually looking for
Proof of authorization, proof of non-infringement, or targeted corrective steps that fit the exact complaint.
How this differs
IP is about rights and permission. It is not the same as proving a product is genuine or proving a listing was matched correctly.
Adjacent scenarios
This case already has a dedicated guidance page.
Catalog Integrity
These cases concern how products were listed, grouped, or matched to detail pages. Amazon is usually checking whether the listing created customer confusion or misrepresented the item.
Misuse of ASIN Variations
Amazon believes unrelated items were grouped as variations in a way that misled buyers or distorted the catalog.
Amazon is usually looking for
Catalog corrections plus an explanation of what was grouped incorrectly, why it happened, and what controls now prevent it.
How this differs
This is a catalog-structure issue, not usually a supplier-proof or rights-owner case.
Adjacent scenarios
This case already has a dedicated guidance page.
Product Detail Pages Infringement
Amazon believes the offer was attached to the wrong detail page, wrong condition, or wrong product representation.
Amazon is usually looking for
Invoices and product proof showing the item matched the ASIN, condition, and product detail page used.
How this differs
The product may be genuine and still fail here if it was listed against the wrong detail page.
Adjacent scenarios
This case already has a dedicated guidance page.
Product Feeds
Amazon feed uploads were blocked, deleted, or suppressed, but the feed symptom usually sits downstream of another unresolved listing, catalog, or account issue rather than deserving its own live route.
Amazon is usually looking for
Reconstruct the earlier enforcement and decide whether the real issue is ASIN-level suppression, catalog structure, restricted-product pressure, or a broader account block before treating feed restoration as the main task.
How this differs
This stays hub-first because Product Feeds is usually a downstream symptom. Variation misuse is about invalid grouping, detail-page infringement is about offer-to-page mismatch, and generic blocking means the visible message may still be hiding the root cause.
Adjacent scenarios
This case should stay on the hub until the deeper underlying issue is clearer.
Restricted & Regulated Products
These cases focus on whether the item is allowed for sale and whether the listing, shipping, and compliance controls meet Amazon's rules for regulated products.
Restricted Products
Amazon believes the account listed or sold products that are prohibited, unsafe, or otherwise restricted.
Amazon is usually looking for
Proof the product is allowed and listed correctly, or removal and control measures that prevent restricted items from being listed again.
How this differs
This category is broader than age-restricted delivery issues and narrower than a vague generic blocking message.
Adjacent scenarios
This case already has a dedicated guidance page.
Age-Restricted Products
Amazon is focused on age-verification, delivery controls, or repeat compliance failures for age-gated products.
Amazon is usually looking for
Evidence that the cited offers and shipments followed the required age-verification and fulfillment rules, or a clear factual challenge to Amazon's conclusion.
How this differs
This is more operational and product-specific than a broad restricted-products case.
Adjacent scenarios
This case already has a dedicated guidance page.
Performance Metrics
These cases are driven by account health metrics and buyer impact. Amazon is usually looking for the operational cause of the failures and the controls that now prevent them.
Order Defect Rate
Amazon sees too many serious buyer problems on the account, such as A-to-z claims, chargebacks, or negative feedback.
Amazon is usually looking for
A root-cause analysis that explains what caused the defects and the operational changes that now reduce buyer harm.
How this differs
ODR is about harmful outcomes for buyers. It is not the same as a late shipping confirmation problem.
Adjacent scenarios
This case already has a dedicated guidance page.
Late Shipment Rate
Amazon sees too many seller-fulfilled orders confirmed after the expected ship date.
Amazon is usually looking for
An explanation of why ship confirmations were late and what changed in order handling, staffing, carrier cutoff management, and confirmation timing.
How this differs
Late Shipment Rate is about when you confirm shipment, not when the carrier delivers.
Adjacent scenarios
This case already has a dedicated guidance page.
High Order Cancellation Rate
Amazon sees too many orders canceled before shipment because inventory, syncing, or acceptance controls were unreliable.
Amazon is usually looking for
A root-cause explanation tied to inventory accuracy, order acceptance, and the controls that now prevent oversells or bad accepts.
How this differs
This differs from unfulfilled orders because the orders were canceled before they reached shipment.
Adjacent scenarios
This case already has a dedicated guidance page.
Unfulfilled Orders
Amazon believes the seller accepted orders and then failed to fulfill them, and the current live route is still the broader Performance Issues page rather than a standalone unfulfilled-orders page.
Amazon is usually looking for
A factual explanation of why the orders were accepted, what blocked fulfillment afterward, how the affected buyers were remediated, and what now prevents accepted orders from outrunning real fulfillment capability.
How this differs
This is not the same as high cancellation rate or late shipment. The key question is why accepted orders were left unfulfilled at all, even though the live public route still sits under the broader performance umbrella.
Adjacent scenarios
This case already has a dedicated guidance page.
Review Manipulation & Abuse
These are high-trust cases involving system abuse, not ordinary seller mistakes. Amazon usually expects clear facts, credible controls, and direct answers.
Fake Reviews / Review Manipulation
Amazon believes the account used, encouraged, or benefited from manipulated reviews or review-seeking practices that violate policy.
Amazon is usually looking for
A factual explanation of what happened, any third parties or methods involved, what was stopped, and the controls that now prevent repeat conduct.
How this differs
These cases are judged as trust and manipulation issues, not ordinary performance or customer-service problems.
Adjacent scenarios
This case already has a dedicated guidance page.
Improper FBA Reimbursement Claims
Amazon believes reimbursement claims were unsupported, excessive, or abusive.
Amazon is usually looking for
Shipment-level and inventory-level proof showing the reimbursement claims were legitimate and tied to real units and events.
How this differs
This is not just a payout dispute. Amazon treats repeated improper claims as abuse of its reimbursement system.
Adjacent scenarios
This case already has a dedicated guidance page.
Funds & Payment Recovery
These cases are about withheld payouts, reserve pressure, or money Amazon says the account owes. The financial pain is immediate, but the underlying reason may sit elsewhere.
Negative Balance
Amazon says the account owes money and is restricting the account until the balance is repaid or resolved.
Amazon is usually looking for
Repayment or a documented explanation of the balance, together with any card or billing updates needed to clear the account.
How this differs
This is different from a funds hold. The core issue is money Amazon says is owed, not just delayed disbursement.
Adjacent scenarios
This case already has a dedicated guidance page.
Funds on Hold
Amazon is holding payouts because of reserves, verification pressure, policy risk, or a linked enforcement issue.
Amazon is usually looking for
A clear timeline of disbursement delays, reserve changes, verification requests, and any related policy or account notices.
How this differs
Funds on hold is often the effect of another problem. The right response depends on whether the hold is driven by verification, performance, or policy risk.
Adjacent scenarios
This case already has a dedicated guidance page.
Mixed cases that need careful diagnosis
Some of the hardest cases involve two problems at once. When that happens, the order of response matters because one issue can change the evidence, timing, and strategy for the other.
Related Accounts plus Hacked Account
A security breach can create the appearance of related accounts or expose real links Amazon then treats as suspicious. Both the compromise and the linkage need to be explained.
Next step
Map the breach timeline, every person with access, and every account or device affected. If Amazon is already pointing to linked accounts, start there while keeping the security evidence organized.
Counterfeit or Unsupported Sales plus Manipulated Invoices
A sourcing problem becomes much more serious if the documents submitted to defend it look altered or unreliable.
Next step
Stop uploading more paperwork until the document trail is defensible. Rebuild the evidence chain first, then respond through the manipulated-invoices route only if the documents can withstand scrutiny.
Restricted Products plus Generic Blocking
A seller may end up with a vague rejection message even though the real problem may be repeated restricted-product enforcement.
Next step
Start by reconstructing the notice trail, product history, policy warnings, and affected ASINs before responding. If the visible wording is still vague, diagnose the hidden theory first instead of forcing a restricted-products appeal too early.
Fake Reviews plus Warning-Stage Intervention
Some review-manipulation cases appear first as warnings or Account Health outreach before a full suspension.
Next step
If the warning already points to review manipulation, treat it seriously now. Early action is often safer than waiting for a full block.
Identity, Bank, and Legal Entity Loops
Identity checks, bank verification, and business-record mismatches often appear as separate requests even though Amazon is reviewing one connected record.
Next step
Treat the account details, bank details, and entity documents as one file. The goal is one clean, consistent record Amazon can verify from end to end.
Amazon seller terms worth understanding before you respond
These are the terms that most often help sellers make sense of a notice, an Account Health warning, or a document request. The goal is plain-language clarity, not internal jargon.
Account Health Dashboard
The Account Health view in Seller Central. It shows active account or listing issues, the reason Amazon is showing, and the next step it is asking for.
Account Health Support
An Amazon support function that may contact sellers or offer a call before full enforcement in some cases, especially when the issue is still at warning stage.
Know Your Customer
Amazon's identity and business verification process for confirming who owns and controls the account.
Order Defect Rate
A customer-harm metric built from issues such as A-to-z claims, chargebacks, and negative feedback. It measures buyer outcomes, not just shipping timing.
Late Shipment Rate
A seller-fulfilled metric based on orders confirmed shipped after the expected ship date. It is about confirmation timing, not the carrier's final delivery date.
Plan of Action
A written response that explains root cause, corrective actions, and the steps that prevent recurrence. It is only as strong as the evidence and controls behind it.
Order Cancellation Metric
The metric Amazon uses when sellers accept orders they cannot actually fulfill. It usually points to inventory accuracy, sync, or order-acceptance discipline problems.
Common questions about suspension and deactivation case types
These answers are meant to help you identify the right case family before you upload more documents or send another appeal.
If the case type is clear, follow the right guidance. If it is mixed, start with a clean case review.
This page is meant to help you classify the problem, not force a bad fit. If the facts still cross categories, start with a full review. If withheld funds, stranded inventory, or repeated rejections make delay risky, use the emergency option because the timing issue is real.