Duration: 25:29
Part 1 — Analytical Summary 🚀
Title: Streamline dine-in, delivery, and takeaway using Presets in POS for restaurants
Duration: 25:29
💼 Context
An Odoo product specialist delivers a theory-plus-live-demo session unveiling the new Presets feature in Odoo 19 Point of Sale (POS) for restaurants. The talk tackles a common operational headache: juggling dine-in, takeaway, and delivery orders with different pricing, taxes, timing, and identification requirements—often leading to errors and chaos. The promise: configure once, automate everywhere, and keep front-of-house, kitchen, and bar perfectly in sync.
🧠 Core ideas & innovations
At the heart of the release are configurable Presets (e.g., Dine-In, Takeout, Delivery) that attach operational logic to each order type. Restaurants can create as many presets as needed—per Point of Sale, with a default applied automatically—and flip among them mid-order without losing context. Each preset can enforce a Pricelist (e.g., 10% discount for takeout), map a Fiscal Position for tax automation (e.g., different VAT for dine-in vs takeaway, as seen in Belgium and other countries), and define an independent Time Schedule with slot duration and capacity. This enables pre-scheduled orders minutes or days in advance—even while the POS session is closed—and clearly flags full time slots while still allowing staff to override when needed.
Operational identification is streamlined: presets can require a name for takeout or a full address for delivery. These identifiers appear consistently across POS tickets, the Preparation Display, and receipts, helping teams match items to customers and pickup times with fewer mistakes. The Preparation Display consolidates kitchen and bar production queues, highlighting the order type, customer, due time, and waiting duration. Larger venues can split multiple displays by product category or by POS to route items to the right station.
The live demo shows how prices and taxes adapt instantly as staff switch from dine-in to takeout or delivery, with self-ordering screens reflecting the same logic (e.g., a burger at €20 when Dine-In, €18 with a 10% Takeout discount). Staff can also override the automatically applied Pricelist for exceptional cases. Orders can be edited easily: change times with a tap, attach additions to an existing “open active order,” and accept split payments (cash/card). The Active Orders view centralizes control: filter by preset (only see Takeout, or only Delivery), spot future-dated orders, and finalize payments at pickup. In the backend, Odoo keeps an audit trail—storing which Preset, Pricelist, and Fiscal Position were used—so managers can investigate anomalies or training issues later.
⚙️ Impact & takeaways
With Presets, Odoo 19 compresses complex restaurant rules into a few clear configurations that drive real-time automation across POS, self-ordering, and the kitchen. Teams gain:
- Faster order flow with fewer errors, as pricing, tax, and timing rules apply automatically by Preset.
- Better capacity management via time slots and per-preset schedules, including future-dated orders.
- Clearer communication: names/addresses travel through POS, receipts, and Preparation Displays, reducing pickup mistakes.
- Flexibility when reality intrudes—override slots, change presets mid-order, or swap Pricelists when needed.
- Strong compliance and traceability thanks to retained order metadata on presets, taxes, and pricing.
💬 Notable limitations and tips from Q&A
- Order-capacity limits are per order, not by product workload (e.g., 15 sandwiches vs 5x3). Not supported yet.
- No visual “late” alert timer in the Preparation Display; a multi-step workflow can be used as a workaround.
- Removing a preset mid-session requires a reload and isn’t recommended operationally.
- You can disable name capture and rely on codes, but the presenter recommends names for real-world clarity.
Overall, Odoo 19 POS Presets bring a cohesive, low-friction approach to running mixed-mode restaurants—where the difference between smooth service and chaos often rests on small automations done right. 🧠⚙️
Part 2 — Viewpoint: Odoo Perspective
Disclaimer: AI-generated creative perspective inspired by Odoo’s vision.
When we design features like Presets, the goal isn’t to add options; it’s to remove friction. Restaurants juggle many tiny rules—price differences, taxes, schedules, and identification—and the system should shoulder that complexity. If a waiter can switch order modes with one tap and everything else “just works,” we’ve done our job.
Integration is our leverage. POS, self-ordering, and kitchen displays share the same configuration and data, so everyone—front-of-house, kitchen, bar—operates with the same truth. As always, community feedback will guide what comes next: finer scheduling controls, richer kitchen workflows, and even simpler setup so more teams benefit from this level of automation.
Part 3 — Viewpoint: Competitors (SAP / Microsoft / Others)
Disclaimer: AI-generated fictional commentary. Not an official corporate statement.
Odoo’s Presets are a smart UX abstraction for SMB and mid-market restaurants, compressing pricing, tax, and scheduling into a simple operational model. The integrated self-ordering and preparation display story is compelling for fast-moving venues where configuration depth and speed of change matter.
The challenges will surface at scale: multi-country compliance nuances, enterprise-grade capacity planning (e.g., workload-based slot limits), and advanced SLA monitoring in kitchens. Differentiation versus larger suites will hinge on governance, audit, and enterprise reporting breadth. That said, Odoo’s pace and product cohesion make it an increasingly credible option for multi-site operators who value usability and rapid iteration.
Disclaimer: This article contains AI-generated summaries and fictionalized commentaries for illustrative purposes. Viewpoints labeled as "Odoo Perspective" or "Competitors" are simulated and do not represent any real statements or positions. All product names and trademarks belong to their respective owners.