Process Platform Orders in GWMS

Updated: 2026-05-28

1. Scenario

Platform Orders receives orders synced from authorized stores. Users can review details, dispatch orders to a warehouse, bind warehouse SKUs, and write shipment results back to the platform.

Dispatching to a warehouse creates a dropshipping outbound order in GWMS. Warehouse users then pick, pack, and ship it through the dropshipping workflow. When the warehouse finishes shipment, GWMS automatically writes the result back to the ecommerce platform. If writeback fails, click 【Mark Shipped】 manually to retry.

Use this page when:

1. You need to pull authorized-store orders into GWMS.
2. You want to review recipient details, item lines, or the current processing status of an order.
3. A B2C order needs to be dispatched to a warehouse and the warehouse SKU still needs to be bound.
4. A B2B purchase order needs acknowledgment before warehouse dispatch.

Do not use this page when:

1. You want to change the original platform order amount, payment result, or platform order number. Those fields follow platform sync data.
2. You still need to connect the store itself. Complete authorization first in GWMS-Ecommerce Platform Integration-Platform Authorization.

2. Operation Guide

Prerequisites

Confirm the following before you start:

1. Your account can access GWMS-Ecommerce Platform Integration-Platform Orders.
2. The target store has already been authorized in GWMS-Ecommerce Platform Integration-Platform Authorization.
3. If you need warehouse dispatch, the warehouse, business setup, and shipping channels are already configured.
4. If you need a self-pickup channel, prepare the shipping label in PDF format and keep each file within 10 MB.

Processing flow

B2C platform orders are usually processed in this order:

1. Complete store authorization.
2. Wait for automatic sync, or click 【Manual Sync】.
3. Open order details and review recipient information and item lines.
4. If no warehouse SKU is bound, maintain the mapping first or bind it in the single-order dispatch dialog.
5. Select the target warehouse and shipping channel, then click 【Confirm Dispatch】. GWMS creates a dropshipping outbound order.
6. After warehouse shipment is completed, GWMS syncs the shipment result back to the platform. If it fails, click 【Mark Shipped】 manually.

B2B platform orders must be acknowledged before warehouse dispatch. During acknowledgment, GWMS checks the acceptable quantity based on inventory in the selected warehouse.

2.1 Open Platform Orders

Menu path: GWMS-Ecommerce Platform Integration-Platform Orders

After entering the page, the top area is split into two tabs:

• B2C Orders (Buyer Direct Fulfillment)
• B2B Orders (Purchase Order / Replenishment)

The page supports filters such as 【Platform Order Number】, 【Store】, 【Order Status】, 【Order Source Channel】, and 【Order Time】. The B2C tab also supports 【Recipient Name】 and 【Tracking Number】.

If an exception appears under the order, review it before continuing.

2.2 Manually sync B2C orders

If a platform order has not appeared in the list yet, or you need to pull a specific time range or specific order numbers again, click 【Manual Sync】 in the B2C tab.

1. Click 【Manual Sync】.
2. Select the store or stores to sync.
3. Choose a sync mode.

The current page supports three modes:

• 【Immediate Sync】: sync the latest orders currently available from the selected stores.
• 【Time Range Sync】: pull orders by start time and end time.
• 【Order Number Sync】: pull specific orders by order number.

4. Click 【Start Sync】.
5. After the sync task is submitted, check GWMS-Ecommerce Platform Integration-Order Sync Log for the result.

Manual sync runs asynchronously. Check Order Sync Log for the result.

2.3 View B2C order details

In the operation column, click 【Actions】 and then open 【View Details】.

The detail dialog shows information by tab:

• 【Basic Info】: order time, shipping warehouse, shipping provider, WMS shipping cost, fulfillment status, buyer note.
• 【Payment Info】: payment method, currency, payment time, shipping fee, tax, discount, and similar fields.
• 【Recipient Info】: recipient name, phone, country, state/province, city, address, and zip code.
• 【Item Details】: warehouse SKU, platform SKU, platform product name, quantity, shipped quantity, and discounted unit price.

If 【Warehouse SKU】 shows 【Not Mapped】 or 【Platform SKU】 shows that the platform did not provide an SKU, continue with the dispatch workflow below and review whether SKU binding or upstream product data needs attention.

Order amount, payment result, and platform order number come from the platform sync result.

2.4 Dispatch to warehouse and bind warehouse SKUs during dispatch

When a B2C order is in 【Pending】 status, you can click 【Dispatch to Warehouse】 from the operation menu. For multiple selected orders, you can also use the top-level 【Batch Dispatch to Warehouse】 action.

If you open dispatch from a single order action menu, or select only 1 order in the list and then click 【Batch Dispatch to Warehouse】, the dialog also shows recipient details and item lines for that one order.

1. Confirm the selected order or orders.
2. Select the target warehouse.
3. Select the shipping channel. The page also shows the carrier and service type.
4. For a single order, the dialog also shows the recipient address and item lines for a final check before dispatch.

If the order line still has no warehouse SKU, you can bind it directly in this dialog.

Binding steps:

1. Click the search field in the 【Warehouse SKU】 column.
2. Search by warehouse SKU keyword.
3. Select the correct warehouse SKU.
4. After the binding succeeds, the line shows the mapped warehouse SKU.

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

If you select 2 or more orders and then click 【Batch Dispatch to Warehouse】, the dialog switches to a batch view. In that mode, GWMS shows only the selected-order summary instead of the detailed recipient and item sections.

Differences in batch view:

1. You can still choose the target warehouse and shipping channel once for the selected orders.
2. The page shows order-number tags only and does not expand each order's recipient or item details.
3. If warehouse SKU binding is still needed, it is better to open the dispatch dialog from a single order first, complete the binding, and then continue with dispatch.

If the selected channel is a self-pickup channel, note the following:

1. A PDF label upload is required.
2. Self-pickup channels do not support batch dispatch.
3. If multiple orders are still listed in the dialog, keep only one order before uploading the label and dispatching it.

Click 【Confirm Dispatch】 after all checks are completed. A single-order dispatch returns the result immediately. If a single-order dispatch fails, the dialog stays open so you can adjust the settings and try again.

After successful dispatch, GWMS creates a dropshipping outbound order and the order enters warehouse processing. If dispatch fails, fix the issue shown in the dialog and retry.

2.5 Process other B2C actions

The B2C action menu also supports follow-up operations depending on the order status:

• 【Mark Shipped】: use when the order has already reached a status where platform shipment writeback is allowed.
• 【Manual Ship】: use when the order does not go through the WMS shipping flow but tracking still needs to be written back to the platform.
• 【Cancel Order】: use for pending or processing orders.

Manual shipping requires shipping information.

Field rules:

1. 【Tracking Number】 is required.
2. 【Shipping Channel】 is required. You can select an existing carrier or enter one directly.
3. 【Service Type】 is optional.

After submission, GWMS writes the tracking information back to the platform and moves the order to the manual-completion status.

GWMS normally writes shipment information back automatically after outbound completion. Use 【Mark Shipped】 or 【Manual Ship】 only when automatic writeback fails, or when the order does not go through warehouse outbound processing.

2.6 View and sync B2B orders

Switch to the B2B Orders (Purchase Order / Replenishment) tab to work with PO or replenishment orders.

Main differences from the B2C tab:

1. The page is intended for purchase-order and replenishment processing.
2. There is no 【Tracking Number】 filter.
3. There is no 【Batch Dispatch to Warehouse】 action. B2B does not support batch acknowledgment or batch dispatch.

If the page is empty, click 【Manual Sync】 to pull B2B orders.

The current dialog title is 【Manual Sync - PO Mode】. It supports the same sync methods:

• 【Immediate Sync】
• 【Time Range Sync】
• 【Order Number Sync】

2.7 Process B2B acknowledgment and warehouse dispatch

The current demo test account does not contain a live B2B order example, so real screenshots of the acknowledgment dialog and post-acknowledgment dispatch dialog still need manual supplementation. In the current system, B2B orders are processed as follows:

1. When the order status is 【Pending】, the action menu shows 【Acknowledge】.
2. During acknowledgment, you first select a target warehouse and GWMS checks available inventory for each SKU in that warehouse.
3. The current page supports 【Accept All】, 【Partial Accept】, and 【Reject All】.
4. If part of the quantity is rejected, or the whole order is rejected, rejection reasons are required for the affected lines.
5. After acknowledgment succeeds, the order moves to 【Acknowledged】.
6. When the order status is 【Acknowledged】, the action menu shows 【Dispatch to Warehouse】.
7. B2B dispatch is handled one order at a time and does not support batch dispatch.

If a SKU has no available stock in the selected warehouse, the page limits the acceptable quantity accordingly. If the SKU is still not linked to a warehouse SKU, inventory checking treats it as unavailable.

B2B acknowledgment affects dispatch quantity: 【Accept All】 accepts all, 【Partial Accept】 accepts only fulfillable quantity, and 【Reject All】 stops dispatch.

3. Notes

3.1 Tabs, fields, and common statuses

Common fields on the Platform Orders page include:

• 【Platform Order Number】
• 【Order Source】
• 【Store】
• 【Order Status】
• 【Order Amount】
• 【WMS Shipping Cost】
• 【Order Time】
• 【Warehouse Name】

Field review suggestions:

1. Check 【Order Status】 first to decide whether the order can be dispatched, acknowledged, or written back to the platform.
2. Check 【Store】 and 【Order Source】 to confirm which authorized store the order belongs to.
3. Before dispatch, review 【Warehouse Name】, recipient information, and item lines.
4. For shipped or completed orders, use 【Tracking Number】 and detail item lines to verify the fulfillment result.

Common statuses on the current page include:

• 【Pending】: the order has entered GWMS but has not yet been dispatched or acknowledged.
• 【Processing】: the order has been dispatched to the warehouse and a dropshipping outbound order has been created.
• 【Partially Shipped】: part of the order has shipment progress.
• 【Shipped】: the order has already been shipped and can continue with platform shipment writeback.
• 【Completed】: the platform order has completed processing.
• 【Cancelled】: the order has been cancelled.
• 【Acknowledged】: a B2B order has finished acknowledgment and is waiting for warehouse dispatch.
• 【Manual Completed】: the order reached its final platform state through manual shipment writeback.

3.2 Exceptions and sync results

If 【Processing Exception】 appears under an order status, hover over it to read the detailed reason.

Common reasons include:

• SKU [xxx] not mapped to a warehouse SKU
• Missing required recipient address fields
• Batch dispatch attempted with a self-pickup channel
• No shippable items

Manual sync, warehouse dispatch, and platform writeback are not all completed instantly on the current page. If the result seems delayed, check:

1. whether the order status has already changed;
2. whether a new exception message appears under the order;
3. whether GWMS-Ecommerce Platform Integration-Order Sync Log already contains the task result.

After the order is dispatched to the warehouse and warehouse shipment is completed, GWMS normally writes the shipment result back to the ecommerce platform automatically. In the normal case, you do not need to click 【Mark Shipped】 yourself.

If the automatic writeback fails, the order usually shows an exception message under the status. In that case, return to GWMS-Ecommerce Platform Integration-Platform Orders and click 【Mark Shipped】 manually for that order to retry the platform writeback.

3.3 Relationship between Platform SKU Mapping and Platform Orders

Maintaining Platform SKU Mapping in advance is recommended, but it is not the only way to proceed.

The current system supports two paths:

1. Bind platform SKUs to warehouse SKUs first in GWMS-Ecommerce Platform Integration-Platform SKU Mapping.
2. If the mapping does not exist yet, bind the warehouse SKU directly in the single-order dispatch dialog from Platform Orders.

After the second method succeeds, GWMS keeps the mapping and reuses it later for the same platform SKU.

If you are currently working in a batch-dispatch dialog, GWMS does not expand each order line. When SKU binding is still needed, open the single-order dispatch dialog first, finish the binding there, and then continue with dispatch.

4. FAQ

Q1: I clicked 【Manual Sync】, so why did no new order appear immediately?

A1: Manual Sync submits a task first, and GWMS then pulls platform orders asynchronously. Refresh the list after a short wait and check 【Order Sync Log】. If the selected conditions do not return any new platform order, the list will stay unchanged.

Q2: Why is 【Dispatch to Warehouse】 or 【Mark Shipped】 disabled?

A2: These actions depend on the current order status. B2C orders are only actionable in the statuses that allow dispatch or shipment writeback. B2B orders must first move to 【Acknowledged】 before warehouse dispatch is available.

Q3: If the platform SKU is not mapped yet, do I have to leave this page and go to Platform SKU Mapping first?

A3: No. For a single B2C order, you can search and bind the warehouse SKU directly in the dispatch dialog. After the binding succeeds, GWMS saves the mapping and reuses it later.

Q4: Why does B2B not support batch acknowledgment or batch dispatch?

A4: B2B processing requires per-order inventory checks, accepted quantities, and possible rejection reasons. Because of that, the current system handles B2B acknowledgment and dispatch one order at a time.

Q5: The warehouse has already finished processing the order, so why would I still need to click 【Mark Shipped】 manually?

A5: Under normal conditions, GWMS writes the shipment result back to the ecommerce platform automatically after warehouse shipment is completed. You only need to click 【Mark Shipped】 manually when that automatic platform writeback fails.