How to manage inventory across multiple hospitality sites

Inventory management at a single site is a process problem. You establish a counting rhythm, you set up categories, you connect to your suppliers, and you maintain it. It is manageable with reasonable effort and the right tools.

Inventory management across multiple sites is a coordination problem. Each site has its own stock, its own team doing the counts, its own supplier relationships, and its own tendency to drift from the standard process when pressure builds. The challenge is not running inventory at five sites. It is ensuring that five sites are running inventory consistently enough that the data they produce is comparable and useful at group level. This consistency question is directly connected to the broader challenge of consolidating reporting across multiple restaurant sites, because the inventory data feeds the GP figures that consolidation depends on.

What breaks when you add sites

The most common failure mode when a hospitality group expands from one site to several is that each new site inherits the inventory process of whoever set it up, rather than the group's standard process.

Site two opens with the category structure that the site manager used at their previous employer. Site three uses a different stock take app because the new GM prefers it. Site four was set up in a hurry and the category codes never got properly standardised. By the time there are five sites, the group has five slightly different approaches to counting the same thing.

This creates two problems. The first is operational: no one in the group team can look at stock data across all sites and make meaningful comparisons, because the data is not structured consistently. The second is financial: the GP figures produced at each site are calculated from inventory data that is not comparable, so consolidated GP is a sum of inconsistent inputs.

Centralised versus decentralised inventory management

Multi-site inventory management sits on a spectrum between two approaches.

Decentralised: each site manages its own inventory independently. The site team does the counts, manages the suppliers, and produces reporting locally. The group sees the outputs but does not manage the process.

Centralised: a central purchasing or operations function manages supplier relationships, sets category structures, and defines the counting process. Sites execute the process locally but within a framework determined centrally.

Most growing groups operate somewhere in between, and the right balance depends on the degree to which sites share a menu and supply chain. A group with five sites running the same concept from shared suppliers benefits significantly from centralised purchasing and a standardised inventory framework. A group with five sites each running distinct concepts with different menus and supply chains may need more local flexibility.

The critical requirement, in either model, is that the category structure and counting methodology are consistent enough for group-level reporting to be meaningful.

Supplier management at scale

One of the practical advantages of managing inventory across multiple sites is purchasing leverage. A group buying from the same supplier across five sites has negotiating power that a single site does not.

Realising that leverage requires knowing, accurately, how much each site is spending with each supplier and on what products. Supplier management at group level requires visibility of purchasing activity across the estate, not just per-site invoice processing.

A central purchasing function that can see total group spend by supplier, by category, and by product can negotiate on the basis of real data rather than estimates. It can identify where different sites are buying the same product at different prices and standardise. It can see which suppliers are consistently over-invoicing and address it across the group rather than site by site.

Stock take consistency across sites

Stock take quality at a multi-site group is only as good as the process at the weakest site. A strong central count at the flagship will not compensate for estimated counts at sites three and four. The lessons that experienced multi-site operators share consistently point to inventory process standardisation as one of the things they wish they had addressed earlier rather than later.

Building count discipline across a group requires three things: a standardised process that every site follows, a review mechanism that catches counts that look unreliable, and accountability for the quality of the output rather than just its completion.

Completion is easy to verify: the count was done or it was not. Quality is harder to assess without the data to do it. A stock take health check that looks at whether the output is statistically plausible, whether the variance patterns are consistent with the site's trading, and whether specific categories are consistently coming in at exactly expected, is the tool that catches poor-quality counts before they feed into GP figures that will be relied on.

The technology requirement

Managing inventory across multiple sites without a system that connects them is a manual coordination exercise. Someone at the centre is aggregating site outputs, normalising categories, chasing submissions, and building group views from local data that was not designed to be consolidated.

A system that provides a consistent framework across all sites, with centrally managed category structures and supplier databases, site-level data entry and counting, and automatic consolidation to group level, removes most of that coordination overhead.

The GM at each site sees their own inventory. The regional manager sees a cluster. The group operations team sees everything. Each level of visibility is produced from the same underlying data without a manual assembly step.

That is the structure Hops was built to provide for multi-site groups: inventory management that scales consistently as the estate grows, rather than becoming harder to manage with each new site.