Skip to content
English
Sign in
  • There are no suggestions because the search field is empty.

What are the downstream impacts of deleting a recipe?

Deleting a recipe in Galley has permanent effects across menus, recipes, reporting, and integrations. Because recipes are core building blocks in Galley, it’s important to understand exactly what happens before you delete one.

What Happens When You Delete a Recipe in Galley

Deleting a recipe in Galley is permanent and impacts multiple areas of the system. Once deleted, a recipe cannot be restored.

Impacts of Deleting a Recipe

Recipe

  • The recipe page is no longer accessible.

  • The recipe cannot be used in other recipes or in menus.

  • Deleted recipes cannot be undeleted.

Menus

  • Menu items that referenced the deleted recipe remain in place.

  • These menu items no longer have a cost.

Recipe Items (Sub-Recipes)

  • If the deleted recipe was used as a sub-recipe, any recipe items referencing it are deleted.

  • The parent recipe remains, but without the deleted items.

API

  • Deleted recipes are no longer discoverable in the API.

  • API calls that previously returned the recipe will no longer include it.

Cycle Counts

  • Existing cycle counts that included the recipe remain unchanged.

  • The recipe will not be available in future cycle counts.

Best Practices Before Deleting a Recipe

  • Review menus to confirm the recipe is not needed, since deletion removes its cost data.

  • Check whether the recipe is used as a sub-recipe, as those references will be removed.

  • Confirm whether external systems rely on the recipe through the API.

  • Be aware that the recipe will not appear in future cycle counts.

Key Takeaway

Deleting a recipe permanently removes it from Galley and impacts menus, sub-recipes, the API, and cycle counts. Make sure to review dependencies before deletion to prevent gaps in costing or workflows.