Latest industry insights, tutorials, best practices and case studies.
6 articles
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.
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.
Tutorial: backhaul store-level sales, returns, and inventory data from heterogeneous POS systems to the brand's data platform. Covers SaaS POS open APIs, local database collection, and file-based fallback, plus data cleansing essentials.
First-time ERP onboarding usually means syncing years of historical orders and hundreds of thousands of SKUs. A single-shot pull will always time out. This article compares offset, cursor and time-window pagination, and lays out a resumable, re-runnable checkpoint design.
A hands-on tutorial: turn a distributor order flow based on emailed Excel files into an automated pipeline that cleanses, maps, and writes orders into Kingdee Cloud via APIs — with field mapping, idempotency design, and incremental scheduling.
