Modifiers: letting guests change a dish, safely

Medium rare. No onions. Dressing on the side. Extra cheese. Swap the chips for a salad. Every busy service brings dozens of small changes to the dishes on the menu, and every one of them is a chance to please a guest or to send the wrong plate to the table.

Modifiers are the way a venue handles those changes: the choices, extras and removals that turn a dish on the menu into the dish a particular guest wants. Done well, they make guests feel looked after, add a little to the bill and reach the kitchen clearly. Done badly, they slow the line, cause remakes and, at worst, put an allergen on a plate meant for someone who cannot eat it.

This guide covers which changes to allow and which to refuse, how to set modifier pricing for extras, why an allergy is never just a preference, and how every modifier must reach the kitchen tickets so nobody misses it. Every figure in it is an example.

A modifier is any change to a dish that the menu allows the guest to make. It helps to separate four kinds, because each is handled differently.

The first three can be set up in advance, as options the server or the guest picks. The fourth is free text, which is useful for genuine one-offs and risky for everything else, because a note is easy to write and easy to miss.

Guests increasingly expect some control over what they eat. Dietary choices, allergies, dislikes and plain preferences all lead to requests, and a venue that says no to every change feels rigid. One that handles changes smoothly feels generous.

Modifiers also matter commercially. Paid extras add to the bill, and a well-chosen extra offered at the right moment, a side, a sauce, an upgrade, is one of the gentlest ways to raise spend. Our guide to increasing average spend without raising prices covers how.

But every modifier is also a risk. Each change is a variation the kitchen has to remember, cook correctly and plate correctly, under pressure. The more changes a dish allows, the more ways it can go wrong. The aim is not to allow every change or to refuse every change, but to allow the ones the kitchen can deliver reliably and to make each one impossible to miss.

The best modifiers are the ones the kitchen can deliver every time without slowing the line. They tend to share a few qualities: they are simple to execute, they do not change the dish's timing much, and they are asked for often.

Common examples include the cooking point of meat and fish, swapping one side for another, sauce on the side, a different bread, adding a simple extra, and removing an ingredient that is placed rather than cooked into the dish, such as onion on a burger or croutons on a salad.

Build these into the menu as proper options. A server who can pick "medium rare" or "no onions" from a list is faster and more accurate than one who types it, and the kitchen reads the same words every time. If the same request appears as a note night after night, it is a sign it should become an option.

Some changes should be refused, politely and consistently.

Refuse changes that cannot be made: an ingredient that is cooked into a sauce made in the morning cannot be removed at eight o'clock. Refuse changes that break the dish so badly the kitchen would not be proud to send it. Refuse changes that slow the line at the busiest moment, such as a complicated rebuild of a dish on a station already under pressure.

Most importantly, refuse to promise what you cannot guarantee. If the fryer is shared, chips cannot be gluten free, however the request is worded. If a dish is prepared on the same surfaces as nuts, it cannot be made safe for someone with a nut allergy by removing the visible nuts.

Write down which changes each dish allows and which it does not, so servers do not have to ask the kitchen mid-service and every guest gets the same answer.

The most important distinction in handling modifiers is between a preference and an allergy. "No onions" from a guest who dislikes onions and "no onions" from a guest who is allergic to them look identical on a ticket. They are not.

A preference can be handled with a removal: the onions are left off. An allergy needs more: checking every component of the dish, including sauces, dressings and garnishes, making sure the kitchen avoids cross-contact, and confirming that the plate leaving the pass is the safe one. A removal on a ticket does none of that by itself. Wikipedia's overview of food allergy explains why even a trace can matter for some guests.

So train servers to ask, every time a guest asks to remove an ingredient: is that a preference or an allergy? If it is an allergy, it must be recorded and flagged as an allergy, not as a modifier, and the kitchen must treat it accordingly. Our guide to allergy notes, the record that must not fail covers how to make that record reliable.

Every modifier can change a dish's allergens. A swap from chips to a salad may add mustard in the dressing. An extra of cheese adds milk. A different bread may add sesame or remove gluten. A dish that was safe for a guest becomes unsafe through a modifier nobody thought about.

That means the allergen matrix, the record of which allergens are in which dishes, has to cover the options as well as the base dishes. Each extra, each sauce and each side that can be swapped in needs its own allergen information, so that when a guest picks it, the server and the kitchen know what it adds.

Keep the two in one place if you can. A matrix that lists dishes but not their options is incomplete the moment a guest changes anything. Our guide to building an allergen matrix that stays correct covers how to keep it accurate as the menu changes.

Modifier pricing is often set casually: a round number that felt right when the menu was written. It deserves the same care as the price of a dish.

Start with the cost of the extra itself: the ingredient, the portion, and any packaging or extra prep. Then price it to earn a similar margin to the rest of the menu, rounded to a price that feels fair. An extra of cheese that costs very little can carry a modest price and still earn well; a premium extra such as a side of prawns needs a price that reflects what it costs.

Be consistent. If extra cheese is one price on the burger and another on the pasta for no reason, guests and servers notice. And decide deliberately which swaps are free. Swapping chips for a salad of similar cost is often best left free, because charging for it feels petty; swapping a side for a more expensive one can carry the difference.

The line between free and paid changes should be clear to servers and guests alike.

Removals are almost always free: guests do not expect to pay for less. Equal swaps are usually free. Upgrades, such as a larger portion or a premium side, carry a price. Extras added on top carry a price.

Show the price of each paid option at the moment of choosing, on the menu, on the screen the server uses and on any digital menu guests order from. A guest who discovers a charge for an extra only on the bill feels tricked, however small the amount. A clear price at the moment of choice is part of what makes an extra feel like a good offer rather than a catch.

Some choices are part of the dish: a steak needs a cooking point, a coffee needs a size, a set lunch needs a choice of main. These should be required. The order should not be able to go to the kitchen without them, because a steak with no cooking point is a question the kitchen has to send back to the floor.

Other options are optional: extras, sauces on the side, removals. These should never block the order.

Set limits where they matter. A choice of sauce might be one and only one. Toppings on a pizza might be up to three. A side might be optional, with one allowed. Clear limits stop impossible orders, such as two cooking points for one steak, and help the kitchen plan, because it knows the shape of every plate before it starts.

It is tempting to offer every possible change, because every change is something a guest might want. But a long list of options for every dish slows ordering, confuses guests and multiplies the ways the kitchen can go wrong.

Offer the changes guests actually ask for, and no more. A burger might offer a cooking point, a choice of cheese, two or three extras and a few removals. It does not need twenty options, most of which nobody picks.

Look at what is ordered. If an option is almost never chosen, remove it. If a note keeps appearing for the same request, add it as an option. Over time, the list of modifiers for each dish should come to reflect what your guests really want, not every possibility.

The words on a modifier matter, because the kitchen reads them in a hurry. Keep them short, consistent and unambiguous.

Use the same word for the same thing everywhere: "no" for removals, "add" for extras, "swap" for substitutions, the cooking point in the words the kitchen uses. "No onion" is clearer than "hold the onion please", and "Swap chips for salad" is clearer than "salad instead".

Name extras by what they are, not by marketing language. "Add fried egg" is clearer on a ticket than "Make it a brunch burger". Keep allergen-related removals worded plainly too, so a cook skimming a ticket cannot mistake them for something else.

A modifier is only as good as the way it reaches the kitchen. Every change must appear on the kitchen tickets, attached to the dish it changes, where the cook cannot miss it.

That means modifiers belong directly under the dish, not in a general note at the bottom of the ticket. Removals should stand out, because a missed removal is the most common way a changed dish goes wrong; many kitchens show them in a different colour or style. Allergy information should be the most visible thing on the ticket, at the top, so it is read before anything is cooked.

Our guide to kitchen tickets that never need a shout covers what belongs on a ticket and in what order. The principle for modifiers is simple: if the cook has to look for it, it will eventually be missed.

Free-text notes have a place. Genuine one-offs, such as a birthday candle in the dessert or a dish for a child cut into small pieces, cannot all be options. A note handles them.

The danger is when notes replace options. A note saying "no onions" is easier to miss than a removal, and a note saying "allergic to nuts" written at the bottom of a ticket can be overlooked in a rush. Notes also vary: one server writes "no onion", another "without onions", a third "NO ONION!!", and the kitchen has to read each one carefully.

Use options for anything that happens regularly, and keep notes for the rare and the specific. Make sure notes appear next to the dish they refer to, and that allergies are never recorded only as a note.

Order accuracy is where modifiers succeed or fail. A changed dish should be checked at the pass before it goes out, against the ticket, by someone who reads the modifiers.

Many kitchens make changed plates easy to spot: a marker on the plate, a different position on the pass, or a ticket that shows changes clearly enough for the person running the pass to check them at a glance. The check is quick, but it catches the missing removal or the wrong cooking point before the guest does.

When a changed dish does go out wrong, record it. Remakes caused by missed modifiers point to a problem: an option worded unclearly, a ticket layout that hides changes, or a station that is overloaded at the moment changes arrive. Fix the cause, not just the plate.

When guests order from their own phones, they choose their own modifiers. That removes the server's mishearing, but it also removes the server's question about allergies, so the menu has to do more of the work.

Show every option clearly, with its price. Make required choices impossible to skip. Show the allergens of each option, not only of the base dish. And ask guests with allergies to tell the venue, rather than relying on a removal to keep them safe. Our guide to QR ordering, where the table orders and the kitchen cooks covers the rest of the flow.

The kitchen should receive a guest's choices in exactly the same form as a server's, under the dish, with removals and notes in the same places. A ticket that looks different depending on who placed the order is a ticket that will be misread.

For orders taken by servers, the point of sale should make modifiers quick and accurate. When a server adds a dish with a required choice, the screen should ask for it. Extras and removals should be a tap away, with prices shown. Notes should be available but not the first resort.

The server's role is also to listen. A guest who says "no onions, I'm allergic" has asked for two things: a removal and an allergy record. A good point of sale lets the server do both, and good training makes sure they do.

Repeat changes back to the guest when taking the order: "So that's the burger medium, no onions, with a side salad instead of chips." It takes a few seconds and catches misunderstandings before they reach the kitchen.

Servers handle most modifiers, so they need clear guidance. Train them on which changes each dish allows, which it does not, and why. Give them the words to refuse a change gracefully: "I'm sorry, the sauce is made in advance, so we can't take the garlic out, but the grilled chicken comes with a herb dressing instead."

Train them always to ask whether a removal is a preference or an allergy, and to record allergies properly. Train them to repeat changes back, and to tell the kitchen about anything unusual in person as well as on the ticket.

New servers should shadow experienced ones on busy services before taking orders alone, because handling changes under pressure is a skill that comes from practice.

Every few months, look at how modifiers are used. Which options are chosen often, and which almost never? Which notes keep appearing for the same request? Which changed dishes come back as remakes?

Each answer suggests an action. Remove options nobody chooses. Turn repeated notes into options. Investigate remakes: is a modifier worded unclearly, or is a particular change hard for the kitchen to deliver in a rush? Check that modifier pricing still makes sense as ingredient costs change.

A modifier list that is reviewed regularly stays short, useful and accurate. One that is never reviewed grows into a long list of options that slow the order and confuse the kitchen.

An invented burger restaurant lets servers write any change as a note. On busy nights, the kitchen gets tickets with notes like "no onion, cheese extra, well done??", remakes are common, and twice in a month a burger goes out with onions to a guest who had asked for none.

The restaurant sets up proper modifiers for each burger: a required cooking point, a choice of cheese, four paid extras with clear prices, and five common removals. Servers are trained to ask whether a removal is a preference or an allergy, and to record allergies separately. Tickets now show each change under the dish, with removals in a different colour.

Within a month, remakes fall, the kitchen stops sending questions back to the floor, and paid extras appear on more checks because servers can offer them with a tap. The restaurant reviews the options after three months, removes two extras nobody orders, and adds a removal that kept appearing as a note.

In servearound, each dish can have variants, one list of choices whose price replaces the dish's own, such as a size or a cut, and groups of add-ons, each priced on top. An add-on group can be marked required, so a cooking point or a sauce has to be chosen before the order goes, and can allow one choice or several, and a group set up on one dish can be copied to others. Guests choose options on the QR menu and servers on the point of sale, where the dish's ingredients can also be tapped off the plate and a note added for the kitchen.

On the kitchen screen, each dish on a ticket shows its options, any ingredient taken off as "No" in its own colour, its note and its allergens, with the guest's own allergies at the head of the ticket and any matching allergen in red. Before a QR order is sent, the guest confirms they have reviewed the allergen and dietary information. See the menus module and Order Fulfillment.

The changes a guest can make to a dish: choices built into it, such as a cooking point, extras added for a price, removals, and free-text notes for anything else.

Ones the kitchen can deliver reliably without slowing the line: cooking points, simple swaps, sauce on the side, simple extras, and removing ingredients that are placed rather than cooked in.

Ones that cannot be made, such as removing an ingredient from a sauce made in advance, ones that break the dish, and any promise about allergens the kitchen cannot guarantee.

From the cost of the extra plus a margin similar to the rest of the menu, rounded to a fair price, consistent across dishes and shown at the moment of choice.

No. An allergy needs its own record, a check of every component and care against cross-contact. Always ask whether a removal is a preference or an allergy.

Yes. Each extra, sauce and side that can be added or swapped in needs its own allergen information, so the allergen matrix stays correct when a dish changes.

Directly under the dish they change, with removals easy to spot and allergy information at the top of the ticket.

For genuine one-offs. Anything requested regularly should become an option, and allergies should never be recorded only as a note.

Use clear options instead of notes, show changes prominently on tickets, check changed plates at the pass, and review which changes cause remakes.

Modifiers let guests change a dish, and they please guests, add to spend and, handled badly, cause remakes and allergy errors. Allow the changes the kitchen can deliver reliably, refuse the ones it cannot, and never treat an allergy as a simple removal. Price extras carefully and consistently, show prices at the moment of choice, and make required choices impossible to skip.

Keep the list of options short and worded plainly, cover every option in the allergen matrix, and make every change appear under its dish on the kitchen tickets, with removals easy to spot and allergies at the top. Check changed plates at the pass, train servers to ask and repeat back, and review the modifiers every few months.