Delivery aggregator orders often arrive through a separate tablet or phone. If staff do not enter them into the restaurant workflow, the kitchen may lose visibility and owners may miss item movement in daily reports.
What to include in the workflow
- Zomato and Swiggy orders accepted by staff.
- Phone orders from regular customers.
- Walk-in pickup and counter orders.
- Aggregator order references or customer phone numbers.
- KDS status updates for pending, cooking, and served handoff.
A simple operating model
Accept the order in the aggregator app, enter the same items in TabloSync New Order, use table 0 or a pickup counter number, then send the ticket to the kitchen. The order can then be tracked like any other ticket.
Why Standard and Premium restaurants need it
Once delivery orders are part of the dashboard, managers can see kitchen load and owners can review completed order totals, item demand, category revenue, and operational pressure more accurately.
Common setup tips
- Use a consistent counter code such as table 0 for delivery and pickup.
- Copy item notes exactly from the aggregator app.
- Keep payment settlement in the original aggregator channel.
- Mark the internal kitchen ticket complete after handoff.
Related guides
Delivery mode works best with a restaurant KDS, restaurant analytics, and billing workflow.
Common questions
What is Delivery Aggregator Mode?
Delivery Aggregator Mode is a workflow for entering delivery, pickup, Zomato, Swiggy, and phone orders into the same restaurant system used for kitchen tickets and reporting.
Which TabloSync plans include Delivery Aggregator Mode?
Delivery Aggregator Mode is included on Standard and Premium plans.
Why should aggregator orders be entered into the restaurant dashboard?
Entering aggregator orders into the dashboard keeps kitchen workload, item movement, completed order counts, and category analytics more accurate.
Book a TabloSync walkthrough to see Delivery Aggregator Mode inside the manager dashboard.