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
- Partner feed to order
Partner feed to order
Kitchen Coordinator compares the mapping version and effective date with the original order. Order Operator keeps the order number and partner definition linked during the correction. 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
-
Identify organization Admin
Confirm the operating scope and owner. Admin checks the linked record before the next handoff.
- Confirm the operating scope and owner
- Updates Organizations, People
-
Check partner Kitchen Coordinator
Use the partner code and effective dates. Kitchen Coordinator checks the linked record before the next handoff.
- Use the partner code and effective dates
- Updates Kitchen partners
-
Check mapping Kitchen Coordinator
Compare source fields and snapshot coverage. Kitchen Coordinator checks the linked record before the next handoff.
- Compare source fields and snapshot coverage
- Updates Source mappings, Source snapshots
-
Register order Order Operator
Keep source identity and the selected partner definition. Order Operator checks the linked record before the next handoff.
- Keep source identity and the selected partner definition
- Updates Kitchen orders
Who does what
Roles and permissions- Admin
- Maintains the organization, Kitchen Coordinator checks partner and mapping records, and Order Operator registers the order.
Set up Ghost Kitchen Aggregator your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.