EatSure orders
Takes EatSure orders straight into the kitchen. Every order lands on the Online orders screen with the rider, the delivery OTP and the customer's items, prints its kitchen tickets by itself, and is accepted or refused without leaving the counter. EatSure is the food delivery app of Rebel Foods that also lists outside restaurants, so one order can hold dishes from several kitchens.
| At a glance | |
|---|---|
| Type | Add-on module |
| Group | Sell |
| Price | Free |
| Provides | Receive orders from food-delivery platforms |
| Needs | Nothing to switch on. Orders become ordinary orders, and kitchen tickets need Restaurant ops (KOT). |
| Offered to | Restaurant |
| Permission | Manage add-ons (addons.manage) to connect; View orders to see Online orders |
What it does
EatSure orders works exactly as Zomato orders and Swiggy orders: all of them provide Receive orders from food-delivery platforms, and any one opens Online orders under General in the menu and on the POS top bar. A restaurant on several platforms sees all their orders on one screen, each with its platform's logo, with a platform filter.
Each order arrives as an ordinary order on the online channel (kitchen tickets print, stock moves, reports count it), with EatSure's order id, the rider's name and phone, the delivery OTP and EatSure's money breakdown. Items are priced from your menu, matched by SKU, then short code, then name; a dish your menu has never heard of still reaches the kitchen under EatSure's name. A repeated push never makes a second order.
Connecting EatSure
- Go to Workspace → Modules, filter to Add-on modules. EatSure orders is under Sell, with EatSure's logo.
- Open its ⋮ menu and choose Enable.
- Choose an Order push token. Give EatSure the Order push URL shown at the top of the dialog, with the token as the
x-api-keyheader. - Press Enable.
| Field | Required | What to enter |
|---|---|---|
| Order push URL | (shown) | Read-only. EatSure's order push endpoint. Treat it like a password. |
| Order push token | Yes | Any secret string, sent by EatSure as the x-api-key header. A push without it is refused. |
| EatSure restaurant ID | No | Your outlet id at EatSure, used when sending your decisions back to them. |
| Platform GSTIN (e-commerce operator) | No | EatSure's own GSTIN, as printed on its invoices to you. Stamped on each order as it arrives and named by the GST returns. Changing it later applies only to orders that arrive afterwards. |
| EatSure partner API key | No | From your EatSure partner manager. Needed only to send your decisions back to EatSure. Write-only once saved. |
EatSure's own webhooks. Besides new orders, EatSure can send its other news to the same Order push URL with ?event= added: order, status, rider, fetch_status, cancel_request, outlet_status, menu_processing and menu_moderation, exactly as for Zomato. When the outlet is connected through the platform itself rather than through your own address, EatSure reaches you by your EatSure restaurant ID, so make sure it is right.
Working the orders
Everything on Zomato orders → Working the orders works the same for EatSure:
- a new order rings on every screen until someone acts on it;
- Accept with a preparation time (EatSure's own suggestion when it sends one), or Refuse with a reason and, for Items out of stock, the dishes that ran out;
- Food ready and Handed to rider, with the missing-item checklist when EatSure asks for it;
- Answer the cancel request when the customer asks EatSure to cancel;
- Call customer or rider (masked numbers, asked for when you open it and never kept) and Ask for another rider on a bulk order;
- Stores opens or closes the outlet on EatSure with a reason, and Help from EatSure opens EatSure's support chat (only ever a page on EatSure's own site);
- Out of stock switches the dishes that ran out off until tomorrow without refusing the order;
- Settle issues the order's bill and records it as paid by EatSure (by default the moment it is handed to the rider), so it counts in the day close as EATSURE and in the GST returns.
On the POS Live view each EatSure order is a card in EatSure's colour with its logo, the OTP, the rider, the customer's area, a Prepare in countdown and its next step as one button, and a EatSure chip shows the count and whether the store is taking orders.
Your menu on EatSure
Online orders → Menu sends your whole menu to EatSure (dishes, sizes, add-on groups, categories and their hours, prices, taxes and packaging charges) after the same checks as for Zomato, and shows EatSure's answer underneath. Switching a dish, a size or an add-on off on Item on/off tells EatSure at once, and the ordering hours in Settings → Online orders are sent as your delivery timings.
Without the partner API key and restaurant ID, everything works here; the decisions are simply not sent back to EatSure.
Turning it off
Turn off on the ⋮ menu asks first. EatSure's pushes are refused from that moment; the settings are kept for when it goes back on. Online orders stays while another delivery platform is still connected.
Ready-made automations
None. Its orders go straight to the kitchen display and Online orders; the automation engine has no food-delivery event to react to yet.
In the desktop and mobile apps
The restaurant desktop app shows Online orders as an online-only screen (one notice when offline), and the EatSure cards on its Live view while online, with the logo built into the app. The Captain phone app does not carry them.
Related guides
- Online orders, Zomato orders, Swiggy orders, Restaurant ops (KOT)
- Module guides index