Heart Attack — Restaurant Ordering

Overview

Multi‑branch restaurant ordering: cuisines and items, delivery zones with per‑zone charges, partial and offline payments, customer referrals and automated message templates.

01The challenge

The restaurant takes orders through four different channels — app, website, cashier and table — and each channel had its own tool. The kitchen could not tell which order came first, the cashier could not see app orders, and management could not read one figure for the day’s sales.

Multiple branches compound it: menu, price and availability differ by branch, and no branch should see another branch’s orders.

02What we built

We unified the four channels into one order pipeline: whatever the source, an order is one row in the same table with one status and one change history. The kitchen reads an ordered queue, the cashier sees everything, and management reads one number.

The menu is branch-scoped: the same product carries a different price, availability and promotion per branch, and each branch has a dashboard that sees nothing else. Tables carry QR codes that open the menu and open an order already bound to that table.

On top of that: delivery areas with different charges, couriers with live tracking and ratings, customer wallet, loyalty points and referrals, and more than twelve payment gateways with partial and offline payment options.

03The outcome

Branches are run from a per-branch dashboard with one consolidated report for management, and the kitchen works from a single queue instead of three conflicting screens.

QR table ordering removed a whole intermediate step: the guest orders from their phone and it reaches the kitchen already bound to a table number.