v 17.0 Third Party 1205
Download for v 17.0 Deploy on Odoo.sh
Odoo Online
On Premise
Odoo Apps Dependencies Restaurant (pos_restaurant)
Point of Sale (point_of_sale)
Discuss (mail)
Inventory (stock)
Invoicing (account)
Lines of code 1912
Technical Name pos_kitchen_screen_odoo
Versions 17.0 15.0 16.0
You bought this module and need support? Click here!
Odoo Online
On Premise
Odoo Apps Dependencies Restaurant (pos_restaurant)
Point of Sale (point_of_sale)
Discuss (mail)
Inventory (stock)
Invoicing (account)
Lines of code 1912
Technical Name pos_kitchen_screen_odoo
Versions 17.0 15.0 16.0

POS Kitchen Screen

Streamline Your Restaurant Operations With The POS Kitchen Screen Designed Exclusively for Odoo 17 Community.

Key Highlights

Real-time Orders:

The POS Kitchen Screen is a feature in Odoo 16 that is specifically designed for restaurants and other food-related businesses. With this feature, restaurant staff can easily view and manage orders in real-time

Efficient Order Management:

Streamline kitchen operations by creating and managing orders seamlessly through the dedicated kitchen screen, enhancing workflow efficiency.

Comprehensive Order Details:

View detailed information for each order, including order time, table name, cashier name, order internal reference, and floor details, providing a holistic overview.

Error Prevention Mechanism:

Safeguard against errors by restricting payment processing until order completion and preventing the addition of food items to completed orders, ensuring accuracy in transactions.

User-Friendly Interface:

Enjoy a user-friendly design that allows easy navigation and order creation, enhancing the overall user experience and promoting efficiency in kitchen and POS operations.

Multi-Order Capability:

Create multiple orders for the same table effortlessly by utilizing the 'Order' button in the top-right corner, providing flexibility and convenience in managing customer requests.

First set the access right for the user as 'Kitchen Cook'

Create a kitchen screen from the POS

Configure the POS session and associated category to seamlessly integrate kitchen orders into the dedicated kitchen screen for efficient order processing.To access the detailed information pertaining to kitchen orders, kindly utilize the "Kitchen Screen" button located in the image above.

This is the initial view of the kitchen order interface, displayed when no orders have been created for the kitchen.

We can effortlessly generate kitchen orders by utilizing the designated 'Order' button displayed in the image below.

After creating the order in the POS session it will come under the cooking stage.Here you can gain comprehensive insights into each order, including Order Time, Table name, Cashier name, Order Internal Reference, and Floor details, and Order Count of the 'Cooking' stage for a complete overview of your kitchen operations.

After cccepting the Order in the cooking stage it will come under this "Ready" stage. when the food was ready we can simply click the DONE button, and it will automatically goto the Completed stage. Here also you can see all the details of your order.

All the Completed foods are shown in the 'Completed' Stage. Experience a detailed view of your Orders, showcasing essential information such as Order Time, Table name, Cashier name, Order Internal Reference, and Floor details, providing comprehensive oversight.

Payment processing is enabled only upon order completion, ensuring a structured workflow that aligns with efficient kitchen operations.Attempting a payment before completing kitchen orders results in an error, promoting a streamlined process and ensuring all food items are prepared before finalizing transactions.

Once an order is completed, any attempt to add additional food items to the kitchen is restricted, reinforcing accuracy in order fulfillment and kitchen management.Adding any food item after order completion prompts an error

Effortlessly create additional orders for the same table by clicking the 'Order' button located in the top-right corner.

  • One of the main advantages of the POS Kitchen Screen is that it provides a clear and organized display of all active orders, making it easy for kitchen staff to see what needs to be done next.
  • The POS Kitchen Screen is a valuable tool for any restaurant or food-related business that wants to streamline their operations and improve their customer service.
Version|Released on:10th Jan 2024

Initial Commit for POS Kitchen Screen

Related Products

Our Services


Odoo Customization


Odoo Implementation


Odoo Support


Hire Odoo Developer


Odoo Integration


Odoo Migration


Odoo Consultancy


Odoo Implementation


Odoo Licensing Consultancy

Our Industries


Easily procure and sell your products


Easy configuration and convivial experience


A platform for educational management


Plan, track and schedule your operations

E-commerce & Website

Mobile friendly, awe-inspiring product pages

Service Management

Keep track of services and invoice


Run your bar or restaurant methodically

Hotel Management

An all-inclusive hotel management application


Need Help?

Got questions or need help? Get in touch.


Say hi to us on WhatsApp!

+91 99456767686

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.
Please choose a rating from 1 to 5 for this module.
This module still have bug, error when try to process Return in Odoo POS backend
on 5/13/24, 6:49 AM
Traceback (most recent call last):
  File "/odoo17/odoo17-server/odoo/http.py", line 1765, in _serve_db
    return service_model.retrying(self._serve_ir_http, self.env)
  File "/odoo17/odoo17-server/odoo/service/model.py", line 133, in retrying
    result = func()
  File "/odoo17/odoo17-server/odoo/http.py", line 1792, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "/odoo17/odoo17-server/odoo/http.py", line 1996, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "/odoo17/odoo17-server/addons/website/models/ir_http.py", line 235, in _dispatch
    response = super()._dispatch(endpoint)
  File "/odoo17/odoo17-server/odoo/addons/base/models/ir_http.py", line 222, in _dispatch
    result = endpoint(**request.params)
  File "/odoo17/odoo17-server/odoo/http.py", line 722, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "/odoo17/odoo17-server/addons/web/controllers/dataset.py", line 28, in call_button
    action = self._call_kw(model, method, args, kwargs)
  File "/odoo17/odoo17-server/addons/web/controllers/dataset.py", line 20, in _call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "/odoo17/odoo17-server/odoo/api.py", line 468, in call_kw
    result = _call_kw_multi(method, model, args, kwargs)
  File "/odoo17/odoo17-server/odoo/api.py", line 453, in _call_kw_multi
    result = method(recs, *args, **kwargs)
  File "/odoo17/odoo17-server/addons/point_of_sale/models/pos_order.py", line 1066, in refund
    'res_id': self._refund().ids[0],
  File "/odoo17/odoo17-server/addons/point_of_sale/models/pos_order.py", line 1050, in _refund
    refund_order = order.copy(
  File "/odoo17/odoo17-server/odoo/models.py", line 5547, in copy
    record_copy = self.create(vals)
  File "", line 2, in create
  File "/odoo17/odoo17-server/odoo/api.py", line 414, in _model_create_multi
    return create(self, [arg])
  File "/odoo17/odoo17-server/addons/pos_online_payment_self_order/models/pos_order.py", line 25, in create
    return super().create(vals_list)
  File "", line 2, in create
  File "/odoo17/odoo17-server/odoo/api.py", line 415, in _model_create_multi
    return create(self, arg)
  File "/odoo17/custom/addons/pos_kitchen_screen_odoo/models/pos_orders.py", line 77, in create
    for lin in vals_list[0]["lines"]:
TypeError: 'bool' object is not iterable

The above server error caused the following client error:
RPC_ERROR: Odoo Server Error

Re: This module still have bug, error when try to process Return in Odoo POS backend
Cybrosys Technologies
on 5/14/24, 5:31 AM Author

We regret to inform you that despite conducting a thorough test of the module along with its entire workflow, we were unable to reproduce the error you have reported. Could you please provide us with additional information to enable us to replicate the issue? You can send an email to odoo@cybrosys.com.

Excellent apps
on 2/9/24, 10:25 AM

its great apps thanks, but for a better apps, it still have minor bug, after we make payment at table 1 (for example), it still have the order that previously we already pay, please get it fixed. thanks
Henry Kurniawan
on 2/1/24, 10:29 PM

Nolito Putong
on 5/1/24, 9:21 PM

hi, this is good apps for CE version but requires fine tuning on the functionality, do you have a paid version that works fined?

Cybrosys Technologies
on 5/2/24, 5:34 AM Author

Sorry, there is no paid version. If you need any customisation, Please write to odoo@cybrosys.com

Adding item to exising order
Mohamed Sharif
on 4/28/24, 11:04 AM

hi, is it possible to allow cashier to add new item to existing order in the kitchen after it was completed. 

at the moment, if a customer request additional item, it created completely new transcation. 

Abraham Ponce
on 4/4/24, 7:05 PM

 The module has an error when using the point of sale with a tablet (for the waiter) and a PC at the same time. Orders are duplicated. Hope you can fix it.