Org catalog + local exceptions
LiveAdd a SKU once at the org level and every store gets it. Any store can still override price or turn the item off locally without editing the shared record or forking the catalog.
Product · Multi-store
One store's product, built to hold at a hundred.
Counterly doesn't fork a “lite” product for a single store and a different one for a chain. Org controls sit on top of the same data model — 1 store is the simple case of the same system that reconciles at 10 or 100.
Store transfers & store clone
LiveTransfer inventory between stores with a clear paper trail on both sides. Cloning a store copies its categories, price books, and settings so a new location starts from a proven configuration instead of a blank slate.
Multi-store rollup reporting
LiveSee performance store-by-store or rolled up across the whole organization — same report types owners already trust at one store, aggregated for ten or a hundred.
Scoped multi-store managers
LiveAssign a manager role to a specific subset of stores. They get full manager access inside that scope and no visibility into stores outside it — no shared logins to fake the boundary.
How the scale bar works
1 store
Full register + Admin ops — sell, age check, tender, shift close, stock, purchasing, staff, reports. Org catalog is just your own catalog.
10 stores
Same features, plus rollup reporting, price-book push across stores, stock transfers, and scoped managers who see only their assigned locations.
100 stores
Same features still correct under load — no silent data loss, staff access holds, and reports and exports finish. No “works on demo only” paths.