Restaurant stock management system: the promise on your menu

Most writing about stock control is aimed at the storeroom. This one is aimed at the screen. Every dish your page is still offering is a promise that you will cook it, and a restaurant stock management system is really the machinery that keeps you from making a promise you cannot keep. That is worth thinking about from the customer's side, because that is where the damage happens.

What breaking the promise actually costs

Follow one order through. A customer picks the dish they came for. Ten minutes later somebody phones to say it is finished. Now three things happen at once.

The customer has to decide again, usually while doing something else. Your member of staff spends the call apologising instead of working. And whoever suggested a substitute has quietly changed the order without the customer seeing a new total, which is where arguments at the door come from. A guest who has waited 45 minutes to be told the dish is off will not order again soon.

Do that on an evening with 12 orders needing calls and you have lost the evening, not the dish.

What shops do about this, and why food is different

Retail has studied this for years and reached a sensible answer for retail.

Baymard's research on product pages found that 68% of sites do not allow users to order temporarily out-of-stock products, and that this pushes roughly 30% of determined buyers to abandon the site altogether. Their advice is to let people buy anyway and simply extend the delivery time.

That is good advice for a shirt. It is useless for dinner. You cannot back-order a plate of grilled chicken for Tuesday when the customer is hungry on Sunday. A kitchen has one honest option: stop offering what it cannot cook, at the moment it can no longer cook it, and show something else instead.

So the target for food is not a clever waiting list. It is speed. The gap between the last portion leaving and the item disappearing from the page is the whole problem.

The review you cannot buy your way out of

The other cost arrives later and lasts longer.

A customer who was let down writes about it, and there is no legitimate way to buy that back. Google's own content policy states that contributions should reflect a genuine experience, disallows reviews or ratings that have been paid for, and explicitly forbids offering incentives such as payment, discounts or free goods in exchange for posting a review.

Which means the rating your restaurant carries is built from evenings, one at a time. Asking for reviews is fine and worth doing. Get Menu asks for one automatically a while after the meal, when the customer actually knows how it went. Whether that request lands on a good memory is decided hours earlier, by whether the page told the truth about what you had.

What the system has to do, from the guest's side

Four things, and none of them should need a person.

The count for an item has to fall the moment an order is placed, not when someone gets round to it. Choices need counts of their own, because running out of one sauce should remove that choice and leave the dish selling. The item has to go to sold out on its own at zero. And a cancelled order has to put the portions back, or the number drifts away from the shelf within a fortnight.

What ours does

Counts per item fall as orders come in. Options carry counts of their own. Sold out flips itself at zero with nobody watching, so the dish greys out on the page while the kitchen is busy doing something else. Low-stock alerts reach you before it becomes a problem, which is the point at which a cook can still start another batch. Cancel an order and the stock comes back. A movement history shows where every unit went, for the evenings when the shelf and the screen disagree.

"Sold out is not a warning we show a manager. It is a change the customer sees, on the page, without anybody deciding to make it." — Tanzeel ur Rehman, co-founder of Get Menu

Selling the next thing instead

Removing a dish is only half the job. The other half is having something ready to take its place.

Upsells offer pairings, quantity ladders and spend thresholds, so a guest whose first choice has gone is shown a sensible second one rather than an empty space. Bundles let you sell a fixed group of items for one price. Coupons carry caps, exclusions and expiry dates, and discounts never stack by accident because the best one wins. A sales dashboard by day and item tells you which dishes keep running out, which is usually a purchasing decision rather than a software one.

Where the counts sit in the rest of it

The stock side is part of an ordering page, not a separate product. The menu lives on your own address on getmenu.ae, included from the first day, with 12 page layouts, and item names can be written in Arabic as well as English. Upload the whole menu from a spreadsheet instead of typing it. Every line is priced again from your live menu at checkout, so a substitution can never quietly change what somebody pays.

When an order arrives, a confirmation goes to the customer, a ticket to your managers' group, and a dispatch link carrying the GPS pin to whoever delivers it. Indoors, a code is generated for every table. Stamps and tiers bring regulars back, with the card sitting in Google Wallet. Invoices carrying your tax registration number download as a PDF.

Payment is cash or a card machine at the door. There are no online payments in the product, so nothing is charged before the food arrives.

What it is not

It does not hold recipes, deduct ingredients, or manage suppliers. It counts sellable portions of the dishes on your menu and keeps the page honest about them. If you want cost per plate from a recipe card, that is different software and you should buy it separately.

Where to start

Switch counts on for the three dishes you run out of most often. Leave the rest of the menu alone. Come back in two weeks and see whether the apology calls have stopped.

For more, inventory tracking covers keeping numbers accurate, inventory management software covers waste, and menu engineering covers which dishes deserve the space. You get 15 days to try it, with no card asked for at signup.

Frequently asked questions

Should a restaurant hide dishes that are out of stock or grey them out?

Show them as sold out rather than hiding them. A guest who cannot find a dish assumes you removed it for good, while a greyed-out line tells them to come back another day.

When does the stock count go down?

When the order is placed, so two people cannot buy the same last portion. If the order is cancelled, the portions return.

Can I be alerted before something runs out?

Yes. A low-stock alert reaches you while there is still time to cook more or change the menu, rather than after the fact.

Does this stop customers ordering something we cannot make?

Yes, for anything you have given a count. The item shows as sold out at zero without anybody remembering to do it.

Does it track ingredients as well as dishes?

No. It counts the portions you can still sell. Ingredient and recipe costing is a separate kind of software.