Updated · 6 min read · By the Digiboy team
A blueprint is a worked example for a typical business of this kind. It is not a client project and it reports no results. It shows how we would plan the work, so you can judge our thinking before you hire us.
- Business
- 60-seat family restaurant with takeaway, Kozhikode
- Main problem
- Online orders come only through delivery apps, and phone orders are missed at peak hours
- What we would build
- Own-site ordering with a QR menu, delivery zones, UPI payment and WhatsApp confirmation
- Typical timeline
- 6 to 8 weeks
- Typical budget band
- ₹60,000 to ₹2,00,000 (market range, not a quote)
This is a blueprint: a worked example of how we would plan direct online ordering for a typical restaurant. It is not a client case study and it describes no delivered project. In short, a restaurant like this needs one menu that feeds its website and QR code, ordering for pickup and nearby delivery, UPI payment and a WhatsApp confirmation. That typically costs ₹60,000 to ₹2,00,000 and takes six to eight weeks.
The situation
Picture a 60-seat family restaurant in Kozhikode known for biryani and meals, with a busy takeaway counter. Online orders arrive only through delivery apps. Phone orders come to one handset at the cash counter, and at 1 pm on a Friday nobody answers it.
The owner has two worries. The apps charge a commission on every order, including orders from regulars who would have ordered anyway. And the restaurant does not know who those customers are, so it cannot tell them about a Ramadan menu or a new catering offer.
Own website or delivery apps: which is better?
Neither replaces the other. Delivery apps bring discovery, which means people who did not know the restaurant find it while browsing. In return they charge a commission and keep the customer relationship. The rates vary by platform and contract, so check your own agreement.
Direct ordering is for people who already know you: regulars, office lunch groups, families nearby. They order from your site, you pay only the payment fee and delivery cost, and you keep their contact details with their consent.
The plan, then, is to keep the apps for new customers and move regulars to direct ordering over time.
What does the system need to do?
The system needs to take a correct order, get paid and tell the kitchen, without adding a job for the cashier. In detail:
- Show the current menu with photos, prices and what is sold out today.
- Take pickup and delivery orders, with a delivery fee that depends on distance.
- Accept UPI, cards and, if the owner wants, cash on delivery.
- Confirm on WhatsApp so the customer has proof and the restaurant has a number to call.
- Alert the kitchen or counter clearly when an order arrives.
What we would build
First version
- A fast restaurant website: menu, photos, timings, location and one Order button.
- One menu database feeding both the ordering pages and a QR menu for tables.
- Ordering for pickup and for delivery inside defined zones, with a minimum order value.
- Item options such as portion size, spice level and add-ons.
- Payment by UPI and cards through a payment gateway, which is a service that collects online payments for you. See our article on UPI payments on your website.
- WhatsApp confirmation to the customer and an order alert with sound on a counter tablet.
- A simple admin screen to accept orders, mark items sold out and change prices.
- Opening hours and a pause button for when the kitchen is overloaded.
Later
- Scheduled orders for parties and catering enquiries.
- Repeat-last-order and saved addresses.
- Offers by WhatsApp to customers who have opted in, through WhatsApp automation.
- A kitchen display, and a link to the billing software.
Pages and screens
| Page or screen | Who uses it | What it does |
|---|---|---|
| Home | Customers | Photos, timings, location, Order and Call buttons |
| Menu and ordering | Customers | Browse by category, add to cart, choose options |
| Checkout | Customers | Pickup or delivery, address, payment |
| Order status | Customers | Accepted, being prepared, ready or on the way |
| QR menu | Diners at the table | Same menu, view only, in English and Malayalam |
| Catering and party orders | Customers | Enquiry form that goes to WhatsApp |
| Orders screen | Counter staff | New orders with sound, accept or reject, print |
| Menu manager | Owner or manager | Prices, photos, sold-out items, hours, delivery zones |
Technology choices and why
We would build this as a website, not an app. A regular customer will tap a link in a WhatsApp message or scan a QR code on last week’s parcel. Asking them to install something first loses many of them. If the restaurant later wants an icon on the customer’s home screen, the site can become a progressive web app, which is a website that can be installed like an app.
The menu would live in one place. Many restaurants end up with a PDF menu, a QR menu and an app menu that all disagree. One source prevents that.
Menu pages would be built to load quickly on mobile data, with compressed photos. Payment would go through an established Indian payment gateway instead of anything custom, because handling card data is their job, not the restaurant’s.
Order messages would start with simple WhatsApp confirmations. When volume grows, the official WhatsApp Business Platform allows automatic status updates.
How much would it cost and how long would it take?
A project like this typically falls between ₹60,000 and ₹2,00,000 and takes six to eight weeks. These are typical market ranges in Kerala for 2026, not Digiboy’s price list.
| Item | Typical market range |
|---|---|
| Website with direct ordering and QR menu | ₹60,000 to ₹2,00,000, one time |
| Domain name | ₹800 to ₹1,500 a year |
| Hosting and upkeep | From about ₹5,000 a year, more for busy sites |
| Payment gateway fee | Typically around 2 percent per online payment. Check current pricing |
| WhatsApp automated messages | Charged by usage. Check the provider’s current pricing |
A menu-only website with a QR menu and WhatsApp ordering sits well below this band and is a fair starting point for a very small kitchen. The upper end covers large menus, several delivery zones and links to billing software. For a wider view of store pricing, see the e-commerce website cost guide.
What to measure after launch
- Direct orders each week, and how many are repeat customers.
- The share of all online orders that are direct, compared with the apps.
- Average order value on the site.
- Orders rejected or cancelled, and why.
- The time from order placed to order accepted.
Write down the current app and phone order numbers before launch. Without a starting point, nobody can say whether direct ordering is working.
Mistakes to avoid
- Building before delivery is decided. Own riders, a delivery service or pickup only: this choice shapes the whole system.
- No one watching the orders screen. An order that sits unaccepted for fifteen minutes loses the customer for good.
- Too large a delivery area. Cold biryani earns bad reviews. Start small and widen later.
- Expecting orders without telling anyone. Put the QR code on bills, parcels, tables and the Google Business Profile.
- A menu without photos. People order what they can see.
- Promising offers the kitchen cannot sustain. A small first-order discount is enough to start the habit.
Planning ordering for your restaurant?
See what we build for restaurants and food businesses and how our e-commerce development service works. A first call is free, and the quote that follows is fixed and in writing.

