Jushuitan Qimen Integration Guide: Order and Inventory Downstream Sync

What Qimen Is

Qimen is a gateway protocol defined within the Alibaba ecosystem for e-commerce warehousing and ERP scenarios: requests pass through a unified HTTP gateway, business payloads travel as XML (or JSON) in the body, and system parameters (method, app_key, session, timestamp, sign, etc.) ride in the URL query string. Jushuitan exposes order and inventory data to third parties via Qimen custom APIs.

Common Parameters and Signing

Every request URL carries system parameters: method (e.g. taobao.qimen.trade.query), app_key, session (the merchant session obtained via authorization), timestamp, format (xml or json), v (2.0), sign, and target_app_key which routes the call to Jushuitan. Per the Qimen standard, the signature is computed by sorting all parameters except sign by name in ASCII order, concatenating them as secretkey1value1key2value2...secret (secret at both ends), MD5-hashing, and uppercasing. Watch out: only query parameters participate in signing — the body does not; sign before URL-encoding parameter values; and an out-of-sync clock fails verification immediately.

Merchant Routing

Jushuitan is multi-tenant, so beyond target_app_key (given in Jushuitan's open-platform docs), the payload must include a customer_id (or owner-related field) whose value is obtained during merchant authorization. For multi-merchant integrations, that pair is the routing key — get either wrong and you query the wrong merchant or hit permission errors.

Order Downstream

For incremental order pulls: overlap the modified-time window by 5–10 minutes and deduplicate by order number — overlapping plus dedup beats precise windows because status transitions shift modification times. Keep page sizes conservative since the gateway enforces timeouts; declare only the fields you need; and build the status enum mapping table between Jushuitan and your system first.

Inventory Downstream

Clarify with Jushuitan whether inventory messages carry full-overwrite or delta-adjustment semantics — mixing the two is the biggest source of inventory discrepancies. Respect per-package item limits and split batches accordingly. Before major promotions, reconcile a full snapshot manually; during the promotion, run deltas only.

Integration Checklist

Validate your signing offline against the official sample payloads before sending real requests; get one merchant's order flow working end-to-end before scaling to many; persist sanitized request/response payloads — Qimen troubleshooting lives and dies by the raw messages; and confirm rate limits with Jushuitan, leaving headroom in your schedule.