GWMS Manual

English

中文

English

中文

Appearance

Configure Proxy Warehouse System in GWMS ​

Updated: 2026-06-04

1. Scenario ​

The proxy warehouse module manages the integration between GWMS and external proxy warehouse systems. Once the system is configured, the warehouse can handle inbound push, outbound push, status callbacks, inventory sync, and exception troubleshooting.

This guide is for warehouse implementers, system administrators, and operations staff responsible for third-party warehouse integration. Common use cases include:

  • Onboarding a new proxy warehouse system
  • Adding warehouse mapping, channel mapping, or checking SKU mapping for an existing system
  • Manually triggering inventory sync for a specific warehouse mapping
  • Checking whether a SKU appears in the mapping list

1.1 How the Proxy Warehouse Works End-to-End ​

Operations workflow overview

Using the proxy warehouse involves three main steps:

Step 1: Configure the proxy warehouse system (first time only)

On the GWMS > Proxy Warehouse > Proxy Warehouse System page:

  • Add a proxy warehouse system and fill in connection details
  • Set up warehouse mapping (important: virtual putaway location and defective location are required)
  • Set up channel mapping
  • Once configured, daily operations can automatically push to the proxy warehouse
  • SKUs are automatically pushed when the first proxy warehouse inbound order is created

Step 2: Daily operations (automatic)

Operations staff work normally in GWMS; the system handles proxy warehouse interaction automatically:

Inbound:

  1. GWMS pushes the inbound order to the proxy warehouse
  2. The system creates a "create task" automatically
  3. The task enters the queue; the system polls for the proxy warehouse result
  4. Once the proxy warehouse finishes, GWMS completes receiving and putaway automatically
  5. If it fails, the task moves to "manual handling" status
  6. If the inbound needs to be cancelled, a new "cancel task" is created

Outbound:

  1. GWMS pushes the outbound order to the proxy warehouse
  2. The system creates a "create task" automatically
  3. The task enters the queue; the system polls for the proxy warehouse result
  4. Once the proxy warehouse finishes, GWMS updates the outbound status automatically
  5. If it fails, the task moves to "manual handling" status
  6. If the outbound needs to be cancelled, a new "cancel task" is created

Inventory sync (different from inbound/outbound — completes in one pass):

  1. Triggered manually or by the system scheduler (every 12 hours)
  2. Key: completes any unfinished inbound/outbound tasks for the same warehouse first, ensuring business actions are processed before sync
  3. GWMS queries the proxy warehouse inventory snapshot
  4. The system creates an "inventory sync task" automatically
  5. Compares GWMS local inventory and identifies discrepancies
  6. Automatically corrects inventory discrepancies:
    • Remote has, local has: update quantity directly
    • Remote has, local does not: add an inventory record
    • Remote does not have, local has: set to zero (check locked inventory first)
  7. Saves the inventory snapshot to the task record
  8. Task is immediately marked as "success" or "manual handling" (no polling required)

Step 3: Review results and handle exceptions

Operations mainly uses two pages:

  • Sync Tasks page (GWMS > Proxy Warehouse > Sync Tasks)

    • View task status: waiting, success, manual handling
    • View execution results and error messages
    • Click 【Sync Now】 to retry failed tasks

  • Logs page (GWMS > Proxy Warehouse > Logs)

    • View request content sent by GWMS to the proxy warehouse
    • View response content from the proxy warehouse
    • Identify the specific cause of failure

Common handling scenarios:

  • Task shows "waiting": Proxy warehouse is still processing — wait or click 【Sync Now】
  • Task shows "manual handling": Check the error message, fix the configuration, then retry
  • Task shows "success": No action needed — the operation completed normally
  • Configuration issue: Return to Proxy Warehouse System to fix warehouse or channel mapping

Inbound/Outbound vs. Inventory Sync — key differences:

ComparisonInbound/Outbound TaskInventory Sync Task
Task typeCreate task / Cancel taskInventory sync task
ExecutionPush to proxy warehouse → wait for processingQuery proxy warehouse → correct local data
Polling needed✅ Yes — repeatedly query proxy warehouse status❌ No — query once and complete immediately
DurationDepends on proxy warehouse speed (minutes to hours)Seconds
Status flowWaiting → Success / Manual handlingSuccess / Manual handling directly
Typical usePush business orders to proxy warehouseSync proxy warehouse inventory to GWMS

Key takeaways:

  1. ✅ Every operation creates a sync task record
  2. ✅ Push is not instant — inbound/outbound requires waiting for proxy warehouse processing
  3. ✅ The system auto-polls the proxy warehouse — no manual checking required
  4. ✅ Inventory sync completes in one pass — no polling needed
  5. ✅ Inventory sync completes unfinished business tasks first
  6. ✅ Most tasks complete automatically — manual intervention is only needed for exceptions
  7. ✅ The Sync Tasks page is the primary operations page
  8. ✅ The Logs page is for viewing detailed messages when troubleshooting

2. Steps ​

Prerequisites ​

Confirm the following before proceeding:

  1. Your account can access GWMS > Proxy Warehouse > Proxy Warehouse System.
  2. You have the connection details provided by the proxy warehouse, such as system type, endpoint, account, and password.
  3. If setting up warehouse mapping, complete the warehouse, zone (storage and defective), and location master data in GWMS first.
  4. If setting up channel mapping, complete logistics channel master data in GWMS first.
  5. If checking SKU mapping, ensure the target GSKU exists in GWMS and has been included in at least one proxy warehouse inbound order.

2.1 Add a Proxy Warehouse System ​

Menu path: GWMS > Proxy Warehouse > Proxy Warehouse System

  1. Open the proxy warehouse system page.
  2. Use the top search bar to filter by 【System Name】, 【System Code】, or 【Config JSON】.
  3. Click 【Add】.
  4. In the dialog, fill in 【System Name】 and 【System Type】:
    • 【System Name】: A descriptive name for this proxy warehouse system, used by operations to distinguish between systems
    • 【System Type】: Currently available options include hipackingWMS, etc.
  5. Based on the selected system type, the page will show different configuration fields — fill them in accordingly.
  6. Click 【OK】. The system shows "Added successfully".

Add system

2.2 Set Up Warehouse Mapping and Trigger Inventory Sync ​

  1. Click 【Warehouse】 on the row of the target system.
  2. The "Paired Warehouse Information" dialog opens.
  3. The dialog table shows the following columns:
    • 【Proxy Warehouse Code】
    • 【GWMS Warehouse Code】
    • 【Virtual Putaway Location】
    • 【Defective Location】
    • 【Actions】: Contains three icon buttons — 【Bind GWMS Warehouse】, 【Sync Inventory】, 【Delete】
  4. Click 【Add Warehouse】 in the top right.
  5. In the new warehouse mapping dialog, fill in:
    • 【Proxy Warehouse Code】: Required — enter the warehouse code in the proxy warehouse system
    • 【GWMS Warehouse Code】: Required — select from the GWMS warehouse list
    • 【Virtual Putaway Location】: Required — select from locations in the chosen GWMS warehouse
    • 【Defective Location】: Required — select from defective zone locations in the chosen GWMS warehouse
  6. Click 【OK】. The system shows "Warehouse mapping added successfully".

Add warehouse mappingAdd warehouse mapping

Run inventory sync

  1. Click 【Sync Inventory】.
  2. A confirmation dialog appears: "Confirm trigger inventory sync for this warehouse mapping?"
  3. After confirming, the system shows "Inventory sync triggered".
  4. Check execution results on the Sync Tasks page — filter by task type "Inventory Sync Task".

2.3 Set Up Channel Mapping ​

  1. Click 【Channel】 on the row of the target system.
  2. The "Paired Channel Information" dialog opens.
  3. Click 【Add Channel】 in the top right.
  4. The system fetches available channels from the proxy warehouse.
  5. The list shows the following fields:
    • 【Proxy Warehouse Channel Code】
    • 【Proxy Warehouse Channel Name】
    • 【Carrier】
    • 【Service Type】
    • 【Available Warehouses】
    • 【Self-pickup】
  6. Select the channels to onboard.
  7. Click 【OK】. The system shows "Channel added successfully".

Add channelAdd channel

Bind a GWMS channel

To map a proxy warehouse channel to a GWMS logistics channel:

  1. Click the edit button on the paired channel row.
  2. In the dialog, select the 【GWMS Channel Code】.
  3. Click 【OK】. The system shows "GWMS channel bound successfully".

Bind GWMS channel

Delete a channel mapping

To remove an unused channel mapping:

  1. Click the delete button.
  2. Confirm the deletion.
  3. The system shows "Deleted successfully".

2.4 Check SKU Mapping Status ​

  1. Click 【SKU】 on the row of the target system.
  2. The SKU information dialog opens.
  3. The table shows the following information:
    • 【SKU Code】
    • 【Sync Status】
    • 【Error Message】
    • 【Actions】: Includes resync, mark, and other actions
  4. The page supports filtering by 【SKU Code】, 【Sync Status】, and 【Error Message】.
  5. To refresh the current results, click 【Pull】 to get the latest status.

SKU mapping

Understanding SKU mapping

Important notes:

  • SKUs are not manually pushed for the first time on this page
  • The system automatically pushes SKUs when the first proxy warehouse inbound order is created
  • A GSKU only appears in this SKU mapping list after it has been pushed via an inbound order
  • After a successful SKU push, the proxy warehouse system records the sync status for that SKU

3. Additional Notes ​

3.1 Relationship Between System, Warehouse, Channel, and SKU ​

Proxy warehouse configuration is maintained hierarchically:

  • Proxy warehouse system: defines which external system is being integrated
  • Warehouse mapping: defines how a proxy warehouse code maps to a GWMS warehouse under this system
  • Channel mapping: defines how a proxy warehouse channel code maps to a GWMS channel
  • SKU mapping: used to check whether a GSKU has been pushed via proxy warehouse inbound and to view its current sync status

Only when a system record exists can the other three mapping types be configured.

3.2 Why Inventory Sync Is on the Warehouse Mapping Page ​

Inventory sync runs per warehouse mapping, not per system as a whole. This means:

  • A single proxy warehouse system can have multiple warehouse mappings
  • Each warehouse mapping generates its own independent inventory sync task
  • During sync execution, inventory correction is based on the GWMS warehouse, proxy warehouse code, virtual putaway location, and defective location configured on that mapping

If a mapping is missing the virtual putaway location or defective location, the system will not allow inventory sync to be triggered.

3.3 Understanding SKU Mapping Status ​

The records on the SKU page are not a complete list of all GSKUs. Only SKUs that have been pushed via proxy warehouse inbound appear in this list.

The 【Sync Status】 field indicates whether the SKU record is currently in sync:

  • 【Synced】: The system considers this SKU successfully synced.
  • 【Not Synced】: The SKU has not been synced successfully, or it was manually reset to unsynced after a previous sync.

If errors appear on the page, check the following first:

  1. Is the GSKU master data complete?
  2. Has a proxy warehouse inbound order with this SKU been created?
  3. Is the proxy warehouse system configuration correct?
  4. Has the relevant request already appeared in Logs or Sync Tasks?

4. Common Questions ​

Q1: Why is the 【Sync Inventory】 button greyed out?

A1: The warehouse mapping is likely missing one of: 【GWMS Warehouse Code】, 【Proxy Warehouse Code】, 【Virtual Putaway Location】, or 【Defective Location】. Open the warehouse mapping dialog and complete all 4 fields.

Q2: Why can't I select a location when adding a warehouse mapping?

A2: The location list is linked to the selected GWMS warehouse. If you have not selected 【GWMS Warehouse Code】 first, or that warehouse has no matching locations, the location dropdown will be empty.

Q3: I added a channel — why do I still need to bind a GWMS channel?

A3: Adding a proxy warehouse channel only creates an "available channel" record in GWMS. Only after binding 【GWMS Channel Code】 can outbound operations map the GWMS channel selection to the proxy warehouse channel.

Q4: The SKU exists in GWMS — why does it still show 【Not Synced】?

A4: The SKU existing in GWMS only means the product record is there. It does not mean it has been pushed to the proxy warehouse. Currently, SKUs are only pushed automatically when the first proxy warehouse inbound order is created. If no proxy warehouse inbound has happened yet, the SKU may not appear in the mapping list.

Q5: Inventory sync was triggered successfully — where can I see the result?

A5: Triggering sync only creates the task; it does not show execution details in the warehouse mapping dialog. Go to GWMS > Proxy Warehouse > Sync Tasks and filter by task type "Inventory Sync Task" or by warehouse to view the execution result.

Q6: I'm integrating with HPK — what should I read next?

A6: See the HPK Guide. That page covers the complete HPK test sequence, inventory interpretation, and common issues in one place.