Decide whether this is a rename or a different dish
Start with a short change record showing the previous item, the revised item and what is actually different. Include recipe, portion, sides, available options and price where relevant. This gives the person updating the menu and the people answering customer questions one shared reference, rather than several slightly different accounts.
Keeping a familiar name helps customers find a favourite when only the wording has changed. However, retaining that name after a substantial recipe or portion change can create the wrong expectation. Use a clear description or a distinct name when needed. If ingredients have changed, have the responsible team member check the relevant ingredient and allergen information before publication; a rename alone does not explain the difference.
- Assign one person to approve the change record.
- Record when the revised menu is intended to take effect.
- List any customer-facing references that also need updating.
Make the choices clear before customers reach checkout
NeroWeb supports direct online ordering with menus, product options, configured collection or delivery and checkout. Use the menu wording to explain what a dish includes before asking customers to choose extras. For example, distinguish an included side from an optional additional side, and make any relevant price difference visible before the order is submitted.
Decide whether a choice belongs within an existing item or needs its own clearly described item. Options can keep related choices together, but a long list can obscure important differences. Do not assume your setup will enforce every preparation rule: actual order availability, stock controls, kitchen routing and supported payment methods depend on merchant setup. Confirm uncertain behaviour before relying on it.
Give each shift a handover they can use
Keep the handover short enough to read before service. It should state what changed, when it changed, what customers may remember and who can resolve an unclear request. Include an agreed explanation for returning customers, such as: “That dish now comes with rice; chips are a separate option.” Staff should explain the difference before confirming an order, not leave the customer to discover it on collection.
Name the person responsible for menu corrections and a backup for their absence. Agree how the team will handle requests for the previous version, without promising substitutions the kitchen cannot provide. Check how orders placed before the change will be identified and handled, especially if preparation or collection falls after the revised menu goes live.
- Ask the incoming shift to explain the change back in their own words.
- Give front-of-house and kitchen staff the same approved version.
- Record unresolved questions for the responsible manager.
Hypothetical example: a regular meal changes its side
Suppose a restaurant previously sold a “House Chicken Meal” with chips included. The revised dish includes rice, while chips become an additional choice. Simply updating the options beneath the old name risks a returning customer repeating a familiar order and expecting chips. The team instead describes the included rice clearly and makes the chips option explicit.
The shift handover records the old and new contents and confirms whether replacing rice with chips is possible. Staff do not offer that swap unless it has been agreed. One colleague then follows the online journey as a returning customer, while another checks what the team receives. Success means both can independently describe the same meal, options and amount due without relying on a verbal correction.
Test the changed journey and resolve mismatches
Review the published menu rather than relying only on the editing view. Follow the changed item through selection, options, basket and checkout, checking whichever collection or delivery routes you have configured. Look for outdated names, unclear defaults, missing choices and descriptions that no longer match the selected dish.
Where appropriate, arrange a controlled test order with the responsible manager, accounting for any applicable payment charges. Check how the order reaches the team in your actual setup; do not assume a particular kitchen routing method. If wording or order details disagree, record the exact item, choices and stage affected. Correct and retest before treating the change as complete, then review questions from the first service.
- Check the changed item on a phone-sized screen.
- Compare the selected options with the order details received.
- Confirm that the next shift can find the approved handover.
GOOD TO KNOW
Common questions
Should we keep the old dish name?
Keep it if it still accurately describes the dish. If the recipe, portion or included sides have materially changed, use wording that makes the difference clear rather than relying on customer memory.
Should staff tell every customer about the change?
Make the change clear on the menu for everyone. Staff should also explain it when a customer refers to the old version or asks for their usual order.
What if an option appears online but cannot be prepared?
Alert the person responsible for the menu and check availability behaviour in your setup. For an affected order, contact the customer to agree the next step rather than silently substituting.