What is a WhatsApp ordering system, in plain words?
It is a way for customers to order from you inside the app they already use all day, without calling, without typing a long message and without a marketplace in between. They see what you sell, tap items into a cart, pay or choose cash on delivery, pick a time, and get a confirmation. You see a clean order, not a stream of chat bubbles.
Most small food and grocery businesses in India already take orders on WhatsApp, just by hand. The owner or a helper reads “1 kg atta, 2 packets milk, the usual biscuits”, works out the total, types it back, waits for a UPI screenshot and scribbles the order on paper. That works at ten orders a day. At fifty it breaks: messages get missed, totals are wrong, and nobody knows which order is ready.
A WhatsApp ordering system replaces the typing and the scribbling. The chat stays, because customers like it, but the catalogue, cart, payment check, delivery slot and kitchen ticket become automatic. Staff step in only for the conversations that need a human.
Which businesses get the most from a WhatsApp ordering system?
Businesses with loyal local customers who reorder often gain the most, because every repeat order moved from a marketplace to WhatsApp keeps the full margin. The shape of the system changes a lot by trade.
Restaurants and cloud kitchens
Short menus with add-ons, lunch and dinner windows, a kitchen that needs orders paced. Slot capacity and a kitchen screen matter more than a big catalogue.
Bakeries and cake shops
Daily items plus custom cakes ordered days ahead. They need a message-on-cake field, photo references, advance payment and next-day cut-off times.
Kirana and grocery stores
Hundreds of items, frequent price changes, weights and pack sizes, and many customers on monthly credit. Search and repeat-last-order save the most time.
Sweet shops, meat, fish and dairy
Items sold by weight, festival rushes and morning-only delivery. Weight options and fixed delivery windows keep things calm.
If your trade sells mainly to other businesses, such as a distributor taking orders from retailers, a B2B ordering app with dealer price lists usually fits better than a consumer-style WhatsApp flow.
Saving marketplace commission without losing new customers
Move repeat customers to direct WhatsApp orders and keep marketplaces for discovery. That split gives you the margin on regulars while strangers still find you where they browse.
Marketplaces do real work: they bring hungry or busy people who have never heard of you, supply riders and handle payment. Their commission pays for that. But when a family that has ordered your thali every Sunday for a year still orders through the app, you are paying a finder’s fee on a customer you already found. We don’t quote marketplace commission rates here because they vary by city, category and contract; check your own settlement statements to see what regulars cost you.
The practical move is gentle. Put a small card in every parcel with your WhatsApp QR code and a reason to use it, such as a free extra on direct orders or first access to specials. Check your marketplace agreement first, because some restrict how you contact customers acquired through the platform; if in doubt, ask your own lawyer. Over months, the regulars drift to the channel that is easier and better value for both sides.
WhatsApp catalogue or web-catalogue link: which should you use?
Use the native WhatsApp catalogue when your list is small and stable; use a web-catalogue link when you have many items, complex options or frequent changes. Both end with the order inside the chat.
The native route lives inside WhatsApp. Meta’s developer documentation explains that inventory is uploaded to a catalogue through Meta Commerce Manager or its Commerce API, and that businesses can send single-product messages or multi-product messages showing up to 30 items organised into sections. Customers add items to a cart, and the documentation notes they can add up to 99 units of any one item. When they send the cart, your system receives it as a webhook notification with the order details.
The web-catalogue route opens a light mobile page from a link in the chat. It handles what the native catalogue struggles with: half-and-half pizzas, cake messages, weights like 250 g of paneer, combos, and search across hundreds of grocery items. The page sends the finished cart back into WhatsApp, so the customer never leaves the conversation for long. For the bigger question of whether a catalogue can replace a full online store, see WhatsApp catalogue vs website.
- Under about 60 simple items, few options → native catalogue
- Add-ons, weights, custom notes or 200+ SKUs → web-catalogue link
- Prices change daily (vegetables, fish) → web catalogue fed from a sheet
- Want both → native catalogue for bestsellers, web link for the full range
How the cart-to-order flow works, step by step
Every WhatsApp ordering system follows the same backbone, whatever the trade. Seeing it laid out helps you spot gaps in any proposal.
- Customer messages “Hi” or scans your QR code; a greeting offers Menu, Reorder and Talk to us.
- They browse the catalogue or web menu and build a cart with options and notes.
- The cart arrives as an order; the system checks stock, delivery zone and slot capacity.
- A summary goes back with the total, delivery charge and slot choices.
- The customer picks a slot and pays by UPI, or confirms cash on delivery.
- Payment is confirmed automatically and the order appears on your dashboard.
- Each status change (accepted, preparing, out for delivery, delivered) messages the customer.
The step people underestimate is the third one. A cart is a wish list until the system checks that the items exist, the address is within range and the kitchen can make it by the chosen time. Skipping those checks is how manual WhatsApp ordering ends in apology calls.
UPI payment and order confirmation inside WhatsApp
Ask for payment after the order is validated and before it is accepted, and confirm it automatically. Checking UPI screenshots by eye is slow and open to fakes.
Three payment patterns work in India. Meta’s developer documentation for its Payments API in India describes sending an order-details message that lets customers pay through the UPI apps installed on their phone, or by cards, net banking and wallets, and says payment status comes back to the business as webhook notifications. A second option is a UPI or payment-provider link with the exact amount, which confirms through the provider. The third is cash on delivery, which many kirana customers still prefer; we record it and mark the order paid when the rider settles up.
Confirmation is where trust is built. The moment payment succeeds, the customer gets a message with the order number, items, total paid and slot, and the kitchen or counter gets the order. If payment fails or times out, the order waits a few minutes, sends one polite nudge, then releases the slot. Refunds for cancelled prepaid orders follow the rules of whichever payment route you use, and we put your refund wording in the confirmation so there are no surprises.
Delivery zones, slots and cut-off times
Set zones by pincode or distance, give each slot a capacity, and add cut-offs for items that need preparation. That keeps promises you can actually keep.
Zones stop the most common headache: an order from across the city that nobody can deliver. The system checks the pincode, or the shared location pin, against your delivery area and either quotes the delivery charge or offers pickup. Different zones can carry different charges or minimum order values.
Slots protect the kitchen. A bakery might accept six cake orders per two-hour slot, a restaurant twenty meals per half hour at lunch, a kirana store one van round every ninety minutes. When a slot fills it disappears from the options. Cut-offs handle advance items: a custom cake ordered after 6 pm moves to the day after tomorrow; tomorrow’s breakfast orders close at 10 pm. Holidays, early closing and “kitchen full, pausing for 20 minutes” are one-tap switches on the dashboard.
The order dashboard your kitchen or store will use
Staff should see new orders loudly, act on them in one tap, and never need to read the chat. A good dashboard does exactly that and nothing more.
We build it as a web app that runs on a cheap Android tablet or any phone browser. New orders chime and flash until someone accepts them. Cards move across columns: new, accepted, preparing, packed, out for delivery, done. Each move sends the matching WhatsApp message to the customer automatically. For restaurants, the card shows items grouped the way the kitchen cooks them; for kirana stores, a packing list sorted by shelf or aisle.
Printing is optional but popular. A thermal printer at the counter can print a kitchen ticket or packing slip for each accepted order. The owner gets a separate view: today’s orders, takings split by UPI and cash, top items and customers who have not ordered in a month. If you later add a till or billing software, the same order data can flow there; our restaurant POS software page covers that side.
Wrong prices and sold-out items are the fastest way to lose trust in a WhatsApp ordering system, so updating them must take seconds, not a call to a developer.
On the dashboard, each item has a sold-out switch and an editable price. Restaurants can schedule menus: breakfast until 11, lunch combos from 12 to 3, a shorter late-night list. Grocery stores with hundreds of lines often prefer to update prices in a Google Sheet they already keep, which the web catalogue reads every few minutes. If you use the native WhatsApp catalogue, the system updates it through Meta’s commerce tools so the chat always shows current availability.
Stock does not need to be perfect to be useful. Most small shops don’t count every packet. We usually track only the items that run out often, such as today’s special cake or fresh fish, and let staff mark the rest sold out by hand. Full inventory can come later if the business grows into it.
How much does a WhatsApp ordering system cost in India?
With BtechWaleTech, a WhatsApp ordering system starts from ₹40,000, and running costs are Meta’s per-message charges plus modest hosting, both billed to you directly. There is no commission and no per-order fee from us.
The build price depends on the catalogue route, the number of outlets, how complex your options are and which extras you want. A single bakery with a native catalogue, UPI and a basic dashboard sits near the starting figure. A cloud kitchen running three brands from one kitchen, with slot capacity, printer tickets and a bot, costs more. Linking to existing billing or POS software is quoted separately.
On Meta’s side, pricing changed on 1 July 2025: its documentation says it now charges per delivered template message, while non-template replies inside an open customer service window are free and utility templates sent inside that window are free too. Because customers start ordering conversations themselves, much of the traffic in a WhatsApp ordering system falls inside that window. Our WhatsApp Business API cost guide explains the model in more detail.
How long does it take to launch?
Most WhatsApp ordering system builds go live in two to four weeks, with Meta account setup running alongside development.
Week one: we collect your item list, photos, prices, zones and opening hours, set up or connect your Meta Business portfolio and WhatsApp number, and submit the few message templates the system needs, such as order confirmed and out for delivery. Week two: catalogue, cart flow, payment and dashboard built on a test number. Week three: your staff place fake orders all afternoon, try to break it, and we fix what they find. Launch follows with a soft start to regulars before the QR codes go up everywhere.
Delays usually come from content, not code. Photographing eighty menu items or cleaning a grocery list with three spellings of “Maggi” takes longer than people expect. Starting with bestsellers and adding the rest later keeps the launch on track.
Getting customers to actually order on WhatsApp
Put the ordering number everywhere customers already look, and give them one clear reason to use it. The system does not advertise itself.
Start with regulars: a printed QR code at the counter, on every bill and in every parcel, saying “Order direct on WhatsApp”. Add the same click-to-chat link to your Google Business Profile, Instagram bio and website. A repeat-order button is the strongest habit builder; once customers can reorder last week’s groceries in two taps, they rarely go back to typing.
Be careful with promotions. Order updates are welcome; unsolicited offers are not. Send marketing messages only to customers who opted in, keep them occasional, and always let people stop them. Meta tracks how customers react, and blocks or reports lower your number’s quality. If you want to be found by new local customers, pair ordering with restaurant SEO or a proper Google profile rather than message blasts. Nobody can guarantee rankings, but a clear local listing that links to your WhatsApp ordering system turns searches into orders.
Tech behind a dependable WhatsApp ordering system
We keep it small and dependable: the official WhatsApp Cloud API, a lightweight backend, a database for orders and customers, and a web dashboard. No unofficial tools, ever.
The backend is usually Node.js or Python on a low-cost cloud server in your own account. PostgreSQL holds orders, items and customers. The web catalogue is a small, fast page built to load on low-end Android phones over patchy data, because that is how many of your customers will open it. The dashboard is a browser app, so any tablet works and there is nothing to install.
Reliability details matter more than features. Incoming WhatsApp webhooks are acknowledged instantly and processed from a queue, so a lunch rush does not drop orders. Every order is saved before any message goes out. If the internet at the shop drops, orders keep arriving in the cloud and appear when the tablet reconnects. Your Meta account, number, server and code are all registered to your business, with access for us that you can remove any time.
Common mistakes when setting up WhatsApp ordering
Most failed attempts share a handful of causes, and all of them are avoidable at the planning stage.
- Using bulk-sender or web-session tools instead of the official API, which risks a banned number
- Keeping the owner’s personal number as the ordering line, so orders stop when the phone is busy
- No slot limits, so a Sunday rush promises more than the kitchen can cook
- Accepting UPI screenshots as proof of payment
- A catalogue nobody updates, showing items that sold out hours ago
- Sending offers to every past customer without consent
- No plan for the customer who just types their order in plain text
That last one deserves a note. Some customers will always type “2 samosa 1 chai” instead of using the cart. We handle it with a friendly nudge to the menu link and, for trusted regulars, a staff member who can build the cart for them from the dashboard. A small WhatsApp chatbot can also read simple typed orders and turn them into a draft cart for staff to confirm.
Worked example: a Mysuru bakery moves regulars to direct orders
A hypothetical to make it concrete. Say a family bakery in Mysuru sells bread, puffs and about thirty cakes, gets a steady flow of marketplace orders, and already receives twenty or so WhatsApp messages a day that the owner answers between bakes.
The build would use the native WhatsApp catalogue for daily items and a web-catalogue link for custom cakes, where the customer picks weight, flavour, eggless or not, the message on the cake and a reference photo. Daily items can be delivered the same day within five kilometres; custom cakes need ordering by 6 pm the day before and full UPI payment upfront. Slots allow six cake deliveries per two-hour window on weekends.
A tablet by the oven shows new orders; the counter gets a printed ticket for each accepted cake. Every parcel from any channel carries a card with the bakery’s WhatsApp QR code. Timeline: about three weeks, mostly spent photographing products.
We would not promise how many orders move from the marketplace; the owner would compare settlement statements month by month. The bakery keeps the Meta account, the number, the server and the code.
WhatsApp ordering system launch checklist
Run through this before the QR codes go up. It catches the problems that otherwise surface during your first busy evening.
- Meta Business portfolio verified and number on the WhatsApp Business Platform
- Display name matching your shop board
- Catalogue complete with photos and correct prices
- Sold-out switch tested for your fastest-moving items
- Delivery zones and charges set; out-of-zone reply tested
- Slot capacities and cut-off times agreed with the kitchen
- UPI payment tested with a real small payment and a failed one
- Cash-on-delivery marking tested
- Status messages approved and firing from the dashboard
- Dashboard tablet charged, mounted and loud enough
- Staff know how to handle typed orders and complaints
- QR cards printed for counter, bills and parcels
For shops that also want a proper storefront later, our bakery website design and sweet shop website pages show how ordering can sit on your own site too.