Restaurant ERP Management

Odoo Restaurant ERP Management is Odoo Point of Sale configured in restaurant mode, integrated with the Kitchen Display System (KDS), Odoo Inventory, Odoo Manufacturing (for recipe BoMs and food costing), Odoo Purchase (for supplier ordering), and Odoo Accounting — all connected in one platform. It covers the full food service operation: floor plan and table management, digital kitchen order routing, recipe-driven ingredient deduction, multi-channel ordering (dine-in, takeaway, delivery), ZATCA-compliant billing, and real-time food cost and sales reporting.

When a server confirms an order at the table in Odoo POS, the order routes instantly to the Kitchen Display System — Odoo's dedicated kitchen screen application running on a tablet or monitor mounted at the kitchen station. Orders appear on the KDS grouped by course (starters, mains, desserts) with an elapsed time counter. The chef marks each dish as ready on the KDS screen; this status update appears immediately on the server's POS device. Order routing rules in Odoo determine which items go to which station — for example, grill items to the grill station, cold starters to the cold section — automatically.

Each menu item in Odoo POS is linked to a bill of materials (BoM) in Odoo Manufacturing. The BoM lists every ingredient, quantity per portion, and unit of measure — including nested sub-recipes (a sauce BoM referenced inside a main dish BoM). When the dish is sold at the POS, Odoo automatically deducts the exact ingredient quantities from Odoo Inventory. The food cost percentage per dish is calculated in real time by comparing the total ingredient cost (at current purchase price) against the menu selling price. This eliminates the monthly spreadsheet food cost exercise and makes recipe profitability visible daily.

Yes. Odoo supports multiple branches as separate locations within a single Odoo instance. The menu, recipe BoMs, pricing, and supplier lists are managed centrally and pushed to all branch POS terminals. Each branch has its own inventory, its own KDS configuration, and its own sales reporting. A management dashboard compares branch performance side-by-side — average ticket, food cost %, table turns, and top-selling items — in real time. Franchise management with separate ownership structures is handled through Odoo's multi-company module, where each franchise entity has its own accounting while sharing the central recipe and menu database.

Yes. iWesabe configures Odoo POS to issue ZATCA Phase 2 compliant receipts from every restaurant terminal. For standard dine-in and takeaway bills (B2C), Odoo generates simplified tax invoices with QR codes printed on the customer receipt — data transmitted to FATOORA automatically. For corporate dining or catering orders (B2B) where the customer requires a full VAT invoice with their VAT registration number, Odoo generates a full e-invoice with UBL 2.1 XML submitted for FATOORA clearance. Saudi VAT (15%) is applied to taxable food and beverage items with correct tax category treatment.

Odoo's open API and webhook architecture allow integration with delivery aggregators. Orders received from a delivery platform are mapped to Odoo POS order format and routed to the KDS alongside in-house orders — so the kitchen sees all orders in one queue regardless of origin. The specific integration with each aggregator (HungerStation, Jahez, Careem Food) is handled through middleware or a direct API connector; iWesabe scopes and configures the applicable integration during implementation based on the client's active delivery platforms.

A standard single-branch restaurant implementation — covering POS setup, floor plan configuration, KDS installation, menu and recipe BoM build, ingredient opening stock, and ZATCA integration — typically takes 4 to 6 weeks. Multi-branch chains (5+ locations) with large menus (150+ items), complex delivery integrations, or simultaneous franchise rollout should plan for 10 to 14 weeks. iWesabe provides a phased rollout plan that goes live with your busiest or flagship branch first, then rolls out remaining locations progressively to minimise operational disruption.