What is Odoo ERP for restaurants?

It is Odoo set up to run a restaurant end to end: point of sale, kitchen display, recipes, inventory, purchasing, HR and accounting on one database. Each sale updates ingredient stock, food cost and the books, so cost and profit are known per dish and per branch. It can run the counter itself through Odoo POS, or sit behind an existing POS such as Foodics. Naqlah configures it for Saudi restaurants, including ZATCA e-invoicing and Arabic and English operation.

Can I keep Foodics and still use Odoo?

Yes. Naqlah recommends keeping Foodics at the counter where it already works well and connecting it to Odoo for inventory, purchasing and accounting. Cashiers keep the screens they know, and sales, payments and consumption reach the back office without retyping. Running the counter on Odoo POS is an equal option, and usually fits new openings or restaurants that want one system end to end. The comparison above shows where each one fits.

Are restaurant receipts ZATCA compliant?

Yes. Every receipt is issued as a ZATCA compliant simplified e-invoice with its QR code and reported through the Fatoora platform. Tax invoices for corporate and catering customers are cleared through the same connection. Naqlah onboards each branch as part of the setup and tests it before go-live, and 15% VAT is applied on every sale and summarised for the return.

Does Odoo connect to delivery apps?

Yes. Naqlah connects delivery platforms to Odoo through Deliverect. Orders arrive at the cash register and the kitchen without retyping, and ingredients are deducted from stock like any other sale. Delivery sales are reported per channel alongside dine in and takeaway, so the restaurant can compare channels side by side instead of reconciling statements at month end.

Can Odoo calculate food cost per dish?

Yes. Each dish has a recipe, and Odoo costs it from what its ingredients were bought for. When supplier prices change, the dish margin changes with them. Shared preparations such as sauces are costed once and reused across dishes. Waste logs and stock counts then show where actual use differs from the recipe, which is usually where portioning or spoilage problems first become visible.

How long does an Odoo implementation take for a restaurant?

It depends on the number of branches and cash registers, the integrations involved, how clean the recipe and product data is, and how much is customised. A single restaurant on a standard setup is a much smaller project than a multi-branch chain with a central kitchen. Naqlah sets the plan in the discovery phase and brings branches live in an agreed sequence.

Naqlah | Odoo ERP for Restaurants in Saudi Arabia

Best for

Single restaurants to franchise groups

Works with

Foodics, Deliverect, Bonat, Jisr

Compliance

ZATCA, VAT, GOSI, WPS

Languages

Arabic and English

Reviewed by Naqlah Team

November 14, 2026

What the setup covers

What Odoo handles, area by area

The challenge

What slows this industry down

Counter and table service
Odoo POS takes dine in, takeaway and delivery orders on one screen. Tables sit on a floor plan per branch, orders are sent course by course, and bills can be split by guest or by item. Notes and modifiers travel with each dish. Guests can also order from a QR code at the table or from a kiosk. If the internet drops, the cash register keeps selling and syncs when the connection returns. Branches already running Foodics keep it at the counter.Connects to Foodics, receipt printers, QR and kiosk ordering
Kitchen display
Each order reaches the kitchen the moment it is confirmed, on a screen or a printer at the station that prepares it: grill, cold section, drinks or pastry. The ticket shows the table, the course and any notes, so nothing is shouted across the pass. Cooks mark dishes as ready, the floor sees the status, and the time each order has been waiting is visible to the kitchen manager during the rush.Connects to Odoo POS, kitchen screens, station printers
Recipes and food cost
Every dish has a recipe listing its ingredients and quantities. When the dish is sold, Odoo deducts those ingredients from stock and works out what the plate cost from what the ingredients were bought for. A supplier price change shows in the dish margin, so menu prices rest on calculated cost. Shared preparations such as sauces and doughs are set up as sub-recipes, costed once and reused across dishes.Connects to Inventory, Purchase
Stock and waste
Each branch and the central kitchen holds its own stock, and every transfer between them is recorded with its cost. Ingredients can be tracked by lot and expiry date, so older stock is used first. Waste is logged with a reason, such as spoilage, overproduction or a returned dish. Regular stock counts then show the gap between what should be on the shelf and what is, per branch and per ingredient.Connects to Inventory, barcode scanners
Purchasing and suppliers
Minimum stock levels raise draft purchase orders for each supplier, so ordering no longer depends on someone noticing an empty shelf. Agreed price lists apply automatically, and orders above a set amount wait for approval. When goods arrive, the received quantities are checked against the order, and the supplier bill is checked against both before it is paid. Supplier balances and payment terms sit in the same system as the stock they relate to.Connects to Purchase, Inventory, Accounting
Delivery apps and loyalty
Orders from delivery apps reach the cash register and the kitchen through Deliverect, so nobody retypes them from a tablet. Ingredients are deducted from stock like any other sale, and delivery sales are reported next to dine in and takeaway, so channels can be compared side by side. Loyalty runs on Odoo's built-in points, rewards and gift cards across all branches, or on Bonat where a chain already uses it.Connects to Deliverect, Bonat
Payments and receipts
Every receipt is issued as a ZATCA compliant simplified e-invoice with its QR code, in Arabic and English. On registers running Odoo POS, Naqlah's Pathfinder integration sends the amount to the card terminal and records the result on the order, so the cashier does not type it twice and card totals match the day's sales. At closing, each cashier counts the drawer against what the system expects, and differences are recorded.Connects to Pathfinder, mada card terminals, ZATCA Fatoora
Accounting per branch
Sales, cost of goods and VAT post to accounting from every receipt, without an end of day export. Each branch has its own profit and loss statement, and the group sees a consolidated view. Bank and card settlements are reconciled against recorded sales, and VAT is summarised for the return. Franchise and multi-company groups keep separate books per legal entity in the same database.Connects to Accounting, bank statements, ZATCA Fatoora
Staff and payroll
Employee records, shifts, attendance and leave are managed per branch, which suits hourly and rotating teams. Attendance feeds the payroll inputs. Payroll itself runs in Jisr or ZenHR, which handle GOSI and WPS, and each payroll run posts to Odoo accounting. Labour cost then sits next to food cost in every branch's results. Reminders flag iqamas, passports and contracts before they expire.Connects to Jisr, ZenHR, HR

Built for Saudi Arabia

How Odoo is localized for Saudi Arabia

Some requirements apply to every company operating in Saudi Arabia. Others are specific to your industry. Odoo, as Naqlah configures it, covers both.

Applies to every Saudi business

ZATCA e-invoicing

Tax and simplified invoices are cleared or reported through the Fatoora platform, with QR code and cryptographic stamp.

VAT

15% VAT is applied, reported, and ready for the return.

Arabic and English

Each user picks their language. Screens switch to right-to-left Arabic, and documents print in both languages.

GOSI and WPS

Handled through the Jisr or ZenHR payroll connection, with each payroll run posted to Odoo accounting.

Saudi riyal

Books are kept in SAR with a chart of accounts suited to Saudi reporting.

Local payments

Odoo POS accepts mada, cards, and cash through integrated payment terminals.

Specific to restaurants

Simplified invoices at the register
Every restaurant receipt is a ZATCA compliant simplified e-invoice with its QR code, reported through Fatoora. Each branch is onboarded as part of the setup.
Foodics
Naqlah builds and maintains the connection between Foodics and Odoo, so counter sales, payments and consumption reach inventory and accounting without retyping.
Delivery apps
Delivery platforms connect to Odoo through Deliverect, so orders reach the kitchen and stock without retyping.
Loyalty
Odoo loyalty works across branches out of the box. Chains already using Bonat keep it, connected to Odoo.
Arabic at the counter and in the kitchen
Cashiers, waiters and cooks each work in Arabic or English on the same system, and receipts print in both languages.
Lots and expiry dates
Ingredients are tracked by lot and expiry date from delivery to use, which supports food safety and halal sourcing records.

Compare your options

Keep Foodics, or run the counter on Odoo POS

Many Saudi restaurants already run Foodics at the counter, and their cashiers know it well. The choice is not all or nothing: both setups below give the restaurant one set of books. Naqlah recommends keeping Foodics at the counter when it already works well, and treats Odoo POS as an equal option.

	Foodics at the counter, Odoo behind it (recommended)	Odoo at the counter and behind it
Counter and kitchen	Cashiers keep the Foodics screens they already use	Odoo POS restaurant mode with floor plans, courses and kitchen display
How sales reach the back office	Sales, payments and consumption flow from Foodics into Odoo	No sync needed. Every sale is already in the same database
Inventory and recipes	Foodics sales sync to Odoo, where recipes and stock are costed	Each sale deducts ingredients in the same system
Card terminal	Stays as it is today	Pathfinder sends the amount to the terminal and records the result
Accounting	Odoo, with Foodics sales posted per branch	Odoo, posted from every receipt
What Naqlah does	Builds and maintains the Foodics connection	Configures the registers and integrates the card terminal
Change for staff	Little change at the counter	New screens at the counter, one system to learn
Fits best when	Foodics already runs well across your branches	You are opening new branches or want one system end to end

In both setups, inventory, purchasing, accounting and reporting run in Odoo, receipts stay ZATCA compliant, and each branch gets its own profit and loss statement. The difference is only which screen the cashier uses and how the sale reaches the back office.

A third route, keeping the POS and exporting sales into accounting once a month, is workable for a single outlet only. With more branches, the gap between the export and what happened on the floor is where stock and margin go missing.

Still deciding whether you need an ERP? Read ERP for restaurants in Saudi Arabia and Is Odoo ERP suitable for restaurants?

Recommended modules

The Odoo bundle for this industry

The modules we typically implement for businesses like yours, all running on one database.

Point of Sale

Fast checkout that syncs stock and accounting automatically.

Inventory

Real time stock across warehouses, stores, and channels.

Purchase

Purchase orders, vendor pricing, and approvals under control.

Accounting

ZATCA compliant invoicing, VAT returns, and real time financial reporting.

HR

Employees, leaves, payroll inputs, and appraisals in one system.

By type of business

The typical setup for each type of restaurant

Single restaurant
One location that wants accurate books and real food cost without changing how the counter works. The priority is knowing what each dish costs and closing the month without rebuilding it from exports.Typical setup: Foodics or Odoo POS at the counter, with Inventory, Purchase and Accounting behind it. HR is added when the team grows.
Quick service and kiosks
Counters, drive-through lanes and kiosks where the guest orders and pays before the food is prepared. Speed at the cash register and accuracy of the kitchen ticket matter most, and the menu changes often with offers and combos.Typical setup: Odoo POS or Foodics at the counter, kiosk or QR ordering, kitchen screens by station, and recipes costed per item.
Table service and fine dining
Orders open on a table, grow over the meal, may be split, and are settled at the end. Courses have to reach the kitchen in the right order, and the floor needs to know what is ready.Typical setup: floor plans per branch, course by course sending to the kitchen display, and bill splitting by guest or by item.
Multi-branch chain
Several branches sharing one menu, often supplied by a central kitchen. The daily questions are which branch is profitable, where stock is sitting, and whether prices and recipes are the same everywhere.Typical setup: one database for all branches, transfers from the central kitchen recorded with their cost, and a profit and loss statement per location.
Cloud kitchen
Delivery-first kitchens running several brands from one line. There is no dining room, so margin depends on delivery costs, packaging and how well shared ingredients are costed across brands.Typical setup: delivery apps connected through Deliverect, recipes and reporting per brand, and one shared stock.
Franchise group
Franchisors and operators reporting across several legal entities. Each entity needs its own books and VAT return, while the group needs one view of sales, cost and menu consistency.Typical setup: one company per entity in the same database, consolidated accounting, and menus and price lists controlled centrally.

What you get

What a Naqlah restaurant setup includes

Delivered by Naqlah's team of 21+ certified Odoo experts, in Arabic and English. Every project covers the eight items below, scoped to the size of the restaurant.

Process review
Workshops with the owner, operations and finance map how an order, a delivery and a supplier bill move through the business today, and what should change.
Configuration
Menu, recipes, branches, floor plans, stock locations, taxes and chart of accounts are set up in Odoo to match how the restaurant runs.
Integrations
Foodics, delivery apps, loyalty, payroll and card terminals are connected where you use them, and tested with real orders, voids and refunds.
ZATCA onboarding
Each branch is connected to the Fatoora platform and tested before go-live, so receipts are compliant from the first sale.
Data migration
Products, suppliers, opening stock and opening balances are cleaned, imported and checked against your current figures.
Reports
Daily sales, food cost, waste and branch profit reports are built around the figures the owner and managers already ask for.
Training by role
Cashiers, kitchen staff, storekeepers and accountants are each trained on their own screens, on your own menu, in Arabic or English.
Support after go-live
Questions are answered, integrations are monitored and Odoo updates are applied under a support plan.

How it is delivered

From first workshop to go-live, in four phases

Discover
Workshops map your menu, branches, suppliers, integrations and reports, and agree what is in scope. Recipes that exist only in the chef's head are written down at this stage.
Configure
Odoo is set up with your recipes, stock locations, taxes and integrations, then loaded with your products, suppliers and opening balances. Each branch is connected to ZATCA.
Test and train
Staff run real orders through a test copy, including a split bill, a void and a refund. Each role is trained on its own screens before anything changes at the counter.
Go live and support
Branches switch over in an agreed sequence instead of all at once. Naqlah stays on hand through the first closings and the first month end, then moves to ongoing support.

What Naqlah needs from your side

One person who owns the project and can make decisions, your current menu with recipes and portion sizes, your supplier list with prices, and exports from the POS and accounting system you use today. The cleaner this data is, the smoother the configuration phase runs. Staff time for testing and training is planned around service hours, so the restaurant keeps trading throughout.

Industry questions, answered

Everything else, we cover in a free 30-minute consultation.

More from Naqlah on this industry

ERP for restaurants in Saudi Arabia: when the cash register is no longer enough

Is Odoo ERP suitable for restaurants? What it does natively and where it needs a technology partner

ERP for fine dining and table service: payment after service, or through the Foodics integration

Other industries

Odoo ERP for Restaurants in Saudi Arabia

What Odoo handles, area by area

What slows this industry down

How Odoo is localized for Saudi Arabia

Applies to every Saudi business

Specific to restaurants

Keep Foodics, or run the counter on Odoo POS

The Odoo bundle for this industry

Point of Sale

Inventory

Purchase

Accounting

HR

The typical setup for each type of restaurant

What a Naqlah restaurant setup includes

From first workshop to go-live, in four phases

What Naqlah needs from your side

Industry questions, answered

More from Naqlah on this industry

Odoo ERP for other industries

Cafes

Restaurants

Trading and Distribution

Services

Manufacturing

Restaurants and Cafes

E-commerce

Retail

Ready to run your business on one system?