Skip to content
PowerOps
All articles
Operations9 min read

Multiple Amazon Accounts: What Actually Links Them

Sellers lose accounts to connections they did not know they were making. A plain list of what links two accounts, and which of it a browser can do anything about.

Marketplaces are unusually good at spotting related accounts, and sellers are unusually good at creating links they never thought about. Before any tool enters the conversation, it is worth being honest about which links a browser can touch and which it cannot.

  • A bank account or card used on more than one seller account
  • A tax identity or registered business address that appears twice
  • A phone number or recovery email reused anywhere
  • The same product listings, photographs or supplier invoices
  • A support ticket that mentions the other account

This is the bucket that ends most stories. No browser setting reaches any of it, and any product implying otherwise is selling you something it cannot deliver.

  • A shared cookie jar, where one signed-in session is visible to the next tab
  • A device identity reported identically to every account you open
  • One outbound address for every account, all day
  • Stored logins and autofill offering one account's details on another's form
  • Extensions that read every page you open, including both accounts

These are what a separate environment per account fixes, and it fixes them by construction rather than by discipline: each profile is a directory of its own, opened by its own browser process, with the identity and route stored on the profile.

A workable setup

  1. One profile per seller account, created before the account exists rather than after
  2. A route assigned to that profile and kept, because a stable address is the unremarkable one
  3. Nothing else signed in inside it — no personal mail, no shared dashboard
  4. Notes on the row recording which entity, which email and which route it belongs to
  5. The same profile every time, so the environment the account was created in is the one it opens in

Why the order matters

Creating the account from a fresh environment is not the same as moving it into one afterwards. A profile made after the fact starts with none of the history the account already has, and the change of environment is itself a change. Set the profile up first, then open the account inside it.

Try it on your own machine

PowerOps runs the profiles described here. Every one of them keeps its own browser directory, device identity and network route, all from one desktop application.

Download for Windows

Put every browser environment in one place

Run isolated browser profiles from one desktop workspace. Each keeps an identity, a network route and a stored session of its own.