10 Locations, 10 Ways of Buying: How to Standardize Without Suffocating

Every time a HORECA group opens a new location, the same pattern repeats: the manager starts buying as they see fit. They choose their suppliers, negotiate their prices, decide their quantities, and manage their deliveries. In a group with 10 locations, that means 10 different purchasing criteria, 10 supplier relationships nobody else knows about, and 10 different ways of managing stock. The result isn't operational diversity; it's invisible chaos.

The real problem: every location is a world of its own

In theory, organized restaurant groups have purchasing policies. In practice, those policies dilute with distance and urgency. The purchasing director centralizes contracts with major suppliers, but day-to-day, each location manager makes decisions that completely escape headquarters' radar.

The consequences are predictable and repeat across nearly all groups that exceed 8-10 locations:

Different suppliers for the same product

The Barcelona location buys olive oil from a regional distributor. Madrid works with another. Valencia orders directly from an oil mill. All three pay different prices for an equivalent product, but nobody knows because there's no consolidated view of the group's purchases.

Inconsistent prices without volume consolidation

When 10 locations buy separately, each negotiates with the power of a single establishment. The group's aggregate volume, which could represent significant negotiating power with key suppliers, fragments into small independent transactions. A group with 15 locations buying 2,000 kg of chicken per month should negotiate as a buyer of 2,000 kg, not as 15 buyers of 130 kg each.

Uncontrolled purchases without approval workflows

Without a structured approval system, any manager can place orders with non-approved suppliers, buy off-catalog products, or accept prices above centrally negotiated rates. These rogue purchases, which pass through no filter, represent in chains of 20+ locations between 8% and 15% of the group's total purchasing.

Why rigid centralization doesn't work

The natural reaction from any purchasing directorate facing this scenario is to centralize. Set a closed catalog, assign single suppliers per category, prohibit local purchases, and require everything to go through an approval workflow. On paper, it sounds perfect. In a restaurant's operational reality, it creates more problems than it solves.

Emergency needs that can't wait

On a Friday at 6:00 PM, the location runs out of lemons and the regular supplier doesn't deliver until Monday. If the manager can't buy at the local market because the system won't allow it, service suffers. Operational emergencies are real and inevitable.

Local and seasonal products

A restaurant in one city needs access to local product suppliers that another location would never use. Fresh product seasons vary by geographic zone. A rigid catalog designed from headquarters can't contemplate all these particularities.

How Controliza Makes This Possible

Controliza's Purchasing module is designed to implement exactly this flexible standardization model. It's not a generic purchasing ERP: it's a platform designed for multi-location HORECA groups that need control without rigidity.

Centralized multi-location catalogs

The purchasing directorate defines the master product catalog, with references, approved suppliers, reference prices, and agreed conditions. Each location accesses the same catalog but can have specific configurations.

Automatic orders from Forecast

Controliza's Forecast engine calculates expected demand by dish, day, and location. From that forecast and current stock, the system generates suggested orders for each supplier. The location manager receives a pre-calculated order that only needs validation.

Configurable approval workflows

Headquarters can define approval rules by amount, product category, or supplier type. An in-catalog, within-budget order is automatically approved. An order to a non-approved supplier or exceeding a threshold requires purchasing director approval.

How Controliza makes this possible

Controliza’s Purchasing module is designed to implement exactly this kind of flexible standardization model. It’s not a generic purchasing ERP: it’s a platform built for multi-site HORECA groups that need control without rigidity.

Centralized multi-site catalogs

The purchasing team defines the master product catalog, including item references, approved suppliers, reference prices, and agreed terms. Each site accesses the same catalog but can have site-specific settings: assigned local suppliers, seasonal products enabled, or specific items for its area.

Automatic ordering from Forecasting

Controliza’s Forecasting engine calculates expected demand by dish, day, and site. Based on that forecast and current stock levels, the system generates suggested orders for each supplier. The site manager receives an order that has already been calculated and only needs to approve it. The time spent preparing orders is drastically reduced, and manual calculation errors disappear.

Supplier comparison and deviation detection

Controliza lets you compare the prices of the same product across different suppliers and different sites in real time. If the Bilbao site is paying 12% more for hake than the A Coruña site, the dashboard shows it automatically. In addition, every delivery note digitized with Trazoon is matched against the original order and the agreed price, detecting deviations before they are rolled into the invoice.

Configurable approval workflows

Head office can define approval rules by amount, product category, or supplier type. An order within the catalog and within budget is approved automatically. An order placed with a non-approved supplier or exceeding a spending threshold requires approval from the purchasing director. The rules are configured once, and the system applies them without manual intervention.

Total visibility without micromanagement

The purchasing team has access to a consolidated dashboard where they can see all group purchases in real time: by site, by supplier, by category, and by deviation from budget. They don’t need to call every site manager to find out what has been ordered. They don’t need to review paper delivery notes. The information arrives structured, compared, and with automatic alerts when something falls outside the expected range.

What standardization looks like when it actually works

The goal is not to turn every location into a copy of headquarters. The goal is to make every purchase visible, comparable, and controllable without slowing down operations. That means defining a homologated catalog, authorized suppliers by category, and clear purchase rules, while still leaving room for justified exceptions. A location can buy outside the usual route if service depends on it, but that purchase should be registered, validated, and measured. If you can’t see who bought what, at what price, and against which agreement, you can’t control food cost, protect margins, or improve recipe costing with reliable data.

This is where most groups fail: they try to standardize the supplier list, but not the operating logic behind it. Real standardization starts when purchasing is connected to actual demand. With Forecasting and real stock, locations can generate orders based on expected sales instead of intuition, reducing both waste and stockouts. Headquarters defines the framework; each location executes within it. The result is fewer emergency purchases, less overstock, and more consistent buying patterns across the chain. In practice, this cuts off-contract purchasing, improves compliance, and gives purchasing teams a real basis to consolidate volume and negotiate better conditions.

Controliza Compras makes that model operational. You centralize the approved catalog, assign authorized suppliers, and automate replenishment rules by location. Then Trazoon adds control where most systems go blind: goods reception. Delivery notes are validated against agreed price and quantity before they become accepted cost. If a supplier delivers outside contract, if the price changes without approval, or if quantities don’t match the order, the deviation is detected at source. That protects traceability, avoids invoice surprises, and prevents small reception errors from becoming permanent margin leaks.

The real advantage is not just tighter control. It is the ability to manage by exception instead of by chaos. You can see compliance by location, zone, or supplier, detect which units systematically buy outside the catalog, and understand whether the issue is operational urgency, poor assortment, or weak enforcement. That level of visibility turns purchasing from an administrative task into an intelligence layer for the whole chain. And when purchasing data is clean, recipe costing becomes more accurate, food cost reflects reality, and decisions stop depending on whoever shouts loudest from the field.

Measurable impact

Data measured in active Controliza clients.