Head office sets products, prices and promotions once. Every branch reports against the same structure, the same day, the same account tree — so comparing stores is a fair comparison.
The point is not to watch every transaction. It is to see a problem while it is still fixable.
Create a SKU once and publish it to selected stores. Branch-level price overrides are allowed only where you permit them, and every override is logged.
P&L by store, by day, by category, on one account tree. Drill from the group number down to the receipt that made it.
See stock at every branch, request a transfer, and let the receiving store confirm. In-transit stock is visible but excluded from both stores' available quantity.
A cashier sees the till. A store manager sees their store. A regional manager sees their region. Nobody sees the group P&L by accident.
Publish a promotion to a set of stores with a start and end date. No phoning eight managers and hoping the price changed everywhere.
Each store closes its own day with a cash count and a variance note. Head office sees which stores closed on time and which did not.
A retailer with one shop can run on instinct. At eight shops, instinct stops working — not because the owner got worse, but because eight daily snapshots arriving by WhatsApp at 11pm is not information, it is noise.
The fix is not a bigger dashboard. It is a single source of truth with three properties: the same product ID everywhere, the same revenue definition everywhere, and a close-of-day that someone is accountable for in each store.
We set those three up during onboarding, because if they are wrong no report will ever be trusted. Our Singapore customer — eight stores, twenty-plus counters, over a hundred terminals including warehouse and office — runs on exactly this structure: sales in English at the counter, reporting reviewed in Chinese by the owner.
One thing we would advise before you scale past three stores: agree the account tree and the revenue definition in writing while the business is still small enough that everyone remembers the argument. Retrofitting it at twenty stores costs months.
| Role | Sees | Can change | Typical holder |
|---|---|---|---|
| Cashier | Own till, own shift | Sales, returns within limit | Counter staff |
| Store manager | Own store, all shifts | Stock, orders, staff schedules, local prices if allowed | Branch manager |
| Area manager | Assigned stores | Transfers, approvals, local campaigns | Regional lead |
| Head office | All stores | Product master, pricing, permissions, campaigns | Owner / operations |
| Finance | All stores, read-only + journals | Nothing operational | Accountant |
Yes. Stores can be grouped into legal entities or business units, with reporting consolidated per group. A franchisee can be given access to their own store only.
The POS keeps queueing sales locally. When it reconnects, sales replay in order with their original timestamps, so the store's daily report still reflects the day it actually happened.
No. You can set a group price with permitted local overrides, or fully local pricing. The choice is per product category, and overrides are logged with the user who made them.
We run comfortably to fifty stores on the standard configuration. Beyond that the constraints are usually report volume and approval workflow depth, both of which we scope per account.
Most chains begin with the two busiest branches, prove the reporting, then roll out. Tell us which two.
Request a free trial WhatsApp us sales@gdyun.online · Reply within one business day · Support 09:00–21:00 GMT+8