Recipes#
A Recipe is a set of ingredients (and optionally other recipes and activities) that produces a yield.
Creating a recipe only requires a name. Everything else is optional and can be added later.
Components#
| Component type | What it is |
|---|---|
| Recipe Ingredient | An ingredient with an amount and unit |
| Sub-Recipe | Another recipe used as a component (e.g. “house vinaigrette” inside a salad recipe) |
| Recipe Activity | A labor task with a duration |
Yield#
Every recipe has a yield — a quantity and a unit. Example: “yields 10 servings.” The yield is what allows other recipes to know how much of this recipe they’re using.
Costing#
- Food Cost = sum of ingredient costs + food costs from any sub-recipes
- Labor Cost = sum of activity costs + labor costs from any sub-recipes
- Total Cost = Food Cost + Labor Cost
If any component is missing its amount, unit, or price, that component’s cost can’t be calculated, and neither can the whole recipe’s cost. Fillet shows a warning in this case.
Preferred Price#
By default, Fillet uses the lowest available price for each ingredient. In a recipe, you can override this for a specific ingredient by setting a Preferred Price — for example, to always use a specific vendor’s price for a key ingredient. This preference is per-recipe, so the same ingredient can have a different Preferred Price in each recipe it appears in.
Sub-Recipe cost contribution#
When a recipe is used as a sub-recipe, its cost contribution depends on how much of it is used relative to its yield. Example: if your vinaigrette recipe yields 1 L and costs $5 total, and you use 200 mL in a salad recipe, the salad gets $1 of that cost.