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.
- Bar & Beverage Management
- Features
- Ingredients and usage
Ingredients and usage
Track ingredient declarations and signed consumption or waste against prepared work.
OverviewActive Ingredients×
Bar & Beverage Management · Ingredients and usage
New
Active Ingredients
Ingredients
| Ingredient code | Name | Base unit | Allergen declaration | Active | |
|---|---|---|---|---|---|
| IC-788 | Ingredient 339 | BU-902 | AD-586 | Yes | |
| IC-795 | Ingredient 832 | BU-363 | AD-682 | Yes | |
| IC-439 | Ingredient 900 | BU-719 | AD-945 | Yes | |
| IC-299 | Ingredient 674 | BU-268 | AD-885 | Yes | |
| IC-498 | Ingredient 208 | BU-619 | AD-229 | Yes |
6 of 6 records
IC-788Ingredients · ING-37200
YesNameIngredient 339
Base unitBU-902
Allergen declarationAD-586
What you can do
Keep planned ingredients separate from actual use
An ingredient record gives the kitchen a stable code, name, base unit, allergen declaration and active state. A recipe ingredient says what quantity is planned per recipe yield. An ingredient movement records what happened: a signed quantity, unit, occurrence time, source meal line and operation key. Those records should be read together, but they answer different questions. A recipe describes an intended preparation; a movement records actual consumption or waste.
The signed movement is especially useful when an order changes after some portions have been prepared. The team can preserve what was used and add a correction or waste movement with its own operation key. Rewriting the recipe or the original movement would hide the cost and cause of the change.
How the work is organized
- Ingredient identity. Ingredients keep codes, units and allergen declarations stable across recipe revisions.
- Planned quantity. recipe ingredients tie a measured amount and waste allowance to a specific recipe.
- Actual movement. ingredient movements keep a signed quantity, source line and operation key for consumption or waste.
Kitchen Lead records preparation on the order line and uses the corresponding ingredient movements to explain what was consumed. Inventory Steward reviews units and movement signs before comparing totals. Service Manager checks that a cancellation leaves served portions and actual usage intact.
What to agree during setup
Choose the base unit for each ingredient and the allowed units for its recipe lines and movements. A signed quantity cannot be compared fairly with a recipe quantity if the units differ without an approved conversion. Agree how the operation key is assigned so a retry finds the earlier movement rather than posting the same consumption again. Decide how waste is named and reviewed, especially when a line was prepared but never served.
Allergen declarations need a person responsible for maintenance and a review after recipe changes. An inactive ingredient should not be treated as available for new preparation just because an older approved recipe refers to it. Historical movements remain available for reconciliation and should keep their original code and unit.
Check the handoff on an actual case
Kitchen Lead prepares part of a meal order using an approved recipe. The prepared time is recorded on the corresponding line. Ingredient movements carry the actual quantities and the line’s source reference. Before service, the guest cancels the remaining portions. Service Manager reviews the unprepared and prepared scope separately. That preparation may create waste, but it does not become a served portion. Inventory Steward can then compare the signed movements with the recipe basis and identify the operation that caused each quantity.
During a pilot, rehearse a repeated submission of the same movement key. The second attempt should return the earlier outcome for review rather than create another consumption entry. Reconcile the order line, ingredient, unit and time before closing an exception.
What your team sees
- Active Ingredients — Current ingredients with code, unit and allergen declaration.
- Approved Menu Recipes — Approved preparation bases to compare with actual movements.
Follow the work through
Use recipe to preparation for planned versus actual quantities and correction and refund for waste after a change.
What it keeps track of
Data model- Ingredients
- Ingredient master data with allergen declarations and base units.
- Recipe ingredients
- Ingredient quantities required per recipe yield.
- Ingredient movements
- Signed inventory movements for ingredient consumption and waste.
- Menu recipes
- Versioned recipe headers for products, with yield and approval state.
- Meal lines
- Individual menu item lines within a meal order.
Who uses it
Permissions- Inventory Steward
- Owns ingredient definitions and movement review.
- Kitchen Lead
- Records actual preparation and ingredient use.
- Service Manager
- Decides how an order change affects unserved scope.
Set up Bar & Beverage Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.