It's Monday and you want to know which of your four locations made the most money last week. Each POS gives you the sales, but ingredient costs are in a spreadsheet, purchases were ordered over WhatsApp, and the accounting arrives at the end of the month. You know how much you sold, not how much each location earned.
When a restaurant group adds locations, brands, or legal entities, the challenge is no longer ringing up sales quickly: it becomes consolidating, comparing, and controlling costs, something a standalone POS doesn't solve.
In this guide you'll see the typical architecture, how to calculate food cost and control waste, why multi-company in Odoo requires the Custom plan (and how that affects cost), and a checklist for choosing between a specialized POS and an ERP.
What restaurant management software is (and what changes with multiple locations)
Restaurant management software is the system that records and connects the operation of a food service business: sales at the register and at tables, kitchen orders, ingredient inventory, recipes, purchasing, staff, and accounting. In a group with several locations, it also consolidates that information by location, brand, and legal entity so you can compare them using the same criteria.
Compared with a single location, restaurant chain management software adds:
- A single recipe catalog, with the same cost at every location.
- Centralized purchasing and, often, a central kitchen.
- Consolidated sales by location and channel: dine-in, pickup, delivery, and online store.
- Accounting by legal entity and a group-wide view.
Typical architecture: POS per location, online ordering, central ERP, HR, and BI
Multi-location restaurant management works when each piece has a clear role and sends its data to a central system:
| Layer | What it handles | What it sends to the central system |
|---|---|---|
| POS per location | Tables, kitchen orders, payment, and receipt | Sales, payment methods, and cash register closing |
| Online ordering | Own online store, pickup, and delivery | Orders with products and channel |
| Central ERP | Purchasing, inventory, recipes, and accounting | It's the group's official record |
| HR | Payroll and attendance | Labor cost |
| Banks | Deposits and transfers | Transactions to reconcile |
| BI and alerts | Dashboards and notifications | Reads the ERP data |
Online ordering for restaurants has to draw down the same inventory as the dining room, or the cost of delivery is left out of the numbers.
At KPB we build this architecture with Odoo for restaurants at the center and three partners: Justo (online store and ordering, which we sync with Odoo), Buk (payroll and attendance), and Fintoc (bank connection and automatic reconciliation).
Restaurant POS: tables, kitchen orders, kitchen display, and combos
A restaurant POS is a point of sale designed for table service: it handles the dining room floor plan, sends orders to the kitchen or bar, and splits the bill. The general POS features are covered in the Odoo for retail guide.
Odoo's point of sale comes with these features out of the box:
- Floor plan and tables, with reservations, order transfers, and courses so dishes go out in sequence.
- Printed kitchen orders, bill splitting, and tips.
- Preparation display by point of sale and category (the bar sees drinks; the kitchen, dishes), with a timer that highlights delays. In Odoo 19 it's part of Enterprise, not Community.
- Combos with a set-menu price and optional surcharges per choice, like a daily set menu.
According to its release notes, Odoo 20 adds combo suggestions, a preparation ticket per product, and the option to pause products, for example when they sell out (only if you're on that version).
Recipes, food cost, and waste: the real margin on every dish
Recipe cost and food cost
Recipe cost is what the ingredients in one portion cost according to its recipe card. Food cost is that cost divided by the net selling price: a dish with CLP 3,200 in ingredients that sells for CLP 11,000 net has a food cost of 29%.
In Odoo, the recipe is a kit-type bill of materials: when the dish is sold at the POS, the ingredients are deducted and the cost is calculated from its components. It requires the Manufacturing app, which also works for the central kitchen (manufacturing guide).
That way you compare theoretical food cost, which comes from the recipes sold, with actual food cost: opening inventory plus purchases minus closing inventory, divided by net sales. The difference is waste, over-portioned servings, or unrecorded ingredients.
Waste control
Waste control means recording and analyzing the ingredients that are lost before they reach the customer. In Odoo:
- Include the yield on the recipe card: for example, how much trimmed tenderloin you get from one kilo.
- Record each loss as scrap at the location, with its reason.
- Send scrap to a loss location linked to an accounting account, so you can see it on the income statement.
- Compare theoretical and actual food cost by location every week.
Centralized purchasing, central kitchen, and transfers between locations
In Odoo, each location and the central kitchen have their own warehouse. Replenishment rules suggest orders when an ingredient drops below the minimum, and internal transfers record what is sent to each location (more in the Odoo Inventory guide). If the central kitchen is a separate legal entity, inter-company transactions create a draft quotation in it when the location confirms its purchase; that requires multi-company.
Multi-company and financial consolidation: which plan it requires
It depends on your legal entities:
- One legal entity with several locations. You don't need multi-company: each location is a point of sale with its own warehouse, and results are separated with analytic accounting.
- Several legal entities. To run them in a single database you need multi-company: separate accounting per company and a consolidated view of the group. On the Odoo pricing page, among the plans with all apps, Multi-Company appears only in the Custom plan, which is also the only one with the external API (checked in October 2026).
Each legal entity also needs its own RUT (Chilean tax ID), its own digital certificate, and its own SII certification (the SII is Chile's tax authority) to issue electronic tax documents.
Electronic receipts, tips, and cash register closing in Chile
- Receipt (boleta). SII Resolution No. 53 of 2025 clarified that the electronic receipt can be delivered printed or digitally, and removed the option of not delivering the electronic proof of payment (SII). Odoo issues receipts from the POS (electronic invoicing guide).
- Tips. Article 64 of Chile's Labor Code requires establishments with waitstaff to suggest a tip of at least 10% on every bill, as an exact amount and on a document separate from the receipt (Dirección del Trabajo, Chile's labor authority). The system must record it separately from the sale.
- Cash register closing. Each POS session is closed with a cash count by payment method, and deposits are reconciled against the transactions that Fintoc pulls from the bank into Odoo (payment methods guide).
Dashboards by location: sales, average ticket, food cost, and labor cost
| KPI | How it's calculated | What it answers |
|---|---|---|
| Net sales | Sales excluding VAT and tips, by channel | Which location is growing? |
| Average ticket | Net sales divided by number of receipts | Are we selling more per customer? |
| Actual food cost | Ingredient consumption divided by net sales | Where is the margin going? |
| Waste | Valued scrap divided by net sales | Which location loses the most? |
| Labor cost | The location's payroll divided by net sales | Does staffing match sales? |
To compare them, set up every location the same way: point of sale, warehouse, and analytic account (or company).
Keep BI adds prebuilt dashboards inside Odoo, such as Sales Status & Performance, Profitability, and Income Statement (plans from 10 to 25 UF + VAT per month, where the UF is Chile's inflation-indexed unit of account, with setup in 7 days). Keep Checking notifies you with alerts such as Product cost increase above X%; put together your selection in the quote builder (more in automatic threshold alerts).
Specialized POS vs ERP: a checklist to decide
| Type | Covers well | Usually falls short on | Best for |
|---|---|---|---|
| Specialized POS | Sales, tables, kitchen orders, and receipts | Recipes, purchasing, and accounting | One or a few locations |
| Restaurant suite | POS with inventory and recipes | Full accounting and multi-company | Groups focused on dining room and kitchen |
| ERP with integrated POS | The entire operation and BI in one database | Requires an implementation | Several legal entities or a central kitchen |
You need an ERP behind the scenes, even if you keep your POS, if you answer yes to two or more of these:
- Do you have more than one legal entity?
- Do you have a central kitchen or centralized purchasing?
- Do you calculate food cost in spreadsheets?
- Does the accounting close for each location take weeks?
- Do you sell through channels that don't draw down the same inventory?
Why do it with KPB Solutions
As an Odoo Gold Partner with a presence in 6 Latin American countries, we design the architecture for your group: Odoo implementation with a restaurant POS, multi-company where it applies, central inventory, and recipes; integrations with Justo, Buk, and Fintoc; and control with Keep BI and Keep Checking.
Book a meeting and let's look at what your restaurant group would look like running on a single system.
