Amazon Affiliate vs Seller Account: Running Both by the Rules

Picture a food blogger. Her recipe site earns Amazon Associates commissions on kitchen gadgets. Two years in, she launches her own spice blends and sells them through Seller Central. One person with an Amazon affiliate account and a seller account, on the same laptop and the same home Wi-Fi.

Then she goes looking for advice and finds a pile of guides telling her to split everything up. Separate browsers with spoofed fingerprints. Separate proxies. Separate banks. Separate email domains. All so Amazon "can't link" the two accounts.

That advice is backwards.

Here's the thing. Amazon already knows she owns both accounts. She went through identity verification for Seller Central and a tax interview for Associates. No browser setup touches that data. The question was never "how do I stop Amazon connecting these" — it's "what do the rules allow, and how do I stay clearly inside them".

The second question has a duller answer, which is probably why so few people write it up. So that's what this covers.

Amazon affiliate vs seller account: what the rules actually say

Short version: as far as we can find, neither program forbids one person or business holding both kinds of account. Amazon's policies change, so treat everything below as a map, not the territory. The Associates Operating Agreement (and its Participation Requirements) and the Seller Central program policies are the documents that count.

Which is where the irritation starts. Those rules sit in half a dozen pages that cross-reference each other, nobody publishes a changelog, and edits land quietly — so the honest version of any sentence here is "that's what it said the last time we read it".

Situation	Generally allowed?	What to check
One person holds an Associates account and a Seller Central account	Yes, as far as the published terms go	Both sets of terms, current versions
Buying products through your own affiliate links (or asking friends, family or staff to)	No — the Associates rules prohibit purchases through your own links	Associates Participation Requirements
Paying or rewarding people to click or buy through your links	No	Associates Participation Requirements
Linking to your own listings from your content	Not banned outright, but disclosure matters	Associates terms plus FTC endorsement guidance
Reviewing your own product on Amazon (or having staff or family do it)	No	Amazon's Community Guidelines on reviews
A second Seller Central account	Only with a legitimate business need (e.g. separate brands run as separate businesses), and only while every account is in good standing	Seller Central's current multiple-account policy
A new account after a suspension	No	Seller Central policies on related accounts

Two things need spelling out. First, the Associates program requires a disclosure that you earn from qualifying purchases, on any page carrying your links. Second, if you own the product you're writing about, that's a material connection under the FTC's endorsement guidance in the US, and readers need to be told. Owning the brand doesn't make the content illegal. Hiding that you own it is the problem.

Why Amazon connects accounts in the first place

Amazon runs fraud detection across its programs, and it doesn't publish the details. What's widely understood is the shape of it: identity and tax records, payout destinations, device and browser characteristics, network information, and how accounts behave over time. (If you want the technical side of how browsers get identified, our WebGL fingerprinting explainer takes one signal apart in detail.)

The point of all that isn't to punish people who sell and also write. It's to catch specific abuse:

Commission self-dealing. Someone builds an affiliate site whose real job is collecting a referral fee on their own sales, or on their own purchases.
Review manipulation. Owners, staff or paid "customers" posting reviews of products they have a stake in.
Suspended sellers coming back. A banned seller opening a fresh account under a new name to keep trading.

Now the contrarian part. For a legitimate operator, being linked is boring and harmless. Amazon sees one person with a blog and a spice brand. Fine. What draws attention is behaviour, not the fact of a connection.

Disguising the connection flips that. If one account is ever reviewed, a deliberately fragmented setup — different fingerprints, different networks, banks chosen so payouts wouldn't match — looks exactly like what the detection exists to catch. And on Seller Central, related-account policies mean enforcement against one account can reach the other regardless. Hiding buys nothing and costs credibility.

The patterns that actually get accounts reviewed

Honestly, these are less mysterious than the forum threads make them sound.

Self-purchases through your own tag. The classic. It also happens by accident: you click your own link to check it works, then buy something in the same session a day later. More on preventing that below.

Incentivised clicks. Giveaways, rebates or cash-back offers tied to using your links. The Associates rules bar them.

"Reviews" that rank your own product first, every time, without saying you own it. Amazon may not care about your blog's opinions, but the FTC cares about undisclosed material connections, and a reader who finds out later cares a lot.

Reviews on Amazon from people with a stake. You, your staff, your relatives. Amazon's guidelines prohibit them, and it removes them and can act against the seller.

Trying to come back after a suspension. Opening another seller account while one is suspended is a policy breach in its own right. It's also the fastest route from "under review" to "permanently gone".

Notice that a shared laptop or home Wi-Fi isn't on this list. When both accounts are yours and both are run by the rules, sharing them isn't the issue — behaviour is.

My honest read is that most of the "separation" writing on this topic exists because proxy sellers and browser vendors are the only people with a commercial reason to publish about it. We are one of those vendors. So treat the paragraph above as the part of our own pitch we would rather you didn't skip.

The legitimate ways to do what people actually want

Most "separation" advice is trying to solve a real need with the wrong tool. Here are the needs, and Amazon's own answers to them.

"I want to earn on traffic I send to my own listings." Associates isn't built for this. You can never buy through your own links, and whether an affiliate link to your own listing earns anything depends on the current Associates terms, so check them. If your brand is enrolled in Amazon Brand Registry, Amazon runs the Brand Referral Bonus program for this exact case: you send off-Amazon traffic to your listings, tagged through Amazon Attribution, and earn a bonus on resulting sales. Check Amazon's program page for current eligibility and rates rather than trusting a figure from a blog post (ours included). It is, to my eye, the most underused answer in this whole topic.

"I want to promote my own products on my content site." You can, with clear disclosure that you own the brand, alongside the standard Associates disclosure. Plenty of publishers simply use plain, non-affiliate links for their own products. Less money, zero ambiguity. I think that's the right call for most people. Not everyone agrees.

"My VA or agency needs into Seller Central." Use Seller Central's user permissions. The account owner invites each person with their own login and only the access they need. Sharing the owner's password is how accounts get compromised, and it leaves you no record of who did what.

"I need a second seller account." Some businesses genuinely do — separate brands run as separate businesses, say. Amazon's current policy allows a second account only for a legitimate business need, and only while all your accounts are in good standing; trouble on one can take down the others. Read Seller Central's multiple-account policy before you open one, because the conditions change.

"I want separate entities and banks." Totally reasonable for accounting, tax or liability reasons. Do it for those reasons and declare everything honestly. It isn't a privacy shield, and treating it as one is where people get into trouble.

If you want to prove your traffic mix later (say, that your recipe site sends most clicks to third-party products), keep clean records. Something like privacy-first analytics on the content site gives you a defensible record of where readers actually went.

If one of the accounts gets flagged

Use the official route named in the notice. For Seller Central, that's the Account Health dashboard and its appeal process, usually with a plan of action that explains what happened and what you've changed. For Associates, it's whatever contact route the termination or warning email gives you.

What helps:

Be straightforward about the relationship. If you own both accounts, say so. Explain the business.
Attach real documents. Business registration, your disclosure pages, analytics showing the spread of products you link to, invoices for inventory.
Fix the cause before you appeal. If there was a self-purchase or a missing disclosure, correct it and say what you changed.
Keep it short. A reviewer reading a clear page does better by you than one wading through ten.

What doesn't help: opening a new account, changing devices or networks to look like a different person, or any appeal "trick". Those break the terms on top of whatever started the review. And, real talk, an appeal can fail even when you've done everything right. A terminated Associates account may simply stay terminated. That's the strongest argument for getting the basics right up front.

Where a browser profile tool fits (and where it doesn't)

We make an antidetect browser, so it'd be odd to pretend we have no stake here. So let's be precise.

What it doesn't do: make two Amazon accounts unconnectable in any way that matters. Amazon connects accounts through identity, tax and payment data a browser never sees. Using one to disguise a relationship Amazon's rules care about is a terms violation, and we won't help with that.

What it's actually good for:

Session hygiene. Keep Associates, Seller Central and your personal Amazon shopping in separate browser profiles. Each profile has its own cookies, so testing your affiliate links in one never leaves your tag sitting in the browser you shop from. That's how you avoid the accidental self-purchase above.
Team access done properly. With JustBrowser, team seats are free and unlimited. A seat runs only the profiles the owner shares with it, and shares carry view-only or launch permission, with owner, admin, member and viewer roles. Pair that with each staffer's own Seller Central user login and you get organised access without passing passwords around.
QA across marketplaces. Check how your links and listings render on amazon.com versus amazon.co.uk or amazon.de, or whether a geo-redirect sends a German reader somewhere sensible. Per-profile proxy routing (HTTP, HTTPS or SOCKS5, with your own proxies; none are included) handles the location side. Our affiliate cookie attribution testing guide covers verifying that tags fire. Test the click path, never complete a purchase through your own link.
Privacy. Keeping your business sessions apart from your personal browsing is reasonable on its own terms.

If you're also buying ads to send readers to your content site, ClickzProtect filters bot traffic out of that spend. Different product, different problem.

Other antidetect browsers, Multilogin and AdsPower among them, can do the same session-separation job. Check their published pricing directly, because those numbers move. JustBrowser is one plan: $9.99/month or $99.99/year, unlimited profiles, free team seats, on Windows x64 and macOS (Apple Silicon). The browser is the smallest part of this, though. Disclosures, Amazon's own permission tools and staying off your own links matter far more. Odd thing to put in our own blog post. Still true.

For broader context, see our Amazon multi-seller post and the antidetect myths post.

Frequently Asked Questions

Can one person run both an Amazon Associates account and a Seller Central account?

Nothing we have found in either program's terms stops one person or business from holding both. What gets an account reviewed is behaviour: buying through your own links, paying people to click or buy, publishing undisclosed reviews of your own products, or using accounts to get around a suspension. Read the current Associates Operating Agreement and Seller Central policies yourself, because both change.

Should I hide the connection between my Associates and Seller Central accounts?

No. Amazon already knows who owns both through identity verification and tax information, which no browser or network setup touches. If you are running both legitimately, being linked costs you nothing. If one account is ever reviewed, a relationship you went out of your way to disguise reads as concealment, and Seller Central's policies on related accounts mean enforcement on one can reach the other anyway.

Can I earn a commission on traffic I send to my own Amazon listings?

Never through purchases you make through your own links, and whether an affiliate link to your own listing earns anything depends on the current Associates terms. If you own a brand enrolled in Amazon Brand Registry, Amazon's own route for rewarding off-Amazon traffic to your listings is the Brand Referral Bonus program, measured with Amazon Attribution. Check Amazon's page for current eligibility and rates.

How should staff or an agency get into my Seller Central account?

Through Seller Central's user permissions, which let the account owner add people with their own logins and only the access they need. Don't hand out the owner's password. A browser profile manager can organise those sessions for a team, but it doesn't replace Amazon's permission system.

What should I do if Amazon flags one of my accounts?

Use the route named in the notice: the Account Health dashboard and its appeal process for Seller Central, or the contact route given in the Associates notice. Be straightforward about how the accounts relate, attach real business records, and fix the cause. Don't open a new account to get around a suspension; that breaks Amazon's terms and usually makes the outcome permanent.

Try JustBrowser

Native Chromium antidetect browser — not extension-based. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, so 40+ identity parameters are genuine, not faked. Local REST API for Playwright, Puppeteer, Selenium. Windows x64 and macOS (Apple Silicon). $9.99/month or $99.99/year. 7-day free trial, card required — cancel any time in the seven days and you are not charged. Unlimited profiles, unlimited team seats.

Get started → · How it differs from Multilogin / GoLogin / AdsPower