What’s Changing?
Within the Menu Cycles app buffet menu items can be planned and sold. On receipt of post-production information, as input in the Menu Cycles application, the composition of the buffet for each day is utilised for accurate depletion of inventory and assignment of revenue in the Inventory product.
Release Date: 27th August 2019
Reason for the Change
Depletion of Inventory for buffet menu items has always been problematic as accurate data on the composition of this type of menu item has not been available. With the introduction of the Menu Cycles application this data is now captured and can therefore be used for depletion and revenue assignment based on utilisation.
Customers Affected
This change is available to customers using Inventory with the Menu Cycles application.
Please liaise with your Fourth contact to have this functionality enabled.
Release Notes
The Menu Cycles application allows for actual production quantities for each recipe within a buffet to be captured, using this information it is possible to more accurately deplete inventory.
When post-production data is saved within the Menu Cycles application it is sent to Inventory and depletion of inventory based on the produced quantity will occur.
When sales data is received for buffet menu items, and post-production data exists, the revenue will exist at the buffet menu item level but for reporting purposes it is also distributed to the ingredient level based on the recipe production received in post-production data. As the composition of buffet menu items can vary, the distribution is applied on a daily basis.
A pre-requisite is for Menu Orchestration to be enabled in RME so that Inventory can receive and create buffet menu items for processing of post-production and sales data against these.
Within the Menu Cycles app buffet menu items can be planned and sold. On receipt of post-production information, as input in the Menu Cycles application, the composition of the buffet for each day is utilised for accurate depletion of inventory and assignment of revenue in the Inventory product.
Release Date: 27th August 2019
Reason for the Change
Depletion of Inventory for buffet menu items has always been problematic as accurate data on the composition of this type of menu item has not been available. With the introduction of the Menu Cycles application this data is now captured and can therefore be used for depletion and revenue assignment based on utilisation.
Customers Affected
This change is available to customers using Inventory with the Menu Cycles application.
Please liaise with your Fourth contact to have this functionality enabled.
Release Notes
The Menu Cycles application allows for actual production quantities for each recipe within a buffet to be captured, using this information it is possible to more accurately deplete inventory.
Fig.1 – Quantities Produced values within a buffet plan
When post-production data is saved within the Menu Cycles application it is sent to Inventory and depletion of inventory based on the produced quantity will occur.
When sales data is received for buffet menu items, and post-production data exists, the revenue will exist at the buffet menu item level but for reporting purposes it is also distributed to the ingredient level based on the recipe production received in post-production data. As the composition of buffet menu items can vary, the distribution is applied on a daily basis.
A pre-requisite is for Menu Orchestration to be enabled in RME so that Inventory can receive and create buffet menu items for processing of post-production and sales data against these.
Comments
Please sign in to leave a comment.