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.
- Bar & Beverage Management
- Data model and import order
The tables behind Bar & Beverage Management
Bar & Beverage 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
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Service orders:
Meal orders, meal lines, service locations and team members identify the request, location, owner and actual served scope.
Kitchen release:
Kitchen tickets and review decisions connect a submitted revision to its independent decision.
Products and recipes:
Products, menu recipes, recipe ingredients and Ingredients define a dated preparation basis and its declared inputs.
Ingredient usage:
Ingredient movements record signed quantities against ingredients and source meal lines.
Payment and fulfillment:
Payment evidence and fulfillment events connect provider and handling events to the parent order.
Review and evidence:
Operation receipts and record attachments retain guarded outcomes and supporting files.
Every table, by feature
- Service orders5
- Kitchen tickets6
- Products and recipes5
- Ingredients and usage5
- Payment and fulfillment5
- Review and evidence6
- Shared and settings3
- 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 - Products
Sellable menu products and packaged goods.
- 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
- 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.
- Meal lines
Individual menu item lines within a meal order.
Linked to Meal orders
- Ingredients
Ingredient master data with allergen declarations and base units.
- 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 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 - 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 - Meal lines
Individual menu item lines within a meal order.
Linked to Meal orders - 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 - 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
Keep the order number stable and link each meal line, ticket, decision, receipt and attachment to its parent order. Preserve recipe code and revision with the effective date used for preparation. Ingredient quantities need their units; money amounts use the recorded USD amount fields. Keep provider event identifiers and external fulfillment identifiers so a repeated source event can be recognized.
The operation key identifies a guarded action. Compare its expected revision and effect references before retrying an uncertain action. A source meal line on an ingredient movement is a text reference, so define the matching convention during migration and verify it against actual lines. Keep the original reviewer and upload identity on historical evidence.
Migration order
- Load Organizations and Users, then team members and service locations with stable codes and identity mappings.
- Load Products and Ingredients with base units, active states and allergen declarations.
- Load menu recipes and recipe ingredients with their effective dates, yields, quantities and approved states.
- Load meal orders and meal lines, then linked kitchen tickets, review decisions and record attachments.
- Load ingredient movements, fulfillment events, payment evidence and operation receipts. Reconcile parent links, quantities, revisions and source identifiers before opening live service.
Set up Bar & Beverage Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.