Centralizing Purchases Across Multiple Locations: Pros, Cons, & How

When a hospitality group expands from one to several locations, a recurring decision is how to organize purchasing. Does each location choose its suppliers and negotiate its prices? Do we centralize everything in one office? Or a hybrid approach?

Intuition suggests "centralizing is efficient." And it is, in theory: more aggregated volume, better prices, more control. The reality is more nuanced. I've seen groups that centralized and improved margins by 4 points. I've seen others that centralized and had to revert because operations broke down.

This article helps you decide if it's right for you, and how to do it if you choose to proceed.

What Exactly Does "Centralizing" Mean

Before discussing pros and cons, it's useful to clarify terms because there are degrees:

Total Centralization. A single person/team decides which suppliers each location uses, negotiates prices, and coordinates orders. Locations execute but do not choose.

Supplier Centralization. The same suppliers are used across all locations for important categories. Locations manage their own day-to-day orders with those suppliers.

Negotiation Centralization. All locations can use their preferred suppliers, but framework negotiations (annual prices, conditions) are conducted centrally by aggregating volume.

Reporting Centralization Only. Each location chooses and operates autonomously. Central only consolidates data for analysis.

These four variants have very different pros and cons. The question "should I centralize?" is not binary.

Pros of Centralizing (Any Degree)

1. Better Prices Through Aggregated Volume. Three locations ordering 500 kg/month of fish separately have less leverage than a group ordering 1,500 kg/month consolidated. The difference in negotiated price can be 5-15% in categories with wide margins.

2. Quality Standardization. If all three locations use the same olive oil from the same supplier, a customer visiting three group locations will find the same taste. This consistency builds your brand.

3. Consolidated Reporting. When a single supplier serves your three locations, you can easily see which location consumes more, which has better costs, and where deviations occur. Without centralization, this is harder due to fragmentation.

4. Less Overall Administrative Work. Three annual negotiations aggregated into one. Three sets of invoices coming from the same supplier (with a central minimum order, distribution to locations, aggregated invoice). Fewer commercial contacts to maintain.

5. Simpler Regulatory Compliance. Traceability, certifications, allergens: if all locations use the same suppliers with the same documentation, your compliance is uniform.

Cons of Centralizing (Also Real)

1. Loss of Local Flexibility. Each location has a market, a season, a clientele. The coastal location orders more fish in summer, the inland one orders more meat. If central management imposes unique suppliers without local sensitivity, head chefs feel constrained, and the menu suffers.

2. Slow Response Time. "I need 8 kg of red mullet for tonight." In a decentralized model, the chef calls the local supplier who arrives in 2 hours. In a centralized model, the order has to go through purchasing, central doesn't respond until tomorrow, and the dish can't be made. If centralization doesn't incorporate flexibility for emergencies, it kills operations.

3. Supplier Dependence. The more volume you place with a single supplier, the more exposed you are to their problems (strike, health outbreak, bankruptcy). Diversification has a cost, but also a benefit in resilience.

4. Cost of Centralization. Centralizing requires a dedicated person or at least a percentage of someone's time. This person needs to understand the operations of the locations, the products, and the suppliers. It's not free.

5. Distance from the Kitchen Team. Head chefs who have spent years talking to their fishmonger lose that relationship. They lose informal information ("this week the hake are beautiful"), lose preferential treatment, and may perceive the change as a loss of professional autonomy.

When Centralization is Beneficial (Rule of Three)

There's a useful rule of thumb: centralization starts to make sense with three or more locations of the same concept. Below three, the costs of centralizing (dedicated person, friction) are often greater than the benefits. From three upwards, the aggregated volume and the costs of not standardizing begin to justify it.

If the locations are of the same concept (same menu, same positioning), centralization is easier because products can be standardized. If the locations are of different concepts (a group with a steakhouse, a Japanese, and an Italian restaurant), centralization makes much less sense — their product needs are too distinct.

There are two categories that are almost always worth centralizing, even with just two locations:

Beverages (beers, soft drinks, water, branded wines): because there are distributors with broad coverage and aggregated negotiation is relatively easy.
Non-perishable products (oils, preserves, flours, condiments): because logistics are simple and the price difference due to volume is significant.

And two categories that almost never are:

Daily fresh produce (fish, seafood, fresh meat, seasonal fruit): local freshness takes precedence over efficiency.
Local specialties (artisan products from small suppliers): these belong to the identity of the location, not the group.

How to Make the Transition Without Breaking Anything

If you decide to centralize, do it in phases. A typical transition that works:

Month 1-2: Diagnosis. Gather data from all locations: which suppliers they use, what volume they move, what prices they pay, which products overlap. This is office work, and you need digitized invoices (without this, there's no real diagnosis).

Month 3: Identify Quick Wins. The two or three categories with the highest aggregated volume and lowest local sensitivity. Typically: beverages, non-perishables, disposable paper goods. Negotiate a framework agreement with a single supplier for these categories.

Month 4-5: Pilot Launch. Implement centralization in these two-three categories. Measure the actual savings. Listen to the team: are there operational complaints? Are there quality issues? Are there friction points?

Month 6-9: Gradual Extension. With the learnings from the pilot, extend to more categories one by one. Do not try to centralize everything at once.

Month 12: Review. After a year, evaluate: how much has been saved, where it works, where it doesn't, what needs to be reverted to the decentralized model.

The Technology Piece

Centralization doesn't work without a system that provides consolidated visibility of:

Volume per product and supplier at each location.
Prices paid at each location (should match if there's a framework agreement).
Pending orders and confirmed deliveries.
Discrepancies between framework agreement and actual invoicing.

Without this, central management works blindly. With this, central management works with data, and locations maintain their operational autonomy within the framework.

Conclusion

Centralizing purchases can be an important margin lever for groups with 3+ locations of the same concept. But it's not a binary decision or uniformly applicable: there are categories where it makes a lot of sense (beverages, non-perishables) and others where it makes little (daily fresh produce, specialties).

The transition works when done in phases, with a prior pilot, active listening to the kitchen team, and a system that provides consolidated visibility. Without these three things, you'll most likely end up reverting to the old model with a bad experience.

If you manage multiple locations and want to consolidate reporting and prices among them without disrupting local operations, Sincrio multi-organization allows you to see everything from a single account.