Revenue
Beverage and dessert upsells on digital menus
How to make drink and dessert suggestions feel useful, measure them honestly, and protect a smooth ordering flow.
6 min read
By eRestro Editorial Team
- digital menu
- restaurant upselling
- beverage menu
A useful menu suggestion answers a guest’s unspoken question: “What would go well with this?” It does not interrupt the order, hide the main item, or make a guest feel pushed into spending more. Digital menus make it easy to add prompts, but ease can create clutter. The restaurant’s job is to offer a clear choice at the right moment and let the guest decline without friction.
Start with the food, not a revenue target. A chilled drink may make sense beside a spicy snack; a small dessert may suit a party that has finished its mains; a hot beverage may be more relevant after a late dinner. If the suggestion is useful, it can improve the meal and occasionally increase the basket. If it is irrelevant, it weakens trust in the whole menu.
Map the moments when a suggestion helps
There are three natural decision points in most table-service and takeout flows. The first is before a guest selects a main course, when an uncomplicated beverage or starter can be easy to understand. The second is after the main choice, when a side, bread, or pairing can complete that choice. The third is after service, when the guest is deciding whether to stay for dessert, tea, or coffee.
Do not show every suggestion at every point. A guest who is choosing from a long biryani list does not need a carousel of six desserts. Keep the prompt close to the relevant decision and limit it to one or two meaningful options. Write the reason in ordinary language: “Cooler choice for a spicy main” is clearer than “Recommended for you.”
| Ordering moment | Helpful prompt | What to avoid |
|---|---|---|
| Before the main | One familiar drink or starter | A full-screen interruption before the menu is visible |
| With a selected main | A compatible side, bread, or beverage | A suggestion that changes the guest’s dietary choice |
| After mains | A shareable dessert or hot drink | A discount message that hides the actual portion or price |
| At takeout confirmation | A packaged drink or dessert that travels well | Adding items without an explicit guest choice |
For dietary and allergen-sensitive items, a pairing must not imply suitability that the kitchen cannot confirm. Keep the same labels and descriptions used in the main menu. The practical discipline in veg, non-veg, and dietary icons applies to recommendations too.
Build a small, credible pairing set
Ask the chef, bar team, and service captains to list the combinations guests already request. Begin there instead of inventing pairings from the point-of-sale report. A strong starting set may have five to eight pairings across the menu, not fifty. Each one needs a current price, accurate availability, serving-size information, and a clear reason it is shown.
Use descriptions that help a guest decide quickly. “Two gulab jamuns, served warm” provides more useful detail than “Chef’s favourite.” “330 ml sparkling lemon drink” is more honest than a generic beverage name. If a dessert is intended to share, say so; if a drink contains dairy, say so; if a component changes daily, avoid a fixed promise.
Pairing copy should be reviewed during the same menu-change process as the dish itself. If an item is paused, its prompt must pause too. A guest who taps a suggestion and finds it unavailable experiences the menu as unreliable. A simple menu change-control routine can keep this update from falling between kitchen, floor, and digital-menu owners.
Make the design calm on a phone
On a small screen, the order of information matters more than decoration. Keep the selected item visible when offering a companion item. Make the “No thanks” or close action obvious. Never pre-select an extra item. Show the full price, quantity, and any applicable choice before the guest adds it.
Photos can help when they show a real, current serving, but they should not carry the whole decision. A guest should be able to understand the dessert, beverage size, and price without an image. This also makes the flow more accessible for people using screen readers or slow connections. Use alt text that describes the food rather than promotional language, and do not put essential price or dietary information inside a picture.
Keep promotions distinct from pairings. A “two beverages together” offer is a commercial offer; a “try this with your kebab” prompt is a service suggestion. Mixing the two can make guests wonder whether the restaurant is hiding a condition. If there is a discount, state the normal price, the offer price, the time window, and any exclusions in readable text.
Measure quality before chasing conversion
The first metric to watch is not just add-on rate. Look at whether guests remove the suggested item, whether the kitchen receives clarifying questions, whether a suggested item is frequently unavailable, and whether service staff hear confusion at the table. A low add-on rate may be healthy if the prompt is being shown only when relevant.
| Check each week | What it can reveal | Useful next step |
|---|---|---|
| Adds divided by eligible views | Whether the prompt earns attention | Keep or simplify the copy |
| Removes after adding | Surprise about price, quantity, or fit | Make the suggestion more explicit |
| Unavailable suggested items | A broken availability handoff | Pause the prompt until stock status is reliable |
| Guest or captain comments | Confusion the numbers cannot show | Rewrite, move, or remove the prompt |
| Dessert and drink preparation delays | A constraint at the bar or dessert station | Limit the prompt during that period |
Compare similar dayparts rather than declaring a winner after one weekend. A dessert prompt at a family dinner may behave differently from one at a weekday office lunch. Take notes on weather, large groups, festivals, and stock changes. The aim is a cleaner decision, not a dashboard that flatters a test.
A seven-day experiment plan
Choose one pairing, one placement, and one success condition. For example: place one sharable dessert after two selected mains, with plain copy about the portion. Train captains to mention it only when the table is still deciding, not after a guest has asked for the bill. Review availability before each service and remove the prompt if the kitchen cannot fulfil it.
- Verify the item, price, dietary label, and availability with the kitchen.
- Write one sentence explaining why it belongs with the selected item.
- Show one or two options, never a wall of extras.
- Keep decline and removal actions visible and equally easy.
- Do not auto-add, bundle invisibly, or disguise the price.
- Collect floor feedback alongside order data.
- Retire prompts that cause more questions than useful choices.
- Repeat only after deciding what the first test taught you.
Thoughtful upselling is a form of hospitality. When a digital menu makes a meal easier to complete, guests retain control and the team gains a reliable way to present the things they are proud to serve.
Keep reading
Related restaurant guides
Restaurant operations
Training restaurant staff on a digital menu: a practical playbook
A role-based training playbook for restaurant teams using a digital menu, with guest language, live scenarios, accessibility support, and shift reinforcement.
5 min read
Menu experience
Digital menu photography guidelines: useful images, not slow pages
A practical guide to planning restaurant menu photography that supports a guest decision, stays accurate, and does not make the mobile menu slow.
5 min read
Restaurant technology
Restaurant mobile menu performance: make the first screen fast
A practical mobile performance guide for restaurant menus: prioritise the first decision, control media, measure real paths, and fix the biggest delay first.
5 min read
Next step
Ready to try eRestro?
Request access, add your venue, and connect the kitchen display — go from QR to served in one flow.