Last year, a Shenzhen-based seller came to me with two suspended accounts. Two brands, two sets of company documents, different legal representatives, different tax IDs, different bank accounts. He was convinced his separation was airtight, and he had no idea what went wrong.
I had him list the backend settings of both accounts side by side. By the third item, I knew. The return address. Both accounts routed returns to the same overseas warehouse in Ontario, California — the same street address. It was printed on the return labels and entered in Seller Central's return settings. Amazon's system saw it plainly: one address, two accounts, linked. Both went down the same day.
What made it worse: one of the accounts already had a performance warning on record. The moment the linkage verdict landed, the healthy account got dragged down with it. Three rounds of appeals, all circling the same argument — these are two independently operated companies. But the address matched, the evidence chain was right there, and Amazon didn't buy it.
This isn't a one-off. In twenty years in supply chain, I've seen this pattern several times a year. Sellers obsess over separating legal entities, tax IDs, and bank accounts, then trip over details they assumed didn't matter.
What Amazon Actually Checks: Relationships, Not Identities
A lot of sellers imagine a human reviewer comparing company names across accounts. That's not how it works. Amazon evaluates a bundle of relational signals: what do these two accounts share? IP addresses and networks, browser fingerprints, bank and credit card details, tax IDs, business addresses, emails and phone numbers, uploaded documents. Line up enough of these, and the system flags the accounts as "related" and deactivates them — often before a human ever looks at the case. Amazon doesn't publish the formula, and appeals won't tell you which signal matched.
One policy point first: Amazon does allow a seller to operate multiple accounts, but only with a legitimate business reason — genuinely different brands, separate legal entities — and every account has to stay in good standing. The details have been adjusted over the years, so check the current policy in Seller Central before you act.
Here are the five most overlooked linking factors, ranked by how often sellers miss them. Each with the mechanism, a real failure pattern, and what to do about it.
1. Return addresses and warehouse addresses — the logistics killer
The mechanism is blunt: return settings in Seller Central, FBA return addresses, and shared overseas warehouses used for return processing are all stored in Amazon's system in plain text. Two accounts listing the same return warehouse address is handing Amazon the linkage evidence yourself.
The failure pattern is the case I opened with. A common variant: a seller ships FBA inbound from the same freight forwarder's warehouse for multiple accounts, and the ship-from address on every carton label is identical. Same signal. The warehousing and logistics layer touches the most data, and it's the layer sellers scrutinize the least.
The fix: give every account its own return address. Even sharing one warehouse, get separate receiving identifiers — a different suite designation, a different consignee name — and make sure the address text in the backend isn't character-for-character identical. Cleaner still: route different accounts through different return processors. Same logic for ship-from addresses — separate them where you can, change the consignee name where you can't.
2. The background in your product photos and videos
This one is the stealthiest. Plenty of sellers shoot their own product photos, and both brands get photographed in the same warehouse corner — same racking, same floor, same lighting. The system can match visual elements across images. More directly, there's EXIF data: photos taken on the same camera, in the same shooting session, distributed across two accounts' listings, with timestamps and device info that line up perfectly.
Video is worse. Sellers film product videos with the warehouse sign, a forklift logo, or wall slogans visible in the background. Two accounts' videos shot on the same floor is a signed confession.
The fix: shoot different accounts' photos in different locations with different cameras, and strip EXIF data before uploading. Before filming video, scan the background and remove anything carrying a company identifier. Treat A+ Content images the same way.
3. Network and device fingerprints
Logging into two accounts from the same laptop on the same Wi-Fi is the classic way to die. Amazon logs more than IP — the browser fingerprint: OS version, browser version, screen resolution, installed plugins. Combined, it's enough to pin down a single machine.
Outsourced customer service and virtual assistants are the danger zone. Your rep serves several sellers from one computer, cycling through logins; Amazon sees one device touching five accounts, one with a violation on record, and marks the other four. I've seen a case where the seller was careful and got burned by a part-time designer — she logged into the seller's ad console and another client's account from her home computer, and the two accounts got linked.
The fix: one account, one dedicated computer, one network environment, no mixing. Outsourced staff go through Amazon's sub-account system with scoped permissions — never the master credentials. Revoke a departing employee's access the same day they leave.
4. Banking and tax information
Bank accounts, credit cards, tax IDs — these are hard-link factors. One match and there's almost no way out. Some sellers, trying to save effort, tie two companies' payouts to the same personal card of the legal representative, or reuse one registered address across entities. All of it gets caught.
A subtler variant: buyer-side payment data crosses over. Someone places a retail order on Amazon from a computer that has also logged into Seller Central, using the same credit card — now the buyer account and the seller account are connected. If that buyer account has also logged into a second seller backend, the chain is complete.
The fix: separate bank account, separate credit card, separate tax ID per account — and don't share the registered address either. Complete financial separation is the floor, not the ceiling.
5. Customer service scripts and operating habits
Two accounts running identical customer service templates — same phrasing, same signatures, same punctuation habits. Product titles built on the same structure, bullet points written the same way, restock rhythms and repricing habits moving in lockstep. Enough behavioral overlap and the system scores it.
This factor alone rarely kills an account, but it's the straw that breaks the camel's back. You've already tripped one or two of the signals above; add identical messaging, and the appeal response is basically "we have confirmed these accounts are related."
The fix: write separate service templates per account — at minimum, rewrite the wording. Stagger your operating rhythm; don't launch and reprice both accounts on the same day.
If You're Already Flagged: Answer Three Questions First
When a linkage suspension lands, the first step isn't rushing out an appeal letter — it's finding the link yourself. Amazon's appeal logic requires you to identify the related account, explain the relationship, and prove the two are independently operated businesses. An appeal that can't name the linking point, no matter how sincere, goes nowhere.
Two hard lessons: first, closing one of the accounts doesn't fix anything — the linkage record is already in the system. Second, don't open a fresh account to "stay alive" during the appeal; the new account gets linked instantly and the old account's appeal is effectively dead.
The blunt truth: separation means looking, in Amazon's eyes, like two companies that have never met. Legal entities, tax IDs, and bank accounts are just the entry ticket. Return addresses, photo backgrounds, and login devices are where accounts actually live or die. Every time you open a new account, run the checklist — address, images, devices, finances — all four independent, then launch.
