Restaurant billing and KOT software
that the kitchen can read.

A bill is read once, by one person, at the end. A kitchen order ticket is read under time pressure, in heat, by someone holding something else. It is the highest-frequency document in the building and the one most restaurants think about least.

Most KOT problems are formatting problems. Modifiers printed in the same weight as the item, so "no onion" reads as decoration. Table numbers at the bottom where they are cut off. Two stations receiving the same ticket, so an item is made twice, or neither station receiving it, so it is made never.

Omega routes each line to the station responsible for it and prints the ticket so the thing that changes the dish is the thing that stands out. Items that belong to no station raise a configuration warning rather than silently vanishing, which is the failure that costs a cover.

In most restaurants the largest unexplained variance is not theft from the till, which is difficult, but discounts and post-fire voids, which are easy and look legitimate. A void applied after the food was made is functionally identical to giving it away.

Omega requires a reason on discount and records the staff member on every void, and reports both by staff member rather than only in aggregate. The intent is not surveillance. It is that a manager can answer the question "why was margin down last month" with something more useful than a shrug.