Here's the verdict up front: account linkage almost never comes down to one fatal mistake. In nearly every suspension case I've seen, the seller didn't get caught on registration details — they got caught on things they never took seriously. Same return address on two accounts. Same broadband line. Same browser on the same laptop. Same customer service script, typos included. Amazon doesn't convict you on a single clue; it convicts you on a chain of clues that corroborate each other. Your job is to cut every link in that chain.
One caveat: this is a guide to clean, compliant operations — not tricks for running ten burner stores.
Why does sharing one return address take down both accounts?
This is the most common cause of death I see among sellers who also run warehouse operations. A home-goods seller I worked with had Store A running beautifully — until Store B got flagged for review manipulation, and Store A was gone within a week. The one thing the two stores shared? The same warehouse address printed on every return label.
Why so deadly? A return address is one of the few things you actively hand Amazon, and it ties into logistics: the platform sees shipment volume from that address, tracking sequences, and return-reason distribution. Two accounts sharing a return address is essentially telling the system "we're the same business." Worse, once a return address enters your account history, it's very hard to wash out later.
How to audit yourself: pull the return address, default ship-from address, and customer service contact address for every account and line them up side by side. Look for overlapping streets, overlapping recipient names, overlapping phone numbers. Plenty of sellers change the address but keep the same contact phone — that counts too.
How to isolate: give every account its own return address. Practical options: use different 3PLs as return warehouses (the addresses are naturally different), or use virtual mailbox / returns-processing services with a distinct suite number per account. My rule of thumb: address, phone, and contact name — at least two of the three must differ.
And the warehouse angle: never store inventory for multiple accounts in the same warehouse zone just to save space. I recommend physical separation by account — different racking areas, separate returns-processing lines. When goods get mixed, mislabeled shipments happen: a buyer on Account A receives a return slip from Account B, screenshots it, files a complaint, and now both accounts are under review. I watched this happen to a client in Ontario last year — a 30,000-plus square foot warehouse, two accounts sharing one packing line, and a returns operator grabbed the wrong slip. Both accounts got investigated off the back of a single customer photo.
Does operating from the same office guarantee a linkage flag?
Not necessarily — but this is the most underestimated factor of the five. IP isn't "same office equals death." Amazon looks at how the IP is used.
What patterns are dangerous? Real cases I've seen: two accounts logged in for months from the same residential broadband IP — when one got suspended, the other followed quickly. Two sellers in different states sharing one cheap cloud server for operations (splitting the cost of a single VPS), with both logins coming from the identical static IP — the system read that as one operating entity. Another one: the phone app and the desktop both on the office WiFi. Different devices, same egress IP, same trail.
How to audit yourself: check each account's recent login IP records (the security settings in Seller Central surface unusual login alerts) and look for any shared public IP across accounts. Pay special attention to three scenarios: cloud servers, office broadband, and phone hotspots.
How to isolate: one dedicated network line per account. On a tight budget, at minimum do "one line per account" — Account A always on Line A, Account B always on Line B, never crossing. Don't share cloud servers; a VPS with a dedicated IP costs a few dollars a month, which is nothing next to what the account is worth. Run the mobile app on its own data plan, not the office WiFi. And remember: the goal is stable and independent. Constantly rotating IPs is itself a risk signal.
Browser and device fingerprints: how "clean" is your clean setup, really?
A lot of sellers think "two accounts on two laptops and I'm safe." Wrong. Amazon collects far more than which computer you used: OS version, screen resolution, timezone, language, installed plugins, canvas rendering signatures. Combined, these identify you with surprising accuracy.
The classic failure: same laptop, two Chrome profiles, one account each. The profiles are separate, but the machine fingerprint, system font list, and hardware characteristics are identical. The sneakier version: an anti-detect browser with multiple environments generated from the same template — identical timezone and language settings. It looks like two people, but the fingerprints are near-duplicates.
How to audit yourself: list every device and browser environment ever used for each account and flag any crossover. Ask three questions: has one computer ever logged into two accounts? Were multiple fingerprint-browser environments bulk-cloned from one template? Has the phone app been installed on two phones for the same account and switched back?
How to isolate: one device per account is the gold standard; at minimum, one fully independent browser environment per account, with differentiated parameters (timezone matching the account's region, different language, different resolution). Anti-detect browsers are fine, but generate and maintain each account's fingerprint separately — never bulk-clone. Keep login habits consistent too: same account, same device, roughly the same hours. Erratic login behavior triggers risk controls on its own.
Payouts, tax info, and service scripts: why are the soft traces the hardest to wash?
The first four are hard traces. This one is soft — and just as lethal.
Payouts and tax info need no explanation: one deposit account or tax ID on two accounts is an open-and-shut case. What's overlooked is the middle layer: two accounts using different sub-accounts under the same payment provider is fine — unless both sub-accounts withdraw to the same bank card, or the KYC documents belong to the same person. Another trap: registering under a relative's details, thinking "different legal entity means safe," then having both accounts' statements mailed to the same address. The address comes back around.
Customer service scripts and image EXIF data are the true invisible killers. I've seen a seller whose two accounts used the same response templates — same wording, same typos. A buyer posted both replies side by side on a forum, and Amazon's risk team followed the thread. Images work the same way: product photos shot on the same camera, through the same editing workflow, carrying identical device info and timestamp sequences in their EXIF. Even more common: A+ content with the same design style and copy structure — a human reviewer spots that in seconds.
How to audit yourself: put the two accounts' standard replies side by side — anything over half-identical needs a rewrite. Check product image EXIF data (free tools online) for matching device models and software versions. Deliberately differentiate your A+ pages and storefront styling.
How to isolate: fully independent payout chains — bank cards, withdrawal accounts, and KYC entities all separate. Write a distinct service script per account: even when the meaning is the same, the wording, tone, and signature must differ. Shoot product photos on different devices, in different settings, re-edit them, and strip EXIF before upload (most editors let you remove metadata on export).
Your 30-minute audit for tomorrow morning
Don't aim for perfection in one sitting. Run through this checklist first — it takes about half an hour:
- Line up every account's return address, ship-from address, and contact phone. Any overlap?
- Check login IP records per account. Any shared public IP?
- Device inventory: has any one computer or phone ever logged into two accounts?
- Fingerprint environments: differentiated parameters, or bulk-cloned from one template?
- Payout accounts, withdrawal cards, and KYC entities fully independent?
- Service scripts compared side by side; near-duplicates rewritten?
- Product image EXIF checked and stripped; A+ styling differentiated?
- Warehouse: inventory for multiple accounts physically separated, returns lines independent?
Running this list will surface at least two or three risks you didn't know you had. Linkage protection is never one-and-done — Amazon's risk rules keep evolving (always check Amazon's official site for the latest policy), but the logic holds: the fewer the traces, the safer your accounts. Make isolation a daily habit — it beats any appeal letter. No reinstatement letter, however well written, is worth as much as leaving no trail in the first place.
