Capture every guest count without slowing down service
A guided prompt captures covers the moment a dine-in table opens — with configurable min/max rules, a manager override for exceptions, and a fast cover/turnover report your kitchen and finance teams can trust.
The problem
Odoo's restaurant POS treats guest count as an optional field, so busy waiters routinely skip it. The result is incomplete cover data and turnover, staffing, and per-cover reports that can't be trusted.
The solution
Guest count becomes a guided first step of opening a table, not a blocking error. Configurable min/max rules keep the data clean, a manager can override with a reason when needed, and covers flow straight into the receipt and a dedicated cover/turnover report.
Everything covers need, nothing they don't
Every capability below is implemented in the module.
Mandatory guest count, dine-in only
Turn on enforcement per POS configuration. Takeaway and direct-sale orders are never blocked — only orders opened on a table.
Guided prompt, not a blocking error
The guest-count keypad appears the moment a required table opens, as a natural first step — never a validation error mid-order.
Configurable minimum and maximum party size
Set a minimum guest count and an optional maximum per POS configuration to catch obvious data errors before they reach a report.
Manager override with reason capture
A POS manager can bypass the min/max rule on the spot for genuine exceptions, while the reason is captured on the order.
Full override audit on the order
Every override records who overrode it and why, visible on the backend order form alongside the amount charged per guest.
Guest count on the customer receipt
The party size prints on the receipt, keeping it visible and useful long after the order is placed.
Fast cover / turnover analytics
A dedicated pivot and graph report breaks down covers, order count, and amount per guest by table and floor.
Detailed cover analysis list
Drill into every confirmed order with its guests, total, amount per guest, and whether the count was overridden.
Per-configuration, multi-location ready
Rules live on each POS configuration and the report groups by configuration, so multi-location and franchise setups stay consistent.
How it works
Configure the rule
Turn on Require Guest Count for a restaurant POS, set a minimum and optional maximum, and allow manager override.
Open a table
The guest-count keypad appears immediately as the first step, before any items are added to the order.
Validate or override
A count outside the configured range prompts a manager to override with a reason, or the cashier to re-enter it.
Track and report
The count prints on the receipt and feeds the Cover Analysis pivot, graph, and list report in the backend.
Frequently asked
No sales fog. If your question isn't here, email us and we'll answer it the same way.
No. The requirement only applies to dine-in orders opened on a table. Takeaway and direct-sale orders are never blocked.
Buy it on the Odoo App Store
Purchase, download and install directly from the official Odoo Apps Store — you'll always get the latest supported build.
POS Restaurant Require Guest Count
Guest count made mandatory on dine-in orders through a guided prompt, with configurable party-size limits, manager override and reason capture, receipt printing and cover analytics.
Buy on Odoo App Store