What it means in a restaurant
Restaurant inventory management tracks ingredients and packaged goods and links them to the menu through recipes, so that selling a dish depletes what went into it. That produces a live stock level instead of a monthly photograph, which is what makes automatic 86ing and real food-cost measurement possible.
The distinction that matters: a stock list somebody updates by hand tells you what you had. Stock connected to the POS tells you what you have.
Theoretical versus actual — the number that pays
Recipes tell you what you should have used. Counting tells you what you did. The gap is variance, and it is the single most valuable number stock control produces.
Variance has boring causes and it is worth knowing which one you have: over-portioning, waste and spoilage, theft, deliveries short of what was invoiced, prep loss, or simply a recipe that does not match what the kitchen actually cooks. You cannot address any of them until the gap is measurable.
Most operators discover the largest single cause is the last one — the recorded recipe was never what the kitchen made.
86ing across channels
The moment you run more than one ordering channel, running out becomes a data problem. A counter knows immediately. A kiosk, a QR menu, a web storefront and three delivery apps each find out whenever they next sync.
Overselling is worse than running out: a guest told at the counter picks something else, while a guest who paid on a delivery app, waited forty minutes and got refunded leaves a review. Two things fix it — availability as one number every channel reads, and an 86 that reaches the marketplaces in seconds. A five-minute sync window is five minutes of orders you cannot fill.
How to start without it collapsing
- Start with your top 20 items by cost, not all 400. Almost every attempt that fails, fails by starting with everything.
- Count the same things at the same time. Consistency beats completeness — a rough count every week is worth more than a perfect one every quarter.
- Write recipes as the kitchen actually cooks them, not as the menu describes them. Watch a service before writing them down.
- Record waste where it happens. Waste reconstructed at month end is fiction.
- Fix your receiving first. If deliveries are not checked against invoices, every downstream number inherits the error.
- Expect three months before the numbers are trustworthy. Anyone promising accuracy in week two is selling something.
Where ThaliPOS fits: the menu and packaged-goods catalog with barcodes and weight-based pricing are available to pilot restaurants; recipe depletion, auto-86, purchase orders and waste tracking are designed and on the build plan but not yet shipped. The current status in detail →