Map Platform SKUs in GWMS

Updated: 2026-05-28

1. Scenario

Platform SKU mapping binds an ecommerce platform SKU to a GWMS warehouse SKU. After orders are synced, GWMS uses this mapping to identify which warehouse SKU should be shipped.

If the mapping is not maintained in advance, users can still bind the warehouse SKU during platform order dispatch.

Use this guide when:

1. A store has been authorized and its platform products need to be synced to GWMS.
2. The platform SKU and GWMS warehouse SKU use different codes.
3. A synced order reports that a platform SKU is not mapped to a warehouse SKU.

Do not use this guide when:

1. The store has not been authorized. Complete store authorization first.
2. The corresponding warehouse SKU does not exist in GWMS. Create and enable the SKU first.
3. The platform product has no SKU code. Add the SKU code in the platform seller center first.

2. Operation Guide

Prerequisites

Confirm the following before mapping SKUs:

1. Your account can access GWMS-Ecommerce Platform Integration-Platform SKU Mapping and has permissions for 【Sync Platform SKU】, 【Auto Match】, or 【Bind】.
2. The target store has been authorized in GWMS-Ecommerce Platform Integration-Store Authorization, and the store is not disabled.
3. The warehouse SKU to bind already exists and is available for selection.
4. The platform product has a SKU code.

Processing flow

Platform SKU mapping is usually handled in this order:

1. Open the SKU mapping page for the target store.
2. Click 【Sync Platform SKU】 to pull platform SKUs.
3. Click 【Auto Match】 for identical SKU codes.
4. Filter 【Unbound】 and manually bind the remaining SKUs.

2.1 Open Platform SKU Mapping

Menu path: GWMS-Ecommerce Platform Integration-Platform SKU Mapping

1. Open the page. GWMS displays the store list first.
2. Filter stores by 【Store Name】, 【Platform Type】, or 【Status】 if needed.
3. Find the target store and click 【Enter Mapping】.

After entering the store, the page title shows "Store Name -> SKU Mapping". The list displays SKU mappings for the selected store.

Mappings are maintained by store. Confirm that you have entered the correct store.

2.2 Sync platform SKUs

Before operation: the store is authorized, and platform products have not been synced to GWMS, or existing platform SKU data needs to be updated.

1. On the SKU mapping page of the target store, click 【Sync Platform SKU】.
2. Select the sync mode:
   • 【Full Sync】: pulls all SKUs from the store. GWMS marks historical SKUs as 【Abnormal】 first, then updates returned SKUs to 【Normal】.
   • 【Incremental Sync】: pulls platform SKUs created or updated after the selected time. Select 【Last Sync Time】 before starting.
3. Click 【Start Sync】.
4. Check messages in 【Sync Progress】.

During sync, GWMS may show these progress messages:

• Start syncing
• Historical SKU status marked
• Pulled N SKUs
• Saved N SKUs
• Auto match completed N records
• Completed

If the store is disabled, authorization is abnormal, or the platform returns an error, GWMS shows the failure reason in the progress area.

After sync completes, check whether 【Warehouse SKU】 is empty. Empty means the platform SKU has been synced but is not bound yet.

2.3 Auto match warehouse SKUs

Before operation: platform SKUs have been synced, but some records are not bound to warehouse SKUs.

1. Click 【Auto Match】.
2. Confirm the prompt.
3. GWMS matches records where the platform SKU code is the same as the warehouse SKU code.
4. After matching, GWMS shows "Auto match completed, N records matched".

Auto match only handles exact code matches. If the codes are different, bind the SKU manually.

2.4 Bind or modify a mapping

Before operation: a record has an empty 【Warehouse SKU】, or an existing binding needs to be changed.

1. Find the target 【Platform SKU】 in the list.
2. Click 【Bind】 for an unbound record, or 【Modify】 for a bound record.
3. In the dialog, check 【Platform SKU】 and 【Current Binding】.
4. Search by SKU code in 【Select Warehouse SKU】 and select the correct warehouse SKU.
5. Click 【Save】.

Result: GWMS shows 【Binding successful】 and refreshes 【Warehouse SKU】 and 【Warehouse Product Name】 in the list.

Before saving, confirm that the platform product and warehouse product are the same item.

2.5 Search and delete mappings

1. Filter by 【Platform SKU/Product Name】, 【Warehouse SKU/Product Name】, 【Binding Status】, or 【Sync Status】.
2. Use 【Binding Status】 to find 【Bound】 or 【Unbound】 records.
3. Use 【Sync Status】 to find 【Normal】 or 【Abnormal】 records.
4. To remove a mapping, select records, click 【Delete】, and confirm.

After deletion, the platform SKU is no longer bound to the warehouse SKU. If later orders still contain that platform SKU, GWMS may report that the SKU is not mapped.

Deleting a mapping only removes the relationship. It does not delete the platform SKU or warehouse SKU.

3. Notes

3.1 Field descriptions

• 【Platform SKU】: the SKU code in platform order items.
• 【Platform Product Name】: the product or variant name returned by the platform.
• 【Warehouse SKU】: the GWMS SKU code used for inventory, outbound, and billing.
• 【Warehouse Product Name】: the product name of the warehouse SKU.
• 【Sync Status】: 【Normal】 means the SKU was returned by the latest sync; 【Abnormal】 means this historical SKU was not updated in the latest full sync.

3.2 Status and result

Platform SKU mapping does not have an order-like status flow. Check these results instead:

1. Binding result: Unbound -> Bound
2. Sync result: Normal / Abnormal

Note: 【Abnormal】 does not mean the binding failed. It means the platform did not return this SKU during the latest full sync. Check whether the product was removed, disabled, or discontinued on the platform.

3.3 Impact on order processing

When platform orders are synced to GWMS, GWMS uses the platform SKU to find the warehouse SKU. If no mapping is found, order processing may show:

SKU [platform SKU] is not mapped to a warehouse SKU

The recommended approach is to complete the mapping first in GWMS-Ecommerce Platform Integration-Platform SKU Mapping, then continue with later order processing.

If the SKU is not mapped here yet, users can still bind the warehouse SKU later in GWMS-Ecommerce Platform Integration-Platform Orders during the 【Dispatch to Warehouse】 flow. After the binding succeeds, GWMS saves the mapping and reuses it for the same platform SKU under the same store later.

Platform SKU Mapping only affects whether order lines can identify warehouse SKUs. Warehouse dispatch also depends on address, shipping channel, inventory, and order status.

3.4 Auto match rule

Auto match searches for a warehouse SKU with the same code as the platform SKU.

Example:

• Platform SKU: ABC-001
• Warehouse SKU: ABC-001
• Result: matched automatically

If the platform SKU is ABC-001-US and the warehouse SKU is ABC-001, GWMS does not treat them as the same item. Bind it manually.

4. FAQ

Q1: Why are there no platform SKUs after I click 【Enter Mapping】?

A1: Click 【Sync Platform SKU】 first. If the list is still empty, check whether the store authorization is normal, whether platform products have SKU codes, and whether the platform supports product data sync.

Q2: Some SKUs are still unbound after auto match. What should I do?

A2: These platform SKUs do not exactly match warehouse SKU codes. Filter by 【Unbound】, click 【Bind】, select the correct warehouse SKU, and save.

Q3: An order reports that a SKU is not mapped. Where should I fix it?

A3: There are two ways to handle it:

1. Go to GWMS-Ecommerce Platform Integration-Platform SKU Mapping, select the store, find the platform SKU from the error, and bind it first.
2. Go directly to GWMS-Ecommerce Platform Integration-Platform Orders and manually bind the warehouse SKU during 【Dispatch to Warehouse】.

After the binding succeeds, GWMS saves the mapping and reuses it for the same platform SKU later.

Q4: Will deleting a mapping affect outbound orders that have already been created?

A4: Deleting a mapping affects later recognition of that platform SKU. For outbound orders already created in GWMS, check the SKU details on the order. If the created order needs to be changed, handle it according to the current outbound order status.

Q5: Do I have to finish the binding on the Platform SKU Mapping page before dispatching to the warehouse?

A5: No. This page is better for maintaining mappings in advance. If the SKU is not bound here yet, users can still manually bind the warehouse SKU later during 【Dispatch to Warehouse】 in GWMS-Ecommerce Platform Integration-Platform Orders.