Argus for e-commerce sellers

Isolation · Fingerprints

One seller account, one device, one story

A marketplace decides two accounts are the same operation from what it can see: the browser they arrive in, the storage that browser carries, and the machine underneath. Open two seller accounts in two tabs of the same Chrome and you have answered the question for them before you have listed anything.

An Argus profile is one account's whole world. It starts from its own directory — separate storage, cache and cookie jar, session restore off — and presents a coherent hardware identity generated as one set, so the platform, CPU cores, memory, screen, timezone and languages agree with each other the way a real machine's do. Two of your storefronts run side by side on one laptop without either being able to see the other.

One honest caveat, because marketplace rules genuinely differ: Argus is for accounts you are entitled to run — a second account the platform permits, separate brands, separate legal entities, separate clients, separate regions. It separates them properly. It does not make an account you are not allowed to hold into one you are.

Proxies

Arrive from the country the account sells in

A seller account registered in Germany that signs in from a Singapore address every morning is a question waiting to be asked, and the answer usually costs a verification cycle. Argus keeps proxies in a shared library and assigns them per profile, so the German storefront arrives from Germany, the Brazilian one from Brazil, and neither has to be reconfigured when you rotate the provider behind it.

Every proxy is health-checked for egress IP, country and latency, and a failing proxy blocks the launch rather than falling back to your own connection — which is the failure that actually links accounts, because it stamps one real address across every profile that happened to launch during the outage. The check also flags a datacenter exit and names the provider behind it, which for marketplaces is the difference between a residential-looking seller and one that gets an identity check on the first listing.

Authenticated SOCKS5 works here — plain Chromium cannot speak that variant at all — and WebRTC leak protection is applied as browser policy on every profile, not as a toggle somebody forgets.

Profiles · Folders · Projects

A folder per brand, a project per season

Sellers accumulate accounts faster than they retire them. Argus sorts profiles into folders with tags, custom status labels and notes, and the list searches, filters and pages instead of scrolling. Bulk launch, bulk edit and bulk delete cover the operations you would otherwise repeat forty times, and delete is soft — Trash first, restore available.

When a piece of work crosses those folders — a Q4 push that touches three brands, two proxies and a scraper — projects hold it together without moving anything. Membership is a link, not a move: nothing leaves its folder, the same shared proxy can serve several projects at once, and deleting the project leaves everything in it working.

Cookie sets · Teams

A VA can run the shop without ever holding the password

Sign in once, save the session as a cookie set, assign it to the profile, and the profile opens already signed in. Whoever is on shift — the listing assistant, the person answering buyer messages, the bookkeeper pulling settlement reports — lands inside the account without the password ever leaving your hands or the two-factor codes going to their phone.

The whole team works from one pool of profiles, proxies and cookie sets, synced to the organization rather than emailed around. Every write touches a single row, so two people working the same list at once cannot overwrite each other, and plan entitlements are enforced in the database rather than only in the interface.

Automation · Datasets

Competitor prices, in a table, before you open the laptop

The research half of selling — what the same item costs on three marketplaces this morning, which of your listings lost the buy box overnight — is a browsing job that nobody should do by hand. Automations run it inside a real profile, behind that profile's own proxy and fingerprint, so the pages load the way a customer in that market would see them rather than the way a datacenter scraper does.

The rows land in a dataset — a table your workspace owns, with columns you named and typed. Import what you already have from CSV, JSON or XLSX, edit in the grid, filter and sort, and export the whole thing back out. Tomorrow's run reads that same table to decide what to check, so the work list maintains itself.

Put it on the calendar and it happens before you sit down — with the one caveat that entries fire only while the launcher is open, and a slot it was closed for is marked missed rather than caught up later.