Back to insights

Restaurant practice

How to Order Shared Snacks: Clarify Portions First, Then Confirm Who Submits the First Round

For shared snacks, clarify whether each serving is sold by the plate or by the piece, the selected portion size, and what sides are shown in the photo. Then have the table confirm the shared order for the first round and who will submit it. A portion information card and first-round list record serving facts and customer intent separately. If the same dish appears again, check the existing order and preparation status first; don’t delete or reorder based on the dish name alone.

MenuSnap editorial teamPublished

When a group orders shared snacks, first confirm the unit each serving is sold in, then confirm which dishes the table wants to share and who will submit the order. The same dish name appearing twice on an order could mean it was submitted twice, or that the guests really do want another serving. Don’t delete an order just because the dish is the same. The menu explains what is served; staff ask what the group intends. Continue entering the order only after the two match.

Clarify what each serving includes with information that can be checked

If the menu shows only a photo of a plate of fried food alongside the dish name and price, guests may assume it is one plate per person or that one order will be divided among the diners. Even if the order quantity is recorded accurately, the kitchen can’t tell from the number alone whether the dish is meant to be shared. So explain the sales unit before entering the order, rather than waiting until the food reaches the table to sort out differing expectations about portion size.

The person responsible for preparing the dish should clarify how it is actually served: by the plate or by the piece, whether different portion sizes are available, and whether the photo shows any extra sides. The dish can keep its distinctive name while staff explain what it includes and its portion size, so first-time guests can understand it too. Servers should use the same explanation and avoid unsupported recommendations about how many people a serving will feed, leaving the quantity up to the guests.

  • Dish and sales unit: Record whether it is sold by the plate, by the piece, or in another actual unit. The name and price should refer to the same unit.
  • Portion selected: Record the currently available portion options and what each actually includes. If quantities vary depending on the ingredients, use a description the restaurant can consistently honor.
  • Accompaniments shown in the photo: State whether extra sides are included. Don’t use a photo of a full plate to imply that the dish is automatically divided according to the number of diners.
  • Language and ingredients: Confirm the original wording first, then check the enabled languages. Have someone familiar with the current recipe verify ingredients and allergens; don’t infer them from the dish name or photo.

MenuSnap Translation review materials call for checking portion sizes and what any extra charge means. The person responsible for preparing the dish should confirm the original wording, which should then be reviewed by someone familiar with the dish and the target language. Don’t expect a translation to fill in details that the original leaves unclear.

The first-round shared list should include only what the group has agreed on

The software can help staff find an existing order, but it can’t tell whether the whole table intends to share the same dish. Front-of-house staff should ask the group in person about its shared choices before filling out the list. Each person’s drink should still be handled according to their own choice.

  • Dish, unit, and quantity: Repeat each shared choice for this round. Don’t treat items guests are still browsing on their phones as their final requests.
  • Individual or shared: Have each person confirm their own drink and the group confirm shared dishes. Don’t guess who an item is for based on where someone is sitting.
  • Who submits this round: Confirm which guest or staff member will proceed. Others should not submit the same list again.
  • Signs of an existing submission: Check the table’s existing orders. Clearly distinguish items that have only been selected but not submitted, those submitted and awaiting confirmation, and those already accepted.

If the same dish appears again, first find out what the guest is asking

  • They’re asking why the original dish hasn’t arrived: Follow the original order and check its acceptance, preparation, and delivery status. Don’t enter the same dish as a new order instead of checking.
  • They clearly want another serving of the same dish: Confirm the unit and quantity for this request, then treat it as an additional order subject to current availability.
  • They want to change the dish or portion size: First check the actual preparation status. The staff member responsible should explain what changes are possible, then pass the request to the kitchen station once the guest agrees.

Browsing, submitting an order, having it accepted, and kitchen preparation are separate steps. A submission shown on a phone doesn’t prove that the dish is being prepared. If a dish that may have been ordered twice has already entered preparation, the shift lead should explain the available options and any charges based on its actual status. Don’t promise that the order can always be canceled or the portion changed. Once the guest agrees, pass the change and the original order identifier to the station handling it, and wait for a response before proceeding.

If questions about portion sizes repeatedly concern the same dish, first review its sales unit, portion options, photo, and translation. If the description is clear but the table still submits the same dish more than once, review the first-round list and who is responsible for submitting it. Keep records limited to the relevant dish and order details; there’s no need to save tourists’ names or itineraries. Nor should guests’ eventual acceptance of a dish be treated as proof that the original description was entirely accurate.

Sources

Live demoStart free