Every evening, the same scene plays out in restaurants across India. Tables sit half empty while the phone rings with reservation requests nobody has time to answer, and the orders that do come in arrive through aggregator apps that keep a fifth or more of every bill. The restaurant is busy. The restaurant is also, somehow, not making money.

A restaurant website with online table reservations fixes a surprising amount of this. Not by replacing the aggregators overnight, but by giving your best customers — the ones who already know your name — a direct way to book a table, see your menu, and pay you without a middleman taking a cut.

The real cost of food aggregator commissions

Food delivery and discovery platforms typically charge restaurants somewhere in the range of 20–30% commission per order, and that is before packaging costs, discounts you are nudged into funding, and advertising fees to stay visible in search results on their own app.

For dine-in, the discovery platforms work differently but the logic is similar: they own the customer relationship. The diner who found you through an app books through the app, reviews you on the app, and gets retargeted by the app — often with offers from your competitors on the same screen.

None of this means aggregators are useless. They are excellent at one thing: putting you in front of strangers. The problem is when strangers who become regulars still reach you through the same expensive pipe. A regular who visits twice a month should not cost you a commission every single time.

Why direct table reservations change the economics

A direct reservation costs you nothing per booking. That is the headline, but the second-order effects matter more:

  • You keep the customer's details. Name, phone number, party size, visit history — with a direct booking, that data is yours, collected minimally and used to serve them better.
  • You control the experience. Confirmation on your terms, your cancellation policy, your special-occasion notes, no third-party branding between you and your guest.
  • Your Google presence starts working for you. When someone searches your restaurant's name and lands on your own website, a "Reserve a table" button converts that intent directly instead of leaking it to a listing page.
  • WhatsApp becomes a booking channel. In India, half your reservation requests probably already arrive as WhatsApp messages. A link to your booking page turns "table for 4 tonight?" into a confirmed reservation in one tap, without anyone at the counter typing into a diary.

What a reservation-ready restaurant website needs

A restaurant website that actually takes bookings — rather than just displaying a phone number — needs a few specific things:

  1. A live reservation system, not a contact form pretending to be one. Guests pick a date, time, and party size and get a confirmed table.
  2. Protection against double-booking. Two families should never be confirmed for the same table at the same slot. This must be guaranteed by the system, not by a manager cross-checking a register.
  3. A crawlable menu with prices, so Google can index your dishes and diners can decide before they book.
  4. Tap-to-call and WhatsApp buttons for the guests who still prefer to talk — many do, especially for large groups.
  5. Mobile-first speed. Most of your traffic is a phone on a 4G connection deciding where to eat in the next hour. A slow site is an empty table.

CommerceOS was built with restaurants as one of its core site types. You start on a restaurant theme, and table reservations come built in with a no-double-booking guarantee — every confirmation is an atomic check against real availability, so overlapping requests can never both succeed. Your menu lives as a structured directory you edit yourself, and the whole storefront serves cached pages in under 50 milliseconds, which matters when a hungry customer is deciding between you and the place next door.

How online table booking works without chaos

The fear most owners have is operational: "What if the website books tables we don't have?" A good system removes that fear structurally.

You define your capacity — how many tables, what sizes, which time slots. Guests book against that capacity. When a slot is full, it simply stops being offered. When two people race for the last table at 8 pm, exactly one booking succeeds and the other is offered the next slot. There is no register to reconcile and no "sorry, we didn't see your message."

Walk-ins still work the way they always have. The website handles the plannable demand — weekend dinners, birthdays, office groups — which is exactly the demand you least want to lose to a busy phone line.

Turning existing traffic into confirmed tables

You do not need new marketing to fill tables through your own site. You need to redirect attention you already have:

  • Google Business Profile: set your website as the primary link, so name-searches land on a page that can take a booking.
  • Instagram bio: replace the aggregator link with your own reservation page.
  • WhatsApp replies: save a quick reply with your booking link for every "do you have a table?" message.
  • Table tents and bills: a QR code to your site converts tonight's walk-in into next month's direct booking.

Payments follow the same direct logic. CommerceOS lets you connect your own payment gateway — Razorpay, PayU, Cashfree, or PhonePe — so any advance payments or event deposits land in your account through UPI, cards, or netbanking, with no platform sitting in between.

FAQ

How much commission do food aggregators charge restaurants in India?

Commissions commonly fall in the 20–30% range per order for delivery platforms, varying by city, category, and contract. Discovery and dine-in products monetize differently — through ads, visibility fees, and dining programs — but the shared pattern is that the platform owns the customer relationship, not you.

Can customers book a table on my website without calling?

Yes. With a built-in reservation system, guests choose a date, time slot, and party size and receive instant confirmation. Calls remain an option for guests who prefer them; the website simply absorbs the bookings your phone line was dropping.

What stops the website from double-booking my tables?

The reservation engine confirms a booking only if capacity is genuinely available at that instant — it is a single guarded operation, not a lookup followed by a save. On CommerceOS this no-double-booking guarantee is a platform rule, not a setting you can accidentally break.

Do I need a developer to build a restaurant website with reservations?

No. On CommerceOS you pick the restaurant site type, start from an industry theme, and arrange your pages in a visual editor with 80+ sections — menu, gallery, reservations, location, reviews. Most owners assemble a working site in an afternoon.

Related reading: if you run more than one outlet or format, see how one login can run every location's website.

Your regulars already want to book with you directly — they just need a place to do it. Set up your restaurant site, switch on reservations, and put the link everywhere your customers already are. You can start free with a 14-day trial, and check pricing whenever you are ready to go live on your own domain.