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). Optional welcome step for guest order types when you configure them on the POS.
• Guest UX (non-combo): tapping a dish opens a detail screen — description_sale, price, variant picker, customer note, and add-ons from pos_optional_product_ids (qty per upsell, variant if the add-on has variants). Add-to-cart respects a sensible max line count aligned with submit rules.
• Guest UX (combo): full-screen combo builder (same constraints as POS: steps, max per group, optional attribute lines); live total estimate from the server for configured combos.
• Prices on the guest phone: list and cart amounts follow the POS setting Tax Display (Tax-Included vs Tax-Excluded, same as Odoo POS pricing); the opened bill view still reflects posted order lines from Odoo.
• 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.

1. 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).
2. Guest lands on the table URL: they browse by category or search, open detail for à-la-carte dishes (note, variants, upsells) or combo for bundle menus, review the cart (including optional swap to another dish in the same POS category), peek at the bill, then submit a round — that creates or extends the table’s draft POS order and a new batch record for audit.
3. 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.
4. 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.
5. 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.
6. Close the loop: POS settlement stays standard Odoo POS; managers use Smart restaurant menus for batches, feedback, and QR reprints.