Skip to Content

Odoo for restaurant groups and cloud kitchens

How restaurant groups and cloud kitchens in Saudi Arabia, the UAE and Egypt use Odoo beyond the till: central kitchen production, recipes and food cost, purchasing from suppliers, multi-brand delivery, branch profit and compliance with ZATCA, ETA and municipality rules.
November 7, 2026

A restaurant group with eight branches and a central kitchen is really three businesses at once: a manufacturer that produces sauces, dough and marinated proteins; a distributor that delivers them to branches every morning; and a retailer that sells plates through dine-in and delivery apps. Most groups run each part on a different tool and never see the true cost of a dish. Odoo connects all three, from supplier invoice to plate sold.

FlexCode Middle East is part of FlexCode Systems GmbH, an Odoo Silver Partner. We implement Odoo, so Odoo is the system we describe, next to an honest look at the topic itself.

Key points

  • Central kitchen as a factory. Manufacturing orders for batches, with lots and expiry.
  • Branches order like customers. Daily transfers from the central kitchen based on par levels.
  • Theoretical versus actual. Recipes show what should have been used; counts show what was.
  • Many brands, one kitchen. Cloud kitchens run several brands on one stock and one team.

The central kitchen

In Odoo, the central kitchen is a warehouse with a production area. Semi-finished items such as tahini sauce, burger patties or pizza dough have bills of materials, and manufacturing orders produce them in batches with a lot number and a use-by date. Each morning, branches receive transfers of semi-finished goods, and the system knows exactly which batch went to which branch, which matters if a food safety issue appears.

  1. Supplier deliveries to central kitchen
  2. Batch production with lots
  3. Morning transfers to branches
  4. Dishes sold at POS and apps
  5. Ingredients deducted by recipe

Production basics are in Odoo Manufacturing basics; batch tracking in lots and expiry dates.

Chefs preparing food in a large commercial kitchen
The central kitchen is a small factory and should be run like one.

Food cost you can act on

Each dish has a recipe with exact quantities. When it is sold, Odoo deducts the ingredients from the branch stock. At the weekly count, the difference between theoretical usage from recipes and actual usage from the count is the variance: waste, over-portioning, wrong recipes or theft. Groups that review this variance weekly usually bring food cost down by several points within a few months.

MeasureHow it is calculatedAction
Theoretical food costRecipe cost of dishes sold divided by salesFix menu prices and recipes
Actual food costOpening stock plus purchases minus closing stock, divided by salesCompare with theoretical
VarianceActual minus theoreticalInvestigate waste and portioning
Menu engineeringMargin and popularity per dishPromote stars, rework weak dishes

Cloud kitchens and delivery

A cloud kitchen in Riyadh or Dubai may run five virtual brands from one kitchen. In Odoo each brand can be its own POS or online menu, with shared ingredients and staff. Orders from delivery apps come in through connectors, so each brand's sales, commission and margin are visible separately while stock and production are shared.

  • Treat each delivery app as a separate channel to see its commission.
  • Reconcile app payouts weekly against orders.
  • Price delivery menus to cover commissions and packaging.
  • Track packaging as stock, it is often a hidden cost.

Front of house features are in Odoo POS for restaurants and cafes.

Purchasing and suppliers

Vegetables, meat, dairy and dry goods come from different suppliers on different days. Odoo keeps each supplier's price list, minimum order and delivery days, and par levels per branch or central kitchen create purchase orders automatically. Receiving is checked against the order, including weight and temperature for fresh goods, before the bill is approved.

See purchasing in Odoo and, for the food supply side, Odoo for food and beverage companies.

Running the group

Per branch

Sales, food cost, labour, rent

Weekly

Variance review

Per brand

Margin in cloud kitchens

Per batch

Traceability from central kitchen

Labour is the other big cost. Odoo Planning schedules shifts by branch and role, and attendance from the POS or a kiosk feeds payroll. With food cost, labour and rent on each branch analytic account, owners see a clear profit and loss statement for every outlet every month.

Saudi branches must follow ZATCA rules for point of sale; Egyptian ones the e-receipt.

FlexCode implements Odoo for restaurant groups

We set up the central kitchen, recipes and food cost, branch POS, delivery channels and supplier ordering, and train chefs, managers and accountants.

Book a free call

Frequently asked questions

Can Odoo run a central kitchen?

Yes, as a warehouse with manufacturing orders, lots and transfers to branches.

How does Odoo calculate food cost?

From recipes for theoretical cost and from stock counts for actual cost.

Can one kitchen run several brands?

Yes. Each brand has its own menu and POS, sharing stock and staff.

Can delivery app orders flow into Odoo?

Yes, through connectors, so stock and sales are complete.

Can I see profit per branch?

Yes, with food cost, labour and rent on branch analytic accounts.

Talk to us about how Odoo fits your business. Book a free call

Run invoicing, stock and accounts from one system.

FlexCode Middle East implements Odoo in Arabic and English for companies in Egypt, Saudi Arabia and the UAE.