Kingdee Real-Time Inventory to Jushuitan Stock-Take Sheet: A Practical Single-Strategy Sync Tutorial
What This Strategy Solves
In the Kingdee Cloud Galaxy–Jushuitan supply chain integration, real-time inventory data forms the foundation of day-to-day operations. A retail enterprise running multiple warehouses often finds that Kingdee's instant stock figures drift from the physical counts kept in Jushuitan. Relying on manual Excel reconciliation introduces latency and missed variances. We use the Qeasy Data Integration Platform to deliver a single strategy that pushes Kingdee inventory snapshots into Jushuitan as stock-take sheets, closing the reconciliation loop.
Data Flow and Field Mapping
Flow direction: Kingdee Cloud Galaxy (real-time inventory) → Qeasy middle layer → Jushuitan (stock-take sheet). The middle layer handles field mapping, code conversion, and dirty-row filtering.
| Kingdee source field | Middle layer field | Jushuitan target field | Notes |
|---|---|---|---|
| Item code | item_code | Product code | Must exist in Jushuitan product master |
| Warehouse code | warehouse_code | Warehouse code | Warehouse masters must be aligned first |
| Stock quantity | qty | Physical count | Snapshot value |
| Batch number | batch_no | Batch attribute | Required when batch management is on |
| Stock date | stock_date | Stock-take date | Defaults to the sync date |
| UOM | uom | Unit | Must be normalized to base unit |
How to Configure on Qeasy
We configure this strategy on Qeasy with these key points:
- Source connectivity: Build a connection to the on-premise Kingdee Cloud Galaxy environment, use its inventory query API, and pull stock by warehouse + item dimensions. Configure Jushuitan's stock-take sheet write API on the target side.
- Centralized code mapping: Maintain item codes, warehouse codes, and UOM codes in a single mapping table on Qeasy, reused by all strategies to prevent drift across scattered tables.
- Transformer and validator: Add a validator in the middle layer to drop rows with zero quantity, empty batches, or disabled warehouses, preventing redundant stock-take lines.
- Idempotent write mode: Use idempotent writing keyed by stock-take date + warehouse so the same sheet is generated only once.
- Retry and alerting: Configure exponential backoff retries (3 attempts) and route write failures, missing fields, and unmapped codes to enterprise WeChat alerts.
Implementation Steps
We recommend a three-phase rollout:
- Phase 1 — Incremental start: Configure the trigger to capture only inventory records changed since the last sync timestamp on the first run. This keeps initial data volume manageable for on-site verification.
- Phase 2 — Full snapshot: After one stable week of incremental runs, manually trigger a full snapshot on Qeasy to push all warehouses and items as stock-take sheets, completing the initial reconciliation.
- Phase 3 — Scheduling: After go-live, run incrementals every 30 minutes by default and a nightly full snapshot at 02:00 as a safety net. Qeasy's scheduler supports both cron expressions and event-driven triggers (e.g., fire on inventory change).
Lessons Learned
- Decentralized mapping — Hardcoding mappings inside each strategy caused mismatched codes three months later, costing two days of investigation. Centralize all mappings in Qeasy's mapping center as a single source of truth.
- Unnormalized UOMs — Kingdee's "box" and Jushuitan's "box" used different conversion factors, breaking quantity totals. The middle layer must perform UOM conversion with traceable coefficients.
- Duplicate stock-take sheets — Repeated pushes for the same warehouse + date created multiple sheets in Jushuitan and disrupted the stock-take workflow. Idempotency keys are mandatory on Qeasy.
- Missing batch data — A sync once omitted batch numbers while Jushuitan required them, causing the entire batch to be rejected. Auxiliary batch attributes are easily overlooked when only main fields are written.
- On-premise network jitter — Kingdee runs inside the corporate network and occasional jitter caused read timeouts. Raise the timeout threshold above 30 seconds on Qeasy and combine with retries to absorb it.
When to Use and When Not
Use when: Kingdee is the ERP master and Jushuitan fronts warehouse or e-commerce operations; periodic reconciliation is needed; inventory changes frequently; stock-take sheets are the natural variance-handling entry point. Do not use when: Both sides act as independent inventory owners with no shared reconciliation baseline, or when Jushuitan's product master has no mapping to Kingdee items at all.