Show the extra charge beside the substitution before the guest selects it, then show the updated item price and basket total before checkout. A guest should not have to add an option just to discover what it costs.
Start with a short list of permitted swaps and a clear price rule for each one. Then check the entire path: the default item, the changed selection, the basket and the final review screen. The goal is for the guest and the kitchen to see the same order without either having to guess what changed.
List the substitutions you actually allow
Write down the standard item first. For a bowl, that might be rice, chicken and a house sauce. Then list the alternatives the kitchen can prepare consistently, such as tofu instead of chicken or a premium sauce instead of the house sauce.
For each swap, record four things: what it replaces, whether the replacement is free or carries an extra charge, whether the original ingredient must be removed, and how the change should appear on the kitchen ticket. A substitution replaces something. An add-on leaves the original in place and adds another item. Those choices can have different prices and produce different dishes.
Get the inputs from the people who use them. The kitchen lead can confirm what can replace what and how the ticket should read. Whoever sets menu prices can approve the guest-facing charge. The person managing the ordering menu can enter the choices and check how they appear on a phone. If delivery packaging changes the decision, include the person responsible for packing orders.
Keep the list narrow enough to fulfill during a busy service. A restaurant might offer tofu instead of chicken but not permit a guest to replace rice with an unrelated side. If a choice is unavailable, decide whether to remove it from the menu or mark it unavailable using the controls your system offers. Ask the provider how quickly a change reaches the ordering page.
Consider how the choice is worded. “Tofu instead of chicken” tells the guest what leaves the bowl. “Add tofu” does not. If a guest can remove chicken without choosing a replacement, decide whether the price stays the same and make that clear where the choice appears. Avoid promising a discount simply because an ingredient was removed unless that is your actual pricing rule.
These are pricing and fulfillment decisions, not just a question of how many modifiers a guest may select. A limit of one protein choice can prevent an invalid combination, but it does not explain the price of switching proteins.
Put the incremental price beside the choice
Use a label that connects the replacement to its charge. For example, show “Swap chicken for tofu: +$2.00” beside the option, rather than putting a generic “charges may apply” notice at the bottom of the page. Show “No extra charge” for a free swap when the alternative might otherwise look ambiguous.
The plus sign matters: it tells the guest that the amount is added to the displayed base price, not the full price of the dish. If your menu instead displays a complete price for each version, label it as the item price. Do not mix full prices and incremental prices in the same list without making the difference obvious.
Place the charge where the decision happens. A note in a menu description can help, but it should not be the only place a guest learns the price. Check the choice on a narrow phone screen, where a long label and its price might be separated or cut off. Also check that the updated price remains understandable when the guest returns to edit the item.
There is a trade-off between detail and speed. A long explanation beside every option slows ordering, while a bare “+$2.00” may not say what the guest receives. Use a short, specific label and put any necessary detail, such as an ingredient description, nearby. If the system cannot show a clear price beside the choice, ask whether the menu can be configured another way before relying on it for paid substitutions.
When comparing restaurant online ordering options, ask to see the guest-facing choice and basket, not just the menu setup screen. The online ordering buying guide can help with the wider purchase; the substitution check should focus on this particular customer decision.
Work through a basket before changing the menu
The following is a hypothetical pricing example, not a claim about any ordering system. Assume a bowl costs $14.00 with chicken and house sauce. The restaurant charges $2.00 to swap chicken for tofu and $1.50 to swap the house sauce for a premium sauce. A separate side costs $9.00. The guest also chooses delivery for $4.00.
The table shows which amounts belong to the changed bowl and which are separate basket charges. Both swaps replace the original ingredients; neither is an additional portion.
| Basket line | Calculation | Amount |
|---|---|---|
| Bowl with two substitutions | $14.00 + $2.00 + $1.50 | $17.50 |
| Separate side | $9.00 | $9.00 |
| Food subtotal | $17.50 + $9.00 | $26.50 |
| Delivery charge | Assumed fixed charge for this order | $4.00 |
| Total before tax | $26.50 + $4.00 | $30.50 |
The $30.50 includes the two assumed substitution charges, the side and the fixed delivery charge. It excludes tax and any other service, payment or exception charges. There are no variable or exception charges in this example; an actual order total may include them. The delivery charge is a guest-facing charge here, not a statement of the restaurant’s delivery cost.
On the item page, the guest should be able to see the $2.00 and $1.50 increases before choosing them. In the basket, the bowl should be identifiable as $17.50, with both substitutions listed. The final review should carry the $26.50 food subtotal and show the $4.00 delivery charge separately before the guest commits. If tax or another fee applies, it should be identified in the final total rather than hidden inside a substitution price.
Now consider the reverse. If the guest changes the tofu back to chicken while retaining the premium sauce, the bowl should return to $15.50. With the same side and delivery charge, the total before tax becomes $28.50. This catches a common pricing problem: an old substitution charge remaining after the choice has changed.
Test defaults, changes and order details
Use a safe simulation or practice environment for these checks. Confirm with the provider that it will not create a real payment, send a guest message or dispatch a courier. If there is no isolated practice mode, ask the provider how to inspect the guest screens and calculations safely before using a live order. A live service pilot is separate: plan it with staff, use real fulfillment only deliberately, and tell participants what to expect.
- Start with the default. Open the bowl without changes. Confirm that chicken and house sauce are the included choices and that the base price is $14.00.
- Choose each swap. Confirm that the $2.00 and $1.50 charges are visible before selection, and that the changed bowl totals $17.50.
- Add the side and delivery. Check the $26.50 food subtotal and $30.50 total before tax under the example assumptions.
- Edit and reverse a choice. Return tofu to chicken. The bowl should be $15.50, and the total before tax should be $28.50. Re-select tofu and check that the charge is added once, not twice.
- Check the order record. In the simulation, inspect the kitchen-facing details. They should identify tofu instead of chicken and premium sauce instead of house sauce, with no conflicting instruction to prepare both versions.
Also check removal without replacement if you allow it, an unavailable substitution, and two identical bowls with different choices. Each basket line needs its own selections and price. If a guest changes quantity, confirm that the substitution charge applies to the intended number of bowls. Repeat the checks on the devices guests commonly use and whenever you change a relevant menu rule.
Record the expected result alongside the actual screen or practice order. A correct total alone is not enough if the kitchen cannot tell what to make. Likewise, a readable ticket does not fix a charge that appears only after the guest has selected an option.
Choose a setup your team can maintain
Ask the ordering provider how staff enter an incremental price, distinguish a replacement from an add-on, and edit an existing choice. Request a demonstration of the guest view, the final review and the kitchen-facing order. Ask what happens when an option sells out and whether an item already in a basket retains an earlier selection or price after a menu change.
Give the person responsible for menu updates a simple approval process: the kitchen confirms the swap, the price owner approves the charge, and the menu manager checks the resulting screens. Keep a dated record of the rule so staff can answer a guest’s question and spot an unintended change.
Your restaurant website may be where guests first read the menu, so check that its descriptions do not contradict the ordering choices. If you also take orders elsewhere, compare the wording and prices across those channels rather than assuming an update carries everywhere.
Use the checklist above on your current setup. If you are evaluating a change, ask Fleksa about its ordering system, show the team your substitution example, and ask about current US availability and the configuration you need.
Frequently asked questions
Should a free substitution show a price?
Labeling it “No extra charge” can remove doubt, especially when neighboring choices have surcharges. Make sure the label matches the basket calculation.
Should the basket show substitutions separately?
It should at least identify the selected replacements and make the resulting item price understandable. Ask your provider how individual charges and choices appear in the basket and on the order record.
What if the total changes after a guest edits an item?
The total should reflect the current choices, not charges for options that were removed. Check the updated item price and final review before accepting the configuration.
