WhatsApp ordering for restaurants in Pakistan: the complete setup guide

Most restaurants in Pakistan already take orders on WhatsApp. A customer messages the number on the flyer, someone at the counter types back "jee, what would you like?", a screenshot of the menu goes out, and the order arrives in pieces over the next ten minutes. It works, until the Friday rush, a lost chat, or a rider sent to the wrong block.

A proper WhatsApp ordering system for restaurants in Pakistan keeps the part customers love (ordering in the app they already open fifty times a day) and replaces the part that breaks (a human retyping orders into a notebook). This guide covers what the official platform is, how menu and payment work inside a chat, what Meta requires, and a checklist you can run through in about a week.

TL;DR

• Use the official WhatsApp Business Platform (the API), not the free WhatsApp Business app, once you want automation, more than one staff member answering, or payment in chat.
• Your menu becomes an interactive list message the customer taps through, not a PDF or a screenshot.
• Payment happens with a secure pay-link sent in the chat: Raast, JazzCash, Easypaisa or card. Cash on delivery stays available.
• Meta needs a verified business, a dedicated phone number, an approved display name and approved message templates.
• Launch in seven steps, starting with nothing more than a photo of your menu.

The free app vs the official platform

There are two very different things people call "WhatsApp for business".

The free app is fine for a single-outlet café handling ten orders a day. The moment you want the bot to take the order while your staff cook, you need the platform. Rapid Eats connects to the platform for you; you do not need a developer.

Your menu as an interactive list

The platform supports interactive messages: list messages (a tappable menu of up to ten rows), reply buttons (up to three quick choices) and product messages that pull from a catalogue. A good ordering flow strings these together:

1. The customer sends anything ("hi", "menu", a sticker).
2. The bot replies with reply buttons: Order now, Track my order, Talk to a human.
3. Order now opens a list of categories: BBQ, Karahi, Rolls, Drinks.
4. Each category opens a list of items with prices in PKR.
5. Sizes and add-ons are reply buttons: Regular / Large, Add raita.
6. The cart is confirmed with one summary message and a Place order button.

Nothing here is a screenshot. Prices come from the same menu you edit once in your Rapid Eats console, so when chicken prices move you change one number, not fifteen posters.

Taking payment inside the chat

WhatsApp's own in-app payments are not available in Pakistan, so payment works through a link. Once the customer confirms the cart, the bot sends a short message: the order summary, the total, and a secure RapidGateway pay-link. The customer taps it, picks Raast, JazzCash, Easypaisa or a card, and completes the payment in their own banking or wallet app. When the payment is confirmed, the order flips to Paid on your kitchen screen and the customer gets a receipt message in the same chat.

Keep cash on delivery as an option. Some customers will always prefer it, and a rider can still collect cash and mark it in the app. What changes is that prepaid orders no longer sit on the pass while you wonder whether the customer will actually open the door.

Templates, the 24-hour window and opt-in

This is the part most restaurants get wrong, and the part Meta polices.

When a customer messages you, a 24-hour customer-service window opens. Inside that window you can send free-form messages: order confirmations, "your rider is five minutes away", a quick question about the address. Outside the window you can only send message templates that Meta has approved in advance. Templates are categorised (utility, marketing, authentication) and Meta charges for template messages, with rates that vary by country and category; check Meta's current pricing for Pakistan rather than assuming.

Practical implications:

• Order-status updates during delivery almost always fall inside the window, so they are free-form.
• "Biryani is back on Friday" is a marketing template. The customer must have opted in (ticked a box, replied YES, scanned a QR that says what they are signing up for) before you send it.
• Spammy templates get rejected, and a low quality rating lowers how many customers you can message per day. Send fewer, better messages.

What Meta requires before you go live

Set these up early; some take days.

• A Meta Business Portfolio (what used to be called Business Manager) with business verification: a registered business name, an address, and a document such as your NTN certificate or a utility bill in the business name.
• A dedicated phone number that is not currently registered on the regular WhatsApp or WhatsApp Business app. A new SIM works best; reusing your existing number means migrating it, with a short period where the old app stops working.
• A display name that matches your real brand. Meta checks it against the business and rejects generic names or names that imply affiliation with another company.
• Approved templates for everything you plan to send outside the 24-hour window.
• Compliance with the WhatsApp Commerce Policy. Restaurants are allowed; keep the catalogue honest and keep alcohol and tobacco out of it.

The optional green tick (Official Business Account) is a separate application and is not required to take orders.

The 7-step launch checklist

1. Send us your menu in any format: a photo of the printed menu, a marketplace listing, an Excel sheet. We load it with categories, sizes and add-ons, and you review every price in PKR.
2. Choose your number. A new SIM for the bot, or migrate your existing one. Decide which staff phones get the shared inbox.
3. Complete Meta business verification. Have your NTN or registration document and a bill ready.
4. Approve your templates. Order confirmation, rider dispatched, delivered, and one marketing template for your first campaign.
5. Set delivery zones and charges. Which sectors you cover, the fee per zone, the minimum order, and opening hours so the bot never takes an order at 2 a.m.
6. Place three test orders yourself: one Raast, one JazzCash or Easypaisa, one cash on delivery. Watch each land on the kitchen screen and in your settlement view.
7. Tell customers. Put the WhatsApp QR on every packaging sticker, table tent and social post, and give the first hundred customers a reason to try it, such as free delivery on their first WhatsApp order.

Mistakes to avoid

• Running the bot from the free app on a personal phone. One lost handset and the business loses its chats.
• Sending the menu as an image. Customers cannot tap an image, and your staff end up retyping everything.
• Messaging customers who never opted in. It is the fastest route to a blocked number.

A WhatsApp ordering system for restaurants in Pakistan is not a chatbot bolted onto a notebook; it is your menu, your payments and your riders living in the app your customers already use. If you want to see your own menu running inside WhatsApp before you commit to anything, book a 20-minute demo and place a test order yourself.