Why KOTs matter
A KOT is two things at once. It is the kitchen's instruction, so nothing is cooked from memory; and it is the restaurant's control, because every dish that leaves the kitchen should trace back to a KOT, and every KOT to a bill. A dish cooked without a KOT is food that may never be charged for.
Orders come in rounds: starters, then mains, then one more naan. Each round is its own KOT, so the kitchen sees only what is new. A KOT carries no prices — it is not the bill. And once a KOT has gone to the kitchen, an item on it should only be cancelled as a void with a reason, because by then something may already be on the fire.
Example
Table 6 orders two butter naan and a dal makhani at 8:10 pm — KOT 41. At 8:35 pm they add two more naan — KOT 44. At the end the bill carries everything from both KOTs; if the dal was sent back and voided, the void and its reason sit on the record too.
How Nivasik handles it
- Kitchen tickets go by round, from the counter or the waiter (captain) app, and a table can order from its own QR code.
- A line the kitchen already has can only leave the bill by a void with a reason; the count of kitchen tickets and printed bills only ever goes up.
- The same order can show on a kitchen display, item by item, by station.