Many restaurants and cafes in Saudi Arabia run Foodics as the point of sale in their branches, while management needs central accounting, purchasing and inventory in a system like Odoo. Without integration, daily sales are re-entered by hand, reports arrive late, and the real cost of each dish is hard to see. This article explains how the integration is usually done and which decisions decide whether it works.
What Foodics offers for integration
Foodics publishes a developer portal with a dedicated guide for accounting and ERP integration. Key points from that guide:
- Authorization through OAuth 2.0 with specific app scopes, such as reading orders and inventory transactions.
- Fetching completed and returned orders, and netting returns against completed sales.
- Using inventory transactions as the source of actual stock movements, and not treating purchase orders as movements, since they are requests awaiting approval.
- Fetching branches, warehouses, currency and time zone settings.
- Testing specific cases: tax-inclusive and tax-exclusive pricing, combos, orders paid with several methods, gift cards and house accounts.
The list is useful even if you are not building the integration yourself: use it to ask any vendor whether their solution covers these cases.
Integration options
An app from the Foodics marketplace
The Foodics marketplace includes ERP apps, such as an app by PlusTech IT that says it relays branch orders into Odoo's sales, accounting and inventory. The Foodics help article notes that enabling it requires an account with that provider. This route suits businesses that want one vendor to manage the link; check its scope and support.
A connector from the Odoo Apps store
The Odoo Apps store has Foodics connectors from various vendors, such as this Odoo 19 connector, which offers several inventory modes, including one that posts revenue and tax without decrementing stock in Odoo. That option alone shows that "where is inventory managed?" is a core decision, not a technical detail. These are third-party modules, so check compatibility with your Odoo version and hosting.
A custom integration
With complex recipes, a central kitchen supplying branches, or specific rules for daily journal entries, a custom integration on the Foodics API may fit best, at the cost of building and maintaining it.
Decisions to make first
| Decision | Options | Effect |
|---|---|---|
| Where is inventory managed? | Foodics, Odoo, or split | Whether Odoo deducts ingredients on each sale or only receives revenue |
| Accounting detail | One entry per order, or a daily entry per branch | Detail adds data; summaries simplify review |
| Payment methods | Cash, mada and cards, delivery apps, credit | Each needs an account or journal for reconciliation |
| Recipes and costing | Defined in Foodics or in Odoo | Where dish cost and waste are calculated |
| Simplified invoice | Issued at the point of sale | Avoid a second invoice for the same sale from Odoo |
E-invoicing in restaurants
Restaurant sales to consumers usually get a simplified tax invoice at the point of sale, and ZATCA's detailed guidelines require simplified invoices to be reported within 24 hours in the integration phase. If the POS issues the invoice, Odoo's role is to record revenue and VAT in the books, not to issue a new invoice. Agree this clearly with your integration provider, and check your own status in Phase 2 integration waves.
Go-live checklist
- Items and combos matched between both systems with consistent codes.
- Each Foodics branch mapped to a branch or warehouse and an analytic account in Odoo.
- Each payment method mapped to a journal, with a clearing account for delivery apps if used.
- Rules for discounts, service charges and tips.
- A full day tested on a copy, with totals matched against the Foodics report.
- An owner who reviews sync errors every day.
FAQ
Can Odoo POS replace Foodics?
It can, with the benefit of native integration with inventory and accounting. Changing the POS in a running restaurant, though, needs a careful look at the cashier and kitchen experience and delivery apps. See Odoo for restaurants and cafes and Odoo POS and e-invoicing.
What does integration cost?
Foodics apps and connectors are priced by their owners; see Foodics pricing and each connector's page. Maham Pro's prices are on our pricing page: systems integration starts from SAR 6,000, with the final cost depending on scope.
How Maham Pro can help
Maham Pro is an official Odoo partner at Ready Partner level. We review how your restaurant and branches work and explain the options: a Foodics marketplace app, an Odoo Apps connector, or a custom integration, and what each needs. See our restaurant solutions and Odoo ERP service, then book a free 30-minute introductory session.