When a dish changes, start with the menu revision—not the photo library. List every item that changed, find each place its picture appears on your website, and compare the image with what the kitchen serves now. Replace or remove any picture that could lead a guest to expect a different dish.
A photo can be outdated even when the dish name stays the same. A new protein, different side, smaller presentation, or removed topping may make the old image misleading. The audit below gives the kitchen, front-of-house team, and person who edits the site a shared way to find and fix those mismatches.
Map changed dishes to every website image
Ask the person responsible for the menu to provide the current item list and a summary of recent changes. Include items that were renamed, removed, added, or changed without a name change. A kitchen lead should confirm what is actually prepared, including standard sides and the usual plating.
Next, ask whoever manages the website and ordering menu to identify where each affected image appears. Start with the menu page and item detail pages, then check homepage features, category banners, specials, and any ordering pages linked from the site. A dish may appear in a promotion long after its main menu image has been updated.
Search by both the old and current dish names. Also look for pictures reused under a category name or attached to an older version of an item. If the ordering page is separate from the main site, check both. An edit in one place should not be assumed to update the other.
Give each image location a simple identifier: the page address, the item name, and a note such as “homepage special” or “ordering item detail.” Record the person who can edit it. If an outside provider controls a page, note whom to contact and how changes are submitted.
Use the table as a working record. Each row represents an image location, not just a dish. A dish shown in two places needs two rows because each location may require a separate correction and live check.
| Image location | Current dish check | Decision | Owner and status |
|---|---|---|---|
| Menu page: roasted chicken | Photo shows fries; dish now comes with rice | Replace or remove photo | Site editor: awaiting approved image |
| Homepage: seasonal salad feature | Dish is no longer sold | Remove feature or update it | Manager: change requested |
| Ordering page: vegetable bowl | Photo matches standard ingredients and plating | Keep; check again after next change | Kitchen lead: approved |
These rows are illustrative. Your record should also include the date checked and, where useful, a link to the approved replacement file. Keep the record somewhere the menu owner and site editor can both access.
Compare the picture with the dish guests receive
Have the kitchen lead compare each image with the current recipe and a normally plated dish. Look at the main ingredient, visible toppings, sides, sauce, portion presentation, and the vessel or packaging shown. For a customizable item, check whether the picture represents the standard version or whether it shows additions a guest must choose separately.
Use three decisions: keep when the image reasonably represents the current standard dish; replace when the dish is still sold but the image creates a material wrong expectation; and remove when the dish is gone or no accurate replacement is ready. An older garnish that varies slightly may not need the same urgency as a photo showing a side that no longer comes with the meal.
For a hypothetical example, a roasted chicken plate used to come with fries and now comes with rice. The name and chicken are unchanged, but the menu photo still prominently shows fries. The kitchen confirms rice is the standard side and fries are not included. Mark that image for replacement or removal, even if the text already says rice. A guest scanning the page may rely on the picture before reading the description.
The same judgment applies to an image showing extras. If a bowl is pictured with avocado that is no longer included, check whether the page clearly distinguishes the extra from the standard bowl. If the image still gives a misleading impression, use a standard-dish photo or remove it. Do not assume a small note elsewhere on the site fixes every image.
Balance accuracy against speed. A new professional shoot may produce a more consistent look, but waiting for it can leave an incorrect image visible. A clear, approved current photo may be a useful interim choice if it represents the dish honestly. If no suitable image is available, removing the old one is often the cleaner temporary decision.
Replace or remove images without creating new mismatches
Before editing, confirm which file belongs to which dish and where it will be used. Give replacement files recognizable names and keep the approved version separate from older files. The editor should update every recorded location, not just the first page found.
For the chicken example, the kitchen lead approves a current photo showing chicken with rice. The editor replaces the old image on the menu page, then checks whether the ordering item and homepage feature use the same or separate image. If the ordering page requires its own edit, that is a second task. If the homepage feature is for an expired special, removing the feature may be more appropriate than changing its photo.
Check the surrounding text at the same time. The dish name, included side, and any visible description should agree with the image and current menu. If the photo depicts a particular option, make sure the page does not present that option as the only version when guests must make a selection. Ask the kitchen lead to resolve any disagreement before publication.
If your editor allows a preview, use it to check cropping and placement before publishing. Look at a narrow mobile view as well as a larger screen. A crop that cuts out the rice could make the new chicken photo less useful; a category tile that enlarges an old detail could still suggest the wrong side. A preview is a visual check only. It should not trigger a payment, guest message, or courier dispatch.
Some pages may use a shared image, while others may have separate files or separate editing access. Ask your provider how image changes reach each page and whether there is a preview. Do not count an update as complete until you have checked the places guests can actually see.
Record approval and check the live page
Use a short approval path rather than sending pictures around without a decision. The kitchen lead confirms the dish and image; the manager approves any customer-facing change; the site editor records what was published. One person may fill more than one role, but each decision should be clear.
- Record the dish, image location, mismatch, chosen action, and person responsible.
- Attach or identify the approved image, or note that the image will be removed.
- Check the preview, if available, for the correct picture, text, and crop.
- Publish the change and open each affected live page on a phone and a larger screen.
- Record the date and result. If the old image still appears, investigate with the site provider and recheck before closing the task.
Open the page as a guest would, rather than relying only on the editing screen. Follow the link from the main site to the ordering page if there is one. Check that the correct item is still available and that its image and description agree. This visual review does not require placing a real order.
A live-page check catches visible problems at that moment; it does not guarantee that every guest’s device will immediately show the same version. If an old picture persists, ask the provider about publishing and image refresh behavior, then document when and where you saw it. Keep the task open until the affected location displays the intended result.
Make the audit part of the menu-change handoff. When the kitchen submits a revision, the menu owner flags affected photos and the editor checks each recorded location. A quick review after a seasonal change is easier than trying to remember months later which pictures were reused.
For a broader review of editing control, see the restaurant website builder comparison. Also check who controls your site address with the domain ownership guide, especially if an outside provider handles changes.
Next step: Use the table and checklist on your latest menu revision. If you need a different setup, explore Fleksa’s restaurant website and online ordering options, then ask Fleksa about availability and setup for your US location.
Frequently asked questions
Which menu photos should I check first?
Start with removed dishes and changes to prominent ingredients, included sides, or toppings. Then check images in high-visibility locations, including the homepage and ordering item pages.
Should I remove a photo if I do not have a replacement?
If it materially misrepresents the dish, removing it is a practical temporary option. Keep the item description accurate and record who will provide and approve a current image.
How often should I audit menu images?
Check affected images whenever the menu changes. A wider periodic review can catch reused photos and old promotions that were missed during individual edits.
