Restaurants
Three ways a restaurant loses money without noticing
By the Zimozo team · · 5 min read
Most restaurants do not lose money in one big moment. They lose it in small, quiet ways that never look wrong on any single day. Here are the three we see most often, and how to close each one.
1. You are guessing your food cost
A menu price is usually set when the restaurant opens and rarely revisited. Then milk goes up, a portion drifts a little larger, and the margin on a best-seller quietly disappears.
The fix: cost every item from its recipe, down to the gram — including the cup, the lid and the straw. Build sub-recipes (a sauce, a syrup, a curry base) once and use them everywhere, so a change in one ingredient's price flows through to every dish that uses it. Then check margin per dish, not just total sales.
2. Delivery orders live on another tablet
When delivery orders arrive on a separate device, someone has to read each one and type it into the POS before the kitchen can start. At peak hours that queue slows the kitchen, items get missed, and orders can go out at dine-in prices while the delivery app still takes its cut.
The fix: bring delivery orders straight into the POS, each with its own price list, so the kitchen ticket prints automatically and delivery sales land in the same end-of-day report as everything else.
3. The drawer never quite balances
An unpaid table, an item quietly removed after it was cooked, a shift closed early — and no way to tell afterwards which it was.
The fix: make the system enforce the rules, not trust. The day should not be able to close while a table is unpaid. Removing a cooked item should need permission and a typed reason, logged with a name and value. And listing voids by cashier, biggest first, lets a pattern surface on its own.
Close all three in one place
EzDine, Zimozo's restaurant product, was built around exactly these three gaps: recipe costing to the gram, delivery orders inside the POS, and a day that cannot close on an unpaid table.