Restaurant software Dubai: choosing tools that fit the city
Software written for another city usually breaks in the same three places here. This is what to test before you sign anything.
Home / Blog / Restaurant inventory management: the routine, not the software
Most kitchens buy software for this before they have a habit for it, and the software then measures a habit that does not exist.
Agha Shah Zaman · Co-founder, Get Menu · 2 September 2026
Restaurant inventory management is usually sold as a purchase. It works better as a habit. A kitchen that counts eight items every Sunday at the same hour, by the same person, learns more in a month than a kitchen that buys a system and fills it in when someone remembers. This article is about building that habit first, then adding the part of the job that software genuinely does better than a person.
Ask a chef what inventory means and you get purchasing: what came in the door, what it cost, what is left on the shelf. Ask a manager on a Friday night and you get something else entirely: can we still sell this dish for the next two hours.
Both matter. The second one has a customer attached to it, so it is the one that costs you money tonight. Most kitchens tackle the first one first, get tired of it, and never reach the second. Doing it the other way around is easier and pays sooner.
A full stocktake of every item in a restaurant is a two-hour job that gets done twice and then quietly stops. Build a short list instead.
Put on it the things that are expensive, the things that move fast, and the things that disappear without anyone noticing. For most kitchens that is meat and seafood, cheese, oil, bottled drinks, and whichever two or three items make up most of your sales. Eight lines is a good target. If a line has never told you anything useful in two months, take it off.
Consumption in the country is well measured even where individual kitchens are not. GASTAT's Food Security Statistics for 2024 put per capita consumption at 52 kg of rice, 46.9 kg of poultry meat and 235 table eggs a year. Those are national averages, not your kitchen. Your own numbers only exist if you write them down.
The routine fails on details, not on principle.
Pick a time when the kitchen is closed and nobody is in a hurry. Give the job to one named person with a named substitute, not to whoever is around. Use the same sheet and the same order of items every week, because the value is in comparing this week to last week, and two different sheets cannot be compared.
Ten minutes, once a week, done properly, beats an hour once a quarter.
A count on its own is a number. It becomes useful when you put it beside what you sold.
You bought twenty of something, you sold fourteen, and four are on the shelf. The missing two are the interesting part. They went somewhere: a spoiled portion, a staff meal, a remake after a complaint, a mistake at the door. You will not identify them from the sheet, but you will know the size of the problem, and that tells you whether it is worth chasing.
Waste at national level has been measured here and is moving. The General Food Security Authority reported the combined food loss and waste index falling from 33.1% to 27.9%, with the waste part down to 15.8% from 18.8% and the loss part to 12.1% from 14.2%. Those numbers move because somebody measured them. The same applies at the size of one kitchen.
Here is the part a person should never do by hand: knowing whether a dish can still be sold right now.
In Get Menu, counts per item fall as orders come in. Options carry counts of their own, so running out of one sauce does not take the whole dish off the page. Sold out flips itself at zero with no one watching, so a customer never orders something the kitchen cannot cook. Low-stock alerts reach you before it becomes a problem. Cancel an order and the stock comes back. A movement history shows where every unit went.
That half runs off the orders themselves, which means it stays accurate on a Friday night without anybody touching a screen.
"We deliberately did not build ingredient counting. A kitchen that cannot say how many portions are left tonight is not rescued by a system that knows how much flour it owns." — Agha Shah Zaman, co-founder of Get Menu
It does not hold recipes, does not deduct ingredients from a dish, and does not manage purchase orders or supplier invoices. If you need food cost calculated from a recipe card, that is a different kind of software and you should buy it separately.
What it does is keep the sellable count honest, and connect it to the ordering page your customers are actually looking at.
The count is not a feature on its own. It lives inside the ordering side of the business.
Your menu sits on your own address on getmenu.ae, included from the first day, with 12 page layouts and item names that can be written in Arabic as well as English. Upload the whole menu from a spreadsheet rather than typing it. Every line is priced again from your live menu at checkout. When an order lands, a confirmation goes to the customer, a ticket to your managers' group, and a dispatch link with the GPS pin to whoever is delivering. Indoors, a code is generated for every table. Invoices carrying your tax registration number download as a PDF, and a sales dashboard shows what sold by day and by item, which is the other half of every count you take.
Payment is cash or a card machine at the door, with no online payments and no card details held anywhere.
Write eight items on one sheet. Count them at closing. Do it again next Sunday and put the two sheets side by side. Switch on stock counts for your five best sellers so the page stops selling what you ran out of. That is the whole first month.
For more depth, inventory management software covers waste, inventory tracking covers keeping a system accurate, and restaurant software inventory covers which kind to buy first. You get fifteen days to try the ordering side with no card asked for.
Once a week for a short list of high-value and fast-moving items, at a fixed hour, by a named person. A full count every quarter is enough for everything else.
Loss happens before the food reaches the customer, in transport, storage and preparation. Waste happens at the end, on the plate or in the bin. A kitchen can act on both, but they have different causes.
No. It counts sellable portions of the items on your menu, not the ingredients inside them. Recipe costing is a separate kind of software.
Yes. The count falls as orders arrive and the item shows as sold out at zero, without anybody remembering to do it.
They can, and it is worth it. If one sauce runs out, only that choice disappears and the dish keeps selling with the other choices.
Software written for another city usually breaks in the same three places here. This is what to test before you sign anything.
Most billing complaints are really about one thing: the paperwork does not match what the kitchen actually sold. Here is what to check before buying anything.
A plain look at where Odoo sits in a restaurant, and what a kitchen still has to solve after the counter software is chosen.
Fifteen days with everything switched on. No card, no commission, ever.
Questions from other owners are answered in the community.