Developer Introduction

This manual is for engineers maintaining and extending WMS Sync Hub. If you are trying to use the plugin as an end user, head to the User Manual.

High-level architecture

Three moving pieces plus a WMS gateway:

• WmsSyncHub.dll (plugin) — DevExpress 22.2 Winforms, hosted by AutoCount 2.2. Runs in-process inside ACHost.exe. Pure UI + database access; does not talk to WMS directly.
• WmsSyncHubApi.exe (companion API) — .NET Framework 4.8 console with OWIN self-host on http://localhost:5006. All WMS traffic flows through here. Runs 5 background workers that poll the DB every 5–15 s and fire WMS HTTP calls, plus 4 controllers (ping, wms-status, po-transfer, wms-callback, logs).
• Database — SQL Server account book. Shared with AutoCount and the sibling "Transfer SO to IV" picking plugin. WMS-owned tables are all prefixed Z_Wms*; shared tables (owned by the sibling plugin) are Z_Picking* and Z_ScannedHistory.
• WMS gateway — Qian Yi / 800best Haiwaicang API at http://edi-glink.800best.com/gateway/api/glink. Signed with partnerId + partnerKey (MD5 over bizData + partnerKey).

Outbound and inbound sequence

What to read next

If you are new to the repo:

1. Repo layout — folder-by-folder tour.
2. Dev loop — the dev.bat inner loop.
3. Workers — the 5 background workers, one per sync flow.
4. UOM round-trip — the single most important design decision in the codebase.

If you are picking up an open task, start at the repo root handoff.md and the reports/ folder.