Floor-standing Odoo self-service kiosk for QSR: touch ordering, guided upsell, card payment, and queue-number tickets. Built to order. One-time license from $499.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Floor-standing Odoo self-service kiosk for QSR: touch ordering, guided upsell, card payment, and queue-number tickets. Built to order.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Touch-optimized full-screen kiosk UI (OWL/QWeb) with category tiles, product images, combos, and modifiers — no Odoo backend chrome exposed to customers
Guided upsell and cross-sell prompts driven by configurable rules (e.g. suggest a drink and side with any main, or a larger size at checkout)
Integrated card/terminal payment via Adyen, Stripe, or Mollie, with the kiosk driving the payment terminal and confirming settlement before finalizing the pos.order
Order-type selection at start: dine-in, takeaway, or collection with a chosen pickup time
Automatic receipt printing plus a queue/order-number ticket so customers can wait for their number
Combos and meal deals modeled as configurable bundles with per-line modifiers (no cheese, extra shot, size upgrades)
The POS Self-Ordering Kiosk is a floor-standing, self-service front end that plugs into your existing Odoo Point of Sale. Customers browse a touch-optimized menu, build their own orders, respond to upsell prompts, and pay independently at the terminal — while your staff stay on the line making food. It is purpose-built for QSR and fast-casual operators who want to convert queue time into order volume without adding front-counter headcount.
This is a build-to-order engagement, not an off-the-shelf download. ECOSIRE designs, develops, installs, and supports a module tailored to your menu structure, brand, payment provider, and store hardware. Typical delivery is 2–4 weeks from kickoff.
The kiosk is delivered as a proper Odoo add-on with a clean __manifest__.py declaring dependencies on point_of_sale (and pos_restaurant where dine-in/table flows apply). New business objects are modeled as models.Model classes with typed fields, computed totals via @api.depends, and validated with @api.constrains. Kiosk sessions, upsell rules, and queue tickets each get their own model, secured through ir.model.access.csv plus multi-company record rules so one store cannot read another's sessions.
The customer-facing screen is a dedicated OWL kiosk client (QWeb/XML templates + JS components) that talks to the POS backend and payment terminal, so it runs full-screen in kiosk mode with no Odoo chrome. Orders land in the same pos.order pipeline your staff already use — kitchen display, receipts, and reporting all work unchanged. Configuration lives in POS settings; automated actions (server actions on records) handle things like flagging a paid order for the kitchen, and the kiosk can be integrated with external menu/loyalty systems over Odoo's XML-RPC / JSON-RPC API when needed.
Runs on Odoo 17, 18, and 19, Community or Enterprise (kiosk-hardware and some payment terminal drivers are richer on Enterprise — ECOSIRE advises on the edition fit during scoping).
A production-ready module, installed on your server or Odoo.sh, configured against your real menu and payment provider, with source code you own, documentation, staff training, and a support window. No fake dashboards, no vaporware — a working kiosk your customers can walk up to and order from.
Runs a multi-site fast-food or fast-casual brand and needs to cut front-counter labor and queue abandonment. Wants kiosks that push order volume and upsell attach rate without breaking the kitchen or reporting workflows already running in Odoo POS.
Operates several stores on one Odoo instance and needs each kiosk scoped to its own menu, pricing, and payment account. Cares about consistent branding across sites and multi-company data isolation via record rules.
Owns the Odoo deployment and is wary of bolt-on apps that break on upgrade. Wants a clean module they can read, own the source of, and maintain across Odoo 17/18/19 — with orders landing in the standard pos.order pipeline, not a parallel silo.
Buy the license on ecosire.com and download the POS Self-Ordering Kiosk 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 POS Self-Ordering Kiosk, 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 |
|---|---|---|---|---|
| Tailored to your menu, brand, and payment terminal | Built to order for your exact catalog, combos, and gateway | Possible but you specify and manage everything | Generic; you bend your setup to fit the app | |
| Self-service kiosk UI (full-screen, customer-facing) | Dedicated OWL/QWeb kiosk client, no backend chrome | Must be built from scratch | Varies; often a stock screen with limited branding | |
| Guided upsell / cross-sell logic | Configurable rule-driven prompts included | Only if you design and build the rule engine | Basic or fixed suggestions if present at all | |
| Integrated terminal payment (Adyen / Stripe / Mollie) | Configured and tested against your live gateway | You integrate and certify each provider yourself | Provider support hit-or-miss; may need extra apps | |
| Orders land in the standard pos.order pipeline | Yes — kitchen, receipts, inventory, reports unchanged | Depends on your implementation discipline | Usually yes, but data model can drift | |
| Multi-store isolation via record rules | Per-store menu, pricing, and payment scoping included | You must design record rules correctly | Often single-store assumptions | |
| Upgrade path across Odoo 17 / 18 / 19 | Validated per version; you own the source to maintain | You carry the full upgrade burden | Tied to the vendor's release cadence and support | |
| Source code ownership | You own the delivered module code | You own it — after paying to build it | Licensed; source may be obfuscated or restricted | |
| Delivery model | Build, install, train, support — 2–4 weeks | Full internal project you staff and manage | Instant download, then you integrate it alone |
No. This is a build-to-order engagement. ECOSIRE designs, develops, installs, and configures the kiosk module specifically for your menu, brand, payment provider, and hardware — it is not a pre-packaged app you download and self-install.
Typical lead time is 2–4 weeks from project kickoff, depending on menu complexity, the payment provider, and how much custom branding and upsell logic you need. We confirm a firm timeline during scoping and keep you updated at each milestone.
Every build includes a post-launch support and warranty window for bug fixes and adjustments. Because you own the source code, ECOSIRE can also validate and adapt the module when you upgrade Odoo (for example 18 to 19), and ongoing support or an enhancement retainer can be arranged.
Odoo 17, 18, and 19, on Community or Enterprise. Some kiosk-hardware and payment-terminal features are richer on Enterprise — we advise on the right edition and version fit during scoping so nothing is a surprise at install time.
Adyen, Stripe, and Mollie are supported out of the box, with the kiosk driving the card terminal and confirming settlement before finalizing the order. If you use a different regional gateway, we can scope that integration as part of the build.
No. Kiosk orders are written into the standard pos.order pipeline, so your kitchen display, receipt printing, inventory deduction, and sales analytics keep working exactly as they do today — the kiosk is an additional front end, not a parallel system.
Yes. The module is multi-company and multi-store aware using Odoo record rules, so each kiosk is scoped to its own store's menu, pricing, and payment credentials, and data stays isolated between stores.
Floor-standing Odoo self-service kiosk for QSR: touch ordering, guided upsell, card payment, and queue-number tickets. Built to order.