Antidetect browser for e-commerce teams
An antidetect browser for e-commerce teams keeps each store's fingerprint, cookies and proxy settings in its own browser profile. WGBrowser includes Amazon, eBay, Shopify and PayPal platform presets, with groups for organizing profiles and assigning team access. You can use separate profiles for stores and payment accounts when their login data and operators need to be managed separately.
Before creating profiles, list the stores, sales platforms, payment accounts and people involved. The browser stores and opens the profiles; product listings, orders and money-related operations remain on the relevant platform's website. This guide covers the setup and handoff checks for a team working across those sites.
Organize profiles around your store list
Record each store's platform, name, account identifier, operating region and owner. Choose groups that reflect how work is assigned: by client if operators handle particular clients, or by platform if teams specialize in one marketplace. Use a consistent naming pattern so a member can match the profile list to their daily work.
Keep using the existing profile for the same store, and create another profile when adding a separate store. Notes, tags and Startup URLs can describe the purpose of a profile. These labels help you choose the right browser window, but you should still verify the store shown on the website.
You can drag profiles into groups and search the list by name, profile number, exit IP, note or account. Organize existing profiles before opening access to new members. See team access for the relationship between groups, roles and permissions.
Create profiles with platform presets
Choose New profile and select the platform under Account & 2FA. Enter its account details, then configure the device template and proxy. Amazon, eBay, Shopify and PayPal have presets. Selecting one prepares the platform information for the profile; you still need an account on that website and must complete its sign-in process.
The browser engine applies the saved fingerprint, and each profile has separate cookies and local storage. Open the target website, sign in and compare the store identity with your list. Close and reopen that profile to check the saved login data before repeating the setup for more stores.
The same group and naming conventions can work across platforms. For a more specific workflow, read about Amazon account profiles or Shopify store profiles. Keep platform-specific permissions and day-to-day tasks attached to the correct store in your records.
Check each store's proxy exit
Prepare the proxy connection details for stores that require a particular exit. WGBrowser supports HTTP, HTTPS and SOCKS5, with a library for saving and checking connections before assigning them to profiles. After entering the address, check the actual exit IP and region instead of relying on the provider's label.
In Fingerprint, Language, Time zone and Location can use Follow IP. The client checks the exit before opening the profile and applies the corresponding settings. If the detected region differs from your operating plan, investigate the proxy configuration first. Changing the language alone does not change the network exit.
A saved proxy endpoint may remain the same while its provider changes the exit IP. Record the detected result when reviewing a connection or renewing a service. The residential proxy guide explains proxy types and the difference between connection details and the exit a website sees.
Separate payment account logins
If PayPal or another payment account needs separate login data, proxy settings or access permissions, create a dedicated profile. Name the account clearly, record its owner and list the stores it serves. You can place store profiles and payment profiles in different groups so that members receive access according to their responsibilities.
Browser profiles separate fingerprints, cookies, storage and proxy settings. They do not change payment relationships already recorded by a sales platform, or transfer ownership of a payment account. Check those relationships in your business records and in the platform itself.
Review store and payment profiles separately during a handoff. A member who only operates listings may not need the payment profile or its login material. Check whether a share or export includes passwords and 2FA secrets before transferring it, and keep group visibility and export permissions consistent with the person's role.
Schedule team handoffs and computer changes
Assign members access to the groups they need, then review permissions for editing profiles, managing proxies and exporting profiles. The client checks whether a profile is in use; the same profile can run on one device at a time. The current operator should finish work and close it before a colleague opens it.
Review Sync before moving to another computer. Cookie changes sync while the profile is running. Selected LocalStorage, IndexedDB and other local data uploads after closing. Wait for that upload to finish, then open the original profile on the next computer. A proxy authenticated through an IP allowlist also needs to permit the new network.
Check the store and session in the website after the data is restored. If the site requests verification, complete it there. Repeatedly copying a profile does not renew an expired website session. The cloud sync guide explains when each kind of browser data is transferred.
Review imports and routine changes
When migrating from another browser, start with a small set of stores and inspect the imported account fields and proxies. An import can restore only the data included in its file. A configuration-only file cannot supply missing cookies or local storage, so check the website login afterward. Use the browser migration guide when preparing files.
Proxy renewals, staff changes, replacement computers and profile transfers all need a clear owner. Record what changed and who will check the next launch. During troubleshooting, change one item at a time so you can identify whether the issue came from the proxy, fingerprint settings or login data. Follow each platform's rules for the accounts you operate.
- Match the profile name and account to the store list, then review its group and operator.
- Check the proxy exit and regional settings, then open the website and confirm the store and login state.
- Close the profile normally and wait for sync; review the selected content before sharing or exporting it.
FAQ
How should I organize multiple e-commerce accounts?
Create a browser profile for each store whose login data you need to manage separately, then group profiles by platform, client or responsibility. Record the store account, proxy and operator for each profile. Keep using that profile for the same store and confirm the actual store identity after opening the website.
Does the e-commerce browser include proxy IPs?
The client provides proxy settings, a shared proxy library and exit checks. You supply the proxy connection details. Assign the proxy to a profile, check its actual exit IP and region, and then review the language, time zone and location settings. A saved provider address alone does not confirm the current exit location.
Should I use a separate profile for PayPal?
A separate profile is useful when you need to manage PayPal login data, proxy settings or team access independently from a store. Record which stores the payment account serves and who can use it. Creating a profile does not change payment bindings, ownership or permissions already recorded by PayPal or a sales platform.
Can I move my store profiles to another computer?
With the required sync options enabled, another computer can restore the profiles' cookies and selected local storage. Close them on the first computer and let uploads finish before opening them elsewhere. Check each website's session, store identity and proxy exit afterward; a website can still require you to sign in or complete verification.