Sub-recipes

A recipe inside a recipe: how it scales, what it costs, and what stops you deleting it.

Last updated: 2026-09-04

One cream, many cakes

Your crème pâtissière is a recipe of its own. In the éclairs and the fruit tart, type its name in the ingredient field. It goes in as a line, with an amount in the unit the cream recipe yields. Change the cream once, less sugar or a new vanilla, and every cake that uses it follows.

It scales to the amount used

The cream recipe makes 800 g and the tart uses 300 g. The app treats that as three eighths of a batch. Ingredients, cost, calories and allergens roll into the tart at that share. The cream’s own overhead and labour come with it. Tap the line to open the cream at exactly that amount. Its base yield stays as it was.

  • Ingredients at the share used
  • Cost with overhead and labour
  • Calories and allergens included
  • Scales again with the cake

Where the sub-recipes travel

Sending the tart to the shopping list asks whether to include the ingredients of its sub-recipes or only its own. Planning it asks whether the cream goes on the plan as a step of its own. An order carries only the tart. The cream is inside its cost and its ingredient list, not a separate item.

Not in the app

Two things a sub-recipe does not do:

  • Contain the recipe that contains it; loops are refused
  • Count towards total weight when it yields pieces; only weight or volume can be weighed

Common questions

Can I delete a recipe that other recipes use?

No. The delete is blocked, and the dialog names every recipe that contains it. Remove it from those first, or keep it. A sub-recipe costs nothing to leave in the library.