Chain-store software means one item, many warehouses, a central price list, and a group report. Spreadsheets between HQ and stores die in week two. KGSM fixes two branches first, then adds the rest.
Audience, risk, and how KGSM works
A retail network lead who wants central prices but per-store stock
Without a branch code on every document, group reports lie and store transfers vanish.
KGSM makes stock, price, and transfers branch-aware and pilots version one on two stores.
Branch on every row
Invoices, receipts, and stock without a branch code will not add up. Store managers see their data; HQ aggregates. Inter-store transfers need two-sided documents. Stores cannot break central prices without permission. Version one: item, two warehouses, sale, transfer.
Require branch codes on invoices and stock. Ten stores without warehouse codes built a group report that matched none of them.
Negative stock and HQ orders
Stores should not oversell unless consignment is explicit. Replenishment is an inbox, not a phone call. HQ sees daily sales the same night. Expiry goods and offline tills change scope.
A verbal transfer made one store negative and the other bloated. Make store transfers two-sided documents.
Scale after the pilot
Adding store ten is cheap when two stores are stable. Promising twenty on day one poisons master data. Cashier training happens in the store. The pilot date is the date for the rest.
Lock central prices. A store discounted for a friend and the central list became meaningless.
An offline till duplicated orders when it came back online. Finish a two-store pilot.
Put replenishment in an inbox, not a phone call. Ten stores without warehouse codes built a group report that matched none of them.
A verbal transfer made one store negative and the other bloated. HQ should see the store day the same night.
Implementation checklist
- Require branch codes on invoices and stock.
- Make store transfers two-sided documents.
- Lock central prices.
- Finish a two-store pilot.
- Put replenishment in an inbox, not a phone call.
- HQ should see the store day the same night.
Field scenario 1
Ten stores without warehouse codes built a group report that matched none of them.
Require branch codes on invoices and stock.
Field scenario 2
A verbal transfer made one store negative and the other bloated.
Make store transfers two-sided documents.
Field scenario 3
A store discounted for a friend and the central list became meaningless.
Lock central prices.
Field scenario 4
An offline till duplicated orders when it came back online.
Finish a two-store pilot.
Approximate investment
A two-store pilot is typically in the tens of millions of tomans or more. Extra stores are cheaper than the first build if item data is clean.
FAQ
Can we start from single-store software?
If you truly have one shop, yes. A chain needs branch from day one.
What is version one?
Item, two stores, sale, transfer, group report. Loyalty later.
Accounting connection?
Per-branch or consolidated vouchers — decided in discovery.
Related KGSM pages
When you apply this on a live team, write it as an operating rule, not a slide: Require branch codes on invoices and stock. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Make store transfers two-sided documents. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Lock central prices. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Finish a two-store pilot. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Put replenishment in an inbox, not a phone call. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: HQ should see the store day the same night. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Ten stores without warehouse codes built a group report that matched none of them. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A verbal transfer made one store negative and the other bloated. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A store discounted for a friend and the central list became meaningless. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: An offline till duplicated orders when it came back online. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Without a branch code on every document, group reports lie and store transfers vanish. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: KGSM makes stock, price, and transfers branch-aware and pilots version one on two stores. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A retail network lead who wants central prices but per-store stock Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A two-store pilot is typically in the tens of millions of tomans or more. Extra stores are cheaper than the first build if item data is clean. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Require branch codes on invoices and stock. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Make store transfers two-sided documents. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Lock central prices. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Finish a two-store pilot. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Put replenishment in an inbox, not a phone call. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: HQ should see the store day the same night. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Ten stores without warehouse codes built a group report that matched none of them. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A verbal transfer made one store negative and the other bloated. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A store discounted for a friend and the central list became meaningless. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: An offline till duplicated orders when it came back online. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Without a branch code on every document, group reports lie and store transfers vanish. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: KGSM makes stock, price, and transfers branch-aware and pilots version one on two stores. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A retail network lead who wants central prices but per-store stock Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A two-store pilot is typically in the tens of millions of tomans or more. Extra stores are cheaper than the first build if item data is clean. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Require branch codes on invoices and stock. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Make store transfers two-sided documents. Then assign an owner and a review date so the rule survives the first busy week.