What is a cloud kitchen website, and how is it different from a restaurant website?
A cloud kitchen website is a delivery-only ordering site: no table booking, no dine-in photos, no “visit us” map. Its only job is to take a paid order, pass it to the kitchen and get it to a doorstep within the promised time.
That changes the design. A restaurant site sells an experience and a location; a cloud kitchen site sells speed and trust in food you cannot see being made. The menu comes first, with prices, portion sizes and veg or non-veg marks visible before a tap. The delivery check comes early, so someone outside your radius learns it on the first screen. And because many cloud kitchens run several brands from one kitchen, the site must handle more than one menu while the kitchen sees one queue.
A cloud kitchen website also becomes your record of who orders what. Aggregator dashboards show totals; your own site shows the customer, their address, their favourite dish and when they last ordered, which is what lets you win them back.
How much can a cloud kitchen save by taking orders directly?
The saving on each direct order is the aggregator’s deduction minus what the direct order costs you to fulfil. The aggregator figure should come from your own payout statement, not from anyone’s blog, because commission and fees differ by contract, city and plan.
Work it out per order. From a recent payout statement, add everything deducted from one typical order: commission, platform or listing fees, payment charges and any discount you funded. Then estimate the direct version of the same order: your payment provider’s fee, delivery cost (your rider’s time or the partner’s charge), and any small incentive you give for ordering direct. The difference is your margin gain per direct order.
Multiply by the orders you can realistically move, not by all orders. Regulars are the realistic group: people who already order from you every week or two. Multiply the monthly gain out, set it against the one-time build cost, and you can see how many months the site takes to pay for itself. Trust that calculation from your own statements over anyone’s promise, including ours.
- Take one typical order from your latest aggregator payout statement
- Add up every deduction on that order
- Estimate the direct cost: payment fee, delivery, any incentive
- Multiply the difference by orders you can move, not by total orders
What does “zero-commission ordering” really mean?
It means nobody takes a percentage of the food bill for listing or passing on the order. It does not mean the order costs you nothing. Every direct order still carries a payment fee, delivery cost and packaging, and the site itself needs hosting.
Some ordering products advertise zero commission but charge a monthly fee, a per-order fee or both. That can be a fair model; just compare it on a full year of your expected orders. With a custom cloud kitchen website from us, you pay a one-time build price, then hosting, domain and payment fees go to those providers directly. Maintenance is free for two months and optional after that from ₹8,000/mo.
The honest comparison is cost per order across a year, at your likely direct volume. At very low volumes a WhatsApp menu site is the cheapest route. At higher volumes a full ordering site is worth more because checkout, delivery hand-off and the kitchen screen save staff time on every order.
How do you run multiple brand menus from one cloud kitchen website?
Build one master item library in the back end and let each brand pick its dishes from it, with its own names, photos, prices and look. The customer sees separate brands; the kitchen sees one list of items to cook.
There are three common front-end set-ups. Separate domains per brand give each one a distinct identity and are the cleanest for search and for brand recall. Sub-pages on one parent site, such as a biryani brand and a bowls brand under your kitchen name, are cheaper to run and let a customer order from two brands in one cart. A hybrid uses separate domains for the two strongest brands and a combined site for the rest.
Google’s Business Profile guidelines matter here. They permit delivery-only brands operating from virtual kitchens if the brand has distinct branded packaging and a distinct website, and they require such brands to add service areas and hide the address. So if you want each brand to appear on Google Maps, each needs its own website presence and its own packaging, which is a strong argument for at least a separate page or domain per brand.
Multi-outlet operators with shared stock may also want multi-branch management software behind the site.
When an ingredient runs out, every dish using it should disappear from every brand at once. That single rule prevents the most common direct-order complaint: paying for something the kitchen cannot make.
We link dishes to their key ingredients or prep items, so marking “paneer” out of stock hides paneer dishes across all brand menus until you switch it back. Combos are built from items, not typed separately, so a price change on one item flows into its combos. Add-ons such as extra raita, a drink or a dessert are grouped per brand, with limits where needed.
Prices can differ between your site and the apps. Many kitchens price direct orders slightly lower or add a free item for direct orders, because the saved commission pays for it. The site does not care which strategy you choose; it just needs one place where you set prices for each channel. Menu timings also live here: breakfast brands switch on in the morning, late-night brands after ten.
WhatsApp and UPI ordering for a cloud kitchen
WhatsApp is often the fastest way to start taking direct orders, because your regulars already message you. A menu page that opens WhatsApp with the order filled in, followed by a UPI request, can run within two weeks.
The menu site shows every brand’s dishes with prices and a cart. At checkout, instead of paying on the site, the customer taps “Order on WhatsApp” and a message with items, quantities, address and phone arrives on your business number. You confirm and send a UPI link or QR. It is simple and cheap, but it depends on someone replying quickly, which is hard at 9 pm on a Saturday.
The next step is a full checkout with UPI and cards on the site, and WhatsApp used for updates: “order received”, “out for delivery”, “delivered”. Customers keep the familiar channel; staff stop confirming by hand. For kitchens with heavy chat volume, automated WhatsApp ordering is another route, starting at ₹40,000 as an automation project.
How the Business API side works is explained on WhatsApp Business API integration.
Delivery for direct orders: own riders or a third-party partner?
Use your own riders if you already have them for peak hours and your radius is small; use a hyperlocal delivery partner if you do not, or as overflow when your riders are busy. The website can support both.
With your own riders, the site assigns orders to a rider list and sends the customer a status link. With a partner, the site sends pickup and drop details to the partner’s API as soon as the kitchen marks an order ready, receives the tracking link and forwards it to the customer. The delivery fee shown at checkout can be calculated by distance bands from your kitchen, and orders beyond your maximum distance are refused before payment.
Which partner to use is your commercial choice. We integrate whichever you sign with, provided it offers an API, and we build a fallback: if the partner cannot assign a rider within a set time, your staff get an alert to arrange one. A late direct order is worse than a lost one, because the customer blames your brand, not the platform.
Keeping your customer data, the right way
Owning your customer list is the long-term value of a cloud kitchen website, and it only works if you collect it fairly. Ask for what you need to deliver, keep it secure, and send offers only to people who agreed to receive them.
At checkout we collect name, phone, address and an optional email, with a separate unticked box for offers on WhatsApp or SMS. Order history is stored against the phone number, so a returning customer sees “Reorder your last meal” on the home page. Data sits in a database in your hosting account, with access limited to staff who need it and a way to delete a customer’s details on request.
India’s Digital Personal Data Protection Act, 2023 sets rules on consent and use of personal data; how it applies to your kitchen is a question for your own legal adviser, and we do not give legal advice. What we do is build the site so consent is recorded, marketing opt-in is separate from ordering, and data is not collected just because it can be.
How do you get customers to order from your cloud kitchen website instead of apps?
Give them a reason and make it easy. The reason is usually a small benefit only available direct; the ease comes from a short link, a QR code and a site that loads fast and remembers them.
The channel that works best is the one you already control: the delivery bag. A card or sticker in every order with a QR code, the direct-order benefit and your WhatsApp number reaches exactly the people who like your food. Check your aggregator contract first for any restrictions on what you can include in packaging. Other channels include your Instagram bio, the brand’s Google Business Profile and a WhatsApp broadcast to customers who opted in.
Once someone orders direct, keep them there: a reorder button, saved address, UPI in one tap and honest delivery estimates. Do not over-discount; the aim is to share part of the saved commission, not to give all of it away.
- QR card in every delivery bag
- A direct-only benefit you can afford
- One-tap reorder and saved address
- Clear delivery time before payment
Where ONDC fits alongside your own cloud kitchen website
ONDC, the Open Network for Digital Commerce, is another channel, not a replacement for your own site. It is an open network set up by the Department for Promotion of Industry and Internal Trade, incorporated at the end of 2021 as a not-for-profit company, which lets sellers be discovered through several buyer apps without being exclusive to one.
Restaurants join through network partners that handle onboarding and menu listing. For a cloud kitchen, that can mean more discovery without depending on a single aggregator. Your own website still matters because the customer relationship and the reorder experience are fully yours there.
If you join ONDC, keep one master menu so prices and stock match across your site, the network and the apps. We can build the site so your menu exports cleanly in the format your network partner asks for. We do not act as an ONDC network participant ourselves.
The kitchen side: order screen, prep times and pausing orders
Direct orders need to land where the cooks already look. A kitchen order screen shows every brand’s orders in one queue, with the brand name in large type so packing uses the right bag.
Each order shows items, add-ons, notes and a timer from the moment it was paid. Tickets print automatically if you want paper. Staff mark orders “cooking”, “ready” and “picked up”, and each step can trigger the customer update and the delivery partner request. If you already run a POS, direct orders can be pushed into it through its API where one exists, so the kitchen still has one system.
The most useful button is “pause ordering”. At peak hours, when the kitchen is full of app orders, you can pause the direct site or lengthen the promised time by fifteen minutes. Promising a delivery you cannot meet costs a regular; saying “45 minutes tonight” keeps them.
A counter-and-kitchen system in more depth is covered on restaurant POS software.
How much does a cloud kitchen website cost in India?
A cloud kitchen website with BtechWaleTech starts at ₹10,000 (US$150) for a WhatsApp menu site and ₹50,000 (US$750) for a full ordering site with checkout, delivery radius and a kitchen screen. Both are starting prices and the quote is itemised.
The main cost drivers are the number of brands and how they are presented (separate domains cost more than sub-pages), the complexity of combos and add-ons, delivery partner API work, POS integration and customer features such as reorder and saved addresses. A single-brand kitchen with a WhatsApp menu sits at the bottom of the range. A four-brand kitchen with separate domains, partner hand-off and a POS link sits well above the store starting price.
An app is a separate project from ₹40,000, and in our view most kitchens should prove direct demand on the website first. For a line-by-line view of online store costs, see the ecommerce website cost guide.
How long does a cloud kitchen website take to launch?
A WhatsApp menu site takes 1–2 weeks. A full ordering site takes 4–8 weeks, depending on the number of brands and integrations.
The first week is about your menus and rules: dishes per brand, prices per channel, add-ons, timings, delivery radius and payment options. The next two to three weeks build the ordering site, checkout and kitchen screen on a staging link. Delivery partner and POS integrations follow, because they depend on accounts and API keys that you obtain. The last stretch is testing with real orders at real addresses, including what happens when a dish runs out mid-order.
Launching a week before a slow period, not before a festival weekend, gives your staff time to learn the kitchen screen while volumes are gentle.
Local search for a delivery-only cloud kitchen website
A delivery-only brand cannot rely on a shopfront address in search, so its visibility comes from service areas, distinct brand identity and a site that clearly states where it delivers.
Each brand’s page or domain carries Restaurant structured data with its menu, cuisine and service area, and the text names the neighbourhoods you deliver to in plain words. Following Google’s Business Profile rules for delivery-only brands, profiles hide the kitchen address and list service areas instead. Dish pages for your signature items, with honest descriptions and photos, give search engines and AI answer tools something specific to quote.
Direct-order sites are usually found by name, so most traffic will come from customers who already know you. Search helps at the margin over months. No one can guarantee rankings, and we do not. If you want steady work on it, see restaurant SEO.
Which technology suits a cloud kitchen website?
Pick by volume and complexity. A static menu site with WhatsApp ordering is cheapest and fastest. A mid-sized kitchen can use WooCommerce with food ordering extensions. A multi-brand kitchen with shared stock, partner APIs and a kitchen screen is usually cleaner as a custom web app built on Node.js or Python with PostgreSQL.
Whatever the stack, performance matters more than for most sites. Hungry customers on mobile data close slow pages, so menus load light, images are compressed, and the cart works even on budget Android phones. A progressive web app lets customers add the site to their home screen without an app store, which covers much of what an app would do for a fraction of the cost.
WhatsApp menu site
Lowest cost; orders confirmed by hand. Suits a single brand or a trial.
WooCommerce with food extensions
Familiar dashboard, good for one or two brands with moderate volume.
Custom ordering web app
Shared item library, multi-brand, partner APIs, kitchen screen, full control.
Progressive web app
Home-screen icon and faster repeat visits without an app store listing.
Worked example: a hypothetical three-brand kitchen in Gurgaon
The following scenario is made up to illustrate a build; it is not a client or a result. A kitchen in Gurgaon runs three delivery brands from one space: a biryani brand, a rolls brand and a healthy-bowls brand. Almost all orders come through aggregators, and the owner wants regulars to order direct.
We would propose a custom ordering site starting at ₹50,000. The biryani and bowls brands get their own domains, because they have the strongest names; the rolls brand sits as a page on the biryani site so customers can combine them in one cart. One item library feeds all three, and marking chicken out of stock hides every chicken dish across brands. Checkout takes UPI and cards; COD is off. Orders within a set radius go to the kitchen’s own riders, and beyond that or during peaks to a delivery partner through its API.
A kitchen screen shows all three brands in one queue with a pause switch. Every aggregator bag carries a QR card offering a small direct-only extra. Customers who opt in get order updates on WhatsApp and a reorder link. Free maintenance for two months covers menu changes and the first round of tweaks after staff feedback.
Cloud kitchen website builds across India
We build cloud kitchen websites remotely for kitchens in any city, with the same process and starting prices. Briefs happen on WhatsApp or a video call, and you test everything on a staging link from your own phone.
Delivery-heavy metros such as Bengaluru, Gurgaon, Noida, Mumbai and Pune have the most multi-brand kitchens, while growing markets like Indore, Jaipur, Lucknow and Bhubaneswar suit kitchens starting with a WhatsApp menu site before a full build.
Related food builds include bakery website design for cake ordering and tiffin service websites for subscription meals.