Connect a WMS, Sync Goods & Map Warehouses

#Inventory Management starts with trusted relationships

Inventory Management is not a table that places several stock numbers side by side. A merchant can have multiple Shops, multiple WMS accounts, platform-operated warehouses, and third-party overseas warehouses. The same SKU can also appear in more than one Shop. Without a shared product and warehouse identity, stock can be counted twice and AI cannot tell which physical warehouse a Shop quantity represents.

TK Copilot therefore separates onboarding into four layers:

1. WMS account: tells the system where to read warehouses and goods;
2. Inventory good: uses Seller SKU to create one product identity across warehouses and Shops;
3. Shared warehouse record: records each real warehouse synchronized from a WMS or platform;
4. Shop warehouse mapping: connects a TikTok Shop sales, return, or fulfillment warehouse to the correct shared warehouse record.

Once these layers are complete, the system can relate WMS physical stock, platform-displayed inventory, and Shop demand in one analysis flow.

APP CAPTUREThe English light-theme Inventory page with WMS accounts, warehouses, and inventory goods.

#Step 1: enable Inventory Management for the Shop

Open Shop Management, select the target Shop, and enable Inventory Management under Overview. A Shop warehouse mapping tab then appears in the Shop workspace.

The switch determines whether that Shop participates in inventory synchronization, mapping, and AI inventory analysis. Customer Service and Affiliate do not require Inventory Management; enable it only for Shops that need shared inventory facts or later inventory actions.

If the Shop is not connected yet, complete authorization in Shop Management.

#Step 2: add a WMS account

Open Inventory Management from the main navigation and select Add WMS account. Complete the fields shown for the selected provider:

• Provider: choose a WMS or ERP currently listed by the page;
• Label: use a name your team recognizes, such as “US West warehouse” or “Primary Yejoin account”;
• Endpoint: enter the provider's API endpoint, not the ordinary web-console login page;
• Currency: used as the default declared-value currency when the WMS does not return one for a good;
• Authorization: providers can require an API token, Client ID and Secret, or one-time OMS authorization;
• Notes: record the business entity, region, or owner for troubleshooting.

Authorization fields change with the provider. Credentials are write-only and are not displayed again after saving. When editing an existing account, leave credential fields empty to keep their saved values; enter them only when rotating credentials.

Saving a new account immediately validates the connection and synchronizes warehouses. If initial validation fails, the new connection is not left active as a production source. If an edit fails, invalid replacement credentials do not replace the previously working connection.

#Step 3: confirm WMS warehouses

Expand the saved WMS account and inspect:

• synchronized warehouse count;
• warehouse name, code, region, and type;
• last synchronization time;
• any synchronization error.

Use Sync warehouses after adding a warehouse in the WMS or changing its metadata. This step updates TK Copilot's shared warehouse records. It does not yet decide which Shop uses each warehouse.

#Step 4: synchronize inventory goods

After the WMS account and warehouses are saved, the Sync inventory goods flow first performs a read-only coverage check. It separates WMS goods into:

• Matched: an active inventory good already exists with the same Seller SKU;
• Needs sync: the WMS has the SKU, but TK Copilot does not yet have an active inventory good with that Seller SKU.

Choose between two synchronization modes:

• Sync new inventory goods: creates only missing goods and preserves the existing product name, measurements, and declared value;
• Sync all inventory goods: WMS attributes overwrite existing goods with the same SKU. Use this only when the WMS is the authoritative source for those attributes.

Inventory goods can contain name, SKU, image, barcode, GTIN, HS code, country of origin, weight, dimensions, declared value, battery, and dangerous-goods flags. These fields support identification and fulfillment; they are not the current sellable quantity.

After synchronization, use search, column controls, and pagination to review the catalogue. You can also add or edit a good manually. Keep the Seller SKU stable and identical for the same business item; otherwise platform listings, WMS goods, and historical demand cannot be joined reliably.

#Step 5: synchronize Shop warehouses

Return to Shop Management, open the target Shop's Shop warehouse mapping, and select Sync Shop warehouses. TK Copilot reads the warehouse rows that actually exist in TikTok Shop.

A Shop warehouse can have different responsibilities:

• Sales warehouse: exposes and decrements sellable inventory;
• Return warehouse: receives buyer returns;
• Fulfillment warehouse: dispatches orders.

Synchronizing real rows before mapping prevents operators from guessing by name or creating a relationship for a platform warehouse that does not exist.

#Step 6: map the warehouses

The page separates warehouses into:

• Official warehouses: confirmed and automatically mapped by the platform, such as platform fulfillment warehouses. These mappings are read-only;
• Third-party warehouses: select the matching WMS warehouse from the list.

The mapping answers: “Which real WMS warehouse is this TikTok Shop warehouse?” When one overseas warehouse fulfills several Shops, map each Shop's platform warehouse to the same shared warehouse record. AI can then understand the shared stock pool without counting the same physical units once per Shop.

Before mapping, compare warehouse code, region, and role rather than relying on a similar name. Clear and replace an incorrect mapping when necessary.

#Why goods sync and warehouse mapping are both required

Goods synchronization answers “what is the item?” Warehouse mapping answers “where is the stock?” Missing either relationship creates a different gap:

Missing relationship	Result
No shared inventory good	WMS quantity cannot reliably join to the Shop Seller SKU and its sales history
No warehouse mapping	The system sees a platform-displayed quantity but cannot identify its third-party physical stock source
Both complete	AI can connect current stock with demand by SKU, warehouse, Shop, and time

#Go-live checklist

1. The target Shop is authorized and Inventory Management is enabled.
2. Every WMS account connects successfully and has no current sync error.
3. Warehouse count and region match the WMS.
4. Needs-sync goods are resolved, with no duplicated or mistyped Seller SKU.
5. Every third-party Shop warehouse maps to the correct WMS warehouse.
6. Official warehouse mappings remain platform-managed and read-only.
7. Continue to Inventory analysis and AI operations to validate stock and demand.