Kandiantong: Jushuitan stock sync can be paused when the counts disagree

Start with the conclusion: WeChat Shop and a self-built mini program are two transaction paths. If the stock is physically the same batch of goods, one system must allocate the sellable quantity.

Which system is the source of truth

Interfaces of a third-party product follow that party's current documentation and the version you bought. This article describes the acceptance criteria when Kandiantong is implemented.

One option is for the ERP to assign a sellable quantity to the shop and to the mall. Without an ERP, designate one side as the inventory master and have the other side deduct on a schedule. Do not let both sides use local stock with no sync between them.

Key fields and failure compensation

Key fields include the shop product id and SKU, the mall SKU, the sellable quantity, and the after-sales status. Use a safety-stock buffer during sync delay. An oversold order goes to a person, and the rule is written in advance: restock or refund.

Configuration and go-live checks

Product mapping and inventory sync are a project. The shop's own review and shipping-fee template are not replaced inside the mall back office. For inventory shared by WeChat Shop and a self-built mall, write down the source of truth first. Two transaction paths are safe only with one inventory. Do not enter a development schedule without interface documentation, a test environment, and one successful message.

A code that is not in the mapping table must not be listed automatically by matching the product name. Dead letters need an owner who can say the same day whether to replay or void them. Kandiantong implements the agreed fields. It does not rewrite the other party's rates or activation status.

Source: https://www.kandiantong.com/integrate/wechat-shop.html