Practical Tutorial on Synchronizing Transfer Orders from Jushuitan to Kingdee Xingchen Transfer-Out Documents

What This Strategy Solves

Retail and distribution enterprises with multiple stores and warehouses often use one e-commerce ERP to manage front-end store warehouses and a separate financial ERP to manage back-end central and accounting warehouses. Once inventory transfers cross system boundaries—between stores, or between stores and the central warehouse—disputes such as "inventory shown on the books but not actually shipped" or "goods shipped but not yet received on the other side" are common. The strategy we are breaking down here automatically converts Jushuitan transfer orders into Kingdee Xingchen transfer-out documents (via the non-Qimen channel), keeping inventory figures consistent across both systems and making each document traceable.

Data Flow and Field Mapping

The overall flow is: Jushuitan (source) → Qeasy Data Integration Platform (intermediate layer, where cleansing and mapping occur) → Kingdee Xingchen (target).

Key fields are mapped as follows (only the columns that matter in practice are listed):

Code mapping is the lifeline of this strategy. Across multiple customer sites, we have seen the Qeasy platform centralize SKU, item code, warehouse code, and customer code mapping into a single mapping table rather than scattering them across each strategy. This "centralized management" approach is the prerequisite for stable long-term operation.

How to Configure on Qeasy

Step 1: Create a new synchronization strategy in the Qeasy Data Integration Platform. Select the Jushuitan transfer order interface as the source and the Kingdee Xingchen transfer-out document save interface as the target (note that this goes through the non-Qimen channel, which differs slightly from the public OpenAPI).

Step 2: Configure the data source connections. This step looks simple, but the most common pitfall at customer sites is authorization and rate limiting. Jushuitan's open interface limits requests per tenant within a unit of time. The Qeasy platform usually automatically paginates at a controlled pace, but we still need to set a reasonable page size in the strategy to avoid triggering throttling.

Step 3: Configure field mapping. The header (document number, date, both warehouses) uses one-to-one mapping. The body (item lines) needs to be split by line and then written line by line. Qeasy's processing of compound documents with "header + body" is phased—write the header first to obtain the target document's internal ID, then fill in the body. This is a common design pattern on the platform.

Step 4: Configure exception handling. It is recommended to enable "failure retry + alert notifications" and persist failure causes into the database for later troubleshooting.

Implementation Steps

A phased rollout is the safe approach.

Phase 1: Define the incremental starting point. Pick a clear time boundary on the source side (for example, a certain early morning) and treat transfer orders modified after that point as the starting point for incremental sync. The Qeasy platform generally deduplicates using a combination of "last successful time + document status" to avoid missing or duplicate documents.

Phase 2: Run a full reconciliation once. Full reconciliation is not "full retransmission"—it compares historical transfer orders with existing transfer-out documents in the target system to identify differences. This is usually done using Qeasy's comparison tool, with the goal of aligning historical accounts before switching to formal incremental sync.

Phase 3: Configure the scheduling frequency. Transfer order volume is not extremely high, but timeliness matters; scheduling every 5–10 minutes is recommended. Meanwhile, set up a daily full validation task as a safety net. This is the "incremental-first, full-as-backup" dual-track model, which most Qeasy customers run.

Phase 4: Observe for about a week. Once document statuses, inventory quantities, and serial numbers are confirmed to match on both sides, formally announce the strategy as live.

Pitfall Review

Pitfall 1: Going live before item codes are aligned between the two systems. This is the most frequent mistake. SKUs in Jushuitan are strings; in Kingdee Xingchen they are internal material IDs, with no natural correspondence. A mapping table must be built first before sync is started.

Pitfall 2: Units not converted. Jushuitan may use "pieces," while Kingdee Xingchen may use "base units" or "sales units." Passing raw values directly causes quantities to deviate by multiples.

Pitfall 3: Transfer order status not filtered. The source side has multiple statuses such as draft, approved, and cancelled. The target side only accepts "approved" and above. Without status filtering, large amounts of invalid writes occur.

Pitfall 4: Rate limiting and timeouts. The transfer order interface is easily throttled during peak hours. It is recommended to add a "pagination + exponential backoff retry" combination in the Qeasy strategy.

Pitfall 5: Ignoring dependencies. Some enterprises still have a "push master data first, then documents" dependency—for example, if warehouse archives are not synced to the target system in advance, writing transfer-out documents will fail. We recommend configuring such dependencies explicitly in Qeasy's strategy orchestration rather than relying on human memory.

Suitable and Unsuitable Scenarios

Suitable: Retail and distribution enterprises with multiple stores and warehouses, frequent inter-store transfers, and a need for real-time reconciliation, hoping for consistent inventory across both systems. The non-Qimen channel suits enterprises that prefer not to route through the open platform and want to use their own authorization channel.

Not suitable: Enterprises running only a single system; enterprises whose item master data has not yet been aligned across both systems; and scenarios requiring cross-organization settlement while also coupling inventory tightly with financial vouchers. For the latter, a separate voucher synchronization strategy is recommended rather than embedding accounting logic into the transfer-out document sync.