· Orqestra Team · 8 min read

Average Ticket Size for a Restaurant: Formula and Benchmarks

Average ticket size is net sales divided by the number of checks. Learn the formula, where to find check counts in Clover, benchmarks, and levers to raise it.

Average ticket size is net sales divided by the number of checks (orders) in the same period. If you rang $7,370 in net sales across 360 checks yesterday, your average ticket was $20.47. Track it by daypart and by order type, because a blended number hides the shifts where the money is made or lost. This article gives the formula, shows where the check count sits in Clover's reports, explains why published benchmarks vary so much, and lists the levers that move the number.

The average ticket size formula

Two versions matter, and they answer different questions.

Average ticket (per check) = Net sales ÷ Number of checks

Average spend per cover = Net sales ÷ Number of guests

Use net sales, not gross. Net sales are sales after discounts and refunds, before tax and tips. If you compute the average on gross sales, a week of heavy comps looks the same as a strong week.

Per check tells you what a single transaction is worth. Per cover tells you what each guest is worth, which is the number a full-service restaurant should watch, since a table of four and a solo diner are both one check. Quick-service and counter-service restaurants usually only have the per-check number, because they do not record guest counts.

Pick one period, one definition, and keep it. Comparing this month's per-check average to last month's per-cover average will send you chasing a problem that does not exist.

Where to find the number of checks in Clover

Clover reports the pieces you need in the Sales Overview. According to Clover's help article on the Sales Overview Trends report, the Sales Summary at the top of the report shows Orders, Gross sales, Net sales, Average ticket size, and Amount collected. Clover defines average ticket size there as net sales divided by paid orders, so the Orders count on that screen is your check count and the Average ticket size line is already the per-check formula above.

To get there: log in to the Clover web dashboard, select Reports, then Sales Overview, then Trends on the right side of the report window. The default date range is Today. Date ranges under three months open immediately; longer ranges are queued as a requested report and emailed to you. The same article notes the arrows above the sales summary cycle to the previous or next period of the same length, which is the quickest way to compare this Tuesday's average ticket to last Tuesday's. More Filters narrows the report by Device, Employee, or Order Type, so you can see the average ticket for dine-in versus online orders, or for one server.

For a per-cover number, Clover's reports overview describes a Guest count report with daily guest volume, average turn time by party size, and average spend per table. It also says the Sales report can be filtered by dayparts such as Breakfast, Lunch, and Dinner once you configure them under business hours. Dayparts are what make the per-daypart breakdown below possible without exporting anything.

If you have never walked through the full report, how to read a Clover sales report covers each section line by line.

Benchmarks: why published numbers disagree

There is no audited public dataset of average ticket size by segment for independent restaurants. The figures that circulate come from POS vendors, consultants, and industry articles, each with a different sample, year, and definition (some include tax, some include beverages, some are per cover). Two recent sources illustrate the spread.

SegmentUpMenu (range)Papaya (median, 2026 estimate)
Quick service$8 to $12$8
Fast casual$12 to $16$14
Casual dining$15 to $30$22
Fine dining$50 to $150 or more$80

The UpMenu figures come from its article on increasing the average check, which cites the National Restaurant Association and others without linking the underlying data. The Papaya figures come from its restaurant revenue benchmarks page, which labels them "Estimates by segment" and gives no methodology. The ordering is consistent across sources (quick service lowest, fine dining highest), but the dollar values are not something to steer your business by.

What is useful: your own trend. A casual-dining spot whose average ticket moved from $21 to $19 over a quarter has a real problem regardless of what any national table says. Compare yourself to yourself, by daypart, by order type, and by server.

Worked example: average ticket by daypart

A neighborhood restaurant doing about $95,000 a month in net sales pulls one Tuesday from the Sales Overview, filtered by daypart.

DaypartNet salesChecksAverage ticketGuestsPer cover
Breakfast (7 to 10:30)$82095$8.63110$7.45
Lunch (10:30 to 3)$2,450140$17.50215$11.40
Dinner (5 to 9:30)$4,100125$32.80290$14.14
Day total$7,370360$20.47615$11.98

The blended $20.47 is almost meaningless. Breakfast is a coffee-and-pastry daypart with a $8.63 ticket. Dinner has fewer checks than lunch but earns 56 percent of the day's sales. If the owner only looked at the day total, a 10 percent drop in dinner average ticket (about $410 a day, or roughly $12,000 a month) would be masked by a busy breakfast.

Per cover adds a second lens. Dinner guests spend $14.14 each, which is low for a $32.80 check, meaning parties are large and probably sharing. That points at a different lever (a per-person add-on like a dessert or a drink) than a low per-check number would (bigger parties, or a prix fixe).

The restaurant sales by daypart article shows how to set up and read this breakdown week over week.

Levers that raise average ticket size

Each lever below changes either the number of items per check or the price per item. Expected effects are described qualitatively; there are few rigorous public studies, and the ones that exist are small.

LeverHow it worksWhat to expectWatch out for
Add-ons and modifiersSide, extra protein, premium bread, sauce, at a small chargeRaises items per check with almost no added labor; the easiest lever to testMust be on the POS as modifiers so staff do not have to remember
Combos and bundlesEntrée plus drink plus side at a price below the à la carte sumRaises the ticket when the base order was a single item; can lower it if guests were already buying all threePrice the bundle above your typical two-item order, not below
Server and cashier promptsA scripted offer at order time ("still or sparkling?", "add a dessert for the table?")Beverage and dessert attachment usually move first; effect depends on consistency, so track attachment rate per employeePrompts that sound like upselling annoy regulars; keep them specific and short
Menu design and pricing formatPlacement, descriptions, price presentationA Cornell study of 201 diners found guests spent $5.55 more, about 8 percent, when prices had no dollar sign; the lead researcher cautioned that "the yield may not be large"One café, one study; test on your own menu before relying on it
Menu engineeringPush high-margin, popular items; re-price or drop low-margin, low-popularity onesRaises margin per check more reliably than it raises ticket sizeNeeds item-level sales and recipe cost; see the menu engineering worksheet
Minimum delivery or online order sizeFree delivery above a thresholdRaises the online average ticket by pulling small orders up to the thresholdCan suppress order count if the threshold is far above your current average
Larger party formatsFamily meals, sharing platters, prix fixe for tables of 4 or moreRaises per-check size, sometimes lowers per coverWatch both numbers so you are not just bundling what the table already bought

The Cornell result comes from the university's own release, Diners spend more when menus don't use dollar signs. Treat it as a cheap experiment to run, not a guaranteed lift.

The menu engineering worksheet walks through the item-level analysis that tells you which items to push. If you want the daypart and per-employee averages without rebuilding the report each week, a sales analytics tool that sits on top of your POS, such as the sales analytics feature in Orqestra, tracks average ticket by daypart, order type, and employee automatically.

How to run a test on one lever

  1. Pick one daypart and one lever. Do not change three things at once.
  2. Record the baseline: average ticket, checks, and attachment rate for the target item over the previous four weeks, same daypart.
  3. Make the change (add the modifier, start the prompt, re-print the menu) and tell the staff exactly what is different.
  4. Run it for four weeks. Pull the same report, same filters.
  5. Compare average ticket and check count together. A ticket that rose 6 percent while check count fell 8 percent is a loss.
  6. Keep what worked, roll back what did not, and start the next test.

Common mistakes

  • Using gross sales. Discounts and refunds inflate the numerator. Clover's Sales Overview uses net sales for its average ticket line; do the same in any spreadsheet.
  • Mixing per-check and per-cover. A full-service restaurant needs both, but never in the same column.
  • Reading only the blended number. A busy low-ticket daypart hides a slide in the daypart that pays the rent.
  • Counting unpaid orders. Clover's average ticket uses paid orders. Open or voided tickets in an export will drag the average down.
  • Chasing ticket size while check count drops. Price increases raise the average and can shrink traffic. Watch both lines on the same chart.
  • Comparing to vendor benchmarks. They are estimates with unknown samples. Your own trend by daypart is the benchmark that matters.
  • Changing the menu and the prompt the same week. You will not know which one worked.