A Weekly Restaurant Photo Workflow for Menu Changes
A restaurant photo workflow connects menu changes to capture, editing, approval, and publication. Start with a recurring review of what changed, then assign a quiet capture window and a person who verifies the actual serving. The schedule below is a planning example; choose days and batch sizes that fit your kitchen.
DishVivid helps with single-photo manual adjustments, original comparison, and reviewed JPEG export, with optional AI candidates. It does not schedule kitchen work, synchronize menus, or automatically upload to POS systems or delivery platforms.
Stage 1: Review the changes before photographing
Identify new items, changed recipes, updated portions, packaging substitutions, and seasonal items returning to service. A recipe change may require a new photograph even when the dish keeps the same name.
Create a short shot list with the menu-item ID, display name, normal portion, included sides, service vessel, and kitchen reviewer. Record when each item becomes available and where its current photographs are used.
Do not infer complete allergen information from a photograph. Have the kitchen maintain recipe and allergen information separately; the image review can flag visible discrepancies, not establish safety.
Use the menu-photo audit guide to decide which existing photographs still match the menu before planning reshoots.
Stage 2: Prepare a repeatable capture station
Reserve a window your team can protect from service interruptions. Wednesday morning may suit one restaurant while another needs a different day or smaller batch. Prepare the surface, light, camera, and a plate stand-in before calling for the finished dish.
- Compare indirect window light or a suitable diffused lamp. Check mixed-light color casts and glare in a test frame.
- Use the actual tableware or takeout container for this item.
- Choose a viewpoint that reveals its identifying ingredients and full serving. Overhead can work for some bowls as well as flat dishes; it is not reserved for one category.
- Leave space for the intended crop and test the destination layout. A fixed margin percentage cannot guarantee every service-side crop.
- Ask the kitchen to follow its normal preparation and holding procedures. Photography is not a reason to change food-handling instructions.
There is no universal 90-second window for all food. Photograph promptly once the usual serving is ready and inspect it before clearing the plate. If setup delays change its appearance, prepare a new normal serving rather than adding shine or reconstructing food digitally.
The shoot checklist and phone workflow help make the capture handoff repeatable.
Stage 3: Select and edit a usable source
Transfer the original file and keep a backup. Check focus, included items, and crop room before editing; a technically poor source may need reshooting.
Open JPEG, PNG, or WebP up to 20 MB in DishVivid Studio. RAW, ProRAW/DNG, and HEIC require compatible external conversion first. Manual brightness, contrast, saturation, and crop adjustments run in the browser and need no account.
Make restrained adjustments while comparing the original. There is no dedicated manual white-balance, temperature, highlights, shadows, sharpening, denoise, or blur-repair control. Correct a strong color cast at capture or in appropriate external software; do not treat a brightness slider as selective shadow recovery.
You can first try the stock sample to learn the manual comparison and download steps. It is not a customer case or AI result.
Optional AI is a separate branch
Use manual editing when it is sufficient. AI requires sign-in and available edits; each generated candidate uses an edit. Check account and pricing before generating rather than assuming a free allowance or a particular checkout state.
AI can change ingredients, portions, containers, and textures. Review each candidate against the original and real dish, reject inaccurate outputs, and approve an acceptable candidate before export. A fidelity prompt does not guarantee the result.
Stage 4: Approve the dish and the final crop
Assign the person responsible for kitchen accuracy, even when someone else edits the photograph. Review the actual recipe and portion alongside the source and final image.
| Check | Decision |
|---|---|
| Item and portion | Piece counts, protein portion, and included sides match the ordering entry. |
| Ingredients | Garnish and sauces match the current recipe; visible discrepancies return to the kitchen reviewer. |
| Service format | Plate, packaging, and separately packed components reflect this order type. |
| Appearance | Colors and textures remain credible against the original and real serving. |
| Crop | The required food remains readable in the final destination preview. |
| Record | Filename, recipe version, reviewer, and approval date are saved. |
If the photo fails, choose another capture, reduce the edit, or reshoot. Do not approve a generated garnish because it looks attractive. Use the restaurant approval checklist for a consistent handoff.
Stage 5: Export, submit, and verify separately
Complete the dish checks and download the reviewed JPEG. Manual export needs no account. Current choices are Original, Delivery wide (1600 × 900), Delivery classic (1500 × 1200), and Social square (1200 × 1200). There is no custom 2048 × 1536 or WebP export.
Keep the untouched capture, reviewed export, and destination copies separately in your photo library. A JPEG is compressed, and an Original export is not a lossless archival replacement.
Check the ratio reference and the destination's current official requirements. Use another suitable tool for required resizing, conversion, or compression and inspect the resulting file. An editor preset does not establish acceptance.
Upload through the relevant website, POS, or merchant portal. Record prepared, submitted, approved, and published states separately. Check the customer-facing page to confirm the right photograph appears on the right item; publishing times and moderation are outside DishVivid's control.
A hypothetical weekly plan
Suppose a bistro introduces an autumn squash risotto. The example below illustrates responsibility and sequence, not a customer result or promised turnaround.
| When | Owner | Handoff |
|---|---|---|
| Monday menu review | Chef and manager | Confirm the normal risotto portion, sage garnish, included sides, and launch date. |
| Wednesday capture window | Photographer and kitchen lead | Photograph the ordinary serving after preparing the light and camera. Keep the source. |
| Thursday edit and review | Editor and kitchen approver | Make modest manual adjustments, inspect the original, and download a reviewed JPEG. |
| Before launch | Menu administrator | Prepare destination files, submit them separately, and record the actual status. |
| After launch | Manager | Check the live item and retire superseded photographs. |
If the recipe changes on Thursday, the earlier photo approval no longer settles the new serving. Update the photograph or hold publication until the image and menu agree.
Common workflow failures
Photographing under difficult mixed light: Compare another station or simplify the sources. Do not assume every heat lamp has the same color or that infrared alone explains a visible cast.
Using a test-batch portion: Ask for a normal order before capture. More elaborate trial plating can misrepresent the production recipe.
Tight crops without destination review: Test the final page or merchant preview rather than relying on a universal border.
Treating AI as a repair guarantee: If the original lacks focus or important detail, reshoot. Generated plausible texture is not proof of the actual dish.
Losing the source after handoff: Verify the stored original and backup rather than relying on a reduced chat copy.
Forgetting retirement: When an item or recipe ends, update its live placements and mark older files inactive. The seasonal workflow covers that step.
Start with one manageable session
Choose the smallest batch your team can prepare, capture, and review carefully. Track time spent, missed handoffs, failed submissions, and incorrect live placements in your own process; no universal batch size or publication speed is established here.
Open one usable source in DishVivid Studio, make a restrained edit, compare it with the original, and download after review. A repeatable schedule makes the work easier to inspect, but it does not guarantee platform approval, search rankings, or increased orders.