Kitchen Display System

KDS in restaurant

One of the modules of the Ordering Stack system is KDS - Kitchen Display System. It is a PWA application that can be run on any touchscreen device. The KDS application aims to support work in the kitchen by transferring orders in an electronic form. On the KDS screen, kitchen workers can see exactly what needs to be prepared for each order. They can also change the status of orders, including marking them as started or completed. The Ordering Stack system allows for the configuration of many KDS screens within one kitchen, so that individual devices show orders for various roles involved in the preparation of orders. In this way, the entire cooking process can be reflected.
An example would be a setup for a burger and fries restaurant. We have 3 roles here:
  1. grill
  2. fries
  3. burgers completition (topping)
  4. order delivery (delivery)
When an order comes in, consisting of a burger, fries, and a drink, the cooking process is as follows:
  1. The new order (grill items only) appears on the grill screen, status: NOT STARTED
  2. The grillman starts grilling the meat for the order and marks it as started on the screen.
    At the same time, this order appears on the screen by the fryer (only items to be made on the fryer). STATUS: NOT STARTED
  3. When the employee starts cooking the fries, he marks the order as started.
  4. The KDS sandwich picking order appears when the grillman starts working, you can see its status.
  5. On the KDS ordering screen, our order appears only when the grill and french fries stand for the end of the order (both of them must finish)

It can be seen in the picture below showing 4 KDS screens in the order fulfillment process: burger kitchen process with kds

It is only one of the many possibilities of KDS configuration within the Ordering Stack.


Technical requirements

The only technical requirement for the KDS screen is the ability to run a web application on a touch screen device connected to the Internet. It can be a tablet with the Android or iOS operating system. Additionally, a launched KDS instance requires the definition of 3 parameters:
  1. tenant id (organization)
  2. venue id (resturant)
  3. optionally specifying a configuration name, e.g. grill, topping or whatever
All Ordering Stack components, including KDS, are based on the idea of ​​pushing data. This means that the KDS application listens for new events after its launch and as soon as they occur, they are handled immediately. In practice, this means that immediately after adding a new order, it will appear on KDS.

Get In Touch

Have any questions or remarks? Need some KDS consultation?

Your Message was sent successfully

Your Message was not sent successfully