Understanding Merca store isolation through familiar Ziniao workflows

In recent conversations about Merca, sellers understood why account isolation matters, but were less sure what the browser actually does. One computer or VPS per store makes sense. Terms like "node" and "browser fingerprint" can make things harder to follow.

I found that using Ziniao as a reference made the explanation easier. Merca also lets you manage several stores on one computer, each with its own network connection and browser environment.

A Ziniao device corresponds to a Merca node

The word "device" can suggest a separate computer for a store. For assigning a store's network, it corresponds to a node in Merca; it does not necessarily mean each store has a dedicated physical computer.

The node determines which IP address the store uses. The purchasing process differs: Ziniao brings providers' network resources into its software for sellers to buy there. Merca does not sell IPs; you choose a provider, buy a proxy, and import it into Merca.

With Merca, you choose the network provider based on region, price, and service. You can also keep using a compatible proxy you already own. You decide whom to buy from and renew with. Once ready, enter the connection details using the add-node guide.

For two stores, prepare two separate IPs and add them as two nodes. Each store can then reach the platform through its own IP, even while you use one computer and the same office internet connection.

Select the node when binding the store

In Ziniao, you add a store account and bind a device. Follow the same sequence in Merca: open My Stores, click Bind Store, enter the platform, marketplaces, and login details, then select a node.

Assign node A to store A and node B to store B. Merca remembers the assignments, so you do not need to repeat the setup. See binding a store for instructions.

Open a store in its own environment

In Ziniao, you open a store from its account entry. In Merca, find the corresponding store and click Launch to start processing orders, uploading products, or managing ads.

The window saves that store's login state and browser data separately from other stores. Websites can also read characteristics such as browser version, language, and CPU thread count, commonly called a "browser fingerprint." Merca configures these per store as well.

Extra windows in an ordinary browser may still share data and settings. Merca manages each store's network, browser data, and fingerprint settings separately to reduce account-linking risk caused by mixed environments.

Save passwords and verification codes with the store

If you have used password management and two-step verification in Ziniao, Merca's workflow will be familiar. Save the login details when binding a store for automatic filling when it opens. Set up the rotating verification code inside that store's window, and you can find it there later without reaching for your phone.

Passkeys can also be saved with the corresponding store. Think of a passkey as a digital key for signing in. Keeping passwords, verification codes, and passkeys with their respective stores makes everyday login and management easier. See the two-step verification and passkey guides for setup.

Separate computers and VPS setups keep store environments apart. Merca lets you manage those environments through the browser. The daily workflow is simple: select a node, bind a store, then open it from its store entry whenever you need it.

An isolation browser addresses the environment; account information and business conduct still need to follow platform rules. To get started, follow the getting-started guide and set up one store.