Update a supplier product or recipe
Change the correct shared record, review its impact, and refresh the materials your team uses.
For: Owners and Editors with editing access
In this guide
Decide which record should change
Start with the actual change in the kitchen. If the same shared ingredient is being replaced everywhere it is used, update that ingredient. If only one dish uses a different product, create a separate ingredient record and change that dish’s selection instead.
This distinction matters because a shared ingredient can reach dishes through house recipes as well as directly. Renaming an ingredient does not create a second product record. Keep separate products distinct when their facts or usage differ.
- Open Ingredients and search for the current product or house recipe.
- Open its detail page and inspect Affected dishes and any compound recipes that use it.
- Choose Edit ingredient and compare the saved facts with the new source.
Enlarge screenshotReview and save the change
- Update the name, brand, supplier, and internal note as needed.
- Review Contains, May contain, and None choices against the replacement product or revised preparation.
- For a house recipe, update its components and inspect Combined allergen preview.
- Choose Review and save.
- Read the affected-dish confirmation, then choose Save and update dishes.
If no dishes are affected, the save may complete without that confirmation. When the change is a dish-specific recipe edit, use its Ingredients list and Save dish instead. Dish-level overrides should not be used to hide an incorrect shared ingredient record.
Check the result and replace old copies
Open affected dishes and confirm their resulting flags, variants, and notes. Check all named menus that use them. Saved changes update the records used by the hosted menu and newly generated outputs.
Generate fresh PDFs and replace printed sheets. An old download or laminated card cannot update itself. Tell staff what changed, where the current card is, and what still needs kitchen confirmation.
If the impact list is larger than expected, cancel before saving and reconsider whether you need a separate ingredient. If you already saved, inspect current records and version history before making another change. Correct the source record rather than repeatedly clearing individual output flags. Keep uncertain information marked for review until it is resolved.
Reviewed against the current Dishcard app. Screenshots use sample restaurant data.