Multi-Location Inventory: How to Stop Branches From Overselling Each Other

A business with a few branches or locations tends to land on one of two setups. Either every location keeps its own count and nobody has a real view of what another branch has on the shelf, or someone at head office maintains a master spreadsheet that's already out of date by the time it's opened. Both fail the same way: a branch promises stock that a different branch already sold.

Why "just call the other branch" stops working

Phoning around to check what another location has works when there are two locations and a slow week. It doesn't survive five locations, a busy day, or a customer standing at the counter waiting for an answer. Past a certain size, checking with everyone else before promising an item becomes slower than just being wrong sometimes - and being wrong sometimes is exactly how you end up overselling.

What a real shared count actually requires

• One number, not several reconciled later. If each location has its own count and a nightly job tries to merge them, there's a window every single day where the numbers disagree and a sale can slip through on stale data.
• Real-time, not scheduled. A sync that runs every 15 or 30 minutes still leaves a gap exactly the size of that interval, during which two locations can both believe they hold the last unit.
• An atomic booking, not "check, then update." Checking availability and reducing stock have to happen as one step. If they're two separate steps, two branches can both pass the check in the same instant and both proceed to sell.

This is the same problem as overselling across sales channels

A branch, for the purposes of stock, is just another channel reading the same inventory. The fix is identical to what stops a website and a marketplace listing from both selling the last unit of something: one shared count, and an atomic booking that can't be raced. Whether the two competing sales come from two websites or two storefronts three miles apart makes no difference to the underlying mechanism.

How Feedwyre approaches this

Head office manages one product feed for the whole business - the real stock count, not a branch-by-branch guess. Every branch gets its own consumer portal login into that same feed, so a branch manager can see the real number and book against it directly, with no spreadsheet and no integration to build. Two branches booking the same item at the same moment still can't both succeed, because every booking goes through the same atomic stock decrement no matter which branch - or which outside customer - it comes from. We walk through a six-branch hardware business running exactly this setup in the multi-branch case study.