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
- Integrations
Integrations
Plan partner feeds, delivery receipts and external outcome evidence.
- Ghost Kitchen Aggregator
- Kitchen partner feeds
- Delivery evidence
- External order outcome source
- Source data for metrics
Systems to connect
- Kitchen partner feeds. Agree the partner code, source fields, target fields and effective mapping version before importing an order.
- Delivery evidence. Record a driver reference on the order and a receipt reference on an operation step when an external delivery source supplies one.
- External order outcome source. Supply the external reference, expected and confirmed amounts, currency and evidence reference for reconciliation.
- Source data for metrics. Capture the source system, coverage period and freshness status before using observations in a result.
How connections are governed
Agree the source identity for each order and external outcome. Record the effective partner policy and mapping used at intake. If a provider outcome is uncertain, investigate the original operation key and step receipt. Use a follow-up action for the named person resolving the difference. Review snapshot coverage and metric definition before sharing calculated results.
Set up Ghost Kitchen Aggregator your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.