Use sub-recipes without double-counting

Overview

• A Recipe can use another Recipe as a component.
• The child Recipe's unit cost is based on its own full batch cost divided by its Output quantity.
• The parent Recipe then uses only the requested quantity of that child output.
• This is useful for shared preparations such as sauces, flavoured cream cheese, cooked fillings, or dough batches.
• MiniTill checks the Recipe graph and blocks direct/indirect circular references.

When to use this

• Use a sub-recipe when the same prepared component is used by several menu Recipes and should have one consistent cost definition.

Step-by-step

1. Create the reusable child Recipe first.
2. Give it a realistic Output quantity/unit.
3. Open the parent Recipe and add the child Recipe as a component.
4. Enter how much child output the parent batch uses.
5. Review the nested breakdown to confirm the rolled-up cost.

Common mistakes

• Do not copy all child Ingredients into every parent Recipe if the preparation should be managed as one reusable sub-recipe.
• Do not use the child batch quantity as though it were one unit; use the child Output unit correctly.
• Do not create a dependency loop.

Troubleshooting

• If the sub-recipe cost is unavailable, fix the child Recipe first; the parent cannot calculate through a broken child.
• If quantities look inflated, check the child's Output quantity and the amount consumed by the parent.