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.
- Restaurant + POS + Inventory + Delivery
- Features
- Menu and recipes
Menu and recipes
Maintain products, recipe versions and ingredient quantities for the menu.
OverviewActive Menu Products×
Restaurant + POS + Inventory + Delivery · Menu and recipes
New
Active Menu Products
Products
| SKU | Name | Base unit | Standard price USD | Active | |
|---|---|---|---|---|---|
| SKU-632 | Product 300 | BU-128 | 750 | Yes | |
| SKU-741 | Product 528 | BU-673 | 80 | Yes | |
| SKU-711 | Product 840 | BU-310 | 670 | Yes | |
| SKU-942 | Product 708 | BU-337 | 270 | Yes | |
| SKU-448 | Product 801 | BU-996 | 730 | Yes |
6 of 6 records
SKU-632Products · PRD-96278
YesNameProduct 300
Base unitBU-128
Standard price USD750
What you can do
Give the kitchen a usable source
Products identify sellable menu items and packaged goods. A product has its own SKU, base unit, standard price and active state. A meal line records the item and actual portion or price used for a specific order. Keeping those records distinct lets Inventory Manager maintain the menu while Order Manager can explain the amount charged on the individual order.
A menu recipe belongs to a product and has a recipe code, revision, effective date, yield and approval state. Its ingredients specify quantities per yield, units and waste allowances. Kitchen Operator needs to know which approved revision applies to the work at hand. If a recipe changes while an accepted order is in preparation, the team should keep the chosen recipe code and revision in the order’s supporting evidence.
How the work is organized
- Products establish the menu. The active product list keeps available items, base units and standard prices together.
- Recipes have versions. Approval and effective date identify a revision for planning and preparation.
- Ingredients remain explicit. Each recipe ingredient holds its own quantity and unit, while the ingredient master carries the allergen declaration.
What to agree during setup
Set a consistent SKU and recipe code convention. Choose base units that kitchen staff can use without guessing at conversion. Review ingredient allergen declarations with the people responsible for menu information. Decide who may approve a recipe revision and when the new effective date applies. A kitchen handoff should identify the approved version before ingredient use is recorded.
Review the product’s standard price and the meal line’s unit price together. They serve different purposes, so a price change should have an owner and an effective operating rule. If the restaurant serves packaged goods as well as prepared dishes, decide which products need recipes and which require only the product record. Avoid assigning an ingredient movement to a product when the actual source is a specific meal line.
Check the handoff on an actual case
Take a menu product that uses two ingredients and has a declared allergen. Inventory Manager confirms the product is active, then reviews the approved recipe revision and each ingredient quantity per yield. Order Manager adds the menu item to an order and checks the meal line’s portion and allergen declaration. Kitchen Operator uses the chosen revision when planning preparation.
Now change one ingredient quantity for the next recipe revision. Keep the earlier recipe code and revision with the accepted order so the kitchen plan remains explainable. The updated recipe can guide later work only when the responsible team has reviewed its approval and effective date. If a prepared portion uses an unexpected amount, the signed ingredient movement and source meal line provide the follow-up trail.
What your team sees
- Active Menu Products — Available menu items and packaged goods with their units and standard prices.
- Approved Menu Recipes — Approved recipe revisions, yields and effective dates.
- Active Ingredients — Ingredient codes, units and allergen declarations used for recipe review.
Follow the work through
What it keeps track of
Data model- Products
- Sellable menu products and packaged goods.
- Menu recipes
- Versioned recipe headers for products, with yield and approval state.
- Recipe ingredients
- Ingredient quantities required per recipe yield.
- Ingredients
- Ingredient master data with allergen declarations and base units.
- Meal lines
- Individual menu item lines within a meal order.
Who uses it
Permissions- Inventory Manager
- Maintains menu, recipes and ingredient master data.
- Order Manager
- Checks the product and price on an order.
- Kitchen Operator
- Prepares from an approved recipe and records actual use.
Set up Restaurant + POS + Inventory + Delivery your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.