Odoo 19 POS Smart — Restaurant Self-Order & Kitchen (F-056)
by POS Master Team http://posodoo.com
Odoo
$ 352.80
In-App Purchases| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Point of Sale (point_of_sale) • Restaurant (pos_restaurant) • Website (website) • Inventory (stock) • Invoicing (account) |
| Lines of code | 8379 |
| Technical Name |
pos_smart_restaurant |
| License | OPL-1 |
| Website | http://posodoo.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Point of Sale (point_of_sale) • Restaurant (pos_restaurant) • Website (website) • Inventory (stock) • Invoicing (account) |
| Lines of code | 8379 |
| Technical Name |
pos_smart_restaurant |
| License | OPL-1 |
| Website | http://posodoo.com |
POS Smart • F-056
Restaurant self-order & kitchen foundation
What you get: guests order from a table QR (or staff-only mode), payments are gated by policy, the web kitchen sees batches with timers, the web runner delivers and prints table or per-batch bills, the web cashier verifies payment before release, and guest feedback (stars + message) is stored in Odoo — built for busy restaurants, beach bars, and small chains.
Restaurant /
pos_restaurant
website public route
Batch + audit
1. What this module helps you do
Plain language for owners and IT buyers — no Odoo jargon required to understand the promise.
- Table digital ordering: put a QR on each table so guests browse your menu and submit rounds from their phone (or disable self-order and keep a classic staff-only flow).
- Control when the kitchen cooks: in pay-first venues, money or cashier approval can sit before food prep via batches and cashier actions — fewer “unpaid kitchen fires”.
- Three web boards + POS: dedicated browser screens for kitchen (line states, timers, overload hints), cashier (verify / release / proofs), and runner (ready-to-serve lines, KPI timestamps, print bills).
- Guest voice: optional star rating and text feedback tied to the visit, visible in the back office for quality control.
- Per-restaurant rules: each POS configuration picks its own mode (self-order vs staff-led), PIN requirement, and whether Odoo’s native preparation sync is used — good for multi-site brands.
2. How operations run (end-to-end)
Typical self-order + pay-before-kitchen path; your pos.config may shorten or skip steps.
- Open session & table: waiter opens the table in POS as usual; each table has a secret QR token (printed from the manager wizard or copied from the table form).
- Guest lands on the table URL: they add items, see a running bill, and submit a round — that creates or extends the table’s draft POS order and a new batch record for audit.
- Payment gate: depending on policy, the guest marks paid (with optional proof), or only staff marks payment — until the cashier verifies and releases to kitchen, batches stay out of the cook queue you defined.
- Kitchen board: lines move through your smart states (e.g. new → cooking → ready) with timers and session-wide quantity hints so the brigade sees pressure at a glance.
- Runner board: staff sees ready lines by floor, taps Served to log handoff for KPIs, and can open Customer bills to print the whole table or a single batch slip for the guest.
- Close the loop: POS settlement stays standard Odoo POS; managers use Smart restaurant menus for batches, feedback, and QR reprints.
3. Value for your business
- Faster table turns: guests order without waiting for a runner to return; kitchen sees structured waves instead of verbal chaos.
- Less revenue leakage: configurable pay-before-kitchen and cashier verification align service with your cash discipline.
- Better coordination: separate large touch targets for kitchen, cashier, and runner roles — no shared POS login fights during rush hour.
- Measurable service: line-level timestamps (e.g. kitchen done vs runner served) support later KPI dashboards and staff coaching.
- Audit trail: batches and many actions ride on
mail.thread-style visibility so disputes have a paper trail.
4. Main technical features (for implementers)
- Models include
pos.smart.restaurant.batch,pos.smart.restaurant.feedback, and extendedpos.order/pos.order.linewith smart kitchen state fields. - Public guest entry:
/pos/smart/table/<token>with rate limits and optional session PIN (seedoc/BUSINESS_SPEC.md). - Standalone JSON + OWL UIs for guest cart, kitchen, cashier, and runner; assets load with
web.assets_frontend. - POS session still holds the commercial order; web boards use dashboard tokens issued from POS configuration.
5. First-time setup
- Install the module; enable Smart restaurant on each POS configuration that should participate.
- Use Restaurant → Floors → Tables to copy each table’s public token and build the QR (or the manager Print table QR wizard).
- Open the printed kitchen / cashier / runner URLs on fixed tablets or wall PCs — each URL is scoped to one POS session token.
- POS Manager menus: Smart restaurant → Batches / Guest feedback / Print table QR.
- Detailed bilingual steps:
README.mdanddoc/USER_GUIDE.md; architecture indoc/TECHNICAL_DESIGN.md.
6. Tiếng Việt (tóm tắt)
Module giúp nhà hàng bán qua QR bàn, kiểm soát nhả bếp theo batch/thu ngân, có màn web bếp–thu ngân–runner và góp ý khách. Quy trình vận hành và chính sách tiền/bảo mật được mô tả đầy đủ trong doc/USER_GUIDE.md và doc/BUSINESS_SPEC.md.
Implementation note
Do not install on the same database as pos_retail (POS Smart catalog rule).
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module