19:40
Zomato and Swiggy orders on the same rail as everything else
Aggregator orders arrive by webhook, match to your outlets and menu, reach the kitchen, and are recorded at the price the partner settles.
Link each branch to its Zomato and Swiggy outlet and map the partner's item ids to your menu once. From then on, orders arrive on their own, go to the kitchen display and stock, and sit in order history beside counter and table orders.
An aggregator order keeps the totals the partner sent. That is the figure you are settled on, so EasyTable never recomputes it from your own price list and your books agree with their remittance.
How it works
01
Every delivery kept as evidence
Each incoming payload is stored before it is processed — the record of what the partner actually sent when an order is disputed weeks later.
02
Signed, per outlet
Webhook signatures are checked against the named outlet's own signing secret before any order is created.
03
Retries never double an order
A partner retrying a delivery is recognised and ignored, so the kitchen never cooks the same order twice.
04
Unmapped items still reach the kitchen
An item nobody has mapped yet is kept under its partner name, flagged for mapping, and still cooked.
Questions about zomato & swiggy
- Does EasyTable push menus or accept orders on Zomato and Swiggy?
- Inbound orders are built: they arrive by webhook and flow into the kitchen, stock and reports. Outbound calls such as menu push and accept or reject need partner credentials and are not built yet.
- Can delivery apps have different prices from the counter?
- Yes. Each channel can have its own price for any item at any branch, or inherit the branch price.