Ghost Kitchen Aggregator holds kitchen orders by organization, owner and partner definition. An operator follows each order from receipt through acceptance, preparation, dispatch and delivery, with the kitchen code, driver reference, promised time and actual delivery time on the order.
Kitchen orders in one list
Independent Reviewer decides from the selected revision and linked evidence.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep a received kitchen order identifiable through every revision.
Acceptance waits for the order operator
| Number | Order date | Kitchen code | Definition | Owner | |
|---|---|---|---|---|---|
| KO-44941 | 16 Oct | CSP-DT | North Fork Prep Co. | Nia Patel | |
| KO-85511 | 21 Oct | WHT-WS | Harborline Kitchen Co. | Owen Brooks | |
| KO-65321 | 17 Oct | BTK-ND | Juniper Tray Collective | Jules Dubois | |
| KO-40251 | 12 Oct | NFP-MT | Harborline Kitchen Co. | Marco Silva | |
| KO-12612 | 18 Oct | JTC-LK | Harborline Kitchen Co. | Marco Silva |
Keep partner coverage and source mappings tied to the organization that uses them.
Kitchen partners
| Code | Name | Effective from | Effective to | Policy reference | Organization | |
|---|---|---|---|---|---|---|
| CSP | Copper Spoon Kitchen | 23 Oct | 28 Oct | POL-2026-ROUTING-01 | Harborline Food Service | |
| WHT | Willow Hearth Foods | 17 Oct | 26 Oct | POL-2026-PREP-02 | Marigold Kitchen Network | |
| BTK | Blue Table Kitchen | 15 Oct | 19 Oct | POL-2026-PICKUP-03 | Blue Table Delivery Group | |
| NFP | North Fork Prep Co. | 18 Oct | 20 Oct | POL-2026-REFUND-04 | Blue Table Delivery Group | |
| JTC | Juniper Tray Collective | 16 Oct | 25 Oct | POL-2026-MENU-05 | Copper Spoon Operations |
Give an independent reviewer the exact order revision and supporting documents.
Action waits for the independent reviewer
| Source | Source revision | Decision | Reviewer | Evidence reference | |
|---|---|---|---|---|---|
| Rice bowl lunch, downtown | 70 | Pending | Theo Park | handoff_10418.jpg | |
| Grain bowl dinner, east end | 690 | Pending | Jules Dubois | kitchen_accept_10419.pdf | |
| Breakfast wrap order, harbor | 830 | Pending | Sara Haddad | courier_scan_10420.json | |
| Market salad order, midtown | 470 | Pending | Ravi Menon | refund_0772.pdf | |
| Noodle box lunch, north district | 730 | Pending | Owen Brooks | menu_stock_1184.csv |
Track preparation, dispatch and delivery against one order.
Kitchen orders
| Number | Name | Status | Order date | Promised at | |
|---|---|---|---|---|---|
| KO-99420 | Rice bowl lunch, downtown | Received | 22 Oct | 27 Oct | |
| KO-37194 | Roasted chicken dinner, west side | Accepted | 11 Oct | 17 Oct | |
| KO-47003 | Noodle box lunch, north district | Preparing | 14 Oct | 20 Oct | |
| KO-11884 | Market salad order, midtown | Dispatched | 14 Oct | 20 Oct | |
| KO-94907 | Family pasta dinner, lakeside | Delivered | 18 Oct | 20 Oct |
Work delivery exceptions and external amount differences against their source order.
Follow-up actions
| Title | Due date | Status | Source | Resolution | |
|---|---|---|---|---|---|
| Confirm missing soup item | 25 Oct | Open | Soup and sandwich, campus | Soup item refunded to guest | |
| Reconcile duplicate courier scan | 18 Oct | In progress | Roasted chicken dinner, west side | Courier scan corrected | |
| Call kitchen about late pickup | 01 Nov | Completed | Rice bowl lunch, downtown | Pickup time confirmed by kitchen | |
| Review spilled sauce complaint | 04 Nov | Open | Breakfast wrap order, harbor | Replacement meal credited | |
| Correct salad substitution | 16 Oct | In progress | Market salad order, midtown | Salad swap approved by guest |
Read order measures alongside source coverage and calculation validity.
Metric results
| Metric | Period start | Period end | Dimension key | Value | Source row count | |
|---|---|---|---|---|---|---|
| Order handoff accuracy | 26 Oct | 01 Nov | kitchen:CSP-DT | 820 | 16 | |
| Courier pickup delay | 13 Oct | 21 Oct | zone:west-side | 30 | 3 | |
| Refund rate by kitchen | 14 Oct | 21 Oct | meal:lunch | 330 | 32 | |
| Missing item incidence | 20 Oct | 27 Oct | channel:direct | 550 | 9 | |
| Late delivery share | 26 Oct | 03 Nov | day:weekday | 580 | 22 |
Order receipt to verified delivery ships ready to use. One step needs a named approval before the work moves on: Approve revision (Independent Reviewer).
Capture the source order, owner and organization.
Check active partner coverage and mapping dates.
Review documents linked to the selected revision.
The Independent Reviewer records the revision decision.
Keep the kitchen and driver references with the order.
Compare observed fulfillment with the actual delivery time.
Open any kitchen order to see its external reconciliations, the roles that work on it, its process stages and its approvals on one page.
Order date, Driver reference, Promised at and Owner.
Each line is linked to this kitchen order.
Admin, Order Operator and Kitchen Coordinator, each with their own permissions.
Register order and Route order, with the role that acts.
Approve revision, with who decides.
Courier route 184 · Received
| Source | External reference | Value date |
|---|---|---|
| Grain bowl dinner, east end | ORD-2026-10418 | 16 Oct |
| Breakfast wrap order, harbor | DSP-2026-8412 | 21 Oct |
| Breakfast wrap order, harbor | PAY-2026-1541 | 30 Oct |
Signed in as Independent Reviewer
| Decision | Approver | |
|---|---|---|
| Approve revisionThe Independent Reviewer records the revision decision. | Independent Reviewer | |
| Approve review decisions | Independent Reviewer |
Everyone opens Ghost Kitchen Aggregator to the work that is theirs. Pick a role to see what it starts with.
Maintains operating organizations, people and access policy.
Owns the intake and status of kitchen orders in the assigned organization.
This is the first screen this role sees.
Kitchen orders · Order Operator
Checks partner coverage, policies and feed mappings before routing.
This is the first screen this role sees.
Source snapshots · Kitchen Coordinator
| Name | Source system | Coverage start | Coverage end | Freshness status | |
|---|---|---|---|---|---|
| Lunch order feed, October 14 | Order routing feed | 04 Nov | 11 Nov | Fresh | |
| Dinner delivery feed, October 14 | Kitchen tablet feed | 02 Nov | 05 Nov | Stale | |
| Kitchen capacity, October 14 | Courier dispatch feed | 14 Oct | 19 Oct | Failed | |
| Courier dispatch, October 14 | Payment ledger | 22 Oct | 28 Oct | Fresh | |
| Refund ledger, October 13 | Menu inventory feed | 31 Oct | 03 Nov | Stale |
Decides whether evidence supports the selected order revision.
This is the first screen this role sees.
Review decisions · Independent Reviewer
| Source | Source revision | Decision | Reviewer | Evidence reference | |
|---|---|---|---|---|---|
| Rice bowl lunch, downtown | 70 | Pending | Theo Park | handoff_10418.jpg | |
| Grain bowl dinner, east end | 690 | Pending | Jules Dubois | kitchen_accept_10419.pdf | |
| Breakfast wrap order, harbor | 830 | Pending | Sara Haddad | courier_scan_10420.json | |
| Market salad order, midtown | 470 | Pending | Ravi Menon | refund_0772.pdf | |
| Noodle box lunch, north district | 730 | Pending | Owen Brooks | menu_stock_1184.csv |
Tracks driver references, fulfillment observations and action ownership.
This is the first screen this role sees.
Kitchen orders · Fulfillment Coordinator
Investigates discrepancies between expected and confirmed external outcomes.
This is the first screen this role sees.
External reconciliations · Reconciliation Analyst
Reviews metric definitions and the evidence behind reported results.
This is the first screen this role sees.
Source snapshots · Metrics Analyst
| Name | Source system | Coverage start | Coverage end | Freshness status | |
|---|---|---|---|---|---|
| Lunch order feed, October 14 | Order routing feed | 04 Nov | 11 Nov | Fresh | |
| Dinner delivery feed, October 14 | Kitchen tablet feed | 02 Nov | 05 Nov | Stale | |
| Kitchen capacity, October 14 | Courier dispatch feed | 14 Oct | 19 Oct | Failed | |
| Courier dispatch, October 14 | Payment ledger | 22 Oct | 28 Oct | Fresh | |
| Refund ledger, October 13 | Menu inventory feed | 31 Oct | 03 Nov | Stale |
Answer operational questions from orders, events, reconciliations and metric results.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Received | 25 | ||
| Accepted | 14 | 56% | |
| Preparing | 9 | 64% | |
| Dispatched | 7 | 78% |
Sample counts per stage
Group kitchen orders by Definition and Status to see where orders stand.
Compare promised at and delivered at for each kitchen orders record with a delivery date.
Sum refund amount by Organization from kitchen orders.
Group order fulfillment events by Parent and Outcome.
Group follow-up actions by assigned to and Status with due date.
Compare expected amount and confirmed amount on external reconciliations with Status.
Show captured at, coverage start, coverage end and freshness status for source snapshots.
Group metric results by Metric and Status with source row count and Reason.
See how Ghost Kitchen Aggregator fits your kind of team.
A group can keep orders from several kitchen partners within an operating organization.
A network can follow driver references and fulfillment observations as orders move through dispatch.
Regional teams can separate operating organizations while using the same order and review model.
Operators with many partner feeds can review source mappings and snapshot coverage before reporting results.
Each stage of order receipt to verified delivery names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Give each team member help with the order records and decisions they own.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 19 tablesStart with one team and one process, then add the rest once the basics are running.
Create the organization, people and partner definition for the first kitchen route.
Review the partner code, mapping fields, effective dates and source snapshot coverage.
Use a received order with a selected revision and evidence document; record a pending decision, then an approved or returned decision with a reason.
Follow the same order through preparation, dispatch and delivery with driver reference, observed event and actual time.
Compare expected and confirmed external amounts and assign a due action for a difference.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Ghost Kitchen Aggregator for your business. Begin with one organization, one partner and one order that your team can follow from receipt through review and delivery.
Each kitchen order links to an organization and a person. Agree the owner before the order enters the daily queue.
Use the partner code and organization on the partner definition. Check its active state, effective dates and policy reference for the order date.
The reviewer checks the selected revision and its evidence, then records a pending, approved, returned or rejected decision with a reason where needed.
Keep it on the kitchen order alongside the kitchen code, promised time and delivery time.
Review the fulfillment event outcome and the order's operation trace, then assign a follow-up action with a due date and resolution.
Use an external reconciliation linked to the order. It carries expected and confirmed amounts, a status and an evidence reference.
Check the definition, observation period, source snapshot, source row count and validity state before using the value.
The status history, review decisions, evidence documents, operation runs and steps retain the trail connected to the order.
Start free, then use Proto to change fields, steps and approvals before your team goes live.