A restaurant ingredient substitution notice keeps a temporary kitchen change from becoming a guest surprise. Name the dish, state the confirmed replacement in plain words, show where and when it applies, then test the public menu before the next guest relies on it.

This is not a generic disclaimer or a way to hide an unapproved recipe change. It is a short operational control for a dish that remains available but no longer matches its usual guest-facing description.

Confirm the substitution before anyone edits the menu

Start with the decision a guest needs to make, not with an inventory note. A message such as “use seasonal vegetables” is not enough if the guest sees a named side, a set menu, or a modifier that now means something different.

Check Confirm before publishing Owner
Dish scope Exact guest-facing dish, option, location, and service period Kitchen lead
Replacement Ingredient or component now used, with approved wording Kitchen lead
Guest effect What a guest will see, choose, or need to ask about Menu owner
Safety check Whether an allergen-sensitive question needs confirmation Trained food-safety contact
End state Who confirms the original ingredient has returned Kitchen lead

Keep this record operational. It does not need a guest name, phone number, or order history. The purpose is to give the next person a confirmed source, not to build a second guest file.

If the kitchen cannot serve the dish at all, use the sold-out item process instead. If a guest is choosing among permanent add-ons or exclusions, use the digital menu modifier guide. A substitution notice has a narrower job: make one temporary difference visible before the guest chooses.

Write the substitution notice a guest can use

Put the changed information beside the item or choice it affects. Do not bury it in a photo caption, a vague “ask us” label, or a staff chat message.

For example, write: “Grilled salmon is served with roasted squash instead of green beans for dinner today.” That statement tells a guest what changed and when it applies. It does not promise a nutrition profile, a dietary fit, or an unverified ingredient list.

The W3C guidance on labels and instructions is a useful test: a guest should understand the relevant choice where it is made. Name the replacement clearly, and state any affected option separately. “Vegetable substituted” leaves too much work to the guest and the server.

When the replacement also changes price, use the digital menu price update checklist for the price path. A substitution notice should not create an unofficial price or leave a modifier showing an amount the floor team must explain.

Treat allergen-sensitive information as a confirmation gate

An ingredient substitution can change more than flavor. It can also change what a guest needs to know before deciding. The FDA’s food-allergy guidance is a reminder to work from current, confirmed information rather than memory.

The menu editor should not infer whether a replacement is safe for a guest, nor should a server turn a temporary notice into an allergen guarantee. When a question involves ingredients, preparation, or cross-contact that the team cannot confirm, say that the information is not confirmed and escalate it through the restaurant’s approved food-safety process.

This guide is operational guidance, not legal or medical advice. Menu, consumer-information, and food-safety requirements can vary by jurisdiction and service model. Use local advice for the restaurant’s actual obligation.

Test every public route before service

Saving a change in an editor does not prove a guest can see it. Test the same route a guest uses after publishing the approved notice.

  1. Scan the table, counter, or takeout QR code on an ordinary phone.
  2. Open the affected dish, set menu, and every modifier that can show the old ingredient.
  3. Confirm the location and service period match the kitchen decision.
  4. Read the notice without relying on a staff account or internal context.
  5. Repeat through a shared or saved public link if guests commonly use one.

This is more focused than a digital menu audit, which reviews the full public menu on a regular schedule. Here, the test proves one temporary change is clear before the next service.

Brief the floor team, then close the loop

Give the host, server, or counter lead one approved sentence and one place to verify the current menu. For example: “That dish uses roasted squash instead of green beans for dinner today. I can check the current ingredient information with the kitchen.”

The team should not invent a return time, substitute a different dish, or answer an unconfirmed ingredient question from memory. Record only the change, its owner, the public route tested, and the result. If the same mismatch repeats, include it in the next menu audit.

When the original ingredient returns, do not simply delete a note from one screen. Confirm the kitchen is using it again for the stated location and service, publish the correction, retest the guest route, and tell the next shift. A restaurant that needs one public menu to review after each approved update can check the current digital menu software scope.

Five questions before the next guest sees the dish

  • Is the affected dish, option, location, and service period specific?
  • Does the notice name the confirmed replacement in plain words?
  • Have allergen-sensitive questions been routed to a person who can confirm them?
  • Did someone test the actual QR code or public link on a phone?
  • Does the team know where to verify the current version and when to remove it?

A clear substitution notice is small work. It protects the guest’s choice, lets the kitchen adapt without improvisation, and leaves the next shift with one current menu instead of several competing stories.