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.
- Ghost Kitchen Aggregator
- Data model
The tables behind Ghost Kitchen Aggregator
Ghost Kitchen Aggregator ships with 19 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
- 19
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Operating scope
Organizations and People identify where work belongs and who owns it; kitchen partners gives the partner definition.
Order work
Kitchen orders anchors order fulfillment events, external reconciliations and follow up actions.
Review trail
Evidence documents, review decisions and state history retain support and decisions against the source order.
Execution and measures
Operation runs and operation steps retain operation evidence; metric definitions, metric observations, metric results and source snapshots support reporting.
Every table, by feature
- Order intake4
- Kitchen partners4
- Review and evidence5
- Fulfillment and delivery5
- Exceptions and reconciliation6
- Metrics and provenance6
- Shared and settings2
- Kitchen orders
Parent order revisions routed through kitchen partners and pooled drivers.
Linked to Organizations, People, Kitchen partners - Organizations
Authorized operating organizations and reporting scope.
- People
Operators, reviewers, and analysts associated with an organization.
Linked to Organizations - State history
Immutable order status transition history.
Linked to Kitchen orders, People
- Kitchen partners
Kitchen partner definitions, effective policies, and active coverage.
Linked to Organizations - Source mappings
Reviewed source-to-target mappings for kitchen partner feeds.
Linked to Kitchen partners - Organizations
Authorized operating organizations and reporting scope.
- Source snapshots
Captured source-system coverage and freshness evidence.
- Review decisions
Independent revision-specific decisions on order evidence.
Linked to Kitchen orders, People - Evidence documents
Source evidence documents and verification metadata.
Linked to Kitchen orders, People - Kitchen orders
Parent order revisions routed through kitchen partners and pooled drivers.
Linked to Organizations, People, Kitchen partners - State history
Immutable order status transition history.
Linked to Kitchen orders, People - Follow up actions
Open and completed actions required to resolve order exceptions.
Linked to Kitchen orders, People
- Kitchen orders
Parent order revisions routed through kitchen partners and pooled drivers.
Linked to Organizations, People, Kitchen partners - Order fulfillment events
Observation-level fulfillment and delivery events linked to an order.
Linked to Kitchen orders - Operation runs
Durable idempotent workflow runs and actual results.
Linked to Kitchen orders - Operation steps
Numbered workflow trace with input, output, and receipt evidence.
Linked to Operation runs - State history
Immutable order status transition history.
Linked to Kitchen orders, People
- External reconciliations
Expected versus confirmed external order outcomes.
Linked to Kitchen orders - Follow up actions
Open and completed actions required to resolve order exceptions.
Linked to Kitchen orders, People - Kitchen orders
Parent order revisions routed through kitchen partners and pooled drivers.
Linked to Organizations, People, Kitchen partners - Order fulfillment events
Observation-level fulfillment and delivery events linked to an order.
Linked to Kitchen orders - Operation runs
Durable idempotent workflow runs and actual results.
Linked to Kitchen orders - Operation steps
Numbered workflow trace with input, output, and receipt evidence.
Linked to Operation runs
- Metric definitions
Reviewed metric definitions with explicit grain and aggregation method.
Linked to Kitchen partners, People - Metric observations
Observation-level metric inputs tied to source orders and snapshots.
Linked to Kitchen orders, Source snapshots - Metric results
Workflow-calculated metrics with source row counts and validity state.
Linked to Kitchen orders, Metric definitions, Operation runs - Source snapshots
Captured source-system coverage and freshness evidence.
- Operation runs
Durable idempotent workflow runs and actual results.
Linked to Kitchen orders - Kitchen orders
Parent order revisions routed through kitchen partners and pooled drivers.
Linked to Organizations, People, Kitchen partners
Keys and references
An order has its own Number and Revision. Linked records use their source reference to the order. The partner definition belongs to an organization; a reviewer and assignee refer to People. An operation run belongs to an order, while its steps belong to the run. A metric result can refer to its definition, source order and run.
Migration order
- Load Organizations and People, then kitchen partners and source mappings.
- Load source snapshots and metric definitions for the partner context.
- Load kitchen orders with organization, owner and partner definition.
- Attach evidence documents, review decisions and order fulfillment events to their source orders.
- Bring in follow up actions, external reconciliations, operation history and metric observations or results with their references intact.
Set up Ghost Kitchen Aggregator your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.