Two shops, one brain: multi-site stock without the phone calls

The second shop is where inventory management stops being a memory exercise and starts being a system problem. With one location, the owner's head is the stock system, and it mostly works. With two, the most expensive phrase in the business becomes: "Ring the other shop and ask if they've got one."

Three disciplines separate small chains that handle this from small chains that suffer it. None of them requires enterprise software. All of them require deciding to behave like a network instead of two shops that share a name.

One truth, not two spreadsheets

Both locations must read and write the same stock record, updated as things sell — not reconciled at the weekend. Every multi-site pathology starts here: the phone calls, the promises to customers of stock that sold an hour ago, the "phantom" units that exist in the spreadsheet and nowhere else. If your two shops cannot see each other's shelves, everything downstream is guesswork with extra steps.

Reorder by location, never by average

The same product sells differently in different places — different neighbours, different footfall, different rhythm. A single reorder rule split between sites guarantees a permanent imbalance: the fast shop stocks out while the slow shop quietly composts the surplus. Each location needs its own reorder point built from its own sales rate and its own delivery lead time. This is the least glamorous fix on this list and the one that moves the most money. It is also, at network scale, exactly the imbalance we described in Your best shop is subsidising your worst — visible only when you measure the sites separately.

Transfers are transactions, not favours

Moving stock between shops feels like moving it between rooms, so nobody writes it down — and every unrecorded "borrow" corrupts both locations' records at once: the sender now looks overstocked, the receiver understocked, and both reorder wrongly next cycle. The rule is absolute: every transfer gets recorded like a sale, however informal the van journey. And before celebrating a transfer as a save, count its real cost — the trip, the time, the depleted buffer at the sending shop. A chain that transfers constantly does not have a clever rebalancing culture; it has a reorder-point problem wearing a high-vis vest.

Where Kauzio fits, stated plainly

Kauzio watches each location's sales and stock separately, learns each site's own rhythm, and challenges the decisions — the reorder that ignores the gap between your two shops' sell-through, the transfer that costs more than it saves. It will tell you *which* shop's shelf is about to go empty while there is still time to act, and it keeps the record of what each intervention actually saved. The system holds the network in its head, so yours is free for the two shops in front of you.

Start with the three disciplines this week: one shared record, per-site reorder points, transfers written down. The software makes them easier. Skipping them makes everything harder.