POS Kitchen Display (KDS)
Live kitchen display for POS: station routing, prep status and timers on every order line
POS Kitchen Display (KDS) turns any screen behind the counter into a real-time kitchen board, no extra hardware or Enterprise module required. Order lines are routed automatically to the right prep station by product category, then walked through a strict New to Served workflow with rush priority and a live elapsed timer, so nothing gets lost during the rush.
Key Features
Configurable kitchen stations
Define one or more prep stations (Grill, Bar, Dessert...), each mapped to specific product categories and optionally restricted to specific points of sale; a station with no category acts as the catch-all default.
Automatic category-based routing
Every order line is routed to the correct station the moment the product is added, walking the product's full category tree so a station configured on a parent category still catches its sub-categories.
Strict prep-status workflow
Each line moves New to Sent to Kitchen to Preparing to Ready to Served, with every transition validated so a ticket can never skip a step or go backwards.
Rush priority + FIFO queue
Mark any line as rush so it always sorts ahead of older, non-rush tickets in both the prep queue and the ready-to-serve queue.
Automatic dispatch on payment
Lines already bound to a station are pushed to the kitchen the instant the order is paid, with a manual Send to Kitchen action available for catch-up or re-sends.
Live OWL kitchen display
A Kitchen Display button inside the POS itself opens a station-grouped board with large Start/Ready/Served buttons and a running elapsed timer, built to be read from across the kitchen.
Backend kitchen-ticket monitor
A plain list view of every active kitchen line for floor staff or managers who don't have a dedicated kitchen screen, including an order-level rolled-up kitchen status.
Station load overview
Each station shows a live count of tickets currently pending or in preparation, computed from its routed order lines.
Use Cases
Screenshots
02 Kitchen Stations List
03 Kitchen Station Form
Why Choose This Module
Because the routing, workflow and queueing rules live in a small, independently unit-tested pure-python engine, the same logic that decides which station a line belongs to also drives the live OWL display and the backend monitor, so the two views can never drift out of sync.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: 35+
- Author: Pokutsoft
- Dependencies: point_of_sale
- Support: odoo@gencbaris.com
- Update date: 2026-07-13
| 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 | 649 |
| Technical Name |
pos_kitchen_display_kds |
| License | OPL-1 |
| Website | https://pokutsoft.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