Kandiantong: Stock can be viewed per store
When a brand moves from a single store to many stores, the biggest pain is often not whether it can sell, but information silos: stock figures differ by store, members cannot be recognized across stores, coupon redemption is messy, and headquarters cannot see live operating data. Many women's-apparel and beauty chains, after growing to 5 to 20 stores, end up reconciling in Excel, reporting numbers in a WeChat group, and handing over by word of mouth from the store manager. That is slow, easy to get wrong, and hard to support repeat purchase in a private domain.
Organization, products, stock, and members
The Kandiantong multi-store system is for chain retail, catering, beauty, mother-and-baby, and local services. It puts headquarters, regions, stores, and shopping guides in one permission and data system. Products can be listed uniformly, or differ by store. Orders can be fulfilled by the store or shipped by headquarters. Member assets (points, stored value, and cards and coupons) can work across stores. The operating dashboard is summarized by store, for supervision visits and assessment.
For a private-domain mall, multiple stores are not simply several more addresses. They send public-domain traffic to a local store and settle the private domain into one member pool. After a user orders in the mini program, they can choose pickup at a nearby store or same-city delivery. A redemption in store automatically records the purchase, which is the base for later precise outreach. See the omnichannel private-domain capability notes and the private-domain mall system overview.
A multi-level organization tree of headquarters, region, and store is supported. Headquarters can configure role templates (operations, finance, store manager, shopping guide, warehouse) and authorize by store or region. Sensitive actions (price changes, refunds, stock adjustments, member export) can be switched on their own and leave an audit log, which lowers the risk of permissions getting out of control as the chain expands. Three pitfalls are common in actual configuration. One is giving the store-manager role visibility of every store, so cross-store data is exported at will. Two is leaving a shopping guide's account active after they leave, so they can still look up a member's phone number. Three is sharing one role template between franchise stores and directly operated stores, so a franchisee sees the direct-store cost price. Authorize the minimum that is enough. Member details are masked by default. Each export records the operator, the time, and the row count. Review permissions once a quarter.
Headquarters can keep one product master, and a store can enable or disable it, set in-store stock, a promotion price, and listing hours. That fits a brand strategy of the same national style plus regional exclusives. A mother-and-baby chain can set imported formula at one national price and still let an individual store list local complementary food. A catering brand can price set meals differently by city. A price system works better in three layers: a headquarters guide price, a regional adjustment factor, and a temporary store promotion price. Set a float ceiling for store price changes (for example not below 85% of the guide price) and an approval flow, so obvious gaps between regions do not draw price-comparison complaints. Specifications, barcodes, and units on the product master are maintained only by headquarters. Stores only list, delist, and manage stock. That stops the same SKU from being created as several records in different stores.
The central warehouse, regional warehouses, and store warehouses are managed on separate accounts, with inter-store transfer, stocktake, and safety-stock alerts. Orders can be routed by rule: an online order deducts the nearest warehouse or a named warehouse, store pickup deducts the store warehouse, and a store that is out of stock automatically switches to shipment from the central warehouse. To avoid overselling during a community promotion, set a sellable waterline for the store warehouse (for example 80% to 90% of physical stock joins online sales), and keep a lock on order with a timeout release. Fulfillment status, tracking numbers, and redemption results are written back to the order center together, so the store and customer service see the same progress and do less chasing. More detail is in inventory and warehousing, and in order fulfillment.
A member who registers at store A and spends at store B can have points and stored value shared under a headquarters policy, or limited to the home store in a franchise system. A coupon can set which stores it applies to, and redemption checks the store and the category, so it is not used in the wrong place. The settlement basis has to be agreed in advance: which store's performance a cross-store redemption of a session card or a stored-value spend counts as, and how stores split the funds. That is the largest difference between a directly operated chain and a franchise chain. A common practice is performance belongs to the store where the spend happened, and cost is charged back to the store that issued the card, with cross-store entries listed on their own in the monthly statement. For the user-asset system, see user assets (stored value, cards and coupons, points). Split rules can be designed together with profit-sharing settlement.
Where it fits, and how to land it
Typical pains in beauty and medical aesthetics are cross-store redemption of session cards, technician scheduling, and who owns the performance. The landing focus is in-store redemption, shopping-guide performance, and member tiers. Catering and tea drinks care about stock across stores, peak output, and in-store pickup. The landing focus is store fulfillment, queued pickup, and coupons. Apparel and retail care about size stock being scattered and transfers being slow. The landing focus is stock by warehouse, shipping from the nearest site, and a data dashboard. Mother-and-baby and local services often have community group buying and store pickup at the same time. The landing focus is store pickup points, relay group buying, and private-domain outreach.
Go live in stages. Stage one finishes organization, products, store stock, and basic orders. Stage two connects member assets and marketing. Stage three connects an ERP or inventory system and a finer operating dashboard. When selecting, compare a SaaS template versus custom development, and the plan pricing, to judge the budget.
The core of multiple stores is unified data and permissions, not simply copying a shop. Products, stock, fulfillment, and member assets need to be configurable to the chain's strategy. Go live in stages: organization and stock, then member marketing, then the ERP and the dashboard. Link it with private domain, marketing, and WeCom, and in-store traffic can settle into repeat purchase.
Implementation and operating advice
A multi-store system is usually used together with a marketing tool suite, a coupon center, a points mall, and an SCRM WeCom connection. Headquarters launches the campaign, and stores redeem it. WeCom reaches the store's community. The dashboard compares conversion and average order value by store. A brand that needs to connect an existing inventory system can go further and assess an ERP or supply-chain integration.
The company should name one business owner and one operations executor. The first confirms rules and the acceptance standard. The second handles daily configuration, campaign scheduling, and exceptions. Before launch, run one full-path rehearsal with real products and real stores, including order, payment, fulfillment, after-sales, and asset rollback. Rule conflicts found in the rehearsal (for example whether a coupon can stack with a member price, and whether points work across stores) should be written into the configuration notes, so launch does not depend on a verbal agreement.
In delivery, Kandiantong (Shenzhen DaXi Technology Co., Ltd.) usually advises closing the loop first, then going deeper: keep the main flow stable and operable, then add advanced plays or a deeper integration. That lowers the delay from requirements spreading all at once, and it lets store teams learn the system. If the organization already has an ERP, a POS, or a WeCom base, name the counterpart and the test environment during requirements, so joint debugging waits less.
For daily operations, set a weekly review: conversion, average order value, refund rate, redemption rate, and member activity, not GMV alone. When the data looks wrong, check three places first: whether campaigns were stacked, whether stock sync was late, and whether channel attribution was counted twice. Also review once a quarter whether the rules still match the business: whether member benefits are too wide, whether the safety waterline is too tight, and whether store permissions should be taken back. Keep the review conclusion as a configuration-change record, rather than depending on one experienced person's memory. That is what supports chain expansion and staff turnover.
You do not have to turn on every capability at once. Most growing brands fit a phased plan better. Phase one runs the organization, the product master, store stock, and order fulfillment, so every store can complete a sale and settle. Phase two connects member assets, coupons, and in-store redemption. Phase three does external integrations such as ERP and WeCom. The premise of phasing is that the information architecture leaves extension points in advance, especially store codes, SKU codes, and a unique member identifier, so phase two does not have to be rebuilt.
Look at acquisition cost, repeat-purchase rate, average order value, fulfillment cost, and after-sales rate together. For multi-store capabilities, set one or two north-star metrics (for example on-time pickup rate, coupon redemption rate, or the share of cross-store repeat purchase), use 4 to 8 weeks as the observation window, then decide whether to add weight or change the strategy. In the short term, work can run in parallel: for example Kandiantong carries the transaction and the member, while content is still produced on public-domain platforms. In the middle term, channel parameters and the member record do the attribution. In the long term, fold duplicate tools and lower operating complexity. During the overlap, keep price and promotion wording unified, so there are fewer user complaints.
A multi-store system should serve a clear operating goal, not be bought so the feature list looks complete. Write the goal as a sentence that can be checked (for example store-pickup orders reach 20% of orders within 8 weeks, or the cross-store repeat-purchase rate rises by 5 percentage points), then work backward to the modules, data, and organization. Kandiantong can provide standard product capability and custom extension, but the result still depends on whether the business rules are clear and whether the stores carry them out. If you are still hesitating among several plans, prepare one business sample (products, promotions, fulfillment, and exception orders) and have each candidate demonstrate it on site. Compare whether the flow is completed and how service responds, not how thick the proposal is. After you confirm the work, freeze the first-phase scope and budget the second-phase requirements separately. That is one of the most effective ways to control project risk.
Source: https://www.kandiantong.com/product/multi-store.html