1. Recipe Management System
  2. Data model
Reference

The tables behind Recipe Management System

Recipe Management System ships with 18 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
18
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Organization and people

Organizations, Kitchens, team members and Users establish operating context and order ownership.

Recipe basis

Ingredient master, ingredient yields, menu items and recipe cards connect sold items to approved preparation quantities.

Kitchen work

Production orders and production lines hold the accepted commitment and actual line progress; batch tickets supports separate review.

Evidence

Review decisions, operation receipts, stock consumptions, fulfillment events, payment evidence and record attachments explain decisions and performed effects.

Reference rates

Exchange rates stores effective read-only currency rates.

Every table, by feature

Ingredients and yields

4 tablesAbout this feature
  • Ingredient master

    Ingredient master data with allergen declarations and base units.

  • Ingredient yields

    Ingredient quantities required per recipe yield.

    Linked to Ingredient master, Recipe cards
  • Recipe cards

    Versioned recipe headers for products, with yield and approval state.

    Linked to Menu items
  • Stock consumptions

    Signed inventory movements for ingredient consumption and waste.

    Linked to Ingredient master

Recipe cards and menu items

4 tablesAbout this feature
  • Recipe cards

    Versioned recipe headers for products, with yield and approval state.

    Linked to Menu items
  • Ingredient yields

    Ingredient quantities required per recipe yield.

    Linked to Ingredient master, Recipe cards
  • Ingredient master

    Ingredient master data with allergen declarations and base units.

Order acceptance

6 tablesAbout this feature
  • Production orders

    Customer orders accepted and fulfilled by the kitchen and service team.

    Linked to Organizations, Team members, Kitchens
  • Production lines

    Individual menu item lines within a meal order.

    Linked to Production orders
  • Kitchens

    Dining rooms, outlets, venues and delivery destinations served by the operation.

    Linked to Organizations
  • Recipe cards

    Versioned recipe headers for products, with yield and approval state.

    Linked to Menu items
  • Operation receipts

    Durable receipts for guarded operations and their outcomes.

    Linked to Production orders

Kitchen production

6 tablesAbout this feature
  • Production orders

    Customer orders accepted and fulfilled by the kitchen and service team.

    Linked to Organizations, Team members, Kitchens
  • Production lines

    Individual menu item lines within a meal order.

    Linked to Production orders
  • Recipe cards

    Versioned recipe headers for products, with yield and approval state.

    Linked to Menu items
  • Ingredient yields

    Ingredient quantities required per recipe yield.

    Linked to Ingredient master, Recipe cards
  • Stock consumptions

    Signed inventory movements for ingredient consumption and waste.

    Linked to Ingredient master
  • Fulfillment events

    Allocation, picking, shipping, delivery and return events.

    Linked to Production orders, Menu items

Batch release

5 tablesAbout this feature
  • Batch tickets

    Kitchen tickets submitted for review and release against a meal order.

    Linked to Production orders, Organizations
  • Production orders

    Customer orders accepted and fulfilled by the kitchen and service team.

    Linked to Organizations, Team members, Kitchens
  • Review decisions

    Independent reviewer decisions on submitted revisions.

    Linked to Production orders, Team members
  • Operation receipts

    Durable receipts for guarded operations and their outcomes.

    Linked to Production orders
  • Record attachments

    Files and evidence attached to operational records.

    Linked to Production orders, Team members

Exceptions and evidence

8 tablesAbout this feature
  • Operation receipts

    Durable receipts for guarded operations and their outcomes.

    Linked to Production orders
  • Review decisions

    Independent reviewer decisions on submitted revisions.

    Linked to Production orders, Team members
  • Payment evidence

    Provider-issued authorization, capture, refund and void receipts.

    Linked to Production orders
  • Fulfillment events

    Allocation, picking, shipping, delivery and return events.

    Linked to Production orders, Menu items
  • Record attachments

    Files and evidence attached to operational records.

    Linked to Production orders, Team members
  • Production orders

    Customer orders accepted and fulfilled by the kitchen and service team.

    Linked to Organizations, Team members, Kitchens
  • Production lines

    Individual menu item lines within a meal order.

    Linked to Production orders
  • Stock consumptions

    Signed inventory movements for ingredient consumption and waste.

    Linked to Ingredient master

Shared and settings

4 tables
  • Exchange rates

    Read-only effective exchange rates for this app.

  • Organizations

    Operating organizations within the food and beverage group.

  • Team members

    Staff members linked to an organization and platform identity.

    Linked to Organizations, Users
  • Users

    Users

    Linked to Users

Keys and references

Production orders is the parent for lines, tickets, decisions, receipts and several evidence records. Ingredient yields links ingredient master with recipe cards; recipe cards links to menu items. Team members links the order owner, reviewer and attachment uploader to an organization and a user identity. Preserve external event IDs and operation keys when importing evidence so retries and reconciliation remain traceable.

Migration order

  1. Import Organizations, Users and team members, then active Kitchens.
  2. Import ingredient master and menu items with stable codes and units.
  3. Import recipe cards and ingredient yields with revision and effective-date context.
  4. Import production orders and production lines, then batch tickets.
  5. Import decisions, receipts, stock movements, fulfillment events, payment evidence and attachments with their original references.
  6. Reconcile sample parent links, recipe yields, order portions and provider events before routine operation.

Set up Recipe Management System your way.

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

How to get started