How to Communicate Order Notes and Add-ons Clearly: List Standard Options First, Check Special Requests with the Kitchen

Longer restaurant notes are not necessarily clearer. First, list reliably available specifications as options, and show the price of paid add-ons before guests decide. For requests outside the usual options, ask the kitchen whether they can be accommodated, then associate the request with a specific dish. Don’t leave the chef to guess which dish each request in a single table-wide note refers to.

First decide whether something belongs in the options or needs to be checked individually

• Standard choices: Portions, hot or cold options, and combinations you can reliably provide can be organized as menu options. The wording should explain exactly what changes.
• Paid add-ons: First confirm with the kitchen that they are available, then state the additional quantity and price. Don’t treat an unpriced note as authorization to charge.
• Special preparation or substitutions: Ask the person preparing the dish whether they can accommodate the request, what it will cost, and whether it will affect the wait. Then respond to the guest. A note field does not mean every request can be fulfilled at any time.
• Pacing for the whole table: Communicate this separately from preparation instructions for individual dishes. Specify which items it affects and who will pass on the request, rather than letting one long note apply to everyone.

Use an item selection card for every recurring request

• Dish and specification: ____; which serving the request applies to: ____; quantity for this order: ____.
• Preparation requested: ____; reliably available: ____; details that need to be checked with the kitchen: ____.
• Addition or substitution: ____; whether the original item stays: ____; options that cannot be selected together: ____.
• Included or charged extra: ____; where the amount and explanation are shown: ____.
• Response from the person preparing it: ____; what the guest confirmed: ____; destination station and contact: ____.

MenuSnap supports managing dish specifications and add-on options. The owner and kitchen should first organize the choices they can reliably provide. Then the person who maintains the menu can enter what each option applies to, its price, and its translations. Occasional requests do not all need to become new options, which can make the menu harder to navigate.

Clarify vague requests until everyone means the same thing

“Regular size,” “a little less,” and “the same as last time” rely on what each person remembers. Explain portions using your restaurant’s actual sizes. For “less sauce,” ask whether the guest wants less used or the sauce served on the side. Be upfront about the limits of methods you cannot deliver consistently. If reducing an ingredient involves an allergy or dietary safety concern, a responsible staff member must separately verify the recipe and preparation conditions. Don’t treat it as a taste preference.

In every language, distinguish additions from substitutions, small portions from other meal types, and included items from extra charges. Have someone who knows the dish and the target language check the original and translated wording. If staff don’t understand a guest’s note, ask the guest to explain or find a suitable colleague. Don’t choose a translation that merely looks plausible and send it to the kitchen.

Make sure the person preparing the dish sees the same request

The person taking the order should identify the dish, quantity, specification, and agreed preparation method using the order identifier. The person preparing it should repeat back any details that could be misunderstood. If anything is missing, clarify it on the original order. Don’t use the customer receipt from the register as a substitute for kitchen instructions, or resend the entire table’s order just to add one note.

Depending on the configuration, orders placed by scanning a QR code and POS orders can be sent to a KDS or kitchen printer. This requires the appropriate service plan, kitchen station, and compatible equipment; printing also requires an available sending device or service. The screen and paper ticket refer to the same preparation task. A note appearing in the record does not prove that the kitchen has read or agreed to it; a person still needs to respond to special requests.

Handle changes requested after submission as order changes

Find the original order and item first, then check progress with the person preparing it. Explain the original request, what has changed, and the final quantity required. The available actions differ depending on whether preparation has not yet begun or the dish has already been sent out by the kitchen. After confirming with the kitchen and guest, handle the change in a way that is currently allowed. Clearly mark which original ticket any paper-ticket correction refers to, and check whether the dish has already been prepared before printing another ticket.

Do not infer allergen or cross-contact risks from a dish name, photo, translation, or the removal of an ingredient. If you cannot verify the information, explain that to the guest. For a dish already being prepared, first pause the affected part of the order, then ask the responsible staff member to check. Don’t display sensitive health details on the outside of a bag or announce them when calling an order.

Use recurring notes to improve the menu

At the end of the shift, work out whether follow-up questions at the table were caused by a missing option, unclear wording, a note linked to the wrong dish, or a change the kitchen never received. At the next shift, fix the most common issue first, then observe whether staff still need to clarify it verbally or explain an extra charge afterward. The goal is to make standard choices clear and consistent and ensure special requests get a definite response—not to fill up the notes field.