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 + Inventory + Delivery
- Data model
The tables behind Restaurant + POS + Inventory + Delivery
Restaurant + POS + Inventory + Delivery 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 destinations
Organizations, service locations, team members and Users establish operating context and ownership.
Menu and ingredients
Products, menu recipes, recipe ingredients and Ingredients describe sellable items and preparation requirements.
Orders and service
Meal orders link to meal lines, kitchen tickets and fulfillment events.
Consumption and evidence
Ingredient movements preserve signed use; payment evidence, review decisions, operation receipts and record attachments preserve decisions and outcomes.
Currency reference
Exchange rates holds effective rates for the organization context.
Every table, by feature
- Order intake6
- Kitchen handoff6
- Menu and recipes5
- Inventory movements7
- Payments and fulfillment6
- Review and evidence6
- 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 - Organizations
Operating organizations within the food and beverage group.
- 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
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 - Record attachments
Files and evidence attached to operational records.
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 - Operation receipts
Durable receipts for guarded operations and their outcomes.
Linked to Meal orders
- Fulfillment events
Allocation, picking, shipping, delivery and return events.
Linked to Meal orders, Products - Payment evidence
Provider-issued authorization, capture, refund and void receipts.
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 - Products
Sellable menu products and packaged goods.
- 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 - Record attachments
Files and evidence attached to operational records.
Linked to Meal orders, Team members - 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 - Payment evidence
Provider-issued authorization, capture, refund and void receipts.
Linked to Meal orders
Keys and references
The meal order is the parent for lines, tickets, fulfillment events, payment evidence, decisions, receipts and attachments. Service location and owner references point to their organization records. Recipes reference products; recipe ingredients reference ingredients and the recipe header. Meal lines name menu items as text, so staff must check the corresponding product and recipe when accepting an order. Ingredient movements reference an ingredient and carry a source meal-line identifier. Use operation keys and provider or external event identities to match repeated or delayed effects.
Migration order
- Set operating context. Load Organizations, Users, team members and service locations with active states and clear codes.
- Load menu sources. Add Products and Ingredients, then menu recipes and recipe ingredients with the intended approval and effective dates.
- Bring in order history. Load meal orders before meal lines and kitchen tickets so each child has its parent.
- Add outcomes. Bring in ingredient movements, fulfillment events and payment evidence with their source identities.
- Preserve review history. Load review decisions, operation receipts and record attachments with their parent references and original times.
Set up Restaurant + POS + Inventory + Delivery your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.