Here is my verdict up front: Amazon account linking almost never kills you for the obvious stuff.
I have seen too many sellers do everything right on paper. Separate email addresses. Separate business entities. Two laptops, even. Then one account gets flagged, and the other one goes down with it. The appeal response is always the same single line: related to a deactivated account. Related how? The seller usually has no idea.
There are two sides to this. One side is surface-level separation, which everyone knows how to do. The other side is five hidden factors, and in my experience, most linking cases die on these. Whether your account lives or dies has little to do with how clean your surface separation looks. It comes down to whether these five leaked.
Back in the fall of 2023, a home-goods seller in California came to me. Two brands, two accounts, running clean for over three years. Account A got pulled into a review over a counterfeit complaint. He figured account B was untouched and kept shipping. On day three, account B was frozen too. Reason: related account violation.
We went through everything. Different companies, different emails, different computers, different credit cards. All clean. The problem turned out to be the return address. Both accounts listed the same 3PL warehouse as their FBA return address. When Amazon updated the return-settings page, his ops person copy-pasted the address to save time. One paste, three years down the drain. Account B was sitting on over $400,000 in inventory, one month before peak season, and he could not move a single dollar.
That is the cruelest thing about linking: Amazon does not argue with you. It only reads data. Match on one factor and the whole cluster counts as one.
Factor one: IP and network environment
A lot of sellers think swapping IPs solves it. Naive. Amazon does not look at a single IP. It looks at the subnet, the ISP and ASN, and the login trail. One office broadband line, a few computers rotating through three accounts, IPs changing but always inside the same /24 block — to the system, that is one household.
The sneakier one is the phone. In 2022 I watched a Shenzhen team with airtight separation on desktop get linked because an operator answered one customer message from a phone connected to the office WiFi. Same egress IP as the computers. You can configure an anti-detect browser perfectly and still lose to somebody being lazy.
Factor two: device fingerprint
Canvas fingerprint, WebGL rendering signature, installed fonts, screen resolution, timezone, user agent — combined, they are more precise than an ID card. Two browser profiles on the same machine with one sloppy setting will leak. The most unfair case I ever saw: two accounts on the same Mac, one on Safari, one on Chrome. The seller thought different browsers meant safety. Amazon does not care which browser you use. It reads the machine.
Factor three: bank account and charge method
This is the hardest of the five. The deposit bank account and the charge credit card — match the account holder name and it is as close to a confirmed link as it gets. Early in 2024, an auto-parts seller ran two accounts on virtual cards with different card numbers and thought he was safe. Same issuing bank, same billing address, same cardholder name. Linked. Remember: Amazon is more serious about money than about anything else. A different card number does not mean a different account.
Factor four: tax identity
The EIN or SSN, plus the name, address, and tax number on the W-9 or W-8BEN — a three-in-one package. Two accounts registered under the same tax ID means if one goes down, the other follows. That is ironclad. Some sellers register under a relative's name and think a different name keeps them safe — then they put down the family home address and get matched anyway. Tax identity sits at the core of Amazon's KYC, and it carries the highest confidence of any factor. Check Amazon's official site for the latest requirements.
Factor five: warehouse and return addresses
This is the trap from my opening story. FBA return address, self-fulfilled warehouse address, customer-service contact address — any overlap is a link point. Many sellers change the company, the tax ID, and the bank account, but keep the same overseas warehouse, because switching warehouses means re-stocking and re-labeling. Expensive and annoying. And that exact annoyance is the most common cause of death I see.
Running the numbers: cost first, benefit second
That is my habit with any plan. Cost first.
| What you spend on | Rough cost | What it prevents |
|---|---|---|
| Dedicated network (leased line or VPS) | tens of dollars a month | subnet linking |
| Anti-detect browser | tens of dollars a month per profile | device fingerprinting |
| Separate entity plus tax ID | a few hundred dollars one-time (varies by state) | tax-identity hard link |
| Separate bank account plus charge card | mostly the time cost of opening accounts | money-trail hard link |
| Separate return and warehouse addresses | roughly $10–50 a month | address linking |
Add it up and the "isolation cost" of one account tops out around $1,000–2,000 a year. Now look at the other side. A dead account means inventory frozen in FBA — tens of thousands to hundreds of thousands of dollars sitting in a warehouse. Funds frozen for the whole appeal, weeks at best, months at worst. Listing rankings, accumulated reviews, brand registry — all wiped to zero. Hit peak season and every day of stockout bleeds money.
Put plainly: prevention costs a thousand or two a year; one dead account costs tens to hundreds of thousands. A schoolkid could do this math. So why do sellers still get caught? Because prevention is money you spend every day, visible; the catastrophe is a probability, invisible. Human nature is stingy with small visible money and generous with big invisible risk.
A counter-intuitive take
Many sellers pour all their money and energy into anti-detect browsers while getting lazy on the bank account. Backwards. Browser fingerprinting is an arms race — Amazon's detection keeps upgrading, and what works today may leak tomorrow. But a bank account plus tax ID match cannot be dodged by any tooling. Money and identity are hard links. IP and device are soft links. Never touch a hard link; isolate the soft ones as best you can. Do not get the order wrong.
A three-tier risk framework
When I audit a client, I work in three tiers. Red line, fix immediately: same tax ID, same deposit account, same charge card. Touch any one of these and the account is a ticking time bomb. Yellow line, isolate within the month: same subnet, same device, same return address. Separate them step by step. Gray line, watch long-term: identical customer-service templates, reused product images, matching supplier invoice headers. None of them fatal alone, but piled together they become the last straw when the system decides you are "highly suspected."
Here is the prevention checklist. Print it, stick it on the wall, and go through it every quarter:
- One network per account. Physically separate the operations network from the office network.
- One device environment per account. Regularly check browser profiles for fingerprint leaks.
- One bank account and one charge card per account. Never reuse.
- Independent tax IDs. No overlap in W-9 or W-8BEN information.
- Independent return and warehouse addresses for every account.
- Independent phone numbers for two-factor authentication.
- Independent customer-service emails. Do not share one domain mailbox.
- No reusing hero images or A+ content across accounts.
- For the first three months, a new account touches nothing belonging to an old account.
- Run a linking audit every quarter. Zero tolerance on red-line items.
Account linking is not a technology problem. It is a laziness problem. Every shortcut you take today is a landmine for future you — the only question is when it goes off.
By Lao Mi, Supply Chain Veteran (20 yrs)
