Restaurant POS Live

The kitchen store

Units, locations, ingredients, recipes with yield loss, an append-only stock ledger, and consumption on every KOT — so the food that was used is a cost the day carries.

The store behind the kitchen is a ledger. Every unit has its conversions; every ingredient has a location and a last purchase price; every recipe has its lines and its yield loss; and every KOT that fires consumes the recipe from the store, once.

What is kept

What arrives

Goods received from a supplier go into the store against the order, and the supplier's bill is matched in the books against what arrived and what was agreed before it is owed.

Into the books

The cost of food is what was used, not what was bought. The month's consumption is the cost of sales; what sits on the shelf is stock; and a bad month for deliveries no longer looks like a bad month for the kitchen.

The two reports an owner manages the kitchen by

Recipe cost against menu price, dish by dish; and consumption against what the restaurant sold — the variance that says where food is going that the bills do not.

More on Restaurant POS

The restaurant POSTables across the top, the menu below, the open order down the right. Punch, fire the KOT, settle at the counter or send it to the room. KOTs and the kitchenA ticket per station, a modification the kitchen sees as a reprint, and a KOT the kitchen can hold — with the store drawn down on every fire. Tables, stewards and the floorThe table belongs to somebody. Steward-wise sales are answerable because the captain on the table is a fact, not the login on the till. Charge to the roomThe bill goes to the guest's folio in the same second, as a restaurant charge with its own tax — after the guest's name and room are matched. The bill and its GSTA numbered GST bill per outlet with HSN codes per line, the slab per dish, and service charge that is taxable because the law says so. Tenders and reversalsA tender is controlled — cash, card, UPI, on account, to the room, complimentary — and a bill that was wrong is reversed, not deleted. Cashier shifts and the outlet day endA shift opens with a float and closes with a count; the day end closes every open table, reads the tenders, and refuses to close a day still in the future. An order arrives from somewhere elseZomato, Swiggy, the outlet's own online menu — an order posted as JSON lands as a ticket, once, with unmapped items refused by name. The menu, and a price that knows what time it isCategories, dishes, variants, a price per channel, and a schedule — happy hour is a window on the menu, not a second menu. A restaurant without a hotelThe POS sells on its own — an outlet that is a customer in its own right, with no booking chart, no room, and every till, bill and day end working.