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.
- Food Truck Management
- Data model
The tables behind Food Truck Management
Food Truck 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
Operating context
Organizations, truck stops, team members and Users establish destination and owner context.
Menu basis
Products, Ingredients, menu recipes and recipe ingredients define items and their preparation basis; ingredient movements retain actual use or waste.
Meal service
Service orders own service order lines and line tickets, with stop fulfillment events retaining related fulfillment events.
Evidence and review
Operation receipts, review decisions, payment evidence and record attachments point back to the order.
Reference rates
Exchange rates retain effective currency rates for the app.
Every table, by feature
- Trucks and stops5
- Menu and recipes6
- Service orders6
- Kitchen and service7
- Payments and corrections6
- Review and evidence7
- Shared and settings2
- Organizations
Operating organizations within the food and beverage group.
- Truck stops
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 - Service orders
Customer orders accepted and fulfilled by the kitchen and service team.
Linked to Organizations, Team members, Truck stops
- Service orders
Customer orders accepted and fulfilled by the kitchen and service team.
Linked to Organizations, Team members, Truck stops - Service order lines
Individual menu item lines within a meal order.
Linked to Service orders - Truck stops
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.
- Operation receipts
Durable receipts for guarded operations and their outcomes.
Linked to Service orders
- Service orders
Customer orders accepted and fulfilled by the kitchen and service team.
Linked to Organizations, Team members, Truck stops - Service order lines
Individual menu item lines within a meal order.
Linked to Service orders - Line tickets
Kitchen tickets submitted for review and release against a meal order.
Linked to Service orders, Organizations - Ingredient movements
Signed inventory movements for ingredient consumption and waste.
Linked to Ingredients - Operation receipts
Durable receipts for guarded operations and their outcomes.
Linked to Service orders - Review decisions
Independent reviewer decisions on submitted revisions.
Linked to Service orders, Team members
- Payment evidence
Provider-issued authorization, capture, refund and void receipts.
Linked to Service orders - Service orders
Customer orders accepted and fulfilled by the kitchen and service team.
Linked to Organizations, Team members, Truck stops - Service order lines
Individual menu item lines within a meal order.
Linked to Service orders - Review decisions
Independent reviewer decisions on submitted revisions.
Linked to Service orders, Team members - Operation receipts
Durable receipts for guarded operations and their outcomes.
Linked to Service orders - Ingredient movements
Signed inventory movements for ingredient consumption and waste.
Linked to Ingredients
- Operation receipts
Durable receipts for guarded operations and their outcomes.
Linked to Service orders - Review decisions
Independent reviewer decisions on submitted revisions.
Linked to Service orders, Team members - Record attachments
Files and evidence attached to operational records.
Linked to Service orders, Team members - Service orders
Customer orders accepted and fulfilled by the kitchen and service team.
Linked to Organizations, Team members, Truck stops - Service order lines
Individual menu item lines within a meal order.
Linked to Service orders - Payment evidence
Provider-issued authorization, capture, refund and void receipts.
Linked to Service orders - Line tickets
Kitchen tickets submitted for review and release against a meal order.
Linked to Service orders, Organizations
Keys and references
A service orders record references its Organization, Owner in team members and Counterparty in truck stops. Its lines, tickets, operation receipts, payment evidence, attachments, review decisions and fulfillment events use Parent to point back to the order. Menu recipes reference Products; recipe ingredients reference both menu recipes and Ingredients. Ingredient movements reference Ingredients and retain the source meal line as text. Team members link an Organization and a Users identity. Keep operation keys and provider event IDs stable when bringing historical evidence into the system.
Migration order
- Load Organizations, Users, team members and truck stops with active states and time zones.
- Load Products and Ingredients, then menu recipes and recipe ingredients with effective dates and approved states.
- Load service orders and service order lines, preserving record numbers, revisions, amounts and service times.
- Load line tickets, stop fulfillment events and ingredient movements against their source work.
- Load payment evidence, review decisions, record attachments and operation receipts with original identities and times.
- Load exchange rates by currency and effective date, then reconcile representative orders and receipts.
Set up Food Truck Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.