A recipe models the ingredients of a dish or formulation and nothing else. It answers "what do the ingredients cost the planet", which is the question that matters during menu and product development, before packaging, manufacturing sites and distribution exist.
That narrower scope is the point. A recipe is not an incomplete product, it is a different unit of work.
Find them under Products > Recipes.
Creating one
- Go to Products > Recipes and click 'New'.
- Give the recipe a name and a net amount. The net amount is what the impact figures are reported against, so it is worth getting right.
- Add your ingredients, searching the raw materials library the same way you would on a product.
- Enter a quantity for each.
The impact updates as you go. There is no separate calculate step.
What a recipe does not have
Recipes cover the Raw Materials life cycle stage only. They do not carry packaging, production sites, distribution, storage or consumer use, and they are not eligible for the manufacturing, baseline, forecast or targets screens. A recipe also does not count against your product allowance, because it is not a product.
Grades and reports
Each recipe carries a grade from A to G, calculated per kilogram, so two recipes of different sizes are still comparable.
The report is ingredient-focused: a contribution ranking showing which ingredients carry the impact, rather than the life cycle breakdown a product report gives you. You can export it as a one-page PDF summary to share with a chef, a supplier or a development team.
Turning a recipe into a product
When a recipe becomes something you actually make and sell, you do not rebuild it. On a product, use Import from recipe in the Raw Materials section to take a recipe's ingredients as a starting point, scaled to the product. The product then gains everything a recipe does not have: packaging, sites, distribution and end of life.