Operate TikTok Shop seller center via browser. Use when user asks to check store dashboard, GMV, orders, analytics, customer service messages, product management, or any TikTok Shop backend operation. Supports multi-region stores (US, JP, UK, etc.) with separate browser profiles per store.
| Region | URL |
|---|---|
| 🇯🇵 Japan | https://seller-jp.tiktok.com |
| 🇺🇸 US | https://seller-us.tiktok.com |
| 🇬🇧 UK | https://seller-uk.tiktok.com |
| Cross-border | https://seller.tiktokglobalshop.com |
Treat these as different things:
LIVE & video analytics = the analytics module under Analytics, reached at /compass/live-analysisLive Dashboard = the live-room dashboard for an ongoing session, typically entered from an ongoing-live card or a dedicated LIVE dashboard buttonDo not collapse these terms.
If a task asks for analytics tables, metric configuration, traffic-source breakdown, historical live-session rows, or summary KPIs, go to LIVE & video analytics first.
If a task asks for the actual live-room dashboard during an ongoing stream, open Live Dashboard from the relevant live-session entry point.
Before any dashboard/menu/data task, first confirm the profile is already logged in.
If you see login, captcha, SMS, or human verification:
Do not spend the task budget exploring alternate login flows unless the user explicitly asked for a login task.
⚠️ seller.tiktokglobalselling.com is expired/parked — do NOT use it.
These regional URLs auto-redirect to seller.tiktokshopglobalselling.com?shop_region=XX after login.
If not logged in, authenticate with phone + password. May require captcha + SMS code.
Phone region code may be a dropdown/select control instead of a free-text input. For JP/US/other regional seller centers, choose the correct region code shown by the login UI for that account. Do not guess the code.
When the region code control is a selector:
JP +81)After page loads, verify store name in top-right to confirm correct region.
[Help/学習センター] [Customer Service 🎧] [Messages ✉️] [Profile 👤]
Many left-sidebar menus expand on hover. Do not assume a direct click or guessed URL is enough.
Common top-level areas include Home, Products, Orders, LIVE & video, Analytics, Account Health, Compliance, and Finance, but labels and permissions may vary by region/account.
For concrete menu maps and currently observed submenu structures, read the reference files instead of hard-coding assumptions from this SKILL.md.
LIVE & video analytics recognition notes:
Analytics → LIVE & video analytics, the traffic-source area may include an Impressions column. Treat this as an exposure-related metric. If only shares/distribution are visible and not an absolute count, report it as a partial / substitute exposure metric, not “missing”.Analytics → LIVE & video analytics, trend charts may render as Canvas. If the chart is visibly present but text values are not extractable, report “chart exists but point values were not extracted” — do not say the trend chart is missing.| Category | Metrics |
|---|---|
| Revenue | GMV (total), GMV by channel (LIVE / Product Card / Videos) |
| Orders | Order count, SKU count, items sold |
| Customers | Customer count, AOV (average order value) |
| Traffic | Visitors, page views |
| Operations | Pending shipment, pending returns, low stock count |
| Health | Store health score, product rating |
Use this path only when the task is to monitor a currently ongoing live room from inside the room dashboard.
Analytics → LIVE & video analyticsOngoing LIVE streamsLIVE dashboard/workbench/live/overview?room_id=...For this monitoring workflow:
Live Dashboard as the formal monitoring surfacereferences/live-room-dashboard-monitoring-2026-03-10.md⚠️ This is the buyer-seller chat system. NOT the Messages/notification inbox.
Location: Top nav bar → icon between Help and Messages (headphone/chat icon)
Critical: clicking opens a NEW browser tab. You must switch to it:
1. Click the Customer Service icon
2. browser(action="tabs", profile="<profile>") → list all tabs
3. Find the new tab (URL contains /chat/)
4. browser(action="focus", profile="<profile>", targetId="<new_tab_id>")
5. browser(action="snapshot", profile="<profile>", targetId="<new_tab_id>")
The CS page URL pattern: https://seller.tiktokshopglobalselling.com/chat?shop_region=XX
The CS page shows:
⚠️ Default filter shows only YOUR conversations. To see ALL:
| Data Needed | Where to Find |
|---|---|
| Team workload (all agents) | Main CS page → Select All agents |
| Response rate | Click "查看详情" → 聊天概览 tab |
| Satisfaction rate | Click "查看详情" → 聊天概览 tab |
| Backlog (unreplied) | Status filter → 未回复 |
| Urgent chats | Status filter → 紧急 |
| Unassigned chats | Tab → 未分配 |
| Per-agent stats | Click "查看详情" → 全部聊天 → filter by 客服专员 |
For detailed, region-specific CS system documentation, see:
references/jp-customer-service-system-2026-03-09.mdreferences/us-customer-service-system-2026-03-09.md (needs verification)references/customer-service-system-2026-03-09.mdLeft sidebar → usually enter from Products. Prefer hover first if the sidebar supports flyout submenus. Use the reference files for current submenu names.
Left sidebar → usually enter from Orders. Prefer hover first if the sidebar supports flyout submenus. Use the reference files for current submenu names.
Left sidebar → usually enter from Analytics. Prefer menu entry over guessed URLs; direct URL guessing may return 404.
Left sidebar → Account Health. TikTok's PEAKS framework:
Each metric shows: your value, benchmark, status (Issue / High-impact / Platform-endorsed / Exceeds)
When managing multiple regional stores:
Write reports to workspace memory: memory/YYYY-MM-DD-tiktok-{region}-{topic}.md
Standard format:
# TikTok Shop {Region} — {Topic}
**Date:** YYYY-MM-DD
**Store:** {Store Name}
## Today's Snapshot
| Metric | Value | vs Yesterday |
|--------|-------|-------------|
| GMV | ... | ... |
...
## 7-Day Summary
...
## Action Items
### 🔴 Urgent (24h)
### 🟡 This Week
### 🟢 Long-term
| Pitfall | Solution |
|---|---|
| Wrong store loaded | Verify store name in top-right after page load |
| Customer Service opens new tab | Use browser tabs → browser focus to switch |
| Session expired | Check for login redirect; do a login check first |
| Captcha / SMS / human verification | Human intervention required |
| Data shows 0 early in day | TikTok updates data with delay; note the data refresh timestamp |
| Redirected to wrong region | Wrong browser profile; switch to correct one |
tiktokglobalselling.com shows GoDaddy | Domain expired; use seller-{region}.tiktok.com instead |
seller.tiktokshop.com connection error | Wrong domain; use seller-{region}.tiktok.com |
Use reference files as the changeable layer. Read the smallest relevant one instead of loading everything.
| If the task is about... | Read this file first | Role / status |
|---|---|---|
| Store/profile mapping, entry URL, credential file, environment setup | references/kosbling-config.md | Core Kosbling environment reference |
| US seller center menu structure and navigation discovery | references/us-seller-center-menu-map-2026-03-09.md | US navigation map |
| US "I need metric X, where do I check it?" | references/us-what-to-check-where-2026-03-09.md | US task-routing cheat sheet |
LIVE & video analytics metrics, configurable columns, and analytics entry rules | references/live-dashboard-metrics-2026-03-10.md | Core LIVE analytics reference |
| Ongoing live-room monitoring from inside the room dashboard | references/live-room-dashboard-monitoring-2026-03-10.md | Core room-monitoring reference |
| Customer service system basics that are likely reusable across regions | references/customer-service-system-2026-03-09.md | General CS reference, derived from observed flows |
| Japan customer service page structure and filters | references/jp-customer-service-system-2026-03-09.md | JP-specific CS reference |
| United States customer service page structure | references/us-customer-service-system-2026-03-09.md | US-specific CS draft; verify live before relying on details |
kosbling-config.md.LIVE & video analytics tasks, start with live-dashboard-metrics-2026-03-10.md.live-room-dashboard-monitoring-2026-03-10.md.When a task is blocked by captcha, SMS, or manual verification:
For one-shot browser sub-tasks, prefer spawning a fresh follow-up task after human completion. Use sessions_send only when the original browser worker is intentionally persistent and still active.