Skip to main content

Yield-Based Recipes: Using Weight and Volume Outputs

Yield-Based Recipes: Using Weight and Volume Outputs Why: Yield mode is perfect for creators who use Thermomix, make bulk sauces and dips, or prefe...

Written by Ken Truesdale

Platform 2 Guide — This article applies to the new platform. Looking for classic platform docs? Browse the Platform 1 collection.

Why: Yield mode is perfect for creators who use Thermomix, make bulk sauces and dips, or prefer measuring recipe output by weight or volume rather than servings.

Navigate: App Station > Content Library > Recipes > [Recipe] > Output Type

Quick Start

  1. Open the Recipe Editor for your desired recipe.

  2. Find the Output Type toggle above the servings/yield section.

  3. Select Yield.

  4. Enter the yield amount (e.g., 500) and unit (e.g., g, cups, ml).

  5. Save your changes.


What Are Yield-Based Recipes

Yield-based recipes allow you to define the output of a recipe as a physical quantity, such as weight or volume, rather than a number of servings. This is particularly useful for recipes that don't divide neatly into servings. For example, a hummus recipe might yield 500g total, or a sauce might produce 2 cups.

In contrast, traditional servings-based recipes are anchored to a number of portions, which can be limiting for certain types of recipes. Yield mode lets you express the output naturally, making it easier for your members to understand and use.

When to Use Yield Mode

Yield mode is best suited for:

  • Recipes from appliances like Thermomix that produce a measured output.

  • Bulk condiments and sauces where the quantity is more relevant than the number of servings.

  • Doughs and batters measured by weight.

  • Any recipe where the output is better described by weight or volume than by portion count.

You typically do not need yield mode for standard meals that divide into servings or baked goods sold by the piece.

How to Set Up a Yield Recipe

Setting up a yield-based recipe is straightforward. Follow these steps:

  1. Open the Recipe Editor in App Station.

  2. Locate the Output Type toggle above the servings/yield section.

  3. Select Yield to switch from the default servings mode.

  4. Enter the yield amount (e.g., 500) and the unit (e.g., g, cups, ml).

Note: Existing recipes default to servings mode, and nothing changes until you explicitly switch to yield mode.

How Nutrition Works

In yield mode, nutrition is calculated per unit of yield (e.g., per gram) instead of per serving. For instance, if a recipe makes 500g and has a total of 1000 calories, it will display as 2 calories per gram.

If you choose to override nutrition values, those values will also represent per unit of yield, maintaining consistency across your recipes.

How Scaling Works

When scaling is enabled, members can adjust the yield amount (e.g., changing from 500g to 250g), and the ingredient quantities will scale proportionally. The scaling control will show the yield unit instead of servings, making it intuitive for members to adjust based on the desired output.

How Meal Plans Work

You can add yield-based recipes to meal plans and specify how much yield to use (e.g., 250g of a 500g recipe). This is particularly useful for batch cooking, where you might batch the full 500g and then portion out 125g servings across multiple meals.

Shopping lists will also scale correctly based on yield amounts, ensuring that members have the right quantities of ingredients for their planned meals.

What Members See

Members will see labels like "Makes 500 g" instead of "4 servings." When they interact with yield-based recipes, scaling controls will display yield units, and nutrition will show as "per g" or "per cup." This allows members to engage with the content naturally without needing to understand the underlying differences between yield and servings.

Tips

  • Use consistent units within your app (e.g., grams OR cups, not both).

  • Enter the total yield of the recipe as written to avoid confusion.

For more information on related features, check out these articles:

Did this answer your question?