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 POS System
- Data model
The tables behind Restaurant POS System
Restaurant POS 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
Operating context
Organizations, service locations, team members and Users identify the operating entity, destination and staff member.
Meal execution
Meal orders owns meal lines and kitchen tickets. Product and recipe records supply the menu and preparation basis.
Actual effects
Ingredient movements, fulfillment events and payment evidence retain consumption, delivery and provider outcomes.
Review trail
Review decisions, operation receipts and record attachments retain decisions, guarded action outcomes and evidence.
Every table, by feature
- Meal orders7
- Kitchen release7
- Menu and recipes6
- Preparation and service6
- Payments and corrections6
- Operations evidence8
- 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 - Organizations
Operating organizations within the food and beverage group.
- Team members
Staff members linked to an organization and platform identity.
Linked to Organizations, Users - Service locations
Dining rooms, outlets, venues and delivery destinations served by the operation.
Linked to Organizations - Products
Sellable menu products and packaged goods.
- Operation receipts
Durable receipts for guarded operations and their outcomes.
Linked to Meal orders
- 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 - Operation receipts
Durable receipts for guarded operations and their outcomes.
Linked to Meal orders - 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
- 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 - Recipe ingredients
Ingredient quantities required per recipe yield.
Linked to Ingredients, Menu recipes - Ingredient movements
Signed inventory movements for ingredient consumption and waste.
Linked to Ingredients
- 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 - 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 - 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 - Meal orders
Customer orders accepted and fulfilled by the kitchen and service team.
Linked to Organizations, Team members, Service locations - Kitchen tickets
Kitchen tickets submitted for review and release against a meal order.
Linked to Meal orders, Organizations - 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 - Record attachments
Files and evidence attached to operational records.
Linked to Meal orders, Team members - 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
Keys and references
Meal orders links to its Organization, Owner and Counterparty. Meal lines, kitchen tickets, operation receipts, review decisions, payment evidence, fulfillment events and record attachments refer to the parent meal orders record. Menu recipes refers to Products; recipe ingredients joins menu recipes and Ingredients. Ingredient movements refers to Ingredients and records its source meal line as text. Team members links Organizations to Users. The key and revision of a guarded operation should be retained with its evidence so a repeated action can be reconciled.
Migration order
- Add Organizations and Users, then team members and service locations.
- Add Products and Ingredients, then menu recipes and recipe ingredients with approval state.
- Add meal orders and meal lines with owners, locations and planned service times.
- Add kitchen tickets and the related review decisions.
- Add ingredient movements, fulfillment events, payment evidence, operation receipts and record attachments from actual activity.
- Reconcile open orders, ticket decisions, served portions and pending receipts before the operating cutover.
Set up Restaurant POS System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.