Antidetect browser for Amazon accounts

Create a browser profile for each store

Choose New profile, open Account & 2FA and select Amazon. Enter the platform account, then choose an OS template that matches the computer you use. The generated fingerprint is saved with the profile and reused when you reopen it. Fingerprint settings are applied inside the browser engine; each profile runs in its own browser process with a separate data directory and cookies.

Give the profile a name that identifies the marketplace, store and purpose. Use groups to organize stores or projects, and keep passwords and 2FA secrets in their dedicated fields. The fingerprint settings guide explains which device parameters a profile stores.

1. Compare the profile name and platform account with your store list.
2. Save the device template and fingerprint, then configure and check the store's proxy.
3. Open the profile, sign in and confirm that Amazon shows the intended store before starting work.

Assign and check the store proxy

For a store that uses a fixed proxy, add its connection details to the proxy library and assign that entry to the store's profile. WGBrowser supports HTTP, HTTPS and SOCKS5. Check the actual exit IP and region before signing in; the proxy name or the location selected when buying it does not establish where a connection exits.

Under Fingerprint, you can set Language, Time zone and Location to Follow IP. Review WebRTC as part of the same setup, using Proxy only or Disabled as needed. If the proxy changes, check its connection and exit location before saving the new arrangement. Share that change with the next operator so the store list stays useful. See the proxy setup guide for connection fields and checks.

Save the account and 2FA details

Account & 2FA can store the platform account, password and two-factor authentication secret for the profile. You can fill the verification code when signing in. Check the store assignment when entering these values, particularly if several accounts have similar usernames or email addresses.

The password manager can also suggest saved accounts from the login field and offer to save or update a website password after sign-in. Keep access to these details aligned with each person's responsibilities. Cookies, passwords and 2FA secrets are all login material; deciding who can use the profile should include deciding who may receive that material. If Amazon requests another verification step, complete the website's flow in the same profile.

Give operators access to their stores

An administrator creates members, sets roles and assigns profile access in the web console. Operators sign in to the client with their member accounts and work with the profiles available to them. Organize groups by store or project and compare each member's assignment with the current responsibility list. The team access page covers members, roles and profile access.

A profile opened by a colleague shows that it is in use. A profile lease limits the same profile to one device at a time. During a handoff, the current operator should finish the page operation, close the profile and wait for sync to finish before the next operator opens it. Agree on the handoff time so a colleague's unfinished form is not interrupted.

Check sync before switching computers

With cloud sync enabled, cookie changes upload while the profile is running. Selected local data, including LocalStorage and IndexedDB, uploads as a snapshot after the profile closes. Tab URLs can sync too. Close the store profile on the first computer and confirm that uploads have finished before opening it elsewhere.

Sign in to the same WGBrowser account on the other computer and open the existing profile. Check its name, proxy exit and the store shown on the website. Windows and Apple silicon Macs can use the same account; when moving between operating systems, also review the device template and page behavior. Restored browser data can retain a valid session, but Amazon can still require sign-in or verification. Read more about cloud sync timing.

Transfer the selected profile data

For a change of operator within the team, reassign access to the existing profile. For a handoff to another account or team, a share code can provide a copy when your plan and permissions allow it. Choose whether to include the proxy, login state, account password and 2FA secret, based on what the recipient needs.

Close the source profile and finish syncing before the handoff so the latest storage snapshot is available. On the receiving side, check the store, exit IP, login state and required extensions. Agree on which copy will be used afterward. Revoking a share code stops future claims; it does not remove copies already claimed. Follow Amazon's rules and operate stores only within your authorization.

FAQ