The waiter enters the order, the kitchen sees it on a screen, the sale reaches warehouse records, and at shift close the cash is checked against the records. The fiscal receipt and the dish recipe are a separate matter: we state them openly.
A restaurant works in two places at once: the dining room and the kitchen. The gap between them causes delays, waste and disputes.
Odoo S.A. publishes industry packages for the food service sector in the Apps Store. Odoo describes them as a “ready-configured database”. The Hospitality category (Odoo 20 line, as seen on 25 October 2026) includes “Fine Dining Restaurant”, “Fast Food”, “Bar & Pub”, “Takeaway Restaurant”, “Food Trucks” and “Catering”.
The Fine Dining package is described on its page as covering reservations, orders, warehouse and staff. Its dependencies include Restaurant (POS), Appointments, Planning, Purchase, Employees, Attendances, Website and Project. The Fast Food package combines the cash desk, phone orders, self-ordering via kiosk or QR, the kitchen display, shift planning and purchasing. The Catering package covers the quotation, the menu plan and on-site logistics, for each event.
All three package pages share one condition: the package requires Odoo Enterprise. Availability: Odoo Online, Odoo.sh and your own server. Odoo's restaurant industry page, however, does not mention a separate package and only lists the apps: Point of Sale, Purchase, Appointments, Inventory, Planning and Website.
The foundation is the restaurant cash desk. The other apps connect it with the kitchen, warehouse, purchasing and accounting. Which apps are needed is determined in the diagnostic.
Floor plan, tables, order, courses, bill splitting, tips, temporarily hiding a dish from the menu (Odoo 20).
The order goes by category to the kitchen or bar screen; there are stages and a delay indicator.
Booking a table in advance, resource and capacity. The reservation is visible on the floor plan. Part of Enterprise.
Receipt of raw materials, internal transfers, inventory counts and write-offs.
Expiry by batch (lot), alert date, using raw materials nearing expiry first (FEFO).
Minimum stock rule, request for quotation to the supplier, and order.
Prep items such as sauce, dough and marinade: bill of materials (BoM) and manufacturing order.
Scheduling the waiter, cook and cashier into shifts. Part of Enterprise.
Cash journal, accounting entry at shift close, supplier accounting, invoice to a corporate customer.
Each step leaves a document in Odoo. The dining room, kitchen and accounting look at the same order.
Dishes are placed in categories and combos (sets) are built. The tax setting for dine-in and takeaway is defined separately.
Tables are drawn on the floor plan. For a large party, tables are merged by dragging; they are linked to one order and return to their place after payment.
The waiter selects a table and adds dishes. Courses are set by hand or automatically by category. From Odoo 19, there is allergen management for self-ordering.
When “Send” is pressed, the first course goes to the kitchen display. The following courses stay “Pending” and are released when the waiter presses “Fire”. Where there is no screen, a network kitchen printer works.
The bill is split between guests: each sub-order is paid separately. The tip is recorded as a separate product; Odoo 20 can also add a service charge.
Cash, card or QR. The Odoo receipt is an internal document, while the fiscal receipt comes from the registry-listed cash register device.
Raw material expiry is controlled by lot, and unfit goods are written off with a reason. The consumption of a sold dish depends on the recipe path (below).
The cashier counts the cash, and if the difference exceeds the limit, the manager approves. The owner sees revenue by session, payment method and dish; from Odoo 19 there is also a preparation time report.
Straight answer: Odoo's restaurant documentation does not describe recording ingredient consumption when a dish is sold. Odoo's restaurant industry page does not mention a recipe or an ingredient either. The bill of materials (BoM) and the manufacturing order exist in the Manufacturing app, but their link with the cash desk is not covered in the official restaurant documentation.
There are three paths, and the choice depends on your process. The first: a manufacturing order for prep items (sauce, dough, marinade); the cash desk sells the finished dish, and consumption is checked by periodic inventory counts. The second: a bill of materials of the kit type (Kit). According to the documentation, when a kit is sold the order holds one line, and the components are recorded at delivery; how this works at the cash desk is tested in a test database. The third: third-party modules in the Apps Store. A search for “ingredient” on 25 October 2026 showed 34 apps in the 19.0 line, some of which link a POS product with a bill of materials. Each one's quality is checked separately; Odoo Online is not compatible with them.
The legal side: under the catering rules, the business draws up and approves the recipe formulation of its dishes. Keeping a costing card is not mandatory; it is for internal use and is not a basis for setting prices (Cabinet of Ministers Resolution No. 75, Annex 2, clause 15).
The example is hypothetical, without figures. A restaurant hosts a family dinner at three merged tables. The reservation was entered earlier through Booking and is visible on the floor plan.
The dining room and kitchen part is available in the ready-made apps. Recipe consumption, the fiscal receipt and local platforms are separate work. The information is based on the Odoo 19 and 20 documentation and release news; if your version differs, we check it in the diagnostic.
| Goal | In standard Odoo | Extra work (BUline) |
|---|---|---|
| Tables, floor plan, merging tables | Available: POS Restaurant, floor editor, merging by dragging | Dining room layout, table numbers, roles |
| Sending to the kitchen | Available: kitchen display (works in a browser, IoT Box is not supported, 19.0 documentation) or a network printer | Routing by category: kitchen, bar, dessert; stages |
| Courses | Available: by hand or by category, released with “Fire” | Linking categories to courses, a guide for the waiter |
| Table reservation | Available: Booking in POS; Appointments (Enterprise) with resources and capacity | Reservation rules, cancellation deadline, notification |
| QR menu and self-ordering | Available: “QR menu”, “QR menu + Ordering”, “Kiosk”. At the kiosk, the terminal can only be Adyen, Stripe or Viva.com; cash is not supported | Menu setup, testing a local payment method |
| Bill splitting, tips | Available; in Odoo 20 a service charge can also be added | Adapting the tip and service charge rule to your policy |
| Dine-in, takeaway, delivery | Available: presets and different fiscal positions | Confirm the fiscal position with the accountant |
| Recipe and ingredient consumption | Not mentioned in the restaurant documentation | One of the three paths above, estimated separately |
| Expiry and FEFO | Available: lot, four dates, FEFO. The Odoo 20 POS warns on an expired product | Which raw material groups to enable tracking for |
| Orders from delivery platforms | There is no local platform in the documentation. The Odoo release news mentions GoFood, GrabFood and UrbanPiper integrations (for other markets) | Agreement with the platform and integration, estimated separately |
| Fiscal receipt (online or virtual cash register) | No: the Odoo documentation does not mention a connection to an Uzbekistan fiscal module | Connection to the registry-listed cash register device, or another scheme. Cash desk page |
The items below have been checked against official sources. Those that apply to your type of venue, we list in writing at the diagnostic.
Each connection is assessed and built separately. We do not promise that a “ready-made connector exists.”
Reports are not copied into a separate spreadsheet: they are built from the session, order and warehouse documents in the same database.
The stages follow the general BUline Method. The timeline is agreed in writing after the diagnostic. Implementation process →
We study the dining room and kitchen process, the menu structure, the current cash register device and software, delivery platforms, and the accounting of prep items and recipes. Written questions for the tax service are prepared. Result: a business requirements document (BRD).
We confirm the package or set of apps, the cash desk scheme (after the written answer), the recipe path, the warehouse structure and the hosting type.
First, a pilot with real service in one dining room or one branch: table, kitchen, cash desk, shift close. Then the remaining branches.
Waiters, cashiers, cooks, warehouse staff and managers are trained by role; the practice runs on your own menu data. Guides and video lessons are provided.
After launch, 30 days of enhanced support, then agreed ongoing assistance: a new branch, menu changes, reports.
This list speeds up the diagnostic. We can start even if not everything is ready.
| Mistake | Consequence | How we prevent it |
|---|---|---|
| Not deciding the ingredient consumption path at the start | Cost and warehouse records do not match | Choose the recipe path in the diagnostic and test it in a test database |
| Enabling expiry tracking for all raw materials | Extra data entry at receiving grows | Enable it only for perishable groups |
| Building the cash desk scheme without agreeing it with the tax service | The scheme may fall under the new ban | Get the written answer before the architecture stage |
| Not testing how the kitchen display works when the connection drops | At peak hours the kitchen may be left without orders | Run a connection drop in the test database and write down a fallback procedure |
| Not linking courses to categories | All dishes come out at once | Link categories to courses and teach the waiter the “Fire” procedure |
Yes. Odoo S.A. publishes the “Fine Dining Restaurant”, “Fast Food”, “Bar & Pub”, “Takeaway Restaurant” and “Catering” packages in the Apps Store. They are a ready-configured database, require Enterprise and are also available in Odoo Online. The country localization, the fiscal receipt and local platforms are not part of the package.
Both are available. The kitchen display works in a browser: a phone or a touchscreen connected by USB/HDMI is enough, and IoT Box is not supported (Odoo 19.0 documentation). The printer connects over the network by IP address and serves as a backup.
The restaurant documentation does not describe this. The paths: a manufacturing order for prep items, a bill of materials of the kit type (Kit), or a third-party module. Which one fits your process, we will show with a calculation in a test database.
On its restaurant page, Odoo describes online booking through Appointments, and the reservation is visible on the floor plan. Appointments is part of Enterprise. Reservation rules (capacity, cancellation deadline, deposit) are agreed in the diagnostic.
The Odoo cash desk handles the order, the table and the payment, while the fiscal receipt comes from the registry-listed cash register device. The new wording of clause 4 of Resolution No. 943 bans catering businesses from using accounting programs that are not integrated. We will establish in writing with the tax service whether the Odoo cash desk falls under this definition. Cash desk page →
Odoo's documentation does not cover local platforms; the integrations in Odoo's release notes (GoFood, GrabFood, UrbanPiper) are for other markets. Exchanging orders with Yandex Eats, Wolt or Uzum Tezkor depends on those services' partnership terms. At the diagnostic we get a written answer from the platform and assess the connection route.
Odoo Online is not compatible with third-party and custom modules. If you need a fiscal receipt, platform or ingredient module, Odoo.sh or your own server is chosen. Industry packages are available on Online. Hosting types →
The Odoo licence depends on the number of users and apps (terms at odoo.com). The scope of BUline's work depends on the number of dining halls and tables, branches, apps, customization, integrations, data volume and training. The exact cost and timeline are given in a written proposal after the free diagnostic.
During the diagnostic, we review your processes and tell you where standard Odoo is enough and where configuration is needed — with an app list, edition and phases.