Short answer. Restaurant management software holds four things. The recipe sheet of each dish: its ingredients, their quantities, its cost, and so its margin. The order: taken on the floor, sent to the kitchen, billed with no retyping. Stock: deducted at each sale according to the sheet, then compared with the counted inventory. The service's figures: sales per dish, food cost, margin, till. In this page's example, the best-selling dish earns 340 dinars when the average is 472, and one week's stock gap is worth 34,650 dinars.
This page is for those who run a restaurant, a fast-food brand, a café or a delivery kitchen, and for diaspora founders opening an outlet in Algeria. The definitions come from public sources: restaurant management, menu engineering, contribution margin, shrinkage, stock-taking, food loss and waste. The menu of twelve dishes, its sales, its margins, the quantities and the purchase prices are a constructed example, with fictitious prices. The page covers neither hygiene rules and approvals, nor tax and payroll, and quotes no hardware price.
What is inside restaurant software
The figure stacks five layers; the first makes the other four possible.
The trade. Restaurant management is the profession of leading and administering the operation of a food service establishment: the floor, the kitchen, purchasing and money. The recipe sheet. That is the accented layer. For each dish: the ingredients, the quantity of each, weighed, and their current purchase price. It gives the cost of the dish, and so its margin, and says what each sale must take out of stock. The method is that of a bill of materials, see the cost of a finished product.
Orders. Taken at the table or the counter, they go to the kitchen by station and come back as a bill without being copied; the ways of ordering, kiosk, menu by code, takeaway, are described in the ordering kiosk. Stock. Purchases come in, sales go out according to the sheets, and a counted inventory says what is really left, see the stock movement journal. The till. One session per service, voids traced, see till sessions. The figures. Per dish, per hour and per service, on a dashboard.
The dishes that fill the room, and those that pay
The figure places twelve dishes by their sales and their margin.
Menu engineering. It is the design of a menu to maximise restaurant profits. It classifies each dish by two measures: its popularity, how often it is ordered relative to the other items, and its margin, the selling price less the cost of its ingredients. In the example. Twelve dishes, 5,700 sales in the month, an average margin of 472 dinars per dish sold. The two averages cut the menu into four groups.
Stars. Popular and high-margin: they are left unchanged, recipe and portion, and given a prominent place. Plowhorses. Popular, low-margin: they are kept, and made more profitable through modest adjustments. In the example there are three of them, making 44% of sales and 28% of the margin; roast chicken with fries, 910 sales, earns 340 dinars a dish. Puzzles. Rarely ordered, high-margin: a better description, a more visible position on the menu, promotion. Grilled fish earns 850 dinars and sells 150 times. Dogs. Rarely ordered, low-margin: candidates for removal, which also simplifies the kitchen and the stock. What the software does. It recalculates the margin when the price of an ingredient changes, and redraws the map every month.
«The dish that fills the room is not the one that pays the rent.»
What should have left the stock, and what did
The figure compares, for six ingredients, theoretical and real consumption over a week.
The two consumptions. Theoretical consumption is what sales should have consumed, according to the recipe sheets of the dishes sold. Real consumption is counted: opening stock, plus purchases, minus the stock counted at the end. Stock-taking is the physical verification of quantities; shrinkage, in accounting, is having fewer items in stock than the inventory list expects. In the example. 86 kg of meat should have gone out, 97 kg did: a gap of 11 kg, 24,200 dinars at purchase price. Over six ingredients, the week leaves a gap of 34,650 dinars, that is about 150,000 dinars a month.
Where the gap is. Not everywhere: meat makes 70% of the total, cheese comes next, and drinks, which are counted by the unit, hardly move. Where it comes from. Portions more generous than the sheet, trimming and cooking losses not provided for, products thrown away, dishes given away or sent out without a ticket, receiving errors. Food loss and waste is food that is discarded or lost uneaten: it gets recorded, like a sale. What is done. The portions of the two drifting ingredients are weighed, the sheet is corrected if it was wrong, losses are recorded, and the count is repeated the following week. Purchasing. Quantities to order follow consumption, see replenishment.
«The gap is not everywhere: it is on meat and cheese. That is where you weigh.»
What a sale sets off
The figure follows a sale in six steps, from the order to the service's figures.
The order. Entered on a phone or a tablet, with the table and the remarks: no onion, well done, to take away. The kitchen ticket. Each station receives what concerns it, on a screen or a printer; the floor sees when the dish is ready. The bill. It comes out of the order, per table or per person, with nothing copied.
The deduction. That is the accented step: at the moment of the sale, stock goes down by what the sheet provides for, 220 grams of meat for a grill if that is what the sheet says. Without a connection. Order taking and the till carry on when the connection drops, and synchronise afterwards. Loyalty. The till recognises the person and credits their points, see the loyalty programme. The service's figures. At closing: sales per dish, food cost, margin, till counted.
Eight weeks, starting by weighing
Eight weeks in the example; the sheets are made in the kitchen.
Scoping. One week: your menu, your suppliers, your services, your current notebook and till. Recipe sheets. That is the real work: each dish is prepared as usual and weighed, ingredient by ingredient. It is often then that you discover two people in the kitchen do not make the same dish. Purchase prices. They are updated at each receipt: the cost of the dish follows.
The first inventory. A full count, one evening, gives the starting point; after that, a weekly count on the ingredients that weigh the most. Go-live. A dry-run service with the team, then a real service. What the software does not do. It does not cook, does not replace the person who runs the kitchen, and does not decide prices: it shows what each dish costs and where the goods go. The durations are those of a constructed example.
From the counter to several outlets
The figure gives five kinds of outlet, and what the software brings to each.
- What you receive: recipe sheets with cost and margin per dish; order taking on the floor and kitchen tickets; the bill with no retyping; stock deducted at each sale; the inventory and gaps per ingredient; the till per service; figures per dish and per hour.
- What the restaurant avoids: the menu whose margins nobody knows, meat going faster than sales, tickets lost between the floor and the kitchen, dishes sent out without a ticket, accounts done from memory.
- What is measured: sales per dish and per hour; food cost; margin per dish; gap between theoretical and real consumption, per ingredient; recorded losses; average ticket; time for dishes to come out.
- What Symloop does: scoping, setting up the recipe sheets, order taking and kitchen screens, stock and purchasing, gaps, the till, the dashboard, in Arabic and in French.
At the counter. Everything is decided at the peak hour: the order has to be entered in a few taps. At the table. The floor plan, orders per table, the split bill. The café. Many small tickets: the till has to be fast, and stock is counted by the unit.
Delivery. Orders come from the counter, the phone and the applications: they are gathered on a single screen in the kitchen. Several outlets. Recipe sheets are shared, and food costs are compared from one outlet to another; for a brand that is expanding, see creating a franchise. Ready-made or custom. Restaurant till software exists, and suits taking payment. Custom work is justified when you need recipe sheets linked to stock, gaps per ingredient, several outlets, an ordering application under your name, or a link with your management system.
- What software to manage a restaurant?
- Software that links four things: the recipe sheets of the dishes, order taking between the floor and the kitchen, stock deducted at each sale, and the service's till. A till alone takes payment; it does not say what is left.
- How do you calculate the cost of a dish?
- By adding up the cost of each ingredient on the recipe sheet: the quantity used multiplied by its purchase price. The dish's margin is its selling price minus that cost.
- How do you know which dishes to keep on the menu?
- By placing each dish by its sales and its margin. Popular high-margin dishes are promoted; popular low-margin ones are reworked; rarely ordered low-margin ones are candidates for removal.
- Why is the restaurant full when nothing is left?
- Often for two reasons turnover hides: the best-selling dishes are the ones that earn the least, and part of the goods leaves the stock without being sold.
- How do you track a restaurant's stock?
- Each sale takes out of stock what the dish's sheet provides for; a counted inventory gives real consumption; the difference between the two is the gap, ingredient by ingredient.
- Where do stock gaps come from?
- Portions more generous than the sheet, losses not provided for, products thrown away, dishes sent out without a ticket, receiving errors. The gap says where to look, not whom to blame.
- Are tablets needed to take orders?
- A phone is enough. What matters is that the order goes to the kitchen and comes back as a bill without being copied.
- Does the software work without the internet?
- Yes, for the service: order taking and the till carry on offline and synchronise afterwards.
- How long does it take to make the recipe sheets?
- That is the longest part: each dish is prepared and weighed. In the example, three weeks for a full menu, starting with the best-selling dishes.
- Does the software suit several restaurants?
- Yes: sheets are shared, each outlet has its own stock and till, and food costs are compared from one outlet to another.