A restaurant manager should not need to wait until the end of the month to discover that sales are weakening, discounts are increasing or labor is running ahead of revenue.
A good daily sales report turns yesterday’s activity into a short management review.
It does not need to contain every number the POS can produce. The purpose is to identify the few figures and exceptions that tell the manager whether the restaurant performed normally, where something moved off plan and what needs attention today.
Quick answer: a restaurant daily sales report should show net sales, traffic or transaction count, average check, labor hours and labor cost, discounts, voids and refunds, payment or cash exceptions, major stock-outs and one short operating note. Compare the result with a meaningful target or comparable day, then assign an owner to any material exception. If you need the actual one-page format, use the Restaurant Daily Sales Report Template.
What a daily sales report should do
A useful report should help management answer five questions:
- How much did we sell?
- Where did those sales come from?
- What did we spend in labor to produce them?
- Were there unusual discounts, refunds, voids or cash differences?
- What operating issue needs follow-up?
If the report becomes a twenty-page data dump, the important signals get buried.
Start with net sales, not just gross sales
Gross sales can be useful, but managers usually need a clear view of what happened after discounts, refunds and other adjustments.
A simple report should distinguish:
- gross sales,
- discounts,
- refunds,
- net sales,
- taxes,
- service charges where applicable.
Different POS systems define these fields differently, so the restaurant should document exactly what each number means and use the same definition every day.
Compare sales with a meaningful benchmark
A sales number without context is hard to interpret.
Compare daily sales with one or more useful references:
- budget or target,
- same weekday last week,
- same weekday in a comparable recent period,
- rolling four-week average,
- break-even pace.
For example, $4,800 in Tuesday sales may look acceptable until you see that recent Tuesdays averaged $6,100.
The important question becomes: what changed?
Review sales by daypart
Total daily sales can hide very different performance across breakfast, lunch, afternoon and dinner.
A restaurant may finish only 3% below target while lunch is actually down 18% and dinner is significantly above plan.
Daypart analysis helps management connect sales to:
- staffing,
- opening hours,
- promotions,
- weather or local events,
- delivery demand,
- customer traffic patterns.
It also makes labor decisions more precise.
Track sales by channel
Many restaurants now receive revenue from several channels:
- dine-in,
- takeaway,
- direct online ordering,
- third-party delivery,
- catering,
- other local channels.
Two days with the same total sales can have very different economics if one is mostly dine-in and the other depends heavily on delivery commissions and packaging.
Channel mix should therefore be visible where it materially affects profit and operations.
Average check helps explain whether sales changed because of traffic or spending
Average check is usually calculated as:
Average check = Sales ÷ Number of checks
Illustrative example:
- Net sales: $6,000
- Checks: 300
$6,000 ÷ 300 = $20 average check
If sales fall, compare average check with guest or transaction count.
If average check remains stable but check count falls, the issue may be traffic.
If traffic is stable but average check falls, the issue may be menu mix, discounting or lower add-on sales.
Guest count is different from check count
For dine-in operations, one check may represent several guests.
If the POS captures guest count reliably, review both.
Guest count helps explain:
- table utilization,
- average spend per guest,
- staffing needs,
- sales volume by daypart.
If guest counts are entered inconsistently, do not build important decisions on a number the team does not trust.
Review menu-category sales
Category sales can reveal changes in customer behavior before they are obvious at total-sales level.
Useful categories might include:
- starters,
- mains,
- beverages,
- desserts,
- combos,
- delivery bundles.
If beverage sales suddenly fall while guest count is normal, the manager may need to investigate availability, upselling or service execution.
Track the top-selling items
A short list of top-selling menu items is useful for operations because it affects:
- prep requirements,
- inventory demand,
- production capacity,
- future purchasing.
It also helps connect sales reporting with menu item profitability.
A high-volume item deserves more management attention than a low-volume item even when both have similar recipe-cost percentages.
Discounts need their own line
Discounts reduce revenue immediately.
Managers should review:
- total discount value,
- discount percentage of sales,
- discount reason,
- employee or manager who applied it where appropriate,
- unusual changes from normal levels.
A promotion may explain a higher discount rate. Unexplained growth in manual discounts deserves follow-up.
Voids should be reviewed as exceptions
A void is not automatically a control problem.
Orders are entered incorrectly. Customers change their minds. Items become unavailable.
But repeated or unusual void patterns can reveal:
- training issues,
- menu-entry errors,
- stock availability problems,
- service breakdowns,
- control weaknesses.
Review the exceptions rather than treating every void as suspicious.
Refunds deserve separate attention
Refunds can indicate a different operating issue from voids.
Look for:
- reason for refund,
- channel,
- payment method,
- menu item,
- whether the same issue repeats.
If delivery refunds rise because of missing items, the problem may sit in packing and dispatch rather than customer service.
Compare payment methods
A daily report should reconcile the major payment categories used by the restaurant.
These may include:
- cash,
- credit and debit cards,
- mobile wallets,
- delivery-platform settlements,
- other local payment methods.
The totals should connect with the end-of-day close and reconciliation process.
See our restaurant cash control and end-of-day reconciliation guide for the broader procedure.
Show cash over or short clearly
Do not hide cash differences inside a long report.
A simple daily line should show:
- expected cash,
- actual cash,
- difference,
- explanation if known.
Small differences may occur. Repeated differences from the same shift, register or pattern need investigation.
Add labor hours and labor cost
Sales performance becomes more useful when it is reviewed with labor.
A daily management report can include:
- scheduled labor hours,
- actual labor hours,
- labor cost,
- labor cost percentage,
- sales per labor hour.
One useful productivity measure is:
Sales per labor hour = Net sales ÷ Total labor hours
If you are building this measure, use our Restaurant Labor Productivity guide for a deeper explanation.
Do not judge labor percentage without the sales context
A slow day can create a high labor percentage even when the team followed the schedule reasonably well.
A very busy day can create a low labor percentage while the restaurant is actually understaffed and damaging service.
Daily labor review should consider:
- sales level,
- guest count,
- daypart demand,
- service quality,
- overtime,
- staffing decisions made during the shift.
Track overtime before payroll closes
Daily reporting is useful because it catches overtime while management can still act.
If an employee is already close to the weekly overtime threshold, the manager may have time to adjust upcoming shifts.
Waiting until payroll closes turns a controllable scheduling issue into a historical explanation.
Include delivery performance where it matters
For delivery-heavy restaurants, the daily report can include:
- delivery sales,
- number of delivery orders,
- average delivery check,
- refunds,
- cancellations,
- commission or fee estimate where available.
This helps management understand whether delivery growth is improving total economics or simply increasing low-margin volume.
Track stock-outs that affected sales
Sales reports often explain what customers bought but not what they could not buy.
Record significant stock-outs such as:
- high-volume proteins,
- popular beverages,
- core menu items,
- packaging that prevents delivery sales.
If a major item was unavailable for three hours, a weak sales result may be partly an inventory problem.
This connects daily sales review with purchasing and inventory control.
Add one short operations note
A useful daily report should include context the numbers cannot capture.
Examples:
- heavy rain reduced walk-in traffic,
- large local event increased dinner demand,
- one fryer was unavailable for two hours,
- delivery platform had an outage,
- large group booking drove unusually high sales.
One short note can make future comparisons much more useful.
A simple restaurant daily sales report structure
| Metric | Today | Target / Reference | Variance |
|---|---|---|---|
| Net sales | $6,200 | $6,500 | -$300 |
| Checks | 305 | 320 | -15 |
| Average check | $20.33 | $20.31 | +$0.02 |
| Labor cost % | 28.5% | 27.0% | +1.5 pts |
| Discounts | $186 | $130 | +$56 |
| Cash variance | -$7 | $0 | -$7 |
The figures above are illustrative.
This format allows the manager to see the exceptions quickly.
Use variance, not just totals
Managers should not have to mentally compare every number with last week or the target.
Show the difference directly.
For example:
Sales variance = Actual sales − Target sales
And where percentage is useful:
Sales variance % = (Actual sales − Target sales) ÷ Target sales × 100
Illustrative example:
- Actual sales: $5,700
- Target sales: $6,000
($5,700 − $6,000) ÷ $6,000 × 100 = -5%
The manager can immediately see the size of the gap.
Separate operating exceptions from normal variation
Every day will not match the target exactly.
Do not turn small differences into unnecessary investigations.
Set simple thresholds for attention.
For example, management may decide to review when:
- sales are materially below the expected range,
- labor percentage is unusually high,
- cash variance exceeds tolerance,
- discount or void activity is significantly above normal,
- a major menu item was unavailable,
- delivery refunds increase sharply.
The exact thresholds should fit the restaurant’s size and normal volatility.
Connect daily sales with break-even pace
A daily sales target becomes more meaningful when it relates to the restaurant’s cost structure.
If monthly break-even sales are $90,000, management can translate that into a weekly or daily reference based on the normal day-of-week sales mix.
Use our Restaurant Break-Even Point guide to build the underlying calculation.
Do not use equal daily targets if demand is not equal
Dividing a monthly target by 30 can be useful as a rough reference, but it may not match real restaurant patterns.
If Friday and Saturday normally produce twice the sales of Monday, daily targets should reflect that pattern.
A weighted target makes the report more operationally realistic.
Compare actual sales with forecast where possible
Forecasting can improve daily staffing and prep decisions.
If the restaurant expected $7,500 and generated $6,100, ask why.
If it expected $5,000 and generated $7,200, ask whether:
- staffing was sufficient,
- prep levels handled the demand,
- stock-outs occurred,
- service times suffered.
Strong sales can expose operating weaknesses just as easily as weak sales.
Use the report in a ten-minute management review
The daily report should not become another administrative burden.
A short review can follow this sequence:
- Check net sales versus target.
- Check daypart and channel mix.
- Review checks, guests and average check.
- Review labor and productivity.
- Review discounts, voids and refunds.
- Confirm payment and cash exceptions.
- Review major stock-outs or operating incidents.
- Assign follow-up actions.
The point is to move from data to action quickly.
Keep the report consistent
Do not change the format every few days.
A consistent daily structure makes trends easier to see.
Managers learn where to look. Owners can compare days faster. New managers can understand expectations more easily.
Add new metrics only when they lead to a useful decision.
Do not overload the report with every POS metric
Modern systems can produce hundreds of fields.
That does not mean the daily management report needs all of them.
Keep detail available for investigation, but keep the daily summary focused.
A strong report usually combines:
- sales,
- traffic or transactions,
- average check,
- labor,
- discounts and exceptions,
- cash or payment control,
- one or two operational notes.
Use weekly review for trends and daily review for exceptions
Daily data is excellent for catching immediate issues.
Weekly review is better for identifying patterns.
For example:
- one high-discount day may be a promotion,
- five high-discount days may indicate a control problem.
One weak Monday may be weather-related.
Four weak Mondays may suggest the opening hours, staffing or promotion strategy needs attention.
A daily report should create accountability
The report is most valuable when each important exception has an owner.
Examples:
- kitchen manager investigates stock-out,
- floor manager reviews unusual voids,
- general manager adjusts labor schedule,
- owner reviews delivery economics.
If the same exception appears for a week and nobody owns it, reporting has become observation rather than management.
Build one exception table for the morning review
The most useful daily report makes exceptions visible without forcing the manager to scan every line. Add a short table that shows the measure, expected range, actual result, likely explanation and owner.
| Measure | Reference | Actual | Exception | Owner |
|---|---|---|---|---|
| Net sales | $6,500 | $5,900 | Lunch traffic weak | GM |
| Labor cost % | 27% | 30% | Sales miss + late close | Scheduling manager |
| Discounts | $130 | $240 | Manual discount spike | Floor manager |
The figures above are illustrative.
Use a daily sales bridge to explain the change
When sales move materially, break the result into traffic and spend before guessing at the cause. Check transaction or guest count, average check, channel mix, discounts and stock-outs.
If traffic is down but average check is stable, the problem is different from a day when traffic is stable but average check falls. That distinction tells management whether to investigate demand, menu mix, promotion or service execution.
Compare labor hours with the sales variance
A sales miss becomes more expensive when labor does not adjust. Track actual labor hours beside actual sales and compare both with forecast.
Labor-hours variance = Actual labor hours − Planned labor hours
If sales are 10% below forecast while labor hours finish 5% above plan, the report should flag the combination rather than showing the two numbers in separate sections.
Record stock-outs with lost-sales context
A stock-out line should include the item, approximate start time, end time or resolution, and whether it materially affected a high-volume menu item. This helps explain why an otherwise normal traffic day produced weaker sales.
Create a one-page daily manager report
| Section | Core fields |
|---|---|
| Sales | Gross, discounts, refunds, net sales |
| Traffic | Checks, guests, average check |
| Mix | Daypart, channel, top categories/items |
| Labor | Hours, cost %, sales per labor hour, overtime risk |
| Controls | Voids, refunds, discounts, cash variance |
| Operations | Stock-outs, equipment issues, unusual events |
| Actions | Exception, owner, due date |
Daily sales report checklist
- Net sales use a consistent definition.
- Actual sales are compared with a meaningful target or comparable day.
- Daypart and channel mix are visible.
- Traffic and average check are reviewed together.
- Labor hours and labor percentage are reviewed with sales context.
- Discounts, voids and refunds are shown separately.
- Cash and payment exceptions are reconciled.
- Major stock-outs and operating incidents are noted.
- Only material exceptions are escalated.
- Every important exception has an owner.
Restaurant daily sales report FAQ
What should be included in a restaurant daily sales report?
At minimum: net sales, traffic or transactions, average check, labor, discounts and refunds, payment or cash exceptions, major stock-outs and a short operations note.
Should a daily sales report include labor cost?
Yes. Reviewing labor beside sales helps managers see whether staffing moved with demand instead of waiting until payroll or month-end.
What should managers compare daily sales against?
Use a meaningful reference such as budget, forecast, same weekday, a rolling comparable-day average or break-even pace.
How long should the daily review take?
The summary should be focused enough for a short management review. Detailed POS data can remain available for investigation when an exception appears.
The goal is faster decisions, not more reporting
A restaurant daily sales report should tell management what changed, why it may have changed and what needs action.
It should not be a duplicate of the POS dashboard.
The best daily report combines financial and operational context so the manager can see whether sales, labor, discounts, payments and service conditions are moving together.
When the same structure is reviewed every day, small problems become visible earlier and month-end results become less surprising.
Use the free daily report template
For a one-day close review, use the Restaurant Daily Sales Report Template. It keeps sales, labor, discounts, refunds, cash variance and manager notes on one page without saving data.
Use the completed daily figures to check labor cost or, for a full-period operating view, calculate profit margin from the same sales base.
Labor Cost Percentage Calculator → Profit Margin Calculator →
Operational note: The examples and formulas in this guide are illustrative. Report definitions should be aligned with your POS, accounting practices, local tax treatment and internal management controls.