Restaurant Daily Sales Report: What to Review

A restaurant daily sales report should explain what happened during service and what needs attention next. A revenue total alone cannot tell you whether demand changed, the menu mix shifted, or a small number of refunds affected the close. Start with consistent definitions, then connect the numbers to the service your team experienced.

Choose a business-day cut-off and make sure reports use the same timezone. A venue trading after midnight may need an operating day that differs from the calendar date. Write down which channels, outlets, and transaction statuses are included so comparisons remain useful.

Start with net sales and completed orders

Define gross sales, discounts, refunds, and net sales clearly. Check how your POS treats tax, service charges, tips, cancelled orders, and payment reversals. Different reports can use different definitions, so reconcile the report you use with the records behind it before comparing figures.

Track completed orders alongside net sales. In a hypothetical example, £3,000 in sales from 100 orders gives an average order value of £30. If the next comparable service produces the same sales from 120 orders, average order value is £25. The total is unchanged, but the pattern of demand is different.

Separate channels and service periods

Review dine-in, collection, and delivery separately where the records support it. Compare lunch with lunch rather than a full day with a half-day opening. If an outlet closed for maintenance, annotate that period before including it in a branch ranking.

A rise in delivery sales may change the mix of packaging costs and commissions, even if headline sales improve. Use channel data to identify questions about contribution and workload. Sales alone should not be presented as profit or as proof that a particular channel is performing better.

Look at discounts, refunds, and voids

Review exceptions by reason and responsible role, using appropriate access controls. A high count of voided items can reflect menu-entry mistakes, unavailable dishes, or an unclear process. Investigate with the team before interpreting it as poor performance or misconduct.

• Check unusually large discounts against the approval record.
• Separate a cancelled order from a refunded payment.
• Compare exceptions with the relevant order count.
• Record unresolved payment differences for follow-up.

For example, six voids from a very busy service may mean something different from six voids during a quiet lunch. Read counts and rates together, and check whether a menu or staffing change explains the difference.

Turn reporting into a short manager review

End the report with three notes: what changed, the likely explanation that still needs checking, and the next action. Assign an owner and a review date. A note such as “check availability of the top-selling lunch dish before tomorrow's prep” connects a number to a useful task.

Keep a daily operational view and a separate periodic review. Daily results help identify immediate issues; weekly comparisons make patterns easier to assess. Preserve notes about unusual events so your future self does not mistake a public event, closure, or promotion for a permanent change in demand.

Which metrics should a small restaurant start with?

Begin with net sales, completed orders, average order value, payment exceptions, and one measure linked to your current problem. Add further detail only when someone uses it to make a decision. A short report reviewed consistently is more useful than a large dashboard nobody trusts.