Ecang (Ecang OMS) Agent Warehouse Guide

Updated: 2026-08-06

1. What this page covers

This page only covers rules that are specific to Ecang (Ecang OMS). It does not repeat the generic agent warehouse configuration and task page operations.

Read this page first if you're dealing with:

• What capabilities Ecang currently supports;
• How to interpret Ecang inventory quantities;
• Which outbound flows go through Ecang and which don't;
• How far serial number sync actually goes for inbound and outbound;
• Where to look first when an Ecang task stays pending, a cancellation fails, or inventory doesn't line up.

If you haven't finished configuring the system, warehouse, or channel mapping yet, read Agent Warehouse System first. If you already have a failing task and need to check status and retries, read Sync Tasks.

2. Configuration

2.1 Add an Ecang System

Menu path: GWMS > Agent Warehouse > Agent Warehouse System

1. Click 【Add】
2. Fill in 【System Name】
3. Select "Ecang OMS" for 【System Type】
4. Enter the connection details provided by Ecang:
   • 【API Endpoint】: required
   • 【App Key】: required
   • 【App Token】: required
   • 【Language】: optional, defaults to zh_CN, usually no need to change
   • 【Default Platform】: optional, defaults to OTHER
5. Click 【OK】

Inbound and outbound orders pushed to Ecang are always sent with the verification flag on. There is currently no configuration option to turn verification off.

2.2 Configure Warehouse Mapping (Important)

Menu path: GWMS > Agent Warehouse > Agent Warehouse System > Warehouse

All 4 fields are required:

1. Agent warehouse code
2. GWMS warehouse code
3. Virtual Shelving Location (for Ecang qualified goods)
4. Defective Product Location (for Ecang unqualified goods)

❗ If dedicated locations are not configured:

• Inbound orders can be received but not put away
• Inventory sync cannot be triggered

2.3 Ecang Inventory Quantities

Ecang 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

On top of available/locked, every Ecang inventory batch also carries a qualified/unqualified/pending marker:

• Qualified: counted into the virtual shelving location
• Unqualified: counted into the defective product location
• Pending: not synced at all in the current version — not counted into either location, and not counted into total inventory

In other words, if a batch at Ecang is currently in "pending" status, GWMS temporarily can't see that quantity. It only shows up in the inventory sync result once it moves to qualified or unqualified.

3. Current Scope

3.1 Inbound

1. Create an inbound order in GWMS
2. The system automatically pushes it to Ecang
3. Check task status on the Sync Tasks page
4. Once Ecang finishes processing, GWMS automatically receives and puts away the goods

Cancelling an inbound order:

• Cancellation is only allowed while the inbound order is still in the "accepted" or "processing" stage at Ecang.
• If the order has already moved further along (receiving, putaway, etc.) at Ecang, the cancellation may be rejected — check Logs for the exact reason Ecang returned.

3.2 Serial Number Sync

Ecang currently only supports the "Ecang -> GWMS" direction for serial numbers. Pushing serial numbers from GWMS to Ecang is not supported.

Currently supported:

• When Ecang returns a final inbound result, the system parses the serial numbers from the response and writes them back into GWMS local inbound serial number records.
• When Ecang returns a completed outbound result, the system parses the serial numbers from the response and writes them back into GWMS local outbound serial number records.

Currently not supported:

• Unlike HPK, GWMS does not proactively push already-bound local serial numbers to Ecang after an inbound order is created.
• Subsequent local serial number additions, changes, or deletions are not pushed to Ecang either.

To check whether a specific order's serial numbers were written back from Ecang, go directly to Logs and look at that order's status query response. There's no need to check the "push" direction — it doesn't exist for Ecang.

3.3 Outbound

Ecang currently only supports drop shipping outbound:

1. Create an outbound order in GWMS.
2. The system automatically pushes it to Ecang.
3. The system creates a task and polls Ecang's processing status automatically.
4. Once Ecang completes the order, GWMS advances the local outbound status.
5. If Ecang's completed outbound response includes serial numbers, the system also writes them back into GWMS local outbound serial number records.

❗ Transfer staging outbound is not supported with Ecang. If a transfer staging outbound order is routed to Ecang, the push fails outright and goes to manual handling — it does not fail silently. If your warehouse has both drop shipping and transfer staging outbound business, make sure routing only sends drop shipping orders to Ecang.

3.4 Outbound "Picked" Status

For Ecang, the outbound order's "picked" status is only marked at the moment GWMS is about to perform the local formal outbound step — unlike HPK, which marks it early while Ecang (or rather HPK) is still processing and hasn't shipped yet.

In other words: if you see an Ecang outbound order in the order list or sync tasks that hasn't been marked "picked" yet, that does not mean Ecang hasn't started processing it — it only means the local system hasn't reached the formal outbound step yet. This is currently inconsistent with HPK's behavior and is being left as-is for now.

3.5 Inventory Sync

Triggers:

• Click 【Sync Inventory】 on the warehouse mapping page
• The system also runs it automatically every 12 hours (shares the same scheduled job with HPK)

What it does:

1. Completes any unfinished inbound/outbound tasks for the same warehouse first
2. Pulls an inventory snapshot from Ecang
3. Classifies each batch as qualified/unqualified/pending; pending batches are skipped
4. Automatically corrects the virtual shelving location and defective product location
5. Saves the inventory snapshot

View results: Go to Sync Tasks to see inventory sync task details.

Notes:

• Only the virtual shelving location and defective product location are corrected
• If any single page of the inventory query fails during this sync, the entire sync run is marked failed — it will not overwrite the previously saved snapshot with incomplete data
• Inventory sync itself doesn't rely on polling, but the business pre-processing step before it has a budget on count and duration — it doesn't have to wait for every business task to finish first

4. Common Issues

4.1 "Agent warehouse code not configured" / "Virtual Shelving Location not configured" / "Defective Product Location not configured"

Cause: Warehouse mapping is incomplete

Resolution:

1. Go to Agent Warehouse System and check warehouse mapping
2. Verify the agent warehouse code, GWMS warehouse code, virtual shelving location, and defective product location are all configured
3. Fill in any missing configuration, then trigger inventory sync again

4.2 Transfer staging outbound order push fails

Cause: Ecang currently only supports drop shipping outbound, not transfer staging

Resolution:

1. Check the failure reason for this outbound order on Sync Tasks
2. Confirm whether this order's business type is actually supposed to go through Ecang
3. If it shouldn't, check the channel or routing configuration

4.3 Inbound order cancellation fails

Cause: The inbound order may have already moved past the accepted/processing stage at Ecang, so cancellation is no longer allowed

Resolution:

1. Check Logs for the cancellation result and reason Ecang returned
2. If Ecang has already moved further along, confirm the actual processing status with Ecang before deciding whether manual intervention is needed

4.4 Serial numbers aren't showing up in GWMS

Common causes:

• This link currently only supports "Ecang -> GWMS"; if you're trying to confirm whether local serial numbers were pushed to Ecang, that direction isn't supported in the current version
• Ecang's inbound or outbound status response simply didn't include serial numbers
• The response included serial numbers, but the SKU mapping didn't match a GWMS product

Resolution:

1. First confirm which direction you're checking — only "Ecang -> GWMS" exists
2. Check Logs to confirm whether Ecang's inbound or outbound status response actually included serial numbers
3. Confirm the SKU in the response matches the correct GWMS product mapping

4.5 Some inventory quantity is missing

Cause: That portion of inventory is in "pending" status at Ecang, which the current version does not sync

Resolution:

1. Confirm the current status of that batch with Ecang
2. Once it has moved from pending to qualified or unqualified, trigger inventory sync again

4.6 Task stays in waiting status

Common causes:

• Ecang hasn't reached a final status yet;
• The task has already moved into the next automatic polling cycle;
• The execution summary already shows an error, but it hasn't been handled manually yet;
• Mapping, system configuration, or master data issues haven't been fixed yet.

Resolution:

1. Check 【Execution Summary】 and 【Next Run Time】 on Sync Tasks.
2. If the summary clearly points to a configuration or data issue, fix it first — don't just keep clicking 【Sync Now】.
3. If there's no obvious error, check Ecang's actual response on Logs.
4. Contact Ecang to confirm the order's real processing status if necessary.

5. Related Pages

• Configure the Ecang system: Agent Warehouse System
• Check task status: Sync Tasks
• View request details: Logs
• Compare with the other agent warehouse system: HPK Guide