Turn guest menu feedback into changes your team can make
Collect guest questions and comments about your menu, distinguish content problems from preferences and technical issues, and follow each change through to review.
Questions such as how many people a portion serves, whether the pictured accompaniment is included or where to find a product provide valuable clues about a menu. However, immediately turning one comment into a permanent change can be as unhelpful as leaving every comment in an undefined backlog. A small routine for classifying, verifying and following up feedback helps you make more balanced decisions.
Contents
Record comments with their context
When someone says the menu is confusing, politely establish which screen, category or product they mean. A brief summary, the relevant product and the menu area may be enough for the record. Keep the employee's interpretation separate from the guest's words. For example, finding a product expensive and not seeing its price are different problems that should not be expected to respond to the same edit.
Keeping feedback records does not require collecting guests' personal information. After service, the team can share brief notes about recurring menu questions that day. The same question appearing across different shifts is a particularly useful signal. Include questions heard by new staff and in different service areas, rather than focusing only on the complaint voiced most loudly.
Route the issue according to its type
You can consider feedback in three broad groups: information accuracy, ease of choosing and technical access. An incorrect accompaniment description needs kitchen confirmation, while small text or a broken link needs a different review. Keep personal preferences separate too. A guest disliking spicy food does not, by itself, show that a description is wrong, although unclear information about spiciness may be a content problem.
For example, if two guests ask whether a breakfast plate is suitable for sharing, first check whether the menu includes portion information. Once the kitchen confirms the presentation, you can add clearer wording. Explain concretely how many people the presentation is designed for and what it includes, rather than guaranteeing that the portion will satisfy everyone.
| Comment | First review | Possible action |
|---|---|---|
| I could not see the price | Phone view | Adjust the price position and readability |
| The item in the description did not arrive | Kitchen and current presentation | Correct the description using verified information |
| I could not find the drinks | Category structure | Review the category name or order |
Write a specific reason for the change
Consider impact and repetition together instead of giving every comment the same weight. A clear factual error may need correction after a single report. A suggestion about category preferences may benefit from observing different uses first. In the decision note, state which problem you want to solve. This gives you a starting point for assessing whether the change helped later.
If you do not need to make several changes at once, try the smallest clear adjustment first. Completing an ambiguous portion description may be enough without replacing the product name entirely. Record the team's suggestion too, but do not present unverified expectations of increased sales or traffic as results. The first aim of a menu improvement may simply be to answer the relevant question more clearly.
Complete the feedback loop after publication
Once the edit is published, open the page on a phone and check that the problem has actually been addressed. Then tell service staff what changed so they do not continue using the old explanation verbally. Record the status, change date and any point that needs another look. For pending feedback, explain why it has been deferred so the list does not quietly keep growing.
At the next review, check whether the same question is still being asked. Fewer questions may be a positive sign, but avoid firm conclusions if conditions such as service volume have changed. Content in an Orvunai menu can be adjusted using this feedback; do not assume comments automatically become the correct changes. Regular human review helps distinguish an isolated complaint from a widespread information gap.
Explore the relevant Orvunai product guide to put these steps into practice with your own menu.
Explore QR code menus for restaurants and cafés