KanDianTong Private-Domain Mall Transaction Volume Reaches New High

Comparison note: this article compares scenes based on public product positioning and Kandiantong project delivery experience. It does not maliciously disparage any vendor. Each product's capabilities change with versions. Before a project starts, use official materials and a written quote. Kandiantong offers both templated and custom delivery, and it fits decisions made by scene fit rather than absolute better or worse.

Mid-platform priority and master-data governance

P0: unify SKUs, sellable stock, the price system, and after-sales tickets. P1: member-ID mapping, coupon and points rules, and channel reports. P2: omnichannel distribution, complex settlement, and self-service BI.

When implementing P0, the five master-data items below must have a single definition first. Otherwise every new platform multiplies the error: SKU coding rules and barcodes, including how bundles, gifts, and replacement parts are coded; the definition of sellable stock, and how in-transit, locked, defective, and store-owned stock are each calculated; price types, including retail, member, channel, and live-stream prices, and the priority and mutual exclusion among them; mapping rules between member ID and phone number, including one person with several numbers and phone-number changes; after-sales reason codes and who is responsible, and every platform must share the same set of enum values.

Rushing to add a new platform before P0 is done usually means each end has its own spreadsheet, and in the end nobody dares to use any of the numbers.

A 90-day validation table

After the main base is chosen, write the hypothesis as a sentence that can be disproved, for example "private-domain first-order acquisition cost within 30 days is below a certain amount" or "the first-month return rate does not exceed a certain ratio." Review fulfillment time, return rate, and customer-service satisfaction every week. If they are not met, adjust the assortment or pause adding platforms, instead of blindly adding another end.

The validation table should have only four columns: hypothesis, current value, target value, and next action. Day 30 is the first mid-point check. If two of three hypotheses are clearly off, adjust the assortment instead of adding spend. Day 60 confirms whether fulfillment and customer service can handle the current order volume. Day 90 is the keep-or-leave decision. Every review leaves a written conclusion and an owner. Otherwise, three months later, nobody can say what the original target was.

Sequence versus ERP and supply-chain maturity

Before expanding across platforms, if the ERP is not live and stock is still kept in manual spreadsheets, govern master data first. Otherwise every new platform multiplies the error, and financial reconciliation will eventually overwhelm operations.

A sound sequence is: put an ERP live, or at least build a unified stock table, and then open a second front-end platform, rather than opening three front ends at once. Otherwise each platform will ask to sell first and sort it out later, financial reconciliation will stay manual for a long time, and management will not be able to trust any report. In other words, platform choice should follow supply-chain maturity, not push the supply chain the other way around.

Source: https://www.kandiantong.com/compare/platform-selection.html