HPK Proxy Warehouse Guide
Updated: 2026-06-04
1. Configuration
1.1 Add an HPK System
Menu path: GWMS > Proxy Warehouse > Proxy Warehouse System
- Click 【Add】
- Fill in 【System Name】
- Select HPK (Hipacking) for 【System Type】
- Enter the connection details provided by HPK:
- API endpoint
- Login account
- Login password
- Version number (enter 5)
- Click 【OK】
Test environment URL: http://test.hipacking.cn
1.2 Configure Warehouse Mapping (Important)
Menu path: GWMS > Proxy Warehouse > Proxy Warehouse System > Warehouse
All 4 fields are required:
- Proxy warehouse code
- GWMS warehouse code
- Virtual putaway location (for HPK qualified goods)
- Defective location (for HPK defective goods)
❗ If dedicated locations are not configured:
- Inbound orders can be received but not put away
- Inventory sync cannot be triggered
1.3 HPK Inventory Quantities
HPK returns two types of inventory:
- Available inventory: Quantity that can be allocated to outbound orders
- Locked inventory: Quantity already allocated but not yet shipped
Important: Total inventory = Available + Locked
❌ Wrong: Looking at available inventory only ✅ Correct: Available + Locked = Total inventory
Example:
- HPK shows: Available 80, Locked 20
- Actual total inventory: 100 (not 80)
2. Daily Operations
2.1 Inbound
- Create an inbound order in GWMS
- The system automatically pushes it to HPK
- Check task status on the Sync Tasks page
- Once HPK finishes processing, GWMS automatically receives and puts away the goods
Notes:
- After the push, wait for HPK to finish processing
- If the task stays in "waiting" status, this is normal
- Putaway only fails when dedicated locations are missing
2.2 Outbound
HPK outbound has two types:
- Drop shipping: Shipped directly to the customer — cancellation not supported
- Transfer staging: Shipped to a transfer warehouse — cancellation supported
Process:
- Create an outbound order in GWMS
- The system automatically pushes it to HPK
- Check task status on the Sync Tasks page
2.3 Inventory Sync
Triggers:
- Click 【Sync Inventory】 on the warehouse mapping page
- The system also runs it automatically every 12 hours
What it does:
- Completes any unfinished inbound/outbound tasks for the same warehouse first
- Pulls an inventory snapshot from HPK
- Automatically corrects local inventory discrepancies
- Saves the inventory snapshot
View results: Go to Sync Tasks to see inventory sync task details.
Notes:
- Only the virtual putaway location and defective location are corrected
- Inventory sync completes in one pass — no waiting required
3. Common Issues
3.1 "Virtual putaway location not configured"
Cause: Warehouse mapping is incomplete
Resolution:
- Go to Proxy Warehouse System and check warehouse mapping
- Verify that both the virtual putaway location and defective location are configured
- Fill in any missing configuration
3.2 "Customer account not open, cannot receive"
Cause: Local customer data does not meet receiving requirements
Resolution:
- Check the error details on Sync Tasks
- Verify the customer's account status
- Check whether the customer is bound to the correct warehouse
- After fixing the issue, click 【Sync Now】
3.3 "System configuration error"
Cause: Incorrect system type or configuration
Resolution:
- Confirm that HPK is selected for 【System Type】
- Confirm that warehouse mapping is set up
- Verify the API endpoint, account, and password
- Check error details on the Logs page
3.4 "SKU sync failed"
Cause: GSKU master data is incomplete
Resolution:
- Go to the 【SKU】 page on the proxy warehouse system
- Check required GSKU fields (name, specification, weight, etc.)
- After completing the data, click 【Resync】
3.5 Task stays in waiting status
Cause: HPK is still processing, or there is a configuration issue
Resolution:
- Check 【Execution Summary】 for any errors
- If it shows "waiting for processing", just wait
- If the task times out, check details on the Logs page
- Contact HPK to confirm processing status if necessary
4. Related Pages
- Configure HPK system: Proxy Warehouse System
- Check task status: Sync Tasks
- View request details: Logs