1. Restaurant POS System
  2. Features
  3. Menu and recipes
Feature · Menu and recipes

Menu and recipes

A menu item needs a sellable product and a recipe that the kitchen can use for the accepted order. Menu Steward maintains product identity, standard price, ingredient declarations and recipe yield. Kitchen Lead uses the approved recipe revision when preparing an accepted meal line. Ingredient movements then describe actual consumption or waste against the work performed.

OverviewActive Menu Products
Restaurant POS System · Menu and recipes

Active Menu Products

Products

New
SKUNameBase unitStandard price USDActive
SKU-744Product 402BU-456250Yes
SKU-886Product 711BU-456370Yes
SKU-674Product 932BU-863900Yes
SKU-955Product 234BU-243770Yes
SKU-252Product 747BU-623840Yes
6 of 6 records
SKU-744Products · PRD-35251
Yes
NameProduct 402
Base unitBU-456
Standard price USD250
Example screen with sample data

What you can do

Keep the menu current

Products identify sellable menu goods by name, SKU, unit and standard price. The active flag helps the service team choose from the current menu. Ingredients have a code, name, base unit and allergen declaration. A recipe links a product to a yield and an effective revision. Its ingredient rows specify quantities per yield, units and waste allowance. Approval state makes it possible to distinguish the revision available for kitchen work.

A seasonal dish illustrates why these details matter. Menu Steward can keep the product identity while recording a new recipe revision with a changed ingredient quantity. The kitchen must use the approved revision for the order it is preparing. The ingredient record carries the allergen declaration that the service team needs when accepting a meal line. A change to a recipe after ticket review belongs in a fresh reviewed scope.

How the work is organized

  • Menu product. The sellable item’s SKU, active state and standard price anchor order entry.
  • Recipe revision. Product, code, effective date, yield and approval state identify the preparation basis.
  • Ingredients and movements. Ingredient rows define expected quantities; movements record actual signed consumption or waste.

What to agree during setup

Agree the unit used for each ingredient and how portions convert from recipe yield into kitchen work. Decide who updates allergen declarations and who approves recipe revisions. The team should rehearse a change to a recipe after an order has already been accepted, because the approved revision for that work must remain clear. Set product activation ownership so a discontinued item cannot be accepted by accident.

Menu Steward should also agree the waste allowance convention with Kitchen Lead. A negative movement and a positive movement must have an intelligible business reason, source meal line and operation key. This makes actual consumption review possible when a dish is reworked or cancelled.

Check the handoff on an actual case

Choose an active dish with an approved recipe and ingredient rows. Enter a meal line for several portions, then have Kitchen Lead confirm the recipe revision and calculate the intended ingredient scope. Record the actual preparation and the matching ingredient movements. Compare the movement quantities with the recipe yield, noting separately any waste. Now create a revised recipe and compare the earlier preparation time, approved recipe revision and recorded ingredient movements with the basis used at the time.

What your team sees

  • Active Menu Products — Sellable items available when the service team builds an order.
  • Approved Menu Recipes — Current approved preparation references for Kitchen Lead.
  • Active Ingredients — Ingredient names, units and allergen declarations for review.

Follow the work through

The order acceptance process starts with menu selection. Preparation and service shows how recipe revisions and actual movements follow that accepted work.

What it keeps track of

Data model
Products
Sellable menu products and packaged goods.
Ingredients
Ingredient master data with allergen declarations and base units.
Menu recipes
Versioned recipe headers for products, with yield and approval state.
Recipe ingredients
Ingredient quantities required per recipe yield.
Ingredient movements
Signed inventory movements for ingredient consumption and waste.
Meal lines
Individual menu item lines within a meal order.

Who uses it

Permissions
Menu Steward
Maintains products, ingredients and recipe revisions.
Kitchen Lead
Confirms the approved basis and records movements during preparation.
Service Lead
Uses active products and allergen information when accepting the meal order.

Set up Restaurant POS System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started