Latest industry insights, tutorials, best practices and case studies.
10 articles
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.
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.
A hands-on walkthrough of the Kingdee Cloud WebAPI: the three core endpoints — ValidateUser login, ExecuteBillQuery for querying bills, and Save for writing bills — with parameters, pitfalls, and best practices.
Nearly every e-commerce and ERP platform enforces QPS and daily-call quotas. Instead of being punished with throttling errors and account penalties, govern proactively: this article lays out a complete client-side design with token buckets, concurrency gates, quota budgets and graceful degradation.
Using the example of 'marketplace order → ERP outbound → shipping callback', this tutorial shows how to orchestrate APIs from three systems into one business pipeline with branching, retries, and idempotency controls.
DMS governs the channel while ERP governs internal control. How the data path between them is designed determines the success of channel digitalization. This article compares point-to-point, ESB/middle-platform, and iPaaS patterns.
A breakdown of the Qeasy data integration platform's layered architecture: the connector layer, flow assembly layer, scheduling runtime, and observability layer — and the full path of an integration flow from canvas to production.
Retries are a fact of life in distributed integrations, and idempotency is what makes retries safe. This article compares three mainstream patterns — unique-key constraints, state machines and dedup tables — and explains when to use each in order and inventory sync pipelines.
iPaaS (Integration Platform as a Service) turns system integration from custom development into visual assembly. This article explains the core concepts, how iPaaS differs from ESB and point-to-point coding, and why it has become foundational enterprise infrastructure.
