Why a weekly review beats a monthly surprise
If you own a restaurant but are not at the counter every day, or you run more than one outlet, a fixed weekly review of five reports will tell you most of what you need: what is selling, where money is leaking, when you need more staff, whether food cost is drifting, and whether the money in the bank matches the bills. Daily figures jump around too much to judge, and monthly figures arrive too late to act on.
This article sets out a weekly routine, explains what to look for in each report and suggests the action each one should lead to. It assumes your bills already come from a billing system. If your stock counts are not yet reliable, read our restaurant inventory basics first, because food cost figures are only as good as the counts behind them.
Set up the routine: same day, same reports, same order
Pick one slot each week, for example Monday morning before lunch service, and review the previous Monday to Sunday. Ask the manager to join, and the head cook for the food cost part. Keep a one-page log of what you decided, so next week starts by checking whether last week's actions happened.
Compare each figure with the previous week and with the same week a month earlier. Festivals, exams, cricket matches, weddings and weather all move restaurant sales, so note anything unusual in the log before drawing conclusions.
| Report | Question it answers | Typical action |
|---|---|---|
| Item and category sales | What sells, and what is just taking up menu space? | Reprice, rework or remove items |
| Voids, cancellations and discounts | Is money leaving without a good reason? | Tighten permissions, talk to the shift concerned |
| Sales by hour and weekday | When are we busy, and when are we empty? | Adjust staff rota, prep timing and offers |
| Food cost percentage | Is the kitchen using stock as expected? | Check portions, purchase rates and wastage |
| Payment mode reconciliation | Did every rupee billed reach us? | Chase gaps with the bank, card provider or delivery app |
Sales by item and category: what earns its place on the menu
Open the item-wise sales report and sort by quantity, then by sales value. The top of the list is usually no surprise. The bottom is where decisions hide: dishes that sold three plates all week but need their own ingredients, prep time and space on the menu card.
Category-wise performance shows the bigger shape: veg against non-veg, starters against mains, beverages against food, dine-in against delivery. A falling beverage share, for instance, often means staff have stopped suggesting drinks rather than that guests stopped wanting them.
Sales alone can mislead. Combine sales with each dish's cost from your recipe costing and sort items into four simple groups.
| Sales level | High margin | Low margin |
|---|---|---|
| Sells well | Protect: keep quality and placement | Review: adjust price or portion carefully |
| Sells poorly | Promote: better placement or staff suggestion | Question: rework or remove |
Change only a few items at a time and watch the next two or three weeks, so you know which change made the difference.
Voids, cancellations and discounts: where money quietly leaks
This is the report most owners skip and the one that most often explains a gap. Look at every item cancelled after a KOT was sent, every bill changed after printing, every reprint and every discount, together with who did it and when.
- Concentration: one login accounts for far more cancellations or discounts than others on similar shifts.
- Timing: changes cluster near closing time or during the owner's usual absence.
- Reasons: the same reason, such as "guest changed mind", is used for most entries.
- After-payment edits: items removed from bills that had already been printed.
- Discounts without a named offer: manual percentage cuts rather than a coupon or set offer price.
A pattern is a reason to ask questions, not proof of wrongdoing. Often the cause is a menu problem, such as an item that keeps running out, or a training gap. If your system keeps audit logs, use them to see the full sequence of events. The rules that should govern cancellations in the first place are set out in our guide to the restaurant POS and KOT flow.
Peak hours: staffing and preparation from your own bill times
Every bill carries a time. Group the week's bills by hour and by weekday and you have a picture of when your restaurant is truly busy, which is often different from what the staff feel. Look at the number of bills and, for dine-in, the number of covers in each hour.
Use the pattern to set the staff rota, so you are not paying four waiters during a quiet 4 pm slot and running short at 9 pm. Use it for kitchen preparation too: gravies, marinated items and dough should be ready before the peak, not started during it. If your kitchen screen records preparation times, compare them with the busiest hours to see where service slows.
Quiet hours are an opportunity. A happy hours price on selected items, set in the billing software, can bring in custom at a slow time without permanent discounting.
If your software does not show sales by hour directly, export the week's bills to a spreadsheet and count them by hour. It takes a few minutes and is worth doing at least once a month.
Food cost percentage: one number, calculated the same way each week
Food cost percentage tells you how much of each rupee of food sales went on ingredients. The basic calculation is: (opening stock + purchases − closing stock) ÷ food sales × 100. Use sales before GST, and use stock valued at purchase cost.
Illustrative example with made-up round numbers: opening food stock ₹50,000, purchases ₹1,20,000, closing stock ₹45,000. Food used is ₹1,25,000. If food sales before GST were ₹3,50,000, food cost is about 35.7%. These figures are not a benchmark.
There is no single right percentage for every restaurant. It depends on your menu, prices and style of service. What matters is your own trend and how far the actual figure sits from what your recipe costing says it should be. A sudden rise usually points to one of three things: purchase rates went up, portions grew, or wastage and staff meals were not recorded. The detailed variance check for individual ingredients belongs in your inventory routine, not in this weekly meeting.
Calculate beverages and bar separately from food if you sell them, and keep packaging as its own line, so one category does not hide changes in another.
Payment mode reconciliation: does the bank match the bills?
Your settlement report shows how the week's bills were paid. This weekly check confirms that the money arrived where it should. Shift-level cash counting at the counter is covered in our quick service billing tips; here the owner looks at the whole week.
| Payment mode | Figure from the system | Where to verify | Common reason for a gap |
|---|---|---|---|
| Cash | Cash sales minus recorded cash expenses | Bank deposit slips and petty cash book | Expenses paid from the drawer without entry |
| UPI | UPI total for the week | Bank or merchant statement | Pending payments marked as paid at the counter |
| Card | Card total for the week | Card provider settlement statement | Charges deducted, or a batch not settled |
| Delivery app orders | Orders entered as app orders | The app's payout statement | Orders cooked but not entered, or commissions and deductions |
| Credit / house accounts | Credit bills raised | Customer ledger | Regulars or corporate accounts not followed up |
Any gap should have a named owner and a date by which it will be explained. Small unexplained gaps that repeat every week matter more than one large one-off.
Turning the review into three actions for the coming week
A review that ends with "keep an eye on it" changes nothing. Close each meeting with no more than three actions, each with a person and a deadline, and start next week's meeting by checking them.
- Example action: remove two low-selling, low-margin dishes from the evening menu and watch whether total sales hold.
- Example action: restrict manual discounts to the manager login from Wednesday.
- Example action: move one server from the afternoon slot to the 8 pm to 10 pm peak on Fridays and Saturdays.
If you run more than one outlet, compare the same report across outlets. A dish that sells well in one branch and poorly in another, or a discount pattern that appears in only one outlet, is easier to understand side by side. The same weekly habit works in other trades too; our article on reports for garment and footwear shop owners applies it to retail stock.
What MATROP's restaurant reports cover, and what to ask in a demo
The reports and dashboard in our restaurant software include daily sales, item-wise sales, category-wise performance, the cashier report, the GST report, the settlement report, expense against profit, and outlet-wise reports for multi-branch setups. Audit logs record user actions, and a cloud version gives access from anywhere with consolidated reporting across outlets. An optional mobile app gives managers a dashboard and sales view when they are away from the restaurant.
In a demo, ask to see exactly how cancelled items, edited bills and discounts appear, and how you would get sales by hour, using sample bills from your own menu. Reports are only as good as the entries behind them: if bills are still handwritten or payment modes are not recorded, fix billing first and the reports will follow. To discuss your outlets with us, use our contact page or visit the office in Ranchi.
Questions people ask
If an owner has only ten minutes a week, which report should come first?
Start with voids, cancellations and discounts, because that is where money can leave without anyone noticing. Then glance at total sales against the same week last month.
Should food cost percentage include beverages and packaging?
Calculate food, beverages and packaging separately if you can, because they behave differently. Mixing them hides problems; for example, a rise in takeaway packaging can make the kitchen look worse than it is.
How can we spot discount misuse without accusing honest staff?
Look for patterns over several weeks, such as one login with many more discounts or cancellations at the same time of day, and discuss the pattern with the manager first. Tightening permissions so only managers can discount usually solves it without confrontation.
Can an owner see reports for several outlets together?
Yes, if the outlets share a cloud-based system. MATROP's restaurant software offers outlet-wise reports with consolidated reporting for multi-outlet setups.
