1. Ghost Kitchen Aggregator
  2. Frequently asked questions
FAQ

Questions, answered

Common questions about setting up kitchen orders, review and delivery work.

Ghost Kitchen Aggregator

9 questions

Can't find it? Write to support@erp.ai.

How do I get started?

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.

Who owns an order?

Each kitchen order links to an organization and a person. Agree the owner before the order enters the daily queue.

How do we identify a partner?

Use the partner code and organization on the partner definition. Check its active state, effective dates and policy reference for the order date.

How is an order revision reviewed?

The reviewer checks the selected revision and its evidence, then records a pending, approved, returned or rejected decision with a reason where needed.

Where does the driver reference go?

Keep it on the kitchen order alongside the kitchen code, promised time and delivery time.

How are delivery exceptions handled?

Review the fulfillment event outcome and the order’s operation trace, then assign a follow-up action with a due date and resolution.

Can we compare external outcomes?

Use an external reconciliation linked to the order. It carries expected and confirmed amounts, a status and an evidence reference.

How do we read a metric result?

Check the definition, observation period, source snapshot, source row count and validity state before using the value.

Where can I see an order's history?

The status history, review decisions, evidence documents, operation runs and steps retain the trail connected to 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.

How to get started