All applications611

Find your application

611 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. Food Franchise Management
  2. Features
  3. Recipes and ingredients
Feature · Recipes and ingredients

Recipes and ingredients

Keep the recipe basis and ingredient quantities visible to kitchen staff.

OverviewApproved Menu Recipes
Food Franchise Management · Recipes and ingredients

Approved Menu Recipes

Menu recipes

New
Recipe codeProductRevision numberEffective fromPortion yieldApproved
RC-540PRD-480010017 Oct850Yes
RC-198PRD-17029016 Oct650Yes
RC-731PRD-813862018 Oct580Yes
RC-411PRD-369741004 Oct930Yes
RC-250PRD-663964021 Oct930Yes
6 of 6 records
RC-540Menu recipes · MR-74420
Yes
ProductPRD-4800
Revision number100
Effective from17 Oct
Portion yield850
Example screen with sample data

What you can do

Keep the recipe basis and ingredient quantities visible to kitchen staff

Products identify sellable menu goods. A recipe belongs to a product and carries a code, revision, effective date, portion yield and approval state. Recipe ingredients specify the ingredient, quantity per yield, unit and waste allowance. Ingredients retain their base unit and allergen declaration.

Ingredient movements record signed consumption and waste with time, unit, source meal line and operation key. Those movements make actual use distinguishable from the recipe requirement. A recipe revision is a preparation basis; it does not itself claim that ingredients were consumed or that the meal was served.

How the work is organized

The team uses the order and its linked records as the shared reference. Changes belong to a known actor and the current revision. A status records progress, while the dated record and its evidence explain what happened.

  • Named ownership. Admin maintains products and recipes; Kitchen Lead reads the approved basis before preparation.
  • Exact scope. Product, recipe code and revision connect required ingredients to the menu item.
  • Visible result. The ingredient movement carries its unit, source meal line and operation key for actual use.

What to agree during setup

Agree who approves a recipe revision, how base units relate to recipe units, and when a new revision becomes effective. Review each ingredient allergen declaration against the menu line before service. Keep consumption and waste as separate signed movements so a change in recipe does not rewrite earlier use.

Check the handoff on an actual case

Suppose a recipe yields several portions of a menu product. The Kitchen Lead checks that the current recipe is approved and effective for the service date, then reads each ingredient quantity on the same yield basis. If an ingredient is inactive or the allergen declaration conflicts with an order line, the team resolves the issue before preparation.

Ask the Kitchen Lead to scale the approved recipe yield to the requested portions, then compare ingredient quantities and units. Record the actual movement against the source meal line. A second movement with the same operation key must be checked against the first before another effect is saved.

What your team sees

  • Approved Menu Recipes — Select recipes marked approved and compare their effective dates.
  • Active Ingredients — Check active ingredients, base units and allergen declarations.

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.
Ingredient movements
Signed inventory movements for ingredient consumption and waste.

Who uses it

Permissions
Kitchen Lead
, Kitchen Supervisor and Admin own the work here.
Admin
Maintains active products and recipe revisions.
Kitchen Supervisor
Checks a material change before the kitchen uses a different preparation basis.

Set up Food Franchise Management your way.

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

How to get started