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 Reservation System
- Data model
The tables behind Restaurant Reservation System
Restaurant Reservation 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, service locations, team members and Users define the operating context and order owner.
Service work
Meal orders carry the serving time and status; meal lines and kitchen tickets carry line scope and kitchen handoff.
Menu and stock
Products, Ingredients, menu recipes, recipe ingredients and ingredient movements describe sellable items, recipes and actual usage.
Evidence
Review decisions, operation receipts, payment evidence, fulfillment events and record attachments keep decisions and observed effects connected to the order.
Reference rates
Exchange rates holds effective read-only rates for the app.
Every table, by feature
- Meal order intake5
- Kitchen release5
- Menu and recipes4
- Ingredient control5
- Service fulfillment5
- Review and evidence5
- Shared and settings2
- 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 - 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 - Organizations
Operating organizations within the food and beverage group.
- 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 - Meal lines
Individual menu item lines within a meal order.
Linked to Meal orders - Review decisions
Independent reviewer decisions on submitted revisions.
Linked to Meal orders, Team members
- Ingredients
Ingredient master data with allergen declarations and base units.
- Ingredient movements
Signed inventory movements for ingredient consumption and waste.
Linked to Ingredients - Recipe ingredients
Ingredient quantities required per recipe yield.
Linked to Ingredients, Menu recipes - Meal lines
Individual menu item lines within a meal order.
Linked to Meal orders
- 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 - Kitchen tickets
Kitchen tickets submitted for review and release against a meal order.
Linked to Meal orders, Organizations - Fulfillment events
Allocation, picking, shipping, delivery and return events.
Linked to Meal orders, Products - Service locations
Dining rooms, outlets, venues and delivery destinations served by the operation.
Linked to Organizations
- Review decisions
Independent reviewer decisions on submitted revisions.
Linked to Meal orders, Team members - Operation receipts
Durable receipts for guarded operations and their outcomes.
Linked to Meal orders - Payment evidence
Provider-issued authorization, capture, refund and void receipts.
Linked to Meal orders - 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
Keys and references
Meal lines, kitchen tickets, operation receipts, payment evidence, review decisions, record attachments and fulfillment events reference their parent meal orders record. Recipe ingredients references both its recipe and ingredient. The order’s Owner references team members, while Counterparty references service locations. Keep external event identifiers and operation keys stable when loading evidence.
Migration order
- Load Organizations, Users, team members and service locations.
- Load Products, Ingredients, menu recipes and recipe ingredients.
- Load meal orders and meal lines, followed by kitchen tickets.
- Load ingredient movements, fulfillment events and payment evidence with their parent references.
- Load review decisions, operation receipts and record attachments after the work they explain.
Set up Restaurant Reservation System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.