Kitchen tickets that never go missing
Turn every Point of Sale order into a reliable kitchen ticket — full item detail, station routing, change tracking, and print confirmation, without extra hardware.
Odoo Point of Sale prints a customer receipt only after payment, with no concept of a kitchen ticket. Cooks need the order the moment it is placed, formatted for production, not billing — so staff hand-write tickets, shout orders across the room, or stack several single-purpose apps that each solve only one slice: on-validation OR pre-payment OR category grouping, with truncated item text and no confirmation the kitchen ever received the order.
One server-authoritative kitchen ticket engine with a configurable trigger, real category-to-station routing, full untruncated item text, automatic dedup on reprint, and change-delta tickets when an order is modified. A print-feedback popup with retry and an always-visible Kitchen: ON/OFF badge mean staff always know a ticket really reached the kitchen.
Everything a kitchen ticket needs
Every capability below is implemented in the module.
Configurable print trigger
Choose when kitchen tickets fire: on payment validation, before payment when the order is sent, or purely on demand with the in-POS button — one setting instead of stacking three separate apps.
Category grouping or per-station tickets
Print one ticket grouped by category headers, or split into a separate ticket per kitchen station so the grill, bar, and cold station each get only their own items.
Category-to-station routing
Map product categories to named kitchen stations, each with an optional link to a native Odoo order printer, so routing decisions live in one configuration screen.
No truncation, ever
Every kitchen ticket line carries the full, untruncated product name plus per-line notes — cooks never lose modifiers or details to a 2-3 line cutoff.
Automatic reprint dedup
Reprinting an unchanged order never creates a duplicate ticket — the engine recognizes identical content and marks the existing ticket as reprinted instead.
Change-delta tickets
When a validated order is modified, a delta ticket prints only what changed, with added and cancelled lines visually distinguished so the kitchen cooks the right thing.
Void tickets on cancellation
Cancelling an order the kitchen already started prints a void ticket that clearly tells the line to stop, preventing wasted food.
Minted kitchen tokens
Every ticket gets a sequential, configurably-prefixed token (e.g. K0001) from a per-register sequence, giving cooks and expeditors a fast reference for every order.
Print confirmation, not blind printing
An on-screen popup confirms every ticket that sends and flags trouble with a Retry button, while a persistent Kitchen: ON/OFF badge in the POS navbar keeps the feature state always visible.
How it works
Set up stations
Define kitchen stations such as Grill, Bar, and Cold Station, and map product categories to each from Point of Sale > Configuration.
Configure the trigger
Pick when tickets print — on validation, before payment, or manual only — from the Kitchen Receipt settings page on each POS.
Ring up the order
Cashiers ring up items as usual; the kitchen ticket generates automatically at the configured moment, or on demand with the Kitchen button.
Kitchen gets a clean ticket
Cooks receive full-text, station-routed tickets on screen with token, table, and notes, while delta and void tickets keep every change in sync.
See it in action
From backend configuration to the live POS screen.
Every kitchen ticket ever produced, logged in the backend with kind (new/delta/void) and print-state badges, filterable and groupable by config or station.
A change-delta ticket showing exactly what was added and cancelled after an order was modified, with color-coded lines so the kitchen never cooks the wrong thing.
Kitchen stations — Grill, Bar, Cold Station — each configured with its own product categories and sort order for the ticket layout.
Route product categories to a station and optionally link it to a native Odoo order printer, all from one form.
The Kitchen Receipt settings page on every POS configuration: trigger mode, grouping, suppression, ticket header/footer, token prefix, and an inline station editor.
A persistent Kitchen: ON/OFF badge in the POS navbar plus a one-tap Print Kitchen Receipt control button — the feature state is never a mystery.
The on-screen kitchen ticket — full item names, category headers, notes, and token — with a print-feedback popup confirming success and offering Retry on failure.
Frequently asked
Does this need a special printer or POSBox?
No. The kitchen ticket renders on screen and every ticket is logged server-side; you can link a station to your existing native Odoo order printer if you already use one, but no new hardware is required.
Can I route different categories to different kitchen stations?
Yes. Configure named stations such as Grill, Bar, or Cold Station, map product categories to each, and enable one-ticket-per-station so every station prints only its own items.
What happens if a cashier changes an order after the kitchen already has it?
The app prints a delta ticket showing only the added and cancelled lines, and a void ticket if the whole order is cancelled, so the kitchen always cooks the current state of the order.
Does this work with Odoo POS Restaurant (Enterprise)?
This version targets Odoo Community Point of Sale. It reads the table name defensively when available, but restaurant floor and table features are not required to use it.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Server-authoritative kitchen tickets for Odoo Point of Sale — configurable triggers, station routing, full-text lines, change deltas, and print confirmation.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Lines of code | 848 |
| Technical Name |
cerevantix_pos_kitchen_receipt |
| License | OPL-1 |
| Website | https://cerevantix.com |
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