- Section 3 is the suspension and termination provision in Amazon’s Business Solutions Agreement; it is not the name of one specific policy violation.
- The Performance Notification and Account Health entry are the controlling documents because they identify the account-specific concern and the next action Amazon is requesting.
- A response should follow the evidence: challenge an incorrect enforcement with verifiable proof, or address a real failure with completed corrections and preventive controls.
- Do not create another seller account to bypass the deactivation, alter documents or keep resubmitting a generic appeal that does not answer Amazon’s actual questions.
1. What Section 3 actually means
Section 3 of the Amazon Services Business Solutions Agreement is the part of the agreement dealing with the term, suspension and termination of Amazon services. Amazon’s India agreement states that Amazon may suspend or terminate services in circumstances that include a material breach that is not cured when applicable, suspected deceptive, fraudulent or illegal activity, activity that may harm customers, other sellers or Amazon’s legitimate interests, and an Account Health Rating below published deactivation thresholds.
That means “Section 3” is a contractual basis for enforcement, not a complete diagnosis of what happened in a seller account. The reason a seller was deactivated must be taken from the rest of the Performance Notification, Account Health page, linked policies and any examples Amazon provides.
2. Why two Section 3 cases can require completely different responses
One seller may receive a Section 3 notice because Amazon is asking for business or identity verification. Another may be asked to explain suspicious order activity, sourcing, related accounts, policy manipulation, restricted products or another risk. The words “Section 3” can appear in both cases even though the facts and evidence are different.
For that reason, do not begin by searching for a universal “Section 3 POA”. Begin by identifying the exact allegation, the affected marketplace/account, the examples Amazon names and the specific information or documents requested.
3. Read the Performance Notification line by line
Save the full notice before making changes. Record the date, case or notification reference, ASINs, order IDs, related account name, policy link, deadlines and every question Amazon asks. Separate general policy wording from facts Amazon says are specific to your account.
Pay particular attention to sections such as “Why did this happen?”, “How do I reactivate my account?” and any bullet list describing required documents. These parts usually tell you whether Amazon expects verification, a factual explanation, supporting evidence, corrective actions or a different workflow.
4. Common underlying issue families to investigate
Section 3 notices can be associated with several different issue families. Examples include identity or business verification, product authenticity and sourcing, multiple or related seller accounts, order fulfilment concerns, Seller Code of Conduct issues, restricted or non-compliant products, and activity Amazon believes is deceptive, fraudulent, illegal or harmful.
This is an investigation checklist, not a statement that every Section 3 seller committed one of these acts. Only the notice, Account Health history and seller records can establish which issue is relevant.
- Identity/business: legal name, address, directors/owners, bank/card details, tax and verification records.
- Sourcing/authenticity: supplier identity, invoices, quantities, authorization and traceability.
- Related accounts: ownership, user access, agencies, previous businesses, global registrations and current status of the linked account.
- Fulfilment: dispatch confirmation, carrier handover, first scans, manifests, tracking, cancellations and refunds.
- Conduct/policy: employees, third parties, buyer accounts, review or feedback activity, restricted listings and previous warnings.
5. Decide whether the case is a dispute, verification or corrective-action case
If Amazon has identified the wrong account, incorrect business relationship, incorrect product or another fact that can be disproved, the response should be evidence-led. State what is incorrect and attach the records that demonstrate the correct position. Do not invent a root cause just because a standard POA template contains a root-cause heading.
If Amazon is asking for verification, provide the requested genuine documents and ensure names, addresses and business details are consistent. If a real policy or process failure occurred, explain the verified cause, what has already been corrected and what control will prevent recurrence. These are three different response types and they should not be mixed without a reason.
6. Build an evidence pack before writing the response
Create one working folder for the case. Keep the original notice, relevant screenshots, invoices, supplier details, order and tracking data, user-access records, contracts, listing history, product photographs and evidence of completed corrective actions. Use only genuine and unaltered records.
Then map each item Amazon requested to the document or explanation that answers it. This prevents a common failure: sending a large bundle of evidence but still missing one of Amazon’s explicit questions.
7. Example: orders marked shipped but not actually fulfilled
If the notice refers to orders confirmed as dispatched but not fulfilled, compare the ship-confirmation time against the courier pickup, first carrier scan, manifest, tracking history, delivery outcome, cancellations and refunds. Determine whether the process allowed shipment confirmation before the parcel was genuinely handed over.
Where that failure is verified, the corrective action should address the real workflow: who confirms dispatch, what evidence is required before confirmation, how late pickups are handled and how exceptions are audited. Calling it a “system error” without supporting records usually leaves the actual control failure unexplained.
8. Example: identity or business verification
When the notice asks to verify the business or identity, do not convert the case into a long POA about operations. Focus on the specific documents and data Amazon requests. Check that the seller account name, business registration, tax details, address evidence and bank/payment information do not conflict.
If there has been a legitimate change of business address, ownership or legal entity, prepare a clear timeline and supporting official records. Avoid uploading multiple contradictory versions of the same information.
9. Mistakes that commonly weaken a Section 3 submission
Frequent problems include treating “Section 3” itself as the root cause, sending a generic apology, changing the story after each rejection, blaming a supplier or employee without explaining seller controls, answering only one ASIN when the notice is account-wide, or providing documents unrelated to the request.
More serious mistakes include altered or fabricated invoices, false third-party details, opening another account to continue selling, or hiding a legitimate relationship with another seller account. These actions can create additional enforcement risk beyond the original issue.
10. After submitting: keep the case consistent
Save the exact text and attachments you submitted. Monitor Performance Notifications, Account Health, Seller Central cases and the registered email address. If Amazon asks a follow-up question, answer the new question and keep the facts consistent with the earlier submission.
Reinstatement is not guaranteed. The outcome depends on the underlying issue, evidence available, seller history and Amazon’s review. If the notice is unclear, use Account Health Support or the support route available in the account to understand what Amazon is requesting before sending another version.
Section 3 notice triage checklist
- Save the complete Performance Notification and note the marketplace, date, deadline and response route.
- Copy every ASIN, order ID, related account, policy link and document request named by Amazon.
- Classify the case as verification, evidence-based dispute, corrective response or a combination explicitly requested by Amazon.
- Map each Amazon question to one genuine document or explanation before drafting the submission.
- Check names, addresses, dates, quantities and account details for consistency across all evidence.
- Keep a copy of the final submission and every attachment for follow-up consistency.
Frequently asked questions
Is Section 3 itself the violation?
No. Section 3 is the suspension and termination provision of Amazon’s Business Solutions Agreement. The account-specific reason must be taken from the Performance Notification and related policy information.
Does every Section 3 deactivation need a Plan of Action?
No. Some cases ask for verification documents, invoices, proof of account separation or other evidence. Follow the exact request in the notice rather than forcing every case into a three-part POA.
Can Amazon deactivate a seller even if the Account Health Rating looks healthy?
Yes. Amazon’s guidance says serious concerns such as deceptive, fraudulent, illegal or otherwise harmful activity can result in immediate action regardless of the displayed AHR.
Should I delete all listings immediately?
Not automatically. Containment may be appropriate in some product-policy cases, but deleting unrelated listings does not answer a verification, related-account or other Section 3 issue. Follow the scope of the notice.
Can I open another seller account while the appeal is pending?
Do not open or use another account to bypass an enforcement. That can create additional multiple-account or circumvention concerns.