How to run seller apps for several stores across multiple phones

The multi-store mistake I would bet on first is also the dullest one. Somebody answers a buyer from the wrong shop.

It happens because the phone on the desk has three seller apps on it, or one seller app that switches between shops, and every notification looks the same. A price change goes into the wrong store. A voucher goes live on the brand that wasn’t meant to have one. A staff member who left in June still has the phone with every shop signed in.

This guide is for people who run more than one legitimate store: a brand owner with a shop per brand, or an agency managing stores for clients. It covers why one shared phone causes problems, and how to set up devices, logins and notifications so each store stays in its own lane. It does not change what the platforms allow. Before you open another store, read what Shopee, Lazada and TikTok Shop allow for running more than one store. A second phone won’t make a second shop acceptable if the platform says it isn’t.

Why one shared phone goes wrong

Mistakes come first. Every switch between shops is a chance to act in the wrong one, and a busy person switches dozens of times a day. Chat is the worst of it, because a reply meant for one brand’s customer can land with another brand’s customer, with the wrong product names and the wrong return policy.

Then security. One phone signed into every store means one lost or stolen phone exposes every store. It also tends to mean the owner login is on that phone, because sub-accounts felt like extra work at the start.

Then records. When five people share one device and one login, nobody can tell who changed a price. That matters on the day a platform asks you to explain something, and on the day you need to know which staff member to retrain.

And response times. Platforms track how quickly sellers answer chats, and a shared device where one store’s messages bury another’s is a slow way to work. Check each platform’s current chat metrics in your seller centre, since the definitions differ by platform and market.

What you need

• A list of every store you run: platform, market, brand, and who owns the account.
• Staff sub-accounts or member access on each platform, so nobody uses the owner login day to day.
• One device per store, whether that is a handset, a profile or a cloud phone. The options are below.
• A password manager the team shares properly, with per-person access.
• An hour to set it up, and ten minutes a month to review who has access to what.

Step 1: map who works on which store, and where

Put it in a sheet before you buy anything.

That is an example layout, not a recommendation for how many people you need.

The account owner column matters more than it looks. The owner should be the business that owns the store, verified in its own name. An agency gets staff or member access. It does not open the store under its own details on the brand’s behalf.

If it breaks: if nobody can say who owns an account, fix that first. It is the most important fact in the sheet.

Step 2: give staff their own access

Each platform has its own staff access tools. Use them instead of passing the owner password around.

Shopee Singapore’s Sub-account Platform has a main account that “is the administrator that controls all member accounts”, and six default roles: Administrator, Merchandiser, Fulfilment, Finance, Chat CS and KOL Livestreamer. TikTok Shop Singapore’s Access Management guide says “as a shop owner, you can add sub-accounts for your employees”, and only the shop owner can assign and customise roles. Lazada Seller Center has its own user and role management, but its help pages sit behind the seller login, so check the current version in your account. Other markets may name and scope these differently.

The point is the same everywhere. Each person gets their own login, with only the permissions their job needs, and you can remove it without changing anything for everyone else.

If it breaks: some tasks may still need the owner account. Keep a short list of them, and do them on the owner’s device, not a shared one.

Step 3: choose a device model

There are three sensible options. Most operators end up mixing them.

One handset per store

The simplest. Each store gets its own phone, labelled, charged and kept in one place.

It works well when the team sits in one office and runs a few stores. It gets awkward past that. Phones need charging, updating and replacing. Somebody has to be in the office to use them. Remote staff end up asking for photos of the screen, or worse, installing the seller app on their personal phone.

Android work profiles

Google describes a work profile as a way to “separate work apps and data from personal apps and data”, with work apps “marked with a briefcase icon” (Android Enterprise Help). Android’s developer documentation adds that a work profile “is controlled by an IT admin” (Android Developers).

That is useful for one specific job: keeping a store’s seller app off the personal side of a staff member’s phone, so it can be paused or removed when they leave. It is built to split work from personal, not store from store. If one person handles five stores, a work profile does not give each store its own space.

Cloud phones

A cloud phone is a real Android phone kept somewhere else that you open from a browser. Staff can reach it from any computer, the phone does not leave the building when a person does, and one phone per store stays one phone per store.

This is what we run. cloudf.one hosts real Android phones in Singapore, each on its own persistent Singapore mobile IP, controlled from the browser. Because the phones and their connections are in Singapore, they fit Singapore stores and teams operating Singapore stores. They are not a way to make a store look like it is in another country, and we would not suggest using them that way.

If it breaks: whichever model you pick, test a full day of work on it before moving every store over. Chat, order processing, a price change, a campaign sign-up.

Step 4: label everything

Name each device after its store. Use a different wallpaper for each brand. If you use cloud phones, name each browser tab or bookmark the same way.

It sounds trivial. It is the cheapest fix for the wrong-store reply.

Step 5: set notifications on purpose

On each store’s device, turn on notifications for chat and new orders. Turn off almost everything else. The goal is that a buzz on Phone A always means Brand A needs something.

If it breaks: if staff start ignoring alerts, you have too many turned on. Cut back until every notification needs an action.

Step 6: keep verification details with the business

The email address and phone number used to verify a store should belong to the business, not to whichever staff member set it up. Turn on two-factor authentication where the platform offers it. Never pass one-time codes around in a group chat.

If it breaks: if a verification phone number belongs to someone who has left, update it through the platform’s official process now, before you need it.

Step 7: offboard properly

When someone leaves, remove their sub-account on every platform, sign them out of every device, and rotate any password they knew. Your map from step 1 tells you where to look.

Common pitfalls

• Installing every store on the owner’s personal phone “for emergencies”. That phone is now the single point of failure.
• Sharing one staff login between three people, which defeats the point of having them.
• Running two stores from one device “just for now”. It stays that way for a year.
• Buying devices before deciding who owns each account.
• Assuming a separate device makes an otherwise prohibited store acceptable. It does not.

Scaling this

At two or three stores, a handset each and a labelled shelf is fine. At ten, the handset drawer starts to cost real time, and remote access starts to matter. That is where cloud phones or a proper device management setup earn their keep. At thirty stores across several markets, you need someone whose job includes the access map, a monthly review, and a written offboarding checklist.

Once devices and logins are sorted, the next jobs are commercial. Our seller fees comparison for Singapore covers what each platform takes, and how to track competitor prices on Shopee and Lazada covers a weekly pricing routine. Everything else is on the articles page.

Written by Xavier Fok

disclosure: SEA Seller Desk is published by the team behind cloudf.one, which is mentioned in this article, and the cloudf.one link is marked sponsored. Last reviewed by Xavier Fok on 2026-09-11.