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 in terms of a physical quantity, such as weight or volume, rather than servings. This is particularly useful for recipes that do not divide neatly into servings. For example, a hummus recipe might produce 500g total, or a sauce might yield 2 cups.

In contrast, traditional servings mode focuses on the number of portions, which may not accurately represent the output for certain types of recipes. Yield mode lets you express the output more naturally, making it easier for your members to understand how much they will get from a recipe.

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 total volume or weight is more relevant than portion count.

  • Doughs and batters measured by weight.

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

However, yield mode is not needed for:

  • Standard meals that divide neatly into servings.

  • Baked goods sold by the piece.

How to Set Up a Yield Recipe

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

  1. Open the Recipe Editor for your desired recipe.

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

  3. Select Yield to switch from servings mode.

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

  5. Save your changes.

Note: Existing recipes default to servings mode. 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 override nutrition values for a recipe, those values will also represent per unit of yield, maintaining consistency in how nutrition is presented.

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 display the yield unit instead of servings, making it intuitive for members to understand how much they are adjusting.

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 the yield amounts specified in the meal plans.

What Members See

Members will see the output displayed as "Makes 500 g" instead of "4 servings." The scaling controls will show yield units, and nutrition information will be presented as "per g" or "per cup." This allows members to interact with the recipes naturally without needing to understand the difference between yield and servings.

Tips

  • Use consistent units within your app (either grams or cups, not both).

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

By using yield-based recipes, you can provide your members with clearer, more relevant information about the recipes they are using, enhancing their overall experience with your app.

Did this answer your question?