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
- Process
- Fulfillment to delivery
Fulfillment to delivery
Order Operator and Fulfillment Coordinator compare the event outcome, driver reference and actual delivery time before treating the delivery record as settled. Start with a specific order and keep its organization, owner and partner definition in view. Ask the person at each stage to point to the record that supports the next decision.
Step by step
-
Prepare order Order Operator
Record preparation and the event sequence. Order Operator checks the linked record before the next handoff.
- Record preparation and the event sequence
- Updates Kitchen orders, Order fulfillment events
-
Dispatch order Fulfillment Coordinator
Keep the driver reference and promised time together. Fulfillment Coordinator checks the linked record before the next handoff.
- Keep the driver reference and promised time together
- Updates Kitchen orders, State history
-
Record observation Fulfillment Coordinator
Compare the event with the original execution reference. Fulfillment Coordinator checks the linked record before the next handoff.
- Compare the event with the original execution reference
- Updates Order fulfillment events, Operation runs, Operation steps
-
Confirm delivery Fulfillment Coordinator
Record the actual delivery time and delivered state. Fulfillment Coordinator checks the linked record before the next handoff.
- Record the actual delivery time and delivered state
- Updates Kitchen orders, Order fulfillment events
Who does what
Roles and permissions- Order Operator
- And Fulfillment Coordinator compare the order, event outcome and delivery time before the final handoff.
Set up Ghost Kitchen Aggregator your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.