Five Restaurant Numbers to Check Every Week
Use real restaurant reports to review sales change, top products, order volume by hour, preparation time and refunds, then choose one clear useful action.
6 min read
On this page
In short: compare sales and orders with a like period, then check product mix, busy hours, preparation time and refunds or corrections. One number rarely explains a week. Review the set with service notes and choose one action you can measure next week.
DineHarbor's restaurant reports include sales comparison, top products, preparation time and an hourly heatmap. The Manager copilot can answer supported questions from the same operational data.
1. Sales and order count
Start with completed sales value and the number of orders for the week. Compare with the previous equivalent period and, where useful, the same weekday pattern.
Do not compare a seven day week with five open days. Note closures, holidays, weather, events, menu changes and promotions. A percentage without context can send the team towards the wrong explanation.
Look at sales and orders together. Sales can rise because more people ordered or because baskets were larger. A rough average order value is sales divided by relevant orders, but confirm how the report treats refunds, discounts, taxes and cancelled orders before using it.
DineHarbor's Sales Comparison query provides a consistent window through the branch reporting scope. Keep the chosen windows visible when sharing the number.
Action question: did the change come from traffic, basket value, price, opening time or a one off event? Write the best supported answer and what evidence would disprove it.
2. Top products and product mix
Top products show what guests actually bought. Review both quantity and sales value where available. A high selling low price side and a lower volume premium dish tell different stories.
Check whether a product rose because of a promotion, new position on the menu or availability elsewhere. A product cannot sell while marked unavailable, so stock and menu uptime are part of the result.
Do not remove every low seller immediately. Some products complete a group order, serve a dietary need or contribute well despite modest volume. Combine report data with margin and guest context.
DineHarbor's Reports API has a Top Products query. Use it to select a few products for operational review rather than turning the whole menu into a ranking contest.
Action question: which one product needs better availability, a clearer name, a recipe review or removal from a promotion?
3. Orders and revenue by hour
The hourly heatmap groups order count and revenue by weekday and branch local hour. It helps reveal when demand arrives, not only how much the week sold.
Use it for staffing, preparation and opening decisions. A rush may begin earlier than the team feels because preparation problems become visible only after the queue has built.
Compare several weeks before changing hours. One event can create a bright cell that does not repeat. Check order source too where the supported reports allow, since delivery and dine in can load the kitchen differently.
The DineHarbor heatmap excludes cancelled orders and uses the branch's time zone in the current implementation. That prevents an 8 pm order being grouped under server time elsewhere.
Action question: which single hour needs a staffing, preparation or menu availability change next week?
4. Preparation time
Preparation time connects sales with kitchen capacity. Review typical performance and slower cases rather than only an average. A handful of delayed orders can matter even when the mean looks acceptable.
DineHarbor has a Prep Time report query and a preparation forecast used by operations. The meaning depends on accurate order state updates. If staff bump tickets early or forget completion, the number reflects the input problem.
Compare similar products and channels. A table order with held courses is not the same as a quick collection. Look for station, product or time patterns before asking everyone to move faster.
Use tickets to understand the number. Was a slow order waiting for one station, held deliberately, missing an ingredient or delayed before acceptance?
Action question: what one bottleneck can the kitchen remove or measure during the next comparable service?
5. Refunds, voids and corrections
The plan's core Reports page focuses on sales, products, preparation and the heatmap. Refunds, voids and payment corrections also deserve a weekly operational check through the relevant order, POS and payment records.
Group reasons rather than reading only the total. Wrong item, unavailable product, late delivery, duplicate order and guest change point to different fixes.
Do not use corrections as a simple staff score. A person who records mistakes honestly may appear more often than someone who hides them. Look for menu and process causes, and review permissions for unusual manual activity.
Reconcile refunds with the payment provider and cash records. An order status and actual returned money must agree.
Action question: which recurring correction can be prevented through menu wording, training, stock accuracy or a permission change?
Run the review in 30 minutes
Choose a fixed weekly time and one owner. Use the same reporting window and write down the five observations before discussing explanations.
Invite one service or kitchen lead where possible. They can connect a chart to an equipment fault, event or large booking. Keep the meeting focused on process, not blame.
Use this order:
- Confirm the date range and open days.
- Read sales and order count.
- Review top products.
- Find the busiest hours.
- Review preparation and corrections.
- Choose one action, owner and measure.
Do not leave with ten vague goals. A single test, such as preparing one component before a known rush, can be evaluated next week.
Ask better questions
Instead of asking why sales are bad, ask how completed sales and orders changed versus the previous comparable week. Instead of asking what sells, ask which five products led by quantity in one branch.
Specific questions reduce accidental mixing of locations, dates and measures. State whether the figure includes tax, discounts, cancelled orders or refunds based on the report definition.
DineHarbor's Manager copilot lets authorised owners ask supported sales and operational questions in plain words. It uses controlled insight tools and asks before acting. Read the AI assistant guide for owners before relying on it for decisions.
Keep comparisons honest
Use branch local time and equivalent service periods. Separate a new location from a mature one. Record menu price changes, since higher sales value does not automatically mean more demand.
Do not publish internal figures as customer success claims without consent and evidence. Reports guide the restaurant; they are not an excuse to invent impressive statistics.
Watch the reports and growth guide to find the current screens. Export or retain records according to the business's accounting and privacy obligations.
The best weekly report is the one that changes one useful decision and lets you see whether it helped.
Keep a small, useful written decision log with the date, observation, action, owner and measure. At the next review, close the loop before choosing another change. This stops the same discussion returning every week and protects the team from reacting to one unusual service as though it were a lasting trend.
Ready to run the review on your own operation? Start the 30 day free trial with no card needed.
Questions and answers
Which restaurant report should I check first?
Start with sales and order count compared with a similar period, then use product, hour and preparation reports to understand the change.
Does DineHarbor show busy hours?
Yes. Its Reports area includes an hourly heatmap of orders and revenue in the branch's local time.
Can the Manager copilot answer report questions?
Yes. It can answer supported questions about sales and operations in plain words, using the same underlying insight queries and asking before actions.
See it in DineHarbor
About the author
Editorial team
The DineHarbor team writes this blog for restaurant owners and managers. Every article is checked against the product before it is published, so what we describe is what the software does.
All articles by DineHarbor team