What is a modifier on a restaurant order?

A guest orders a burger, medium, with extra cheese, no onions and the sauce on the side. The server writes it down perfectly, but the till has no button for "sauce on the side", so it goes in a note the grill never reads. Extra cheese is entered as a separate item that prints at the cold section. The burger arrives well done, with onions, the sauce poured over it and no extra cheese. Every change the guest asked for was recorded somewhere. None of them reached the cook who needed it.

What is a modifier? On a restaurant order, a modifier is a change to a dish: a choice the guest makes, such as a size, a cooking temperature or a side; something added, such as extra cheese; or something taken away, such as onions. Modifiers let guests have the dish they want, and they are one of the main sources of mistakes between the order and the plate.

This guide covers what modifiers are, the different kinds, how each should be priced, how they must appear on the ticket, how they affect order accuracy and allergies, and how to set them up so they help rather than confuse. Every venue and figure in it is an example.

A modifier is any instruction that changes how a dish is made or served, attached to that dish on the order. It travels with the dish from the order point to the kitchen, appears on the ticket for the station that makes it and, where it costs extra, appears on the bill.

Modifiers are what turn a fixed menu into a flexible one. A menu with twenty dishes and a few well-designed modifiers can serve hundreds of different orders without a single new dish.

Modifiers fall into a few kinds. Choices pick one option from a set: the size, the cooking temperature, the side, the bread. Additions put something extra on the dish: extra cheese, an egg, a sauce. Removals take something off: no onions, no dressing. And instructions describe how something should be served: sauce on the side, cut in half, no salt.

Each kind behaves differently on the order, the ticket and the bill, so it helps to think of them separately when setting them up.

Some choices are required: a steak cannot be cooked without a cooking temperature, a burger needs a side. Others are optional: a guest may add bacon, but does not have to. A good order system makes the required ones impossible to skip.

A required choice that can be skipped is a question the kitchen has to send back to the floor in the middle of service. Making it required at the order point removes the question.

Modifier pricing is where many venues lose money without noticing. Additions usually cost something: extra cheese uses cheese, an egg uses an egg. If the addition is free, the venue gives away the ingredient and the labour every time.

Price each addition from its cost and the work it adds, as you would price a small dish. Choices may change the price, as a large size costs more than a small one, or not, as a choice of side may be included. Removals usually do not reduce the price, though many venues make an exception for an expensive component left off.

A size is a choice that changes the dish's price: a small and a large soup, a half and a full portion. Price each size from its own cost and portion, not as a fixed amount added to the small one.

Check that the larger size earns at least as much margin as the smaller. A large portion priced too close to the small one sells well and earns little.

Additions are small dishes in their own right. An extra portion of a protein can cost as much as a side, and an extra sauce can use an expensive ingredient. Cost each addition, set a price that covers it with a margin and review the prices when supplier costs change.

Watch which additions sell most. A popular addition priced too low is a quiet leak; one priced well is a quiet profit.

Removals rarely change the price, because the dish's cost is mostly in its main components and its preparation. A burger without onions costs almost the same to make as one with them.

The exception is a removal that takes away something expensive, such as the meat in a dish, where the guest may reasonably expect a lower price. Decide the venue's policy in advance, so servers give the same answer every time.

Modifiers on the ticket must be impossible to miss. The cook needs to see each change clearly, next to the dish it applies to, in the order the cook will make it: the choice first, such as the cooking temperature, then the additions, then the removals, then any instructions.

A ticket that lists the changes in a block of small text, or in a note at the bottom, invites mistakes. One that shows each change on its own line, under its dish, with removals clearly marked, is read correctly even in a rush. Our guide to modifiers on the ticket: "no onions", really covers the layout.

A modifier must reach the station that acts on it. Extra cheese on a burger belongs on the grill's ticket, with the burger; a side salad chosen with it belongs on the cold section's ticket; the sauce on the side belongs wherever the plate is finished.

Set up modifiers so they follow their dish to its station, rather than appearing as separate items that print elsewhere. A change that reaches the wrong station is as good as a change never made.

Order accuracy is the share of orders that reach the guest exactly as they were asked for. Modifiers are where most inaccuracy comes from: a change missed, a removal ignored, an addition made to the wrong dish.

Measure it simply: count the dishes sent back or remade because of a wrong change, over a few weeks. If the count is high, look at how the changes are entered, how they appear on the ticket and how the kitchen reads them.

Removals are often about allergies, and that makes them serious. "No nuts" on a dish may be a preference, or it may be a guest who will become seriously ill. The order must make the difference clear, and the kitchen must treat an allergy as more than a modifier.

Record allergies separately from preferences, so they stand out on the ticket. Our guide to modifiers: letting guests change a dish safely covers how to handle the changes that carry risk.

Free-text notes let the server write any instruction the buttons do not cover. They are useful for the unusual request, but they are a poor substitute for well-designed modifiers. A note is easy to miss, hard to read in a rush and impossible to report on.

Turn the requests that keep appearing in notes into proper modifiers. If "sauce on the side" is written in a note ten times a night, it deserves its own button.

When guests order for themselves, on a digital menu or a kiosk, the modifiers must be just as clear to them as they are to a server. The required choices should be obvious, the additions priced on the screen and the guest able to see their changes before sending the order.

A guest who cannot find how to remove an ingredient will either not order the dish or add a note that may be missed. Design the guest's view of the modifiers as carefully as the server's.

Modifiers can be overdone. A dish with fifteen possible changes slows the order, confuses the guest and burdens the kitchen with variations it cannot make consistently. Every modifier added is a decision for the guest and a step for the cook.

Offer the changes guests genuinely want and the kitchen can make well. A short, clear set of modifiers is better than a long one nobody uses correctly.

Each modification takes the kitchen time. A burger with three changes takes longer than a standard one, and a busy service with many modified dishes moves more slowly than one without.

Watch which modifiers slow the line most, and consider whether they belong on the busiest nights. Some venues limit certain changes at the peak, explaining why to guests who ask.

Modifiers use stock, and stock counts that ignore them make the variance look wrong. A kitchen that adds extra cheese to fifty burgers a week uses more cheese than the recipe suggests, and the count will show it.

Include the popular additions in the expected use, or at least know roughly how much they use. A variance that matches the additions sold is not a mystery.

Train servers on the modifiers: which ones exist, which are required, which cost extra and how to explain them to guests. A server who knows the options can guide a guest quickly; one who does not types notes.

Train the kitchen to read them: where the changes appear on the ticket, how removals and allergies are marked and what to do when a change is unclear. A question asked at the pass is better than a dish made wrong.

Review the modifiers every few months, alongside the menu. Which are used, which are never used, which are priced correctly and which cause mistakes? Remove the ones nobody uses, add the ones that keep appearing in notes and reprice the additions whose costs have changed.

A modifier list that is reviewed stays useful. One that is added to for years becomes a maze.

On the point of sale, modifiers should appear the moment a dish is chosen: the required choices first, then the common additions and removals. A server should be able to enter "burger, medium, add cheese, no onions" in a few touches, without searching through screens.

Lay out the modifiers in the order the server asks the guest. A till that asks for the side before the cooking temperature, when every server asks the other way round, slows every order.

Priced modifiers must appear on the bill clearly, so the guest understands what they paid for. "Burger 14.00, extra cheese 1.50" is easy to read; a burger at 15.50 with no explanation invites a question.

Removals and free choices usually need not appear on the bill, but they should appear on the ticket. Keep the two purposes apart: the bill explains the price, the ticket explains the dish.

Some dishes are designed around modifiers: a build-your-own salad, a burger with a choice of toppings, a pasta with a choice of sauce. For these, the modifiers are the menu, and they deserve the same care as the dishes themselves.

Keep the choices clear and limited, price the additions sensibly and make sure every combination is one the kitchen can make well. A dish with a hundred possible combinations is one the kitchen will make inconsistently.

Drinks have modifiers too: a double, a different mixer, no ice, a slice instead of a wedge, a dairy-free milk in a coffee. They follow the same rules as food: priced where they cost more, clear on the ticket for the bar and reaching the bartender who makes the drink.

A dairy-free milk for a guest with an allergy is not a preference, and it must be treated with the same care as a food allergy.

Look at which changes guests ask for most. A dish that is modified by half the guests who order it may need a new standard version: the dressing on the side as standard, a choice of sides offered on the menu, a version without the ingredient most often removed.

Changing the dish to match what guests want reduces the number of modifiers, speeds up ordering and lowers the risk of mistakes.

A guest who can have the dish the way they like it is a happy guest, but one who is told "no changes" without a reason feels unwelcome. Where the kitchen cannot make a change, explain why: the sauce is made in advance, the dish is cooked as one, the change would affect the allergens.

Most guests accept a reason. Few accept a refusal without one.

Large groups bring many modifiers at once, and each must reach the right plate. Taking the order by seat, with each guest's changes recorded against their seat, lets the runner deliver the right dish to the right guest without asking.

For pre-ordered groups, collect the modifiers with the pre-order, so the kitchen can prepare each change in advance rather than discovering them at the pass.

Before adding a new modifier, test it: enter an order with it on the till, check how it appears on the ticket at each station and on the bill, and ask the kitchen whether it is clear. A modifier that looks right on the till may appear in the wrong place on the ticket.

A few minutes of testing prevent a week of mistakes.

Modifiers tell the venue what guests want. Reports of which additions sell, which removals are most common and which dishes are most often changed show where the menu could follow its guests more closely.

Look at them every few months, beside the menu report. A popular addition may deserve a place on the menu as a dish in its own right.

Name every modifier so that the server, the cook and the guest understand it the same way. "Extra sauce" is clearer than "XS"; "No dairy (allergy)" is clearer than "ND". Abbreviations that make sense to the person who set up the till confuse everyone else.

Read the ticket aloud as a cook would. If a modifier needs explaining, rename it.

Sometimes the kitchen cannot make a change: the sauce is prepared in advance with the ingredient in it, or the dish cannot be cooked another way. The till should not offer changes the kitchen cannot make.

Remove or hide those modifiers for the dishes they do not suit, and tell the floor why. A server who offers a change the kitchen refuses has to go back to the table with bad news.

An invented burger restaurant finds that one in twenty of its burgers is sent back, almost always because of a change: onions that should have been left off, a sauce that should have been on the side. Its till has removals as separate items, additions as free notes and no required cooking temperature.

It rebuilds its modifiers: the cooking temperature becomes required, the common additions become priced options on each burger, the common removals become buttons that print as "No onions" under the burger on the grill's ticket and "sauce on the side" gets its own option. Within a month, send-backs fall to one in a hundred, and the additions, now priced, add noticeably to the average bill.

In servearound, options are set on each dish. Variants are a list of choices, such as a size or a cut, whose price replaces the dish's price; add-on groups are options priced on top, each group marked as required or not, and as allowing one choice or several. A group can be copied to other dishes. Guests choose them on the table's QR menu, and servers on the till, which also lets the server take ingredients off a dish, shown as "No ...", and add notes for the kitchen.

On each station's kitchen screen, every dish shows its options, its allergens, in red when this guest is allergic to one, its removals and its notes. There is no shared library of modifier groups and no limit such as "up to three". See the menus module and point of sale and kitchen.

A change to a dish on an order: a choice, an addition, a removal or an instruction.

Usually, priced from their cost and the work they add.

Rarely, except when something expensive is left off.

Each on its own line, under its dish, at the station that makes it.

They are the main source of mistakes, so they must be clear at every step.

Separately from preferences, marked so they stand out.

For rare requests. Common ones deserve proper modifiers.

Every few months, with the menu.

What is a modifier? It is a change to a dish on an order: a choice, an addition, a removal or an instruction. Set modifiers up so required choices cannot be skipped, price additions from their cost through careful modifier pricing and decide in advance how removals are priced.

Show modifiers on the ticket clearly, under their dish, at the station that makes it, keep allergies separate from preferences and turn common notes into proper options. Measure order accuracy, keep the list short and review it with the menu.