KOT Updates
The Kitchen Order Ticket (KOT) system helps manage and track orders in the kitchen through the grubKDS. It plays a key role in the Kitchen Display System (KDS) by assigning orders, monitoring their progress, and updating their status at different kitchen stations. These tables store detailed order information, including item details and status history, providing real-time insights that improve workflow, efficiency, and visibility across kitchen stations.
In grubCenter’s station routing setup, a single order can create one or multiple KOTs. Since all KOT data comes from the grubKDS, it’s essential for the system to be running properly to ensure accurate and timely order tracking.
Tables
| TYPE | CODE | DESCRIPTION |
|---|---|---|
| KotDetail | gdata_kot_detail | Stores base-KOT information, including order details and station assignments. |
| KotLine | gdata_kot_line | Stores item-level details, including KOT items and their modifiers. |
| KotUpdateHistory | gdata_kot_update_history | Maintains a history of KOT status updates with timestamps for tracking order progression. |
KotDetail
This table stores the base information for each Kitchen Order Ticket. It includes order details and station assignments which help in directing the KOTs to the appropriate station.
| FIELD NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
| id | VARCHAR(255) | Unique identifier for the KOT. This serves as the primary key for the table. |
| tags | VARCHAR(255) | Optional tags or labels associated with the KOT for categorization or filtering purposes. |
| orderid | VARCHAR(255) | Identifier for the order linked to the KOT. This column is indexed to allow quick lookups. |
| displayid | VARCHAR(255) | Order Display ID/ External ID. |
| ordertime | TIMESTAMP | Timestamp indicating when the order was placed. |
| partnerid | VARCHAR(255) | Identifier for the partner associated with the order. |
| brandid | VARCHAR(255) | Identifier for the brand under which the order is placed. |
| brandname | VARCHAR(500) | Name of the brand associated with the order. |
| locationid | VARCHAR(255) | Identifier for the physical location/kitchen where the order is processed. |
| locationname | VARCHAR(500) | Name of the location. |
| stationid | VARCHAR(255) | Identifier for the kitchen station where the KOT is assigned. |
| stationname | VARCHAR(500) | Name of the kitchen station. |
| sourceid | VARCHAR(255) | Identifier representing the source of the order (e.g: uber-eats-api). |
| sourcename | VARCHAR(500) | Descriptive name of the order source. (eg: UberEats). |
KotLine
This table contains item-level details for each KOT. It records the individual menu items, their modifiers, and other specifics related to the items included in an KOT. A KOT can have single or multiple items based on your station routing setup in GrubCenter.
FIELD NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
id | VARCHAR(255) | Unique identifier for the KOT line item. This is the primary key for the table. |
tags | VARCHAR(255) | Optional tags or labels to further classify or provide metadata for the line item. |
kot_id | VARCHAR(255) | Foreign key that references the KOT in gdata_kot_detail. This associates the item with a specific KOT. |
menuItemid | VARCHAR(255) | Identifier for the menu item. This can be associated to thegdata_order_line table |
modifierid | VARCHAR(255) | Identifier for any modifier applied to the menu item (e.g., extra cheese, no onions). This can be associated to the `gdata_order_line table |
menuitemgroupid | VARCHAR(255) | Identifier for grouping a menu item with its modifiers. For example, a burger (menu item) with modifiers such as cheddar cheese, tomato, and a chicken patty will share the same menuItemGroupId. |
itemname | TEXT | Menu Item/Modifier name. |
quantity | DOUBLE PRECISION | Menu Item/Modifier quantity. |
type | VARCHAR(15) | Specify the item type: whether it's a menu item or a modifier.
|
KotUpdateHistory
This table tracks the history of status updates for each KOT. Each record logs the status change along with a timestamp, providing a clear progression of the KOT’s lifecycle. This is crucial for monitoring the workflow and performance of the kitchen stations.
| FIELD NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
| id | VARCHAR(255) | Unique identifier for the KOT. This serves as the primary key for the table. |
| tags | VARCHAR(255) | Optional tags or labels associated with the KOT for categorization or filtering purposes. |
| kot_id | VARCHAR(255) | Foreign key that references the KOT in gdata_kot_detail. This associates the item with a specific KOT. |
| orderid | VARCHAR(255) | Identifier for the order linked to the KOT. This column is indexed to allow quick lookups. |
| partnerid | VARCHAR(255) | Identifier for the partner associated with the order. |
| stationid | VARCHAR(255) | Identifier for the kitchen station where the KOT is assigned. |
| status | VARCHAR(255) | Current status of the KOT (Refer to the KOT status list). |
| timestamp | TIMESTAMP | The date and time when the status update occurred. |
KOT Statuses
A KOT can have several statuses during its lifecycle, including:
- RECEIVED: The KOT has been received at the station.
- STARTED: Preparation of the KOT has begun.
- COMPLETED: The KOT has been prepared at the station.
- CANCELLED: The KOT has been cancelled.
- ON_HOLD: Order preparation is temporarily on hold (e.g., due to issues with kitchen equipment).
- RESUMED: Preparation of an on-hold order has resumed.
Updated about 2 months ago