Average check is the revenue KPI that separates a traffic problem from a spend problem. When sales fall, the first question is whether fewer people came or whether each person spent less — and the answers lead to completely different actions. This article covers the calculation and its variants, how to read the number by daypart and channel, what moves it, and the ways it can mislead.
Definition and formula
Average check = total sales ÷ number of guests (also called average spend per head or revenue per cover).
The alternative — sales ÷ number of tickets or tables — is average ticket size. Both are legitimate; per-guest is more useful for menu and upselling decisions, per-ticket for party-size and table-mix decisions. Choose one as your headline and keep it consistent.
Decide whether sales are gross or net of discounts, tax and service charge. Net of tax and discounts, including service charge only if it is yours to keep, gives the cleanest number for management purposes.
Worked example
A restaurant’s week: $42,000 net sales, 1,150 guests, 520 tickets.
- Average check per guest = 42,000 ÷ 1,150 = $36.52
- Average ticket = 42,000 ÷ 520 = $80.77; average party size = 2.2
The following week: $40,600 sales, 1,160 guests. Guests are up slightly; average check is $35.00. Sales fell $1,400 and none of it is traffic — every dollar of the decline is spend per head. Look at menu mix, drink attachment, and whether a promotion changed what people ordered.
Read it by daypart and channel
A single blended average check hides most of what matters. Split it:
- By daypart. Lunch and dinner have different menus, party sizes and drinking habits. A blended number can rise simply because dinner grew as a share of the week.
- By channel. Dine-in, takeaway and delivery. Delivery orders often have a higher ticket (whole-family orders) but a lower spend per guest and, after commission, a much lower contribution.
- By server, if your POS allows it, for coaching rather than ranking.
How to interpret it
Average check should be read with covers and with gross profit per guest. Two failure modes:
- Average check rises, covers fall: prices went past what the local market accepts, or a menu change narrowed the audience.
- Average check rises, gross margin falls: guests are buying more of the low-margin items (large steaks, premium spirits) — more revenue, not necessarily more profit.
Benchmarks by segment exist (casual dining, fine dining, quick service) and vary by an order of magnitude; they are only useful for classifying your own restaurant. The decision-useful comparison is your own average check over time, by daypart, against your menu’s designed check — what a guest would spend if they ordered the way the menu is built to encourage.
What moves average check
- Menu design: placement, description, anchor pricing, the number of price points.
- Attachment rates: the share of guests adding a starter, a dessert, a second drink. Small changes in attachment move the check more than price rises do.
- Course structure and sharing plates, which change how many items a party orders.
- Server behaviour: suggesting rather than asking, describing rather than listing.
- Pricing, obviously — but price rises that lose covers do not raise sales.
- Promotions and discounts, which reduce the net check even while they increase traffic.
- Channel mix: a growing delivery share usually lowers spend per head and raises ticket size.
Practical actions
- Calculate attachment rates for starters, desserts and drinks from the POS mix. Pick the lowest one and set a service standard around it.
- Re-engineer the menu with contribution per dish in hand: promote high-contribution items, reposition or re-price high-cost popular ones.
- Review price points quarterly against ingredient inflation; small, frequent adjustments beat one large annual jump.
- Separate the delivery menu and price it for the channel’s economics.
- Test one change at a time and read the result over two to three weeks — average check is noisy day to day.
Limitations
Average check is a mean, and means hide distribution: a few large parties or a private event can move a week’s number without anything changing for typical guests. It is also a revenue KPI, not a profit KPI — a higher check built on low-margin items can lower the restaurant’s margin. And pushing it aggressively erodes retention: guests notice being upsold. Use it as a diagnostic beside covers, gross profit per guest and the repeat rate.
Related restaurant KPIs
Average check is the spend half of the revenue equation in the restaurant KPI framework; table turnover and occupancy are the traffic half. Its profit consequence shows up in gross margin, and it sets how many covers you need to reach break-even.
See average check, revenue per cover and revenue per seat next to your cost ratios. They are calculated automatically in the free Restaurant KPI Excel template. The Restaurant Performance System tells you each week whether a sales change came from guests or from spend — and what to do about it.