Marketplace one-identity rules

Amazon, eBay, Etsy, and Airbnb each have language about one person, one company, or one host identity. I read that as a business fact. I will not write a multiply-seller-ID guide, and I will not treat a new browser profile as a new citizen.

The useful caveat: isolation still matters. One identity is not one Chromium folder. You can follow the rule and still keep supplier, retail, and research apart. Ecommerce accounts on one PC is that map.

What the rule is about

Tax identity. Related accounts. Performance history. Host or seller agreements. It is not a command to mash every tab into everyday Chrome.

What I will not do: invent a second Seller Central login in a fresh fingerprint to dodge a metric. Clone a store stencil, not a session is for a second store you already have a right to run, not for a costume.

Platform-shaped siblings

Etsy shop isolation, eBay seller isolation, Shopify multi-store isolation, Airbnb listing isolation. Each page stays on authorized shops and hosts. Shopify is often happier with multiple stores you own. Marketplaces often are not. Read the current seller agreement. This is not legal advice.

Shipping extensions per store still apply when you have two authorized stores. Customer data never belongs in research still applies when you have one.

MaskWright 0.1: Windows 10/11, local profiles, no seats. A new folder is not a new tax ID. profiles.json is encrypted. Chromium user data is not.

What I do instead of multiplying IDs

Fix the performance issue as the owner. Use official appeals. Open a second storefront only where the platform already allows it (common on Shopify, constrained on many marketplaces). Keep folders split for ops quality.

Household IP is allowed. Same last mile is not a crime, and it is not a reason to create a fake second seller.

On a real Windows desk

I write the entity name on the profile: the LLC Amazon already knows, the Etsy shop Etsy already issued, the Airbnb host Airbnb already verified. I do not write new-identity-3.

When a marketplace asks about related accounts, I answer as the owner. A second MaskWright profile is not a disclosure. It is a cookie split for supplier versus retail versus research.

I keep payment instruments in the entity money profile. Putting a second card in a second folder to look unrelated is the chapter I will not write.

Household IP plus two job folders is normal. Household IP plus two secret Amazon sellers is the policy problem. Chrome profiles versus MaskWright does not change Amazon's graph.

If a cloud vendor promises "unique devices," they still hold the session. I keep seller admin local. SmartScreen on our unsigned build is a Windows note, not a reason to outsource Seller Central.

FAQ

Can two LLCs I own have two Amazon accounts?

That is Amazon's related-account policy, not a browser setting. Disclose what they ask. I will not write how to look unrelated.

Does MaskWright hide related accounts?

No. It separates cookie stores on your disk. Payment instruments, documents, and activity are still yours.

Chrome profiles versus MaskWright for one authorized store?

Chrome profiles can be enough. MaskWright helps when you also need per-profile proxies and several job folders.

Cloud browser to look like another device?

The vendor then holds the seller session. I keep admin local. Compare local versus cloud.

Does a new residential proxy count as a new identity?

No. An exit is an exit. Tax IDs and related-account rules do not move because the IP changed. Do not buy a line to look unrelated.

Follow the marketplace's identity rule. Isolate jobs that should not share cookies. Do not treat a profile as a new person.

I skip stealth second sellers, second cards in second folders as theater, and cloud browsers that hold the store for me. I split retail, supplier, and research. I answer disclosure questions as the owner. Household IP plus job folders is normal.

More notes sit under Ecommerce. Download MaskWright for the Windows launcher.