Latest industry insights, tutorials, best practices and case studies.
48 articles
The worst thing about integration incidents is being unable to explain what happened. This article presents a four-layer observability model — task-level monitoring, record-level detail, lineage-level tracing, and semantics-level reconciliation — plus alert grading and replay design.
How long does integration take? What if the legacy ERP has no API? How is historical data migrated? Who owns inconsistencies found after go-live? Six questions customers ask most before kickoff, answered with an engineering perspective.
For seasonal and promotional goods the hard part is rhythm, not formulas: build-up, peak and clearance phases each have different objective functions. Seasonal indices, uplift estimation, phased replenishment and clearance tactics.
Reconciliation done is not the finish line — the confirmed results must become receivables, receipts and GL vouchers in the ERP. Starting from reconciliation output, this tutorial covers account mapping, voucher templates, posting via Kingdee Cosmic / Yonyou APIs, and idempotency control.
How a leading FMCG company used an iPaaS platform to connect hundreds of distributors' order, inventory, and rebate data into one chain: from Excel emails to direct APIs, from monthly reconciliation to T+1 sell-through visibility.
Part 2 covers ten terms at the business-engineering boundary: master data, idempotency, incremental/full sync, Qimen, e-waybill, OMS, WMS, safety stock and three-way matching — precise vocabulary for e-commerce and supply-chain integration.
Full sync is simple but heavy; incremental sync is light but prone to data loss. This article systematically compares five change-capture methods — timestamps, auto-increment IDs, log-based CDC, triggers, and message subscriptions — by reliability, cost, and fit.
Half the communication cost of integration projects comes from terminology mismatch. This glossary defines ten foundational terms: iPaaS, ETL/ELT, API, Webhook, SDK, API orchestration, field mapping, data cleansing, middleware and connector.
A Kingdee Cloud walkthrough of the full loop: suggestion → plan confirmation → order splitting → purchase order Save/Submit/Audit → arrival backfill, with field mapping, idempotency and retry design.
Key points for WDT Enterprise Edition openapi2: the sid/appkey credential system, the MD5 signing algorithm, the unusual timestamp baseline, gzip+base64 request bodies, and pagination/incremental practices for order queries.
The worst failure mode of an integration system is silent breakage — orders stopped syncing for three hours and nobody noticed. This article lays out a three-layer metric system (pipeline health, data quality, business outcomes) plus actionable alert levels and noise reduction.
Reverse cash flows from refunds, returns and exchanges are the most error-prone part of e-commerce reconciliation. This article maps the funds impact of the three aftersales forms, how platforms surface them in statements, and provides a reverse-reconciliation checklist.
