These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Catering Management
- Features
- Menus and ingredients
Menus and ingredients
Connect products, approved recipe versions and ingredient quantities to a real serving plan.
OverviewApproved Event Menus×
Catering Management · Menus and ingredients
New
Approved Event Menus
Event menus
| Recipe code | Revision number | Product | Effective from | Portion yield | |
|---|---|---|---|---|---|
| RC-278 | 700 | PRD-9037 | 11 Oct | 830 | |
| RC-670 | 730 | PRD-7500 | 09 Oct | 720 | |
| RC-990 | 500 | PRD-5699 | 17 Oct | 480 | |
| RC-231 | 470 | PRD-7113 | 12 Oct | 450 | |
| RC-389 | 40 | PRD-8171 | 23 Oct | 390 |
6 of 6 records
RC-278Event menus · EM-65697
Revision number700
ProductPRD-9037
Effective from11 Oct
Portion yield830
What you can do
Menus and ingredients in daily work
A sellable product has a SKU, name, base unit and standard price. A menu recipe links to that product through a recipe code, revision, effective date and portion yield. Each recipe yield identifies an ingredient, required quantity, unit and waste allowance. Ingredient records hold base units and allergen declarations. Together these records give the kitchen a concrete basis for the portions on an accepted event order.
How the work is organized
- Choose an active product. The coordinator uses the sellable item and its price when preparing an order line.
- Check the approved yield. Kitchen Lead reads the recipe revision, ingredient quantities and allergen declarations before release.
- Explain stock use. Signed ingredient movements distinguish consumption from waste for the source work.
The Kitchen Lead checks that the chosen product and ingredients are active, that the recipe revision is approved, and that allergen declarations match the event lines. The approved recipe revision is frozen when work is released to the kitchen. That is the key handoff: a later recipe edit must not silently change the quantities or declarations used for already prepared portions. Ingredient movements record signed consumption and waste separately, with a source meal line and operation key.
What to agree during setup
Decide who maintains product prices, recipe revisions and ingredient allergen declarations. Agree when a recipe becomes approved and how its yield is checked against ordered portions. Use consistent ingredient units, and preserve the approved revision used for released kitchen work. Define who records a waste movement and how its source line and operation key are identified.
Check the handoff on an actual case
For a plated meal, the coordinator selects the menu item and planned portions. The Kitchen Lead checks the approved yield and ingredient units before release. If the recipe yields a different number of portions than the order needs, the team computes the required ingredient quantity from the actual yield rather than copying a standard pack count. A later waste movement explains lost ingredients, while served portions continue to describe what guests received.
A new recipe revision can serve future work while the earlier approved revision remains the basis for portions already prepared. When an ingredient is wasted, its signed movement explains stock use; it does not increase the guest service quantity. The kitchen can compare the recipe yield with the actual order before calculating the required ingredient quantities.
What your team sees
- Approved Event Menus — Effective recipe revisions with their products and portion yields.
- Active Ingredients — Usable ingredients with base units and allergen declarations.
Follow the work through
Follow the process and review roles and permissions before a live handoff.
What it keeps track of
Data model- Products
- Sellable menu products and packaged goods.
- Event menus
- Versioned recipe headers for products, with yield and approval state.
- Recipe yields
- Ingredient quantities required per recipe yield.
- Ingredients
- Ingredient master data with allergen declarations and base units.
- Ingredient movements
- Signed inventory movements for ingredient consumption and waste.
Who uses it
Permissions- Kitchen Lead
- Maintains recipes, checks yields and records ingredient use.
- Event Coordinator
- Selects active products and checks declarations while preparing the order.
Set up Catering Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.