A partial account name and nothing else. Denying it without investigating does not answer the linkage.
For cases we accept: a real investigation of ownership, access and history, a dated connection matrix, and the sequence the notice actually requires.
A real person reads your case and replies within about an hour.
ASA Compliance Group operates Amazon Sellers Appeal. On related-account files we investigate the actual linkage, build the evidence and run the submission in Seller Central.
Include the notice with the partial name, your entity and ownership details, and who has ever had access. A real person reads it and replies in writing.
Or Shamosh · Founder and lead strategist
5,500+ enforcement cases since 2016. Every intake is personally assessed before acceptance.
Send what you have, including prior DIY or agency appeals. We say what is viable in writing before you commit.
Case review form
If the form does not load, open the contact form.
* Across ASA’s accepted and fully managed enforcement cases (all notice types we take on), not related account matters alone. Details under Proof.
That Amazon connected this account to another account or business record which is not in good standing, or decided the multiple-account structure does not meet policy conditions. The notice often shows only part of the linked account's name.
Amazon's code of conduct permits more than one account where there is a legitimate business need and all accounts are in good standing. So the existence of a second account is not itself the finding. The finding is the standing of what you are linked to, or the structure.
Five questions the investigation has to answer before anything is drafted:
Do you recognise the account? Not recognising it is a starting point, and it is not evidence.
A relationship that ended still leaves records, and dated proof that it ended is what answers it.
Ownership, an employee, an agency, a service provider, or compromised credentials. Each needs different evidence.
The other two are whether the structure is legitimate, and what sequence the notice requires. One thing this page will not do is suggest concealment. Changing devices, networks or using a VPN to obscure a relationship creates risk and resolves nothing, and reducing linkage to shared Wi-Fi misses most of how it actually happens.
Shared logins, devices, networks, addresses, payment information and agency access are connection paths worth investigating, not a published list of what Amazon detects. Amazon does not publish every signal it uses or how it weighs them, so treat these as where to look when reconstructing the overlap, and present only what your own evidence supports.
Amazon's multiple selling accounts policy is the reference for when a second account is permitted at all, which is the question a related-accounts notice is usually testing.
Shared network is only one connection path to investigate. The five paths below are common areas to reconstruct from the evidence.
The same people own or control both accounts, directly or through entities. Beneficial ownership counts, and separate legal entities do not establish separate control.
Where the structure is legitimate, the file proves the business need and that every account is in good standing. Where one is not, the sequencing question below is the real issue.
Someone who works across accounts. Shared logins, administrative access, a service provider operating several sellers, payment details or addresses in common.
Map the person's authorised scope, which accounts they touched, the dates, the credentials and whether access is still live. Amazon's guidance on account access is what good governance looks like here.
The account or business changed hands. Historical control leaves records regardless of what the current arrangement is, and a statement that the businesses are now separate is one of the weakest things you can send.
Someone accessed the account without authority. Real, and only supportable with access logs, incident evidence and dates. Asserting it without them reads as a convenient explanation.
You know exactly what the linked account is and it has a problem. This is the most straightforward branch and the one with the clearest sequence: Amazon often expects the original enforcement to be resolved before the related account can return.
Where the wrapper is a broader account-level termination rather than the linkage itself, the diagnosis is a Section 3 matter and the sequencing may differ.
Reviewers are testing a connection theory. Most rejected responses deny it without having looked for it.
The relationship denied with no investigation of owners, employees, contractors, agencies, devices, access, payments, addresses or entity history.
Offered as the whole answer. Amazon does not treat nonrecognition as evidence, and a partial name is usually traceable through your own records.
Entity documents supplied where the connection is operational access or historical control, which they do not address.
New devices, networks, VPNs or bank accounts after enforcement. It adds risk and resolves nothing.
The current account appealed while the named linked account is left unresolved, where the notice requires that first.
An argument built on Amazon requiring prior approval for every additional account, which is not the current rule.
Investigate before you deny. A supported denial is strong; an unsupported one closes the route.
A dated map of every identifier that could connect the accounts, marked known, unknown or ruled out with the evidence that rules it out:
This is the document that makes a denial credible. Without it a denial is an assertion, and reviewers have no way to distinguish an honest one from a convenient one.
Ownership and beneficial-ownership records, entity formation and closure, acquisition or transfer documents, addresses, banking identity and tax records where identity is in play. Where a relationship existed and ended, the dates and the signatures are the evidence rather than the narrative.
Seller Central user permissions, employee and agency relationships, service-provider history, access logs and any credential-compromise evidence. Linkage can also run through vendor accounts, brand registry, merchant tokens or historical control, which is why shared network is a thin theory on its own.
Where third-party access created the connection, show the real relationship and any completed access correction, without overstating that removing access resolves the linked account's standing. It does not.
Establish what the notice actually requires. Where Amazon expects the named account to return to good standing first, appealing this one alone will not move it, and knowing that early saves the cycle.
Where the link is genuinely wrong, the response is a supported dispute built on the matrix. Where it is right and the structure is legitimate, it is the business need plus good standing across every account.
If you genuinely do not recognise the name, say so and send the history anyway. The connection is usually findable in your own records, and finding it is what makes the response work.
Scoped historical outcomes on cases we accepted and fully managed. One seller voice below; deeper galleries live on account reinstatement.
Population: historical cases ASA accepted and fully managed (we prepared the compliance response and ran follow-ups in Seller Central). The figure combines reinstatement and restoration work across notice types in that managed population, not related account matters alone. Declined intakes and self-serve template buyers are not in the rate.
Success: reinstatement or restoration of the privileges Amazon had restricted for that file (account, listing, verification, funds, or related, depending on the case). Amazon decides every outcome; the rate is not a guarantee for future cases.
Review: the underlying records were independently reviewed. Verified as of .
More methodology context and galleries: account reinstatement proof.
“In less than 24 hours after the appeal, my account was reactivated with all products available for sale.”
More outcomes and video proof: account reinstatement proof.
For sellers who already have the Performance Notification. Broader questions: full FAQ library.
If Amazon says your account is related to another, send us the notice and the account history.
Listing removed rather than mis-described: listing reinstatement. Other notice names: all suspension types.
