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 |
|
RME Menu Recipe Changes Displayed as 'Added' or 'Removed' in Menu Cycles 'Added' and 'Removed' recipes from RME menus are now indicated in the Menu Cycles app |
Improvements to Allergen and Intolerances Report The Allergen and Intolerances Report has additional intolerance values and an updated layout |
RME Recipe and Buffet Menu 'Selling Price' to be Transmitted to Menu Cycles RME recipe and buffet menu selling prices will be displayed as the default selling prices on the Planning screen |
New tickbox that will hide all recipes will a planned quantity of '0' on the Planning screen |
Release date for all features: March 29th 2023
Menu Recipes Added/Removed in RME Menus Displayed as 'Added' or 'Removed' in Menu Cycles
- Enabled by Default? - Yes
- Set up by customer Admin? - No
- Enable via Support ticket? - No
- Affects configuration or data? - Yes
- Roles Affected: - Menu Cycle creators and planners
What's Changing?
When a menu in the Recipe and Menu Engineering (RME) app has recipes added or removed and that menu is used in a menu cycle, the menu change is transmitted to local menu cycles on future dates and to 'published' and 'new central' menu cycles. In the Planning, Post-Production and Nutrition screens, these recipes will now be indicated by 'Added' and 'Removed' badges.
Reason for the Change
To make RME menu changes more obvious to Menu Cycles users who use RME recipes and menus to create menu cycles.
Customers Affected
All customers using the Menu Cycles app.
Release Note Info/Steps
On the Planning Screen
For recipes that have been added to a menu cycle:
- The recipe displays the ‘ADDED’ badge
- The recipe is saved in Planning with a default value of '0'
- The menu recipe is fully functional on the Planning screen
- 'Added' Buffet menu recipes will be included in the Buffet menu ratio calculation once the recipe and the Buffet menu have a Planned Quantity of more than 0
For recipes that have been removed from a menu cycle:
- The recipe displays the 'REMOVED' badge
- The row for the removed recipe is disabled so no values can be entered or saved in it
- The ‘three dots’ menu and the ‘+ Tariff’ button on the row are not displayed
- The ‘expand arrow' remains enabled so tariffs can be seen for the removed item
- The removed recipe is excluded from the meal period and daily totals for Planned Quantity, Total Costs, Projected Revenue and GP%
This will happen for menus that are scheduled on a date/time in the future from when the change(s) are made in RME. After 14 days, the badges will disappear. 'Removed' items will no longer be displayed.
Fig.1 - Local menu cycle, 'Added' and 'Removed' recipes and updated figures
On the Post-Production Screen
- 'ADDED' and 'REMOVED' badges will display
- Rows for removed recipes are disabled so no values can be entered or saved in them
- Removed recipes are excluded from meal periods and daily totals
Fig.2 - Local Menu Cycle, future date in Post-production with 'Added' and 'Removed' menu recipes
No indication of ‘added/removed’ recipes will display in the Calendar or Meal Period views.
Removed recipes will be filtered out and added ones will display without the 'ADDED' badge. This applies to both ‘detailed’ and ‘expanded’ views. The most up-to-date version of the menu will display in these views on future dates.
Fig.3 - 'Added' and 'Removed' badges are not displayed in the Meal Period view
Publishing a Central Menu Cycle to New Locations
Menus that are part of the ‘original published’ central menu cycle and are then later modified in RME will be published to new locations with the most up-to-date version of the menu and no ‘badges’.
Copying Menu Cycles
When a menu cycle is copied, any 'removed' recipes will not be copied. Any modified menus will exist in the copied menu cycle as the most up-to-date version when the menu cycle is copied.
Unpublished, archived and locked menu cycles are not impacted by RME menu changes.
Additional Resources
Allergen and Intolerances Report, Additional Values, Layout Changes
- Enabled by Default? - Yes
- Set up by customer Admin? - No
- Enable via Support ticket? - No
- Affects configuration or data? - Yes
- Roles Affected: - Compliance managers for Allergens and Intolerances information
What's Changing?
Allergen and Intolerances Report: additional values, layout changes.
Reason for the Change
Increased information to support local compliance with allergen and intolerance information for consumers.
Customers Affected
All users of local menu cycles.
Release Note Info/Steps
Allergen and Intolerances Report: Both the Excel and PDF reports have been changed to display the columns mentioned below. Common shading has been added to ‘parent’ and ‘child’ intolerance values when displayed in the reports - see Fig.4 below.
The 'description' column has been removed from the PDF version of the report.
In the Excel version of the report, Spelt (Wheat) and Kamut (Wheat) have been removed.
Intolerance value columns, in the order they will be displayed on both reports:
1. Celery
2. Crustaceans
3. Eggs
4. Fish
5. Cereals containing Gluten
6. Barley
7. Oats
8. Rye
9. Wheat
10. Lupin
11. Milk
12. Molluscs
13. Mustard
14. Tree Nuts
15. Almonds
16. Brazil nut
17. Cashew nut
18. Hazelnut
19. Macadamia nut
20. Pecan nut
21. Pistachio nut
22. Walnut
23. Peanuts
24. Sesame
25. Soya
26. Sulphur dioxide/sulphites
Fig.4 - Allergen and Intolerances Report, PDF version, new layout with parent/child intolerance values shaded
RME Recipe and Buffet Menu 'Selling Price' to be Transmitted to Menu Cycles
- Enabled by Default? - Yes
- Set up by customer Admin? - No
- Enable via Support ticket? - No
- Affects configuration or data? - Yes
- Roles Affected: - Recipe and menu selling price managers
What's Changing?
The RME recipe and buffet menu 'selling price' will now be transmitted to Menu Cycles. When recipes and buffet menus are added to the menu cycle 'Meal Period' calendar, the RME selling price for each item will be displayed in the Planning screen in the Menu Cycles application.
Reason for the Change
Reduces the need to change selling prices within menu cycles, both centrally and locally.
Customers Affected
All customers using the Menu Cycles app.
Release Note Info/Steps
For recipes, the 'selling price' field is Sell Price (Inc.) - under 'Default FnB Site Sell Price' - see Fig.6.
For buffet menus, the 'selling price' field is Selling price - see Fig.6.
To access these fields in RME, the User Group permission Allow suggested sell price must be applied.
User groups with this permission should be limited to users who can be trusted to not change the PLU because such changes have caused POS issues in the past for some customers.
Fig.5 - RME Recipe permission to access recipe selling price field Default FnB Site Sell Price, Sell Price (inc.)
The RME selling prices will be displayed as the default Sell Price in Menu Cycles - see Fig.6.
The other default selling price-related values in menu cycle planning have not been changed. For easy reference, these are:
- Default menu cycle tariff: Standard Tariff
- Default tax associated with default tariff: VAT
- Default ‘Price Model’: Fixed
Limitations on Selling Price Updates
When the recipe/buffet menu selling price is updated in RME, the existing price in the Menu Cycles database will be updated unless it has already been saved in the Planning screen in Menu Cycles itself. In this instance, the selling price will not be updated as a consequence of it being updated in RME.
Fig.6 - RME (top images) and Menu Cycle (bottom image) Recipe and Buffet Menu Selling Prices
The selling price calculation within the Planning screen has not been changed. When a selling price is entered in Planning, this selling price is considered to be ‘gross’ (includes tax). When revenue is calculated in the Planning screen, this figure is ‘net’ (without tax). These calculations will not change. The RME selling price will be handled within the menu cycle as a ‘gross’ selling price, just as a manually entered ‘fixed’ selling price is currently handled.
Hide 'Unplanned' Items in Planning: Tickbox
- Enabled by Default? - Yes
- Set up by customer Admin? - No
- Enable via Support ticket? - Yes
- Affects configuration or data? - No
- Roles Affected: - Planning users
What's Changing?
A new tickbox to hide unplanned recipes has been added to the Planning and Post-Production screens.
Reason for the Change
Increases ease of use by hiding items with a planned quantity of '0' so only items relevant for the day are displayed.
Customers Affected
All customers using the Menu Cycles app.
Release Note Info/Steps
In the header of the Planning and Post-production screens, a new Hide Unplanned tickbox has been added.
By default, the tickbox will not be selected and all items, including those with a planned quantity of '0', will be displayed - see Fig.7.
When selected, items with a planned quantity of 0 will be hidden, though buffet menus with '0' planned quantity will remain displayed - see Fig.8.
Fig.7 - Hide Unplanned' tickbox not ticked - all recipes displayed
Fig.8 - Hide Unplanned' tickbox is ticked - recipes with planned quantity of '0' are not displayed. Buffet menus with '0' planned quantity are still displayed
Comments
0 comments
Please sign in to leave a comment.