How to Increase Your Restaurant's Average Check Without Pushy Upselling

Pick a period and a definition you'll stick to: recorded food and beverage sales divided by the number of covers in that same period. Exclude, or report separately, anything that isn't comparable, like a private event versus a regular lunch. Counting orders instead of covers changes the result for large parties, so always note what you divided by.

A purely hypothetical example: one service brings in $600 in sales across 30 covers, or $20 per cover. On its own, that number tells you nothing about profitability, so keep track of food costs and waste too. Without a comparable baseline, it's easy to celebrate an increase that simply came from more tables or a one-off event.

A good suggestion builds on what the guest has already chosen: a non-alcoholic drink with a spicy dish, a dessert that's available at the end of the meal, or a side the combo is missing. Write down the item, the portion and the price. Check with the kitchen and the bar that they can serve it without holding up the rest of the table. Mocktails, desserts and add-ons are separate ideas to test, not three versions of the same tip.

Zeat puts these options on an easy-to-read mobile menu. Check how each one works in a demo. Guests should know the price of an add-on before they order. If your team suggests something that's unavailable or poorly explained, the upsell turns into an awkward correction on the floor.

Continuing the hypothetical 30-cover service: six guests add a $7 dessert and nothing else about their order changes. Sales go from $600 to $600 + 6 × $7 = $642, and the average check rises from $20.00 to $21.40 per cover, an extra $1.40. The math is for illustration only. It's not a result to expect from Zeat.

Extra revenue isn't the same as margin. Subtract ingredient costs, any waste and prep time before deciding whether the test is worth it. Ask your servers, too, whether guests understood the suggestion and whether it came at the right time. An add-on that earns little or causes friction can be dropped even if it sells.

Offer a drink after the main course and it can come too late. Pitch dessert with the appetizers and it can be forgotten by the end of the meal. Go through the Zeat menu from a table: can the guest find the sides, see the prices and tell what's included? Clear presentation saves your team from answering the same questions over and over.

Give your servers a simple, low-pressure script: offer one specific item, answer questions about price, then take no for an answer. Make sure the menu and the instructions you give staff describe the same offer. If every server makes up their own add-ons, you won't be able to measure the test or keep the promise you made to the guest.

After a few comparable shifts, record how many items were suggested and sold, the average check per cover, costs and feedback. Split results by daypart if lunch and dinner work differently. A higher average check may come from a price change, so check before crediting the mobile menu or your floor team.

Keep the suggestion that genuinely helps both guests and operations. Change or drop the one that causes mistakes, waste or extra wait time. What the digital menu gives you is an option that's better presented and easier to update, backed by a decision based on what you've actually seen.