Principles of the Adoria Central Kitchen:
A meal plans on the central kitchen side that will be administered like a classic menu, with only recipes inside.
Definition of selling price for recipes by the central kitchen or default production cost applied.
Specific ordering module for customer sites.
Backlog of orders from "customer" sites and consolidation of quantities at central kitchen level.
Generation of delivery notes to "customer" sites, with associated inventory movements.
Central kitchen settings:
In Settings > Organization management, the site must be set up as follows.
If the "collective on the basis of recipes" mode is not available, please contact your project manager or support.
The central kitchen can then define its "customers" on a dedicated page: Production > Billing settings:
This is the setting that will enable sites to access the Central Kitchen menu.
Meal plans management on the Central Kitchen side:
In Production > Meal plans, the Central Kitchen will be able to:
1. Create your meal plans
2. Integrate recipes to be offered to sites
A dedicated page enables the central kitchen to set its selling prices for "customer" sites. By default, the selling price will be the production cost.
In Production > Production management
Site orders:
Sites will be able to access this specific "central kitchen" ordering module via the main ordering menu.
In Procurement > Orders:
They will be able to indicate the desired quantity per recipe on the day of delivery:
Consolidation and delivery note generation on the Central Kitchen side:
The central kitchen will be able to retrieve the consolidated headcount for its meal plans (click on the three vertical dots: see meal orders), make any modifications (1) and generate a delivery note which will freeze the data on the customer site and central kitchen sides (3).
An export function allows you to print out all quantities by recipe and by site, as well as the transport plan (2).
Reception at customer site:
The customer's site will track the receipt of orders in the same way as a conventional receipt of transfers:
The behavior of a stock placement provides for two behaviors:
If the recipe is not distributed to the receiving site, it must be associated with a generic product with a behavior similar to that of a product/reference association outside the contract*, or put directly into consumption.
If the recipe is distributed to the site, it is broken down into the various generic products that make it up.
At the Central Kitchen level, we behave in the same way as for a transfer: the products present in each recipe will be destocked.
Reporting can be followed in the classic way in Purchasing reports.
*If the customer uses the checkout interface, the Menus page can be used to automate the link between the recipe and a generic product. This is done by selecting a PLU link with a recipe and a product:
