All applications611

Find your application

611 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. Food Franchise Management
  2. Data model
Reference

The tables behind Food Franchise Management

Food Franchise Management 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
7, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Operating context

Organizations, service locations and team members establish where work belongs and who owns it.

Menu basis

Products, Ingredients, menu recipes and recipe ingredients define the product and recipe quantities.

Order work

Meal orders, meal lines and kitchen tickets carry the customer commitment and kitchen review.

Actual effects

Ingredient movements, fulfillment events and payment evidence record consumption, handoff and provider receipts.

Review

Operation receipts, review decisions and record attachments keep decisions and supporting evidence attached to the order.

Every table, by feature

Meal orders

6 tablesAbout this feature
  • Meal orders

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

    Linked to Organizations, Team members, Service locations
  • Meal lines

    Individual menu item lines within a meal order.

    Linked to Meal orders
  • Products

    Sellable menu products and packaged goods.

  • Service locations

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

    Linked to Organizations
  • Team members

    Staff members linked to an organization and platform identity.

    Linked to Organizations, Users
  • Operation receipts

    Durable receipts for guarded operations and their outcomes.

    Linked to Meal orders

Kitchen tickets

5 tablesAbout this feature
  • Kitchen tickets

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

    Linked to Meal orders, Organizations
  • Meal orders

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

    Linked to Organizations, Team members, Service locations
  • Review decisions

    Independent reviewer decisions on submitted revisions.

    Linked to Meal orders, Team members
  • Record attachments

    Files and evidence attached to operational records.

    Linked to Meal orders, Team members
  • Operation receipts

    Durable receipts for guarded operations and their outcomes.

    Linked to Meal orders

Recipes and ingredients

5 tablesAbout this feature
  • Products

    Sellable menu products and packaged goods.

  • Recipe ingredients

    Ingredient quantities required per recipe yield.

    Linked to Ingredients, Menu recipes
  • Ingredients

    Ingredient master data with allergen declarations and base units.

  • Ingredient movements

    Signed inventory movements for ingredient consumption and waste.

    Linked to Ingredients

Preparation and service

5 tablesAbout this feature
  • Meal orders

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

    Linked to Organizations, Team members, Service locations
  • Meal lines

    Individual menu item lines within a meal order.

    Linked to Meal orders
  • Ingredient movements

    Signed inventory movements for ingredient consumption and waste.

    Linked to Ingredients
  • Fulfillment events

    Allocation, picking, shipping, delivery and return events.

    Linked to Meal orders, Products

Locations and people

5 tablesAbout this feature
  • Organizations

    Operating organizations within the food and beverage group.

  • Service locations

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

    Linked to Organizations
  • Team members

    Staff members linked to an organization and platform identity.

    Linked to Organizations, Users
  • Users

    Users

    Linked to Users
  • Meal orders

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

    Linked to Organizations, Team members, Service locations

Payments and fulfillment

5 tablesAbout this feature
  • Payment evidence

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

    Linked to Meal orders
  • Fulfillment events

    Allocation, picking, shipping, delivery and return events.

    Linked to Meal orders, Products
  • Meal orders

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

    Linked to Organizations, Team members, Service locations
  • Products

    Sellable menu products and packaged goods.

  • Operation receipts

    Durable receipts for guarded operations and their outcomes.

    Linked to Meal orders

Review and exceptions

6 tablesAbout this feature
  • Operation receipts

    Durable receipts for guarded operations and their outcomes.

    Linked to Meal orders
  • Review decisions

    Independent reviewer decisions on submitted revisions.

    Linked to Meal orders, Team members
  • Record attachments

    Files and evidence attached to operational records.

    Linked to Meal orders, Team members
  • Meal orders

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

    Linked to Organizations, Team members, Service locations
  • Meal lines

    Individual menu item lines within a meal order.

    Linked to Meal orders
  • Payment evidence

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

    Linked to Meal orders

Shared and settings

1 table
  • Exchange rates

    Read-only effective exchange rates for this app.

Keys and references

Meal orders links to Organizations, team members and service locations. Its child records use Parent to link tickets, lines, payment evidence, fulfillment events, reviews, attachments and receipts. Menu recipes links to Products; recipe ingredients links to its recipe and Ingredients. Ingredient movements links to Ingredients and carries the source meal line as text; that text is not a direct reference to meal lines. Preserve external provider and fulfillment event identities during import so repeated messages can be compared with the original record.

Migration order

  1. Operating context. Bring in organizations, service locations, users and team members.
  2. Menu basis. Bring in products, ingredients, recipes and recipe ingredient quantities.
  3. Open work. Bring in meal orders and lines with their current owner, location, status and revision.
  4. History. Attach tickets, decisions, movements, fulfillment and payment evidence to the right order.
  5. Reconciliation. Check receipts, external references and supporting attachments before opening the live queue.

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