The restaurant operating system
Every sale
counts itself
Ring up a flat white and the beans, the milk and the cup come off stock at the quantities the recipe says. HostOS costs every dish from live ingredient prices, and names the one you are selling below cost before the week is out.
- Alert rules, all arithmetic
- 7
- Roles, enforced server-side
- 4
- Figures the AI invents
- 0
Alert rules, all arithmetic
Roles, enforced server-side
Figures the AI invents
Today · Bole
HostOS
Sales today
18.4k
ETB · 42 dishes
Gross margin
61%
from live unit costs
Needs attention
4
3 stock, 1 margin
Stock items
26
6 below reorder
- Espresso beans2 days
- Oat milk6 days
- Croissants3 days
- Whole milk8 days
- Takeaway cups12 days
- Sugar21 days
What it does
Three loops, running under service
Stock, recipes, sales, staff and pay in one system — with an assistant that only answers from your own numbers.
Stock that follows the recipe
Selling a dish deducts its ingredients. Restocks, waste and corrections are each logged as their own kind of movement, so on-hand is a record rather than a recollection.
- Ingredients deducted per dish sold
- Waste, restock and correction kept apart
- Days of stock projected from real sales velocity
Warnings that are arithmetic
Alerts are calculated from your own rows every time the page opens. Nothing is written by a model, so a warning can always be traced back to the figures behind it.
- Stockout risk from 14 days of consumption
- Recurring waste flagged past 15% over a month
- Dishes sold at a loss, or on a thin margin
An assistant that only knows you
Ask which dish has the worst margin, or what sold today. It answers from your own inventory, recipes and sales, and shows the records it used to get there.
- Grounded in your own records, nothing else
- Sources attached to every answer
- Says so plainly when the data cannot tell
Designed for people standing up, one hand free, mid service.
It will tell you a dish is selling below what it costs to make, and name the ingredient responsible.
Next