Add-ons & surfaces
Your own front door, not a marketplace stall.
An ordering website that belongs to the restaurant — delivery, takeaway and table bookings, on your own domain, serving the same menu and the same stock as the counter. The order arrives in the same queue as everything else, and no one takes a cut of it.
Your domain or ours·one menu, one stock·online payment or pay on delivery·no per-order commission
The site your customers actually land on.
Hero, menu and cart on your own address. Most of its traffic arrives on a phone, so the same storefront is built mobile-first — the layout on the right is not a separate app.
Your ordering website · desktop and phone
Six things this module actually does.
Your own address
Run it on a Tadka Tech address from day one, then point your own domain at it when you are ready. The site keeps the restaurant's name, not ours.
One menu, one stock
The storefront reads the same menu the counter uses. Change a price once; an item whose stock ran out stops being orderable online too.
Delivery, takeaway, table
Delivery inside the radius you set, collection at the counter, and a table booking that lands in the reservations book.
Paid before it is cooked
Online payment by UPI or card through your own gateway account, or cash on delivery — settled against the same bill either way.
Same queue as everything else
A web order shows up beside the QR orders and the counter orders, fires the same kitchen ticket and closes on the same GST bill.
Your customer, your list
The diner signs in with a one-time code, sees past orders and points, and the profile belongs to the restaurant — not to an aggregator.
They can see where it has got to.
The tracking page is driven by the same status the kitchen is working to. When the ticket is bumped on the kitchen screen, the diner's page moves — and a WhatsApp message goes out on the same event.
- Placed, accepted, preparing, ready, on the way, delivered — the real order status
- Rider name and an ETA once the run is assigned
- Sign in with a one-time code — no password, no app to install
- Past orders with a one-tap reorder, and the points balance beside them
- A table booking made here lands in the same reservations book as a phone call

Signed in with a code
- Step 1No password
- Step 2Free to you
- Step 3Their profile
Their order history
480 points- #ORD-039₹1,240Reorder
- #ORD-021₹980Reorder
- BookingConfirmed
Diner · order tracking and account
Back office · storefront settings
Point a domain at it, and you are open.
The storefront exists on a Tadka Tech address the moment the module is switched on. Bringing your own domain is a DNS record and a certificate the platform issues and renews for you.
- Your own domain, with TLS issued and renewed automatically
- Choose what the site accepts: delivery radius, takeaway, table bookings
- Opening hours the site honours — it closes itself when the kitchen closes
- Your own payment gateway account, so settlements go to your bank, not ours
- Offers scoped to the web channel only, if you want the site to have its own deal
A channel, not a second system.
The storefront has no database of its own. It reads and writes the same tables the counter does.
Nobody signs in to use it.
- Your customerNo staff account at all. Browses and orders as a guest, or verifies a phone number with a one-time code to get order history, saved addresses and points.
- OwnerOwns the storefront. Connects the domain and the payment gateway, decides what the site accepts, and sets the delivery radius.
- ManagerKeeps it current. Publishes menu changes, opening hours and web-only offers, and watches what the channel is bringing in.
- SupervisorWorks the incoming orders. Accepts, holds or rejects a web order exactly as a counter order — there is no separate web inbox to watch.
- CashierCloses them out. Settles a web order that was not paid online, and issues the same GST bill.
- Delivery agentRuns the delivery. Picks up the assignment in the rider app, with the address and the amount to collect if it is cash.
Permissions are atomic and checked on every endpoint — a role is a named bundle of them, not a rank. Staff can hold several bundles at once, and effective access is the union.
See it running on your menu.
We set the restaurant up with you — menu, tables, staff and printers — rather than handing over a login and wishing you luck.