Summary
Select the release feature from the table below to be taken directly to that section of the release note.
Feature 1 | Feature 2 | Feature 3 | Feature 4 | Feature 5 |
Recipe carbon calculation using recipe ingredient carbon values is now available |
GET/recipeCO2, Renamed Property and Addition of two New Properties Recipe CO2 renamed, AutoTotalRecipeCO2Value |
New property for GET and POST/ingredientsalternates requests Supplier Order UoM added to these requests |
Nutrition Report, Recipe Ingredients A new report that shows each recipe ingredient's nutrition and its contribution to the recipe |
These values are copied from the parent but were previously not visible on the UI |
Release date for all features: 11th January 2023
Recipe CO2 Calculation
- Enabled by Default? - No
- Set up by customer Admin? - No
- Enable via Support ticket? - Yes
- Affects configuration or data? - No
- Roles Affected: - Sustainability managers with an interest in recipe carbon value
What's Changing?
Recipe carbon calculation using recipe ingredient carbon values is now available.
Reason for the Change
To increase access to recipe carbon footprint information so that hospitality businesses can benchmark their current food-related carbon footprint.
Customers Affected
Optional. Available to all customers.
Release Note Info/Steps
Configuration
For the recipe carbon calculation to be available, the recipe 'CO2' screen (aka 'tab') must be enabled.
Raise a case with Fourth's support team for this request.
New 'Recipe' permissions have been added to control the viewing and editing of the Recipe CO2 tab fields. These permissions should be enabled for user groups that require access to the new tab. These permissions are visible once the Recipe CO2 tab has been enabled.
Fig.1 - New user group permissions to 'view' and 'edit' the Recipe CO2 tab
Data Requirements
1. Recipe ingredient must have a weight value as one of its supply quantity definitions. This weight value can either be the 'base supply quantity' or one of the conversions.
Fig.2 - Avocado with weight value (2 x 150 grams) as a conversion of the base Supply Quantity, 1 x 2 each
To ensure that an ingredient has a weight value, there is a 'global database setting' which can be enabled to make ingredient weight mandatory. Raise a case with Fourth's support team to enable this setting.
2. Recipe ingredient must have an ingredient CO2e value. The ingredient KG CO2e per KG must be a number greater than or equal to 0 and less than 1000.
Non-food ingredients are ignored in the CO2 calculations.
For the recipe calculation to be accurate, the ingredient CO2e value should be KG of CO2e per KG of the ingredient. The ingredient field name 'CO2e per KG' has been changed slightly to clarify this expectation.
Fig.3 - Ingredient KG CO2e per KG field is located on the Supplier Spec tab
3. Sub-recipes (recipes used as recipe ingredients) and the main recipe should have a cooked weight in a weight 'unit of measure'. Like recipe ingredients, this weight value can either be the 'base cooked weight' or a conversion of the cooked weight.
Please note that CO2 will work like recipe ingredient cost when using' alternate ingredients'. The alternate that is the #1-ranked alternate when the recipe is created is the ingredient that will be referenced for the recipe ingredient's KG of CO2e per KG value.
When an alternate ingredient is promoted (via the UI) to become the parent ingredient, the parent ingredient KG of CO2e per KG value is automatically updated. The recipe ingredient CO2 is not updated in this scenario.
Coming soon (March 2023): When the link/action to 'update all recipes to use #1 alternate' is selected, the recipe ingredient CO2 value will be updated, just as its ingredient cost is updated.
Additional Resources
October 26th 2021, Release Note: RME: Change Alternate Ingredient to the Parent Ingredient
Recipe CO2 tab
Recipe ingredient names and quantities are auto-populated on the CO2 tab; these values are taken from the recipe's 'Ingredients' tab. The 'recipe ingredient, kg CO2e value' is the amount of CO2e represented by the amount of the ingredient in the recipe. If this column displays a 'dash' value, it means that the recipe ingredient is missing one of the variables required for the calculation.
Fig.4 - Recipe CO2 tab with auto-calculated CO2e values and 'Auto-calculate' selected as the value to use in other recipes, reports and the API response for GET/recipes
Two calculation modes are available on the Recipe CO2 tab: manual and auto-calculate. By default, all recipes are set to auto-calculate mode.
The auto-calculated recipe CO2 values that are displayed on the Recipe CO2 tab are:
1. KG of CO2e for the total recipe
2. KG of CO2e per serving
Either the auto-calculated or manual KG CO2e Total Recipe value can be selected for use in other recipes, in reports and in the GET/recipes API response. See the Auto-calculate 'radio button' in Fig.4 (above).
Fig.5 - GET/recipes response showing Total Recipe CarbonDioxideValue which is sourced from either the auto-calculated or manual value, depending on the selection in the Recipe CO2 tab (see radio button in Fig. 4, above)
Supported recipe types are Standard, Batch and Choice. CO2 values for a 'Choice' recipe are taken from the Choice Recipe's 'default' recipe ingredient.
When enabled for the first time, it will take some time for the recipes' auto-calculated CO2e values to appear.
Triggers for recalculation - changes to:
- Parent ingredient's KG CO2e per KG value
-
Recipe ingredient changes made within the recipe
-
Recipe ingredient UOM
-
Recipe ingredient quantity in recipe
-
Recipe ingredient ‘Wastage Removed’ status (true/false)
-
-
Recipe's cooked weight conversion
-
Impacts recipes that use this recipe as a recipe ingredient (aka ‘sub-recipe) and that use the conversion.
-
-
Change in recipes' servings number
-
Other triggers
-
Mass delete - removes recipe ingredient(s)/sub-recipes from specified recipes
-
Mass ‘Replace in Recipes’ - replaces specified ingredient or sub-recipe with another ingredient/sub-recipe OR the same ingredient/sub-recipe in a different quantity
-
Recipe ingredient 'wastage removed' and its impact on CO2 value in recipe
1. When 'wastage removed' = false, the CO2 calculation uses the ingredient quantity that is specified in the recipe without any change.
2. When 'wastage removed' = true, the CO2 calculation uses the ingredient quantity that is specified in the recipe plus wastage.
Interaction between 'KG CO2e Total Recipe' field on Recipe 'Details' tab and Recipe 'CO2' tab
When Recipe > Details > Recipe CO2 fields are enabled and when the Recipe CO2 tab is not enabled, then the Recipe CO2 fields (value and ranking) will be displayed on the Recipe Details tab.
Fig.6 - Recipe CO2 manual fields located on the Recipe Details tab
However, when the Recipe CO2 tab is enabled, the Recipe CO2 fields that are located on the Recipe Details tab will be hidden. The manual value KG CO2e Total recipe value will display on the Recipe CO2 tab and not on the Recipe > Details tab (see Fig. 7, below). The value populated in the manual field KG CO2e Total recipe will be displayed on the Recipe CO2 tab.
Fig.7 - Recipe CO2 manual field KG CO2e total recipe which was located on the Recipe Details tab is now displayed on the Recipe CO2 tab and is populated with the manually entered value from the Recipe Details tab
If there is manually entered data in the Recipe CO2 fields that are located on the Recipe Details tab, this data will not be removed when the global setting that hides these fields is enabled. The data will persist in the database.
Note: In the near future the 'CO2 Ranking' field will also display on the Recipe CO2 tab when the above configuration is in place.
Additional Resources
The simple formula to cut your diet’s carbon footprint - BBC Food
GET/recipeCO2, Renamed Property and Addition of Two New Properties
- Enabled by Default? - Yes
- Set up by customer Admin? - No
- Enable via Support ticket? - No
- Affects configuration or data? - No
- Roles Affected: - if applicable
What's Changing?
Within the response from GET/recipeCO2, one existing property name has been changed; two new properties have been added.
If there is an existing integration that uses the property "RecipeCO2Value" from this response, the change in property name will be a breaking change. Please check and update any integrations after the RME release on January 11th, 2022.
Reason for the Change
To increase recipe-related carbon data available in the API to support restaurants and their 'Life Cycle Analysis' partners to aid CO2e benchmarking.
Customers Affected
All customers using the GET/recipeCO2 request.
Release Note Info/Steps
'RecipeCO2Value' property name has been changed to 'ManualTotalRecipeCO2Value'
Properties added: 'AutoTotalRecipeCO2Value' and 'RecipeServings'
Old response
[
{
"RecipeStarChefKey": "0030702",
"RecipeGuid": "6c3fec7d-97c9-48f8-b84e-13bb179b9fa6",
"RecipeName": "Roast Lamb Salad",
"RecipeCO2Value": "55.5",
"RecipeCO2Ranking": "High"
}
]
New response
[
{
"recipeStarChefKey": "0030702",
"recipeGuid": "6c3fec7d-97c9-48f8-b84e-13bb179b9fa6",
"recipeName": "Roast Lamb Salad",
"manualTotalRecipeCO2Value": "55.5",
"autoTotalRecipeCO2Value": "55.5",
"recipeServings": "5",
"recipeCO2Ranking": "High"
}
]
Supplier Order UoM Property Added to GET and POST/ingredientsalternates requests
- Enabled by Default? - Yes
- Set up by customer Admin? - No
- Enable via Support ticket? - No
- Affects configuration or data? - No
- Roles Affected: - if applicable
What's Changing?
The ingredient property 'Supplier Order UoM' has been added to the GET and POST/ingredientsalternates requests.
Reason for the Change
To increase alternate ingredient fields that are available for API users.
Customers Affected
All customers using the requests GET/ingredientsalternates and POST/ingredientsalternates.
Release Note Info/Steps
If included in the payload, the property value must match one of these values: EA / CS / KGM. If the value does not match, an error will be generated.
Property name and example value: "supplierOrderUom": "KGM",
Nutrition Report, Recipe Ingredients
- Enabled by Default? - No
- Set up by customer Admin? - No
- Enable via Support ticket? - Yes
- Affects configuration or data? - No
- Roles Affected: - Nutritionists and Data managers who are troubleshooting recipe nutrition values
What's Changing?
A new report that shows each recipe ingredient's nutrition contribution to the recipe.
Reason for the Change
To increase ease of use when troubleshooting recipes to identify which recipe nutrition variables might be preventing the recipe nutrition from calculating.
Customers Affected
Optional. Available to all customers.
Release Note Info/Steps
This report is available on request. Raise a case with Fourth's support team for the report to be enabled.
Report name: Recipe Ingredient Nutrition
Download as: Excel
Fig.8 - Recipe Ingredient Nutrition report
Data Included in this Report
Recipe level values
Recipe StarChef Key
Recipe Name
Recipe Ingredient values
StarChef Key
Name
Product Type
Quantity in Recipe
UOM in Recipe
Order in Recipe
Wastage Removed
Wastage Percentage
Weight value number
Weight UOM
Recipe Ingredient Nutrition values for the amount of the ingredient used in this recipe
Energy (kcal)
Energy (kJ)
Total Fat
saturates
mono-unsaturates
poly-unsaturates
Carbohydrate
starch
total sugars
Protein
Fibre (AOAC)
Sodium (mg)
Salt (mg)
Data details
Data Source
Source Info
Cooked State
Alternate Ingredient, 'Transfer/Requisition Status' and 'Item Vatable' to Display when Alternate is Created Via 'Copy Parent Values' Method
- Enabled by Default? - Yes
- Set up by customer Admin? - No
- Enable via Support ticket? - No
- Affects configuration or data? - No
- Roles Affected: - if applicable
What's Changing?
When an alternate ingredient is created using the 'copy parent values' method, two properties that were previously saved in the database but not displayed on the UI will now display: 'Transfer/Requisition Status' and 'Item Vatable'.
Reason for the Change
To increase ease of use by aligning values displayed on the UI with those saved in the database.
Customers Affected
All customers creating alternate ingredients manually via the RME UI.
Release Note Info/Steps
When a new alternate ingredient is created via the UI using method 'copy parent values', these values - 'Transfer/Requisition Status' and 'Item Vatable' - which are copied from the parent, will be displayed on the UI.
These fields are editable if the user has permission to create/edit alternate ingredients.
If the alternate is created in the UI using method 'copy and inherit parent values', these values will not be editable in the alternate ingredient record because they will be inherited from the parent ingredient.
Comments
0 comments
Please sign in to leave a comment.