The formula
Average check = Total net sales / Number of guests
Why the formula works this way: the denominator decides what the number means. Divide by guests and you learn what one person is worth, which is the number menu pricing, server performance and daypart comparisons all depend on. Divide by checks instead and you learn what one bill is worth, which mixes party size into the answer: a room full of four-tops looks richer than a room full of couples even if every guest spends the same. Both figures are shown above, but the headline is per guest, because that is the one you can act on.
One supporting figure shows why operators chase this metric:
Value of +$1 on the check = Number of guests x $1, for the same period. A dollar added by an appetizer shared, a drink upgrade or a dessert is a dollar multiplied by every cover you already serve, with no extra marketing spent to get them through the door.
How to use it, with an example
- Pick one period, a week is best, and take sales and guest count from that exact period.
- Use net sales, before tax and tips. Including tax inflates the check with money that was never yours.
- Count guests, meaning individual covers. Your POS guest count, or checks multiplied by average party size, both work if you are consistent.
- Compare like with like: lunch against lunch, dinner against dinner. A blended day hides two different businesses.
- Read the plus $1 and plus $2 lines before reaching for discounts. Growing the check is usually cheaper than growing traffic.
Worked example: A casual dining restaurant takes $18,450 in net sales in a week and serves 615 guests across 402 checks. The average check is $18,450 / 615 = $30.00 per guest, squarely in the casual dining range. The average per check is $45.90, because each check covers about 1.53 guests. If servers lift the check by just $1 a guest, the same week is worth $615 more, and $2 a guest is $1,230 more, from guests who were already sitting down. The calculator above is prefilled with these same numbers.
The guest count is where this metric usually breaks, and it breaks quietly. When the till is a full restaurant system, covers are counted at the table and sales per guest is a standard report by daypart and server. That is the reporting layer described in Odoo for Restaurants: orders taken in the Odoo POS module carry the cover count with them, so average check by lunch and dinner is read off the week, not reconstructed from memory.
Common mistakes
- Dividing by checks and calling it average check. Per-check value is a real metric, but it rises and falls with party size. A Saturday of large groups will fake an improvement that no server earned.
- Including tax and tips in sales. Both pass through your hands without being revenue. A check average built on gross receipts overstates guest spending by the tax rate and more.
- Blending dayparts. Lunch guests and dinner guests behave like different markets. A falling blended average often just means lunch got busier, which is good news disguised as bad.
- Chasing the check with price rises alone. Guests notice headline prices. The durable gains come from attachment: starters, sides, beverages and desserts, which is menu engineering work. The restaurant menu costing guide shows how dish-level margins decide what is worth pushing.
- Ignoring table time while pushing the check. A bigger check that takes twenty minutes longer to serve can cost covers at peak. Check average and table turns have to be read together, which is why restaurant table management tips matter alongside this number.
- Comparing against the wrong concept. A $16 average is strong for fast casual and weak for upscale casual. Benchmark against your own format and your own last quarter first, published ranges second.
FAQs
What is a good average check for a restaurant?
It depends entirely on format. Published industry ranges put quick-service around $8 to $12 per guest, fast casual around $12 to $20, casual dining around $20 to $40, and fine dining from $50 to well over $150. The useful test is your own trend: a check that grows slowly with your menu prices is healthy, whatever the band.
What is the difference between average check and average spend per cover?
Nothing in practice. Cover is the industry word for one guest served, so average spend per cover and average check per guest are the same division. Average per transaction is the different one, because a transaction can cover any number of guests.
Should tips and tax be included in average check?
No. The standard measure uses net sales, because tax is collected for the state and tips belong to staff. Some POS reports show a gross figure including both; if you compare periods, just make sure you never mix the two definitions.
How can I increase my average check without raising prices?
Attachment. One more drink, a shared starter, a dessert for the table. Train servers on two or three specific suggestions rather than a script for everything, put high-margin items where the eye lands on the menu, and use combos that bundle a side or drink at a small saving over separate prices.
How often should I track average check?
Weekly at minimum, split by lunch and dinner. Daily is better during menu changes or server training pushes, because you can see within days whether attachment is actually improving or just being talked about.
Why did my average check fall while sales rose?
Usually because guest count rose faster, often at lunch or through a channel with smaller orders, such as takeout. That is mix, not failure. Read the check by daypart and channel before concluding anything about guest behaviour.
