When an ingredient or supplier changes, review every guest-facing claim that depends on it: dish descriptions, origin and producer names, dietary notices, photos, modifier choices and ordering pages. Start with the kitchen’s actual recipe, then trace where the old description appears. A familiar dish name does not mean the ingredients or preparation are still the same.
Assign one person to coordinate the change, but involve the kitchen, purchasing and whoever edits the website. Record what was checked and who approved each update. For dietary wording, verify the ingredient and preparation with the kitchen, avoid absolute free-from promises, and refer wording to a qualified reviewer where appropriate.
Find the dishes and claims affected
Ask purchasing for the old and new product names, supplier details, ingredient information and the date the kitchen expects to switch. Ask the chef which recipes use the product, including sauces, garnishes, shared prep and optional substitutions. A new dressing, for example, may affect several dishes even if it appears by name on only one menu item.
Build the list from the ingredient outward, not just from the menu page inward. Check specials, catering menus, downloadable menus and descriptions used for pickup or delivery. If a product is used in a base recipe, follow that base into each finished dish. Note whether the old and new ingredients will overlap during the transition; staff may need to know which version is being served on a given shift.
Then look for claims that might no longer fit:
- Ingredient descriptions: Named cheeses, oils, proteins, sauces and garnishes, including ingredients named in modifiers.
- Sourcing statements: A farm, producer, region, country of origin or other supplier-specific description.
- Production claims: Statements about how an ingredient was made, grown or raised.
- Dietary information: Dietary labels, allergen notices and answers in ordering-page FAQs.
- Visual promises: Photos that show a distinctive product or preparation that will no longer be served.
Do not replace a specific claim with a new one just because it appears on a supplier’s sales sheet. Confirm that it describes the product the kitchen will actually receive and use. If the details are still uncertain, remove or pause the affected claim until the team can verify a suitable replacement.
Verify the change with the kitchen
Give the chef or designated kitchen lead the new product information and ask them to compare it with the current recipe. Check the ingredient list, relevant allergen information, package or product documents, and any changes to preparation. Ask whether the new item requires a different sauce, cooking method, garnish or handling routine. An unchanged main ingredient can still be paired with a changed component.
Kitchen verification also needs to cover how food is prepared in the restaurant. Supplier information alone does not describe shared equipment, utensils or preparation surfaces. Staff should know what they can accurately tell a guest and when to refer a dietary question to the kitchen.
For dietary notices, avoid absolute free-from promises. Use wording that reflects what the kitchen has verified without implying that every possible exposure has been ruled out. Have a qualified reviewer assess dietary wording when appropriate, and record that review for the change. Guests with dietary concerns should be encouraged to speak with staff before ordering; that invitation does not replace an accurate description.
Give the review a clear owner and a deadline tied to the first service using the new ingredient. Record the product reviewed, the affected dishes, the kitchen contact, the date, the wording decision and any qualified review. If the product or recipe changes again, reopen the check rather than assuming the earlier decision still applies.
Turn the findings into accurate descriptions
Use the following hypothetical example to see how a change can travel. A restaurant switches the supplier of a lemon dressing used on its grain bowl and a seasonal salad. The old dressing contained no dairy ingredients according to its product information; the new dressing lists milk. The kitchen also confirms that both dishes use the new dressing as standard. This example illustrates a content review, not a determination that either dish is suitable for any particular guest.
The grain bowl page currently says “lemon dressing, dairy-free.” The seasonal salad mentions the dressing but has no dietary label. The restaurant also has a catering PDF that describes both dishes. The team should remove the old dietary claim, check the full recipes and preparation with the kitchen, and seek qualified review of any replacement dietary wording. A plain ingredient description such as “served with lemon dressing containing milk” may be useful if it accurately reflects the verified product and dish; it should not be treated as a complete allergen statement.
The worksheet below shows how the owner could assign the work. It separates the kitchen decision from the places where the result must appear.
| Impact | Kitchen or purchasing check | Content action | Owner |
|---|---|---|---|
| Grain bowl dietary claim | Confirm new dressing and complete recipe | Remove old claim; obtain qualified review of replacement wording | Kitchen lead and content editor |
| Seasonal salad description | Confirm dressing is standard and check preparation | Update ingredient description and any relevant notice | Kitchen lead and content editor |
| Catering PDF | Confirm whether catering uses the same recipe | Replace the outdated file and check its link | Catering manager |
| Ordering modifiers | Confirm whether dressing can be omitted or changed | Match available choices to the actual service | Ordering manager |
If the kitchen can offer a dressing change, confirm the alternative and how staff will execute it before presenting it as an ordering choice. If it cannot, remove a stale modifier rather than leaving guests to request something the team cannot reliably prepare. A modifier name should be clear, but it should not imply an unverified dietary outcome.
Keep a short change record alongside the worksheet: old and new product, effective date, affected recipes, decisions, reviewers and links or file locations updated. The record gives the next shift a way to answer questions and gives the next editor a starting point when the supplier changes again.
Review photos and every ordering destination
A description can be technically current while its photo tells a different story. Compare the image with the dish the kitchen now serves. Does it prominently show the old cheese, a branded package, a sauce color or a garnish that has disappeared? Replace the photo, use an accurate existing image or remove it while a new one is prepared. Avoid treating a caption as a complete fix for a materially misleading image.
Follow the guest’s path from discovery to order. Start at the homepage, then check menu categories, individual dishes, specials, catering pages and any dietary information pages. Open the ordering destination from the site and inspect the item there too. A site menu and an ordering menu may be separate places to edit. Also check downloadable files and any channels your team maintains outside the main site.
Make a destination list before publishing. For each location, note the editor, the update date and whether the old wording or image remains visible. If a third party controls a listing, request the change and track its status. Until it is corrected, staff should know where outdated information may appear and how to respond to questions.
Use a simulated check after edits: open the affected pages on a phone and a larger screen, read the dish and modifier text, and confirm links lead to the intended ordering page. Do not submit an order, take a real payment, send a guest message or dispatch a courier during this practice. A visual check can catch stale text or a broken link; it cannot establish the ingredient’s dietary suitability.
Make the handoff part of service
Before the switch, tell front-of-house and kitchen staff which product changed, which dishes are affected and what they should do when a guest asks about ingredients. Keep the approved description accessible during service. If the old and new products overlap, agree on how the kitchen identifies the version in use and how staff will get a current answer. Do not ask staff to guess from a website label.
After publishing, have someone other than the editor compare the live pages with the change record. Check that the right file opens, the old supplier name is gone where necessary, and the ordering choices match the kitchen’s instructions. Record who checked and when. If an edit cannot be made before the ingredient switch, decide whether to pause the affected item or claim until the information is accurate.
For your next supplier change, use the worksheet to evaluate your current setup: identify who can edit the restaurant website, who controls online ordering, and how quickly each can publish a correction. If you are considering a different setup, the restaurant website builder comparison can help frame the buying questions. Ask Fleksa about current US availability and how your team would update the relevant menu and ordering content.
Frequently asked questions
Does a supplier change mean every menu item needs rewriting?
No. Trace the changed ingredient through recipes and shared components, then review the claims and destinations connected to those dishes. Record unaffected items if that helps the team close the review.
Can we keep a dietary label if the dish name stays the same?
Do not rely on the name. Verify the new product, full recipe and preparation with the kitchen, avoid absolute free-from promises, and seek qualified review of the wording where appropriate.
What if the website is updated but an ordering page still shows the old description?
Assign an owner to correct the ordering page or request the change from its operator. Track the outstanding update and make sure staff know the old description remains visible until it is corrected.
