How to give staff access in Lazada Seller Center without sharing passwords
A shared Lazada login has one flaw you can’t patch later. When a price gets changed at 2am or a chat reply goes out wrong, nobody can say who did it. Everyone was “you”. And when someone leaves, the only way to cut them off is to change the password, which locks out everyone else too, so in practice it doesn’t happen. That login also sits on top of more than most sellers remember: buyer names, delivery addresses and phone numbers on every order, your pricing, and the finance pages where payouts show up. A part-time packer who needs to print shipping labels doesn’t need any of that.
This is for Lazada sellers with one to a handful of helpers: a VA on chat, a packer, a bookkeeper, someone doing listings on weekends. By the end, each person has their own login with only the menus they need, and you can remove any of them in a couple of minutes without touching anyone else.
Two caveats. First, I’m using Singapore as the reference market, so the Seller Center address is sellercenter.lazada.sg. Lazada also runs Seller Center in Malaysia, Thailand, the Philippines, Indonesia and Vietnam, and menu wording can differ by market. Second, I couldn’t verify the current menu labels, the sub-account limit or any per-seat fee for this piece, as of September 2026. Where I’m unsure I say what to look for and where to check. This is not legal or tax advice.
what you need
- Owner access to Seller Center for your market. For Singapore that is sellercenter.lazada.sg. Other markets have their own domain, so log in where your shop was registered.
- One email address per staff member. A mailbox on a domain you own is best, because it stays yours after they leave. A personal Gmail works, you just lose that control.
- A one-line description of what each person does in a normal week.
- A password manager for the owner login. Bitwarden and 1Password both do the job. I haven’t checked their current pricing, so look before you pick.
- Cost: as far as I know Lazada charges nothing per sub-account, but I couldn’t verify that as of September 2026. Check your own Seller Center before you plan headcount.
- Optional: an account on Lazada Open Platform, Lazada’s developer site, if a tool needs to read your orders.
step by step
1. Write down who does what
Take each person and write their week in one line, then list the menus that work needs. “Answers chat, can’t refund.” “Packs orders and prints labels.” “Uploads listings, doesn’t touch prices.” Expected output: a short list where each person has one to three permission areas. If someone needs more than four, you’ve described two jobs, so split it.
If it breaks: if you can’t say what someone does yet, they don’t need access yet.
2. Find the sub-account area in Seller Center
Log in as the owner, using the account the shop was registered with. Look under your account or settings menu for a section about sub-accounts, staff or users. The label differs by market and I couldn’t confirm the current path for each one. Search “sub account” on Lazada University, Lazada’s seller education site, for your market’s wording. Expected output: a page listing your sub-accounts (probably none yet), with a way to add one and usually a separate spot for roles.
If it breaks: if the section isn’t there, you’re most likely on the wrong account, or the feature has another name in your market. Log in with the registration account and look again. Still nothing? Ask Lazada seller support before trying workarounds.
3. Build roles before you add people
If your market lets you create roles, do it now, one per job. I start with three:
- customer service: chat and order view, no pricing, no finance
- fulfilment: orders, packing and shipping labels, no chat, no product edits, no finance
- listings: product create and edit, no buyer details, no finance
Lazada’s permission list may not split this cleanly, so pick the closest match and name each role after the job. If your market ships preset roles, check what each includes before using it.
Here’s a position you may disagree with: finance access stays on the owner login. A bookkeeper gets exported statements from you, not a login. If your accountant needs live access, that’s a fair call, but make it on purpose.
Expected output: named roles, each with a short list of ticked permissions.
If it breaks: if there’s no role feature, the add-sub-account form probably asks for permissions directly. Set them there and note them in your register (step 8).
4. Create one sub-account per person
Add a sub-account, enter that person’s own email (and mobile number if the form asks), pick their role and save. One person, one sub-account, every time. Never create “cs-team” and hand it to three people. That’s a shared login with extra steps.
A sub-account is a staff seat inside your shop. It isn’t a second shop, and Lazada has its own rules on running more than one, which I cover in the rules on running multiple Shopee and Lazada stores. Sub-accounts aren’t a way around them.
Expected output: a new entry showing the email and role, usually marked pending until they activate.
If it breaks: “email already in use” usually means that address is tied to another Lazada login. Use a different one rather than fighting it.
5. Let them set their own password
The staff member should get an invite or activation message and choose their own password. You never see it, never type it, and it never travels over WhatsApp. If your market has you set an initial password instead, send it on a different channel from the username and have them change it at first login. Expected output: the sub-account moves from pending to active once they log in.
If it breaks: if the invite doesn’t arrive, check spam, then resend from the sub-account list. No resend option? Delete the pending entry and create it again.
6. Test the role from their side
Get them to log in on a screen share. Ask them to do three things the role should allow and try two it shouldn’t. For customer service: open chat (yes), open an order (yes), open finance (should be blocked). Expected output: blocked menus are missing or show a permission message, and the allowed ones work.
If it breaks: if they can see something they shouldn’t, tighten the role, then have them log out and back in, in case the change doesn’t apply to a live session. If they’re blocked from something the job needs, add that one permission, not a broader role.
7. Connect tools by authorisation, not login
If an order management tool needs your Lazada data, it should send you to a Lazada authorisation page where you approve access as the owner, and the tool receives a token. Nobody types your Seller Center password into it. That is the mechanism Lazada Open Platform provides. Tokens expire and get refreshed, and I couldn’t verify current lifetimes, so check the docs there. For which tools to try, see my comparison of multichannel order management tools for SEA sellers. Expected output: the tool shows your shop as connected and starts pulling orders.
If it breaks: if a tool asks for your Seller Center email and password, don’t hand them over. Ask whether it supports Lazada’s authorisation flow, or pick another tool.
8. Keep an access register
A plain sheet is enough, one row per person. These rows are placeholders, not real people:
name,role,email,created,created_by,tools_authorised,last_review
Chat VA,customer service,[email protected],2026-09-20,owner,none,2026-09-20
Packer,fulfilment,[email protected],2026-09-20,owner,none,2026-09-20
Review it monthly against the live sub-account list. Expected output: a sheet you can read at a glance that matches Seller Center row for row.
If it breaks: if Seller Center shows someone your register doesn’t, find out who invited them before you do anything else.
9. Remove access the day someone leaves
Disable or delete their sub-account, whichever your market offers. I prefer disable where it exists, since that should keep a record of what they did, though I couldn’t confirm what history survives deletion. Then work through this:
leaver checklist
[ ] sub-account disabled or deleted in Seller Center
[ ] tool accounts and authorisations they set up reviewed, revoked if not needed
[ ] owner password changed, if they ever knew it
[ ] removed from chat groups and shared folders
[ ] buyer data exports on their devices deleted, confirmed in writing
[ ] register updated with the date and reason
Expected output: their login stops working straight away and the register shows them as removed.
If it breaks: if they can still get in, they’re using an old shared password. Change it now, then treat anything they touched recently as worth a second look.
common pitfalls
- Reusing one sub-account for two people. It feels efficient when someone covers a shift, and it puts you back where you started, with no way to tell who did what. Lazada’s seller terms may also say something about sharing credentials. I couldn’t verify the clause, so check the agreement you accepted at registration.
- Picking the broadest role because it’s quicker. The role should match the job, not the relationship, even for a cousin.
- Leaving old sessions alive. If anyone used the owner login on their own phone, changing the password is the fix, but I couldn’t verify how the Seller app treats existing sessions afterwards. Check from your side. If your team shares physical phones for the app, running seller apps across multiple phones covers the practical side.
- Treating buyer data as free to hand out. Order pages hold personal data. In Singapore the Personal Data Protection Commission enforces the PDPA, which expects organisations to make reasonable security arrangements for the personal data they hold. In the Philippines the National Privacy Commission enforces the Data Privacy Act of 2012. Other markets have their own laws. This is not legal advice, so read the current guidance for your market.
- Forgetting that staff actions count on your shop. Slow chat replies and cancellations from a sub-account land on your shop’s numbers. Account health on Shopee, Lazada and TikTok Shop compared shows what each platform measures, so train people before you give them chat or order access.
scaling this
Read these as multiples of where you are now.
At 10x, roughly ten people with access, the roles from step 3 start paying off, because you keep creating the same few kinds of person. Move the register to a shared sheet and put the monthly review in your calendar. This is also where I’d stop relying on memory for offboarding and tie it to whatever process ends someone’s contract.
At 100x the bottleneck isn’t Lazada, it’s discipline. I haven’t run a hundred seats on Lazada and couldn’t verify whether sub-accounts have a cap, so find out before hiring towards one. What I’d do: keep most staff inside your order management tool, using that tool’s own permissions if it has them, so few people ever log into Seller Center. Fewer Lazada logins means fewer to audit.
At 1000x you’re an agency or a large brand, and that’s past what I’ve operated. If you have a Lazada account manager, ask about sub-account limits, audit logs and integration options.
where to go next
- Best multichannel order management tools for SEA sellers: the tool side, once each person has their own login.
- Account health on Shopee, Lazada and TikTok Shop compared: what your staff’s chat and order handling ends up measured on.
- Running seller apps across multiple phones: the phone side, if your team works from mobiles.
The other how-tos are on the blog index.
Written by Xavier Fok
disclosure: this article may contain affiliate links. if you buy through them we may earn a commission at no extra cost to you. verdicts are independent of payouts. last reviewed by Xavier Fok on 2026-09-20.