Build-to-order Odoo POS for dine-in: table plans, KOT/kitchen display, split bills, waiter app and hotel room-charge. Built and installed by ECOSIRE. One-time license from $399.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Build-to-order Odoo POS for dine-in: table plans, KOT/kitchen display, split bills, waiter app and hotel room-charge. Built and installed by ECOSIRE.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
The Restaurant & Hospitality POS Suite is a build-to-order Odoo module that ECOSIRE designs, builds, installs and supports for your venue — this is not a ready-made apps.odoo.com download. It extends Odoo's native point_of_sale into a full dine-in service platform: graphical floor plans, Kitchen Order Tickets (KOT), a kitchen display, split/merge bills, course firing, menu and modifier engineering, a waiter ordering app, and — for hotel F&B — direct room-charge posting against a guest folio.
Graphical floor and table plan editor — draw multiple floors/sections, drag tables, set seats and shapes; live color-coded status (free, seated, ordered, bill printed, needs cleaning) driven by @api.depends computed fields
Kitchen Order Tickets (KOT) routed per station — starters to the cold line, mains to the hot line, drinks to the bar — via automated/server actions and per-category printer/display mapping
Kitchen Display System (KDS) as an OWL screen — tickets appear in real time, bump when done, with prep timers and course-by-course firing to control pacing
Split, merge and transfer bills — split by seat, by item or evenly; merge tables that joined; transfer an open check to another table or waiter without losing the order
Course firing and hold/fire control — group lines into courses (appetizer, main, dessert) and fire each course to the kitchen when the table is ready
Menu, modifier and combo engineering — required and optional modifiers (no onions, extra cheese, cooking temperature), price-adjusting options, and combo/meal-deal products with component pricing
Everything is engineered the Odoo-native way so it upgrades cleanly and stays maintainable. We ship real Odoo models (models.Model) for floors, tables, KOT lines, courses, modifiers and combos; computed fields with @api.depends for live table totals, course status and check aging; access control via ir.model.access.csv plus record rules so a waiter only sees their own tables while a manager sees the whole floor; POS-screen and backend views in XML/OWL that feel like part of Odoo; and QWeb reports for kitchen tickets, itemized guest checks and end-of-day Z-reports. Automated actions and server actions handle order routing to the correct kitchen printer or display station, low-stock 86-listing of menu items, and shift/close reconciliation.
Because it is built on Odoo's own ORM and POS framework, the suite works on Odoo 17, 18 and 19, on Community or Enterprise (we confirm which features map to your edition during scoping), and integrates with the rest of your Odoo: inventory decrements ingredients on sale, accounting posts revenue and tips to the right journals, and the JSON-RPC/XML-RPC API lets third-party ordering, aggregators (delivery apps) or a hotel PMS talk to your POS. Room-charge integration links a POS check to a booking/folio so F&B lands on the guest's final invoice at checkout.
You tell us your menu, your floor, your printers and your workflow; ECOSIRE builds the module to fit, installs it on your server or Odoo.sh, migrates your product catalog, trains your floor and kitchen staff, and stands behind it with a support window. Typical delivery is 2 to 4 weeks depending on scope.
Runs one or several dine-in venues and needs a POS that handles the real floor: table plans, splitting checks between guests, sending orders to the kitchen without hand-written tickets, and knowing food cost. Wants it inside Odoo so sales, stock and accounting are one system, not four.
Lives on the pass and needs clean, legible tickets and a kitchen display that fires courses in the right order, times prep, and lets them 86 an item the moment it runs out — so the line isn't cooking dishes the floor already sold and can't deliver.
Oversees restaurant, bar and room service in a property using Odoo. Needs POS checks to post straight to the guest's room folio so F&B settles at checkout, plus consolidated reporting across every outlet and tight control over who can charge what.
Take orders tableside, manage their own section, split and transfer bills, and cash out shifts. Need a fast waiter app that only shows their tables and a POS that makes reconciliation at close painless.
Buy the license on ecosire.com and download the Restaurant & Hospitality POS Suite module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Restaurant & Hospitality POS Suite, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Fit to your exact floor plan, menu and service flow | Built to spec — floors, courses, modifiers and roles modeled to your venue | Achievable but you scope, build and test it all yourself | Generic feature set; you bend your workflow to fit the app | |
| Kitchen Order Tickets, KDS and course firing | Full KOT routing, OWL kitchen display and hold/fire per course | Possible, but the KDS and routing logic is significant build effort | Varies widely; often KOT only, no real course control | |
| Hotel room-charge / PMS folio posting | Built-in — posts F&B checks to the guest folio via PMS or RPC | You design and build the entire PMS bridge yourself | Rare; most restaurant apps don't touch hotel folios | |
| Odoo 17 / 18 / 19 and Community vs Enterprise coverage | Targeted to your version and edition during scoping | You own version and edition compatibility over time | Locked to the versions the vendor chose to support | |
| Delivery model | Built, installed, menu-loaded and staff-trained by ECOSIRE | Your team or contractor delivers end to end | Instant download, then you self-configure everything | |
| Upgrade safety & maintainability | Native ORM/POS extension + upgrade notes = clean version upgrades | Depends entirely on your code quality and documentation | You depend on the vendor to keep it current | |
| Support and ownership | Post-launch support window, full source handover, ongoing plan | Fully on you; no external support line | Vendor support quality and response times vary |
No. This is a build-to-order module. ECOSIRE builds it to fit your menu, floor plan, printers and workflow, then installs and configures it for you. You are buying a delivered, working solution — not a pre-packaged apps.odoo.com download.
Typical lead time is 2 to 4 weeks from the point we finalize scope (your menu, floors, roles, printer/KDS layout and any hotel/PMS integration). Simpler single-venue setups land near the short end; multi-outlet or PMS-integrated hotel builds sit toward the longer end. We agree a concrete timeline in writing before we start.
Every build includes a post-launch support window for bug fixes and adjustments, plus documentation and staff training. Because the module is built on Odoo's native POS framework and ORM (not brittle hacks), it upgrades cleanly across Odoo versions. After the initial window you can move to an ongoing ECOSIRE support and maintenance plan for updates, new features and version upgrades.
It supports Odoo 17, 18 and 19. Much of the suite runs on Community since it extends the core point_of_sale module; a few capabilities depend on Enterprise-only features. During scoping we confirm exactly which features map to your edition and adjust the build so you get the best result for the version and edition you run.
Yes. The room-charge integration links a POS check to a guest booking/folio so F&B posts to the room and settles on the final invoice at checkout. It works with Odoo's hotel/PMS modules or via the JSON-RPC/XML-RPC API to an external property management system — we confirm your PMS during scoping.
Yes. Sold dishes decrement ingredient stock through Odoo inventory, and revenue, tips and service charges post to the correct accounting journals automatically. It also exposes JSON-RPC/XML-RPC endpoints so online ordering or delivery aggregators can push orders and read menu availability.
Yes. We hand over the full module source with a clean __manifest__.py and upgrade notes explaining how it extends core POS. You own it and can have us — or your own team — extend it later. Building it the Odoo-native way keeps future changes and version upgrades low-risk.
Build-to-order Odoo POS for dine-in: table plans, KOT/kitchen display, split bills, waiter app and hotel room-charge. Built and installed by ECOSIRE.