Average Per Cover Calculator
In restaurant language, every guest is a cover, and the average per cover is the one number that says how much each guest actually spends. It is not revenue per table and not revenue per check: it is total revenue divided by the guests who sat down, which makes it the cleanest read on pricing, menu mix, and upselling you can take from a day’s trading.
The Average Per Cover Calculator below works two ways. Use totals mode for the daily habit, one revenue figure and one guest count, or switch to itemized mode and paste each cover’s spend as a list, the shape a point of sale export actually arrives in. Either way you get the average with its breakdown shown, and the worked example on this page, $4,800 across 160 guests for $30.00 per cover, is already loaded into the tool.
Use net sales (before tax and tip) for a clean number, and apply the same definition every period so trends stay comparable.
Quick Answer
Key takeaways
- A cover is one guest, not one table and not one check. Every figure on this page divides by guests served.
- Use net sales before tax and tips, and the same definition every period, or the trend line lies.
- Compare like with like: lunch against lunch, Friday against Friday. Dayparts have different natural averages.
- A rising average per cover with flat covers means pricing and upselling are working. A falling one means each guest is spending less, even if the room is busier.
- Quick Answer
- How to use the average per cover calculator
- The per-cover formula and what counts as revenue
- Worked example: one day, 160 guests, $4,800
- What a per-cover number actually tells you
- Raising the average without raising prices
- What competing calculators miss
- Frequently asked questions
- Add This Calculator to Your Website
- References
How to use the average per cover calculator
Pick a mode, enter the figures for one period, and press Calculate Average. Totals mode is the daily habit: one revenue number, one guest count. Itemized mode is for samples, such as a stack of checks from one server's section or one seating.
In totals mode, enter total revenue and total covers for the exact same period. In itemized mode, paste each cover's spend separated by commas, semicolons, or line breaks; the tool sums the list, counts the entries, and averages them. Blank and invalid entries are skipped, and negative entries are ignored in itemized mode, so a stray void does not drag the average down.
One warning that saves most bad readings: never mix periods. Revenue from a full week divided by covers from one busy Friday produces a number that looks precise and means nothing.
The per-cover formula and what counts as revenue
The formula is a single division, and all the judgement sits in what you feed it. Revenue is net sales: food, beverage, and other guest spending, before sales tax and tips, because neither tax nor tips reflect what guests chose to spend.
The denominator is where this metric separates from its close cousins. A per-guest figure from individual checks is handled by the average guest check calculator, which works check by check, and a per-transaction figure belongs to the average transaction value calculator, which divides by transactions in a retail framing. This page stays strictly per cover: revenue divided by guests who sat down and ate or drank.
Worked example: one day, 160 guests, $4,800
The calculator is pre-filled with this day, and every number below is what it returns. A bistro takes in $4,800 in net sales and serves 160 guests.
| Figure | Value |
|---|---|
| Total revenue (net sales, before tax and tips) | $4,800.00 |
| Total covers (guests served) | 160 |
| Average per cover ($4,800 divided by 160) | $30.00 |
| Itemized sample (20, 30, 25, 45) | $120.00 across 4 covers, $30.00 each |
The two modes agreeing is the point of the sample: if the itemized average for one section drifts far from the whole-day figure, that section is behaving differently, which is exactly the kind of thing this metric exists to catch. A server whose section averages $38 per cover against a house average of $30 is selling differently, and the gap is worth understanding before it is worth copying.
What a per-cover number actually tells you
Read alone, the average says how much each guest spent. Read next to cover counts, it separates two very different kinds of growth: more guests, or more spend per guest.
Those ranges, compiled in UpMenu's summary of National Restaurant Association and industry data, are orientation, not targets. A cafe at $14 is not failing because a steakhouse sits at $60. What matters is movement inside your own concept: a $2 slide over a month, at 160 covers a day, is roughly $9,600 of monthly revenue that walked out without being ordered. Pair the trend with a takings view such as the bar revenue calculator when drinks are a large share of the check, because beverage attachment is usually the fastest lever on this number.
Dayparts deserve separate lines. Lunch guests order fewer courses and less alcohol, so lunch almost always averages lower than dinner. Averaging the whole day hides a lunch problem behind a healthy dinner, and hides a dinner problem behind a busy lunch. Track lunch and dinner as two series from the start.
Raising the average without raising prices
The honest levers are attachment and mix, not a blunt price rise. A dessert offered to every table, a second drink suggested before glasses empty, and a starter framed for sharing all lift spend per guest while the guest still feels looked after.
Watch the cover count while you push. If the average climbs $3 but covers fall away over the following weeks, guests are voting that the experience got pushier or pricier than the food justifies. Small food operations can sanity-check the whole picture with the food truck profit calculator, which puts per-guest takings next to costs instead of treating revenue as the whole story. TouchBistro's guide to restaurant metrics and how to calculate them makes the same point at server level: the server with lower total sales can hold the higher per-cover average, and that is the one whose habits you want to spread.
What competing calculators miss
We checked the tools ranking for this search before rebuilding the page. The gaps are consistent.
Winning move 1: both input styles in one tool. Brave Calculator and YesCalculator run the totals division only. If your point of sale exports per-guest amounts, you sum them yourself before their tools can help. CalculatorsHub accepts an itemized list, and this tool matches that, then adds the interpretation layer its page skips.
Winning move 2: honest error handling. Brave's page states that entering zero covers defaults the result to 0. Zero guests cannot produce a real average, and a silent 0 looks like data. This calculator refuses covers below 1 and says why.
Winning move 3: denominator discipline. Several ranking pages slide between covers, checks, tables, and transactions as if they were interchangeable. They are not, and mixing them is how a house average gets compared against a per-check figure from a different report. This page defines the cover once, divides by guests only, and points you to the sibling tools when your data really is checks or transactions.
Frequently asked questions
A cover is one guest served. A table of four is four covers, not one, because the bill is shared by four people eating and drinking. Covers are counted per meal period, so the same person at lunch and dinner is two covers across the day.
Divide total revenue for the period by the total covers served in the same period. A day with $4,800 in net sales and 160 guests gives $4,800 divided by 160, which is $30.00 per cover. Use the same period for both numbers or the result means nothing.
No. Use net sales before sales tax and tips. Tax is collected for the government and tips go to staff, so neither reflects what guests chose to spend on food and drink. Including them inflates the figure and breaks comparisons between periods with different tip patterns.
It depends on the concept. Quick service often runs $8 to $12 per guest, fast casual $12 to $16, casual dining $15 to $30, and fine dining $50 and up. Judge your number against your own concept and your own trend first, then against published ranges for your segment.
The denominator and the setting differ. Average per cover divides revenue by guests served in a hospitality setting. A guest check figure is usually read off individual checks, and one check can pay for several guests. Per transaction figures divide by the number of transactions instead, which is the retail framing.
Because covers grew faster than spending. More guests each spending a little less still raises total revenue while pulling the per-cover average down. That pattern often follows a discount promotion or a shift toward lunch and takeaway orders.
Yes. Switch the calculator to itemized mode and paste each cover's spend, separated by commas or line breaks. Amounts of 20, 30, 25, and 45 total $120.00 across 4 covers, an average of $30.00 per cover, the same method applied to a sample instead of the full period.
Add This Calculator to Your Website
References
- TouchBistro, "21 Restaurant Metrics and How to Calculate Them". TouchBistro: Restaurant Metrics Guide. Accessed October 2026.
- Hatco Corporation, "Five Foodservice Calculations You Can't Live Without". Hatco: Five Foodservice Calculations. Accessed October 2026.
- UpMenu, "How to Increase Average Check in a Restaurant". UpMenu: Average Check Ranges by Restaurant Type. Accessed October 2026.
- Complete Controller, "Restaurant Industry Benchmarks Guide". Complete Controller: Restaurant Benchmarks. Accessed October 2026.
- xdage, "Free Average Check and Spend Per Cover (ASPC) Calculator". xdage: Average Spend Per Cover Lab. Accessed October 2026.