WhatsApp Ordering for Nigerian Restaurants: The Operating Playbook
For most Nigerian restaurants, WhatsApp is not a marketing channel. It is the order desk. It carries a large share of takeaway and delivery revenue, and it does so with no commission, no install barrier and no learning curve for the customer.
The problem is that it usually runs with no structure at all: the manager's personal number, no catalogue, no script, no record, and orders lost every evening between 7pm and 9pm. This playbook fixes that. It covers setup, the order flow, payments, kitchen handover, staffing and automation, and it explains when a restaurant has outgrown WhatsApp as its primary ordering system.
Why WhatsApp is the default ordering channel
Three practical reasons, and they are worth understanding because they shape how the channel should be run.
- No install and no account. The customer already has WhatsApp. Compare that with asking them to download an app, create an account and remember a password.
- Negotiation and clarification are natural. Nigerian food ordering involves questions: portion size, spice level, whether you deliver to a specific street, whether transfer is acceptable. A conversation handles this better than a form.
- No commission. Unlike aggregator platforms, the margin stays with the restaurant.
The cost is operational. Every order consumes staff attention, nothing is recorded automatically, and the channel collapses under volume unless it is structured. Structure is what turns WhatsApp from a liability during the rush into your best-margin channel.
WhatsApp Business App or the Business Platform?
Meta offers two products, and choosing the wrong one is a common and expensive mistake.
| Factor | WhatsApp Business App | WhatsApp Business Platform (API) |
|---|---|---|
| Who it suits | Single outlet, one or two people replying | Multiple staff, several outlets, higher volume |
| Devices | One phone plus limited linked devices | Any number of agents through a connected system |
| Catalogue | Built in | Available, usually managed through your provider |
| Automation | Greeting, away message, quick replies | Full automation, chatbots, integrations |
| Integration with POS or CRM | Manual | Supported through the platform |
| Cost | Free to use | Provider fees plus Meta's messaging charges |
| Setup | Minutes | Business verification and a solution provider |
Start with the Business App if you are a single outlet with one person on the line. Move to the Business Platform when several people need to answer simultaneously, when you run more than one outlet, when you need orders to flow into another system automatically, or when message volume makes a single phone unworkable.
Meta's verification requirements, messaging rules and pricing change, so confirm current requirements and charges with the WhatsApp Business Platform documentation before budgeting. Note also that the Platform restricts business-initiated messages to approved templates within certain windows, which affects how you send promotions.
Setting up the account properly
A checklist you can work through in an afternoon:
- A dedicated business line, not a personal number
- Business name exactly as customers know it, with the branch if you have several
- Profile photo: the logo, not a food picture
- Business description stating cuisine, delivery areas and hours
- Address and map location for each outlet line
- Opening hours set correctly, including weekends
- Catalogue built with prices
- Greeting message that states hours and how to order
- Away message that gives the next opening time
- Quick replies for the ten most repeated answers
- Labels configured: new order, awaiting payment, paid, preparing, out for delivery, completed, complaint
- A short link and QR code created for packaging, receipts, Instagram bio and the website
- A named owner of the account inside the business, with access recorded
- A rule for who has the phone on each shift
The labels matter more than they look. They turn a chat list into a basic order board, which is the difference between losing an order and finding it.
Building a catalogue that works as a menu
The catalogue is your menu inside WhatsApp, and customers use it if it is usable.
- Group by category with clear names: rice dishes, swallow, proteins, sides, drinks, combos.
- Show the price in the item, not in the description.
- State the portion where it prevents disputes: one portion, serves two, per piece.
- Photograph the top items with the plates and portions you actually serve.
- List modifiers in the description: available proteins, spice levels, extras and their prices.
- Hide or mark sold-out items during service rather than disappointing customers at confirmation.
- Keep prices current. A catalogue with old prices produces arguments at payment time.
For long menus, pair the catalogue with a link to the menu page on your website, which is easier to scan and faster to update. Many restaurants find the best pattern is a catalogue of the twenty bestsellers plus a link for everything else.
The order flow, message by message
Every order should capture the same seven details. Script it so that any staff member on any shift takes the same order.
- Greeting and confirmation of ordering hours. Automated.
- Menu. Catalogue, or a link to the menu page.
- Items and modifiers. Repeat the order back in a single structured message so the customer can correct it before payment.
- Delivery or pickup, and for delivery, the area.
- Address with a landmark, plus a phone number the rider can call, and a location pin where possible.
- Total, broken down: items, delivery fee, any pack or service charge. No surprises later.
- Payment, with the route and a receipt request.
Then three confirmations: order accepted by the kitchen, order ready or out for delivery, and a short follow-up after delivery.
A worked order-confirmation message looks like this, and it is worth using verbatim:
- Items with quantities and options
- Delivery area and fee
- Total amount
- Estimated time as a range
- The address as you have recorded it, for the customer to confirm
Repeating the address back prevents most failed deliveries. Repeating the total prevents most payment disputes.
Taking payment on WhatsApp
Payment is where WhatsApp ordering leaks money, and three habits fix most of it.
Use a payment link rather than dictating account numbers. A link from a provider such as Paystack, Flutterwave, Interswitch or Moniepoint lets the customer pay by card, bank transfer or USSD, gives you an automatic record, and removes the transcription errors that come with typing account numbers into a chat.
Never release food on a screenshot. Verify against a bank alert, the provider's dashboard or an automated notification. Where volume justifies it, connect the payment notification into your order board so the person confirming can see the payment status without asking a colleague.
Decide your pay-on-delivery policy and write it down. Many Nigerian restaurants accept it for repeat customers, below a value threshold, or in specific zones. Whatever the rule, make it explicit so staff are not negotiating it under pressure.
Two more details worth setting: a clear policy on part payments for bulk and event orders, and a stated refund timeline, since settlement timing depends on the provider and the customer's bank.
Getting the order into the kitchen
This is the step most restaurants skip, and it is the reason WhatsApp orders get lost.
The rule is simple: every WhatsApp order is entered into the POS immediately, by the person who took it, before they reply to the next customer. Not at the end of the rush. Not on a notepad.
Why it matters beyond the immediate order:
- The kitchen works from one queue rather than three.
- Sales data is complete, so stock, recipes and forecasting stay meaningful.
- The order has a reference number for disputes.
- Payment reconciliation works at the end of the shift.
Where volume is high, a WhatsApp Business Platform integration can create the order in your ordering system automatically, with a staff confirmation step. That is usually the first integration worth paying for, and it typically sits within the ₦500,000–₦5,000,000 range for a business automation project depending on the systems involved. Treat that as indicative and get written quotations.
Staffing, shifts and response standards
Treat the line as a station in the restaurant, with a rota.
- A named person per shift owns the line, and the handover is explicit.
- A stated response time, for example within five minutes during service. Publish it internally and check it.
- Two trained people per shift when volume is high, using the Business Platform or linked devices so both can answer.
- A script and a quick-reply set so answers do not depend on who is holding the phone.
- An escalation rule. Complaints, refunds, bulk and event orders go to a manager immediately.
- A closing routine. All labels cleared, all orders reconciled against the POS, all payments matched.
The most common staffing error is asking a cashier to run the WhatsApp line during peak counter service. Both suffer. Separate the roles during peak hours even if the same person covers both when it is quiet.
Example (hypothetical): a Lekki kitchen taking 90 orders a day
This is an illustrative scenario, not a client result.
A Lekki kitchen takes around ninety orders a day, about half through WhatsApp on the manager's personal phone. During the evening rush, orders are missed, the same customer sometimes gets two calls, and payment reconciliation at close takes an hour because transfer confirmations are spread across screenshots and bank alerts.
The changes that address this are not expensive. Move to a dedicated business line with a catalogue of the twenty bestsellers and a link to the full menu. Script the seven-detail order flow and load ten quick replies. Use labels as an order board. Switch to payment links so payments are recorded automatically. Require every order to be entered into the POS as it is taken. Put one named person on the line per shift, with a five-minute response standard.
Once the line exceeds what one person can answer during peak, move to the WhatsApp Business Platform so two agents can work simultaneously and orders can be pushed into the ordering system automatically.
The measures that show whether it worked: missed orders per evening, average response time, reconciliation time at close, and the share of orders paid before dispatch.
The limits of WhatsApp ordering, and when to outgrow it
WhatsApp is excellent up to a point. The signals that you have reached it:
- One person can no longer answer during peak, even with quick replies.
- Orders are regularly missed or duplicated in the same hour.
- Reconciliation takes more than a few minutes at the end of each shift.
- You cannot answer basic questions such as how many customers ordered twice this month.
- Repeat customers re-type the same order and address every time.
- You want loyalty, scheduled orders or pre-orders, which chat handles badly.
Outgrowing WhatsApp does not mean abandoning it. The mature pattern is a web ordering flow or an app for structured, repeat and paid-in-advance orders, with WhatsApp retained for questions, exceptions and customers who prefer to talk. The ordering system becomes the record; WhatsApp becomes the front door.
Metrics to track and mistakes to avoid
Track six numbers weekly:
- Orders taken on WhatsApp, and their share of total orders
- Average first-response time during service hours
- Missed or abandoned conversations during peak
- Share of orders paid before dispatch
- Failed or delayed deliveries caused by address problems
- Repeat-order rate among WhatsApp customers
Mistakes to avoid:
- Using a personal number. It cannot be handed over, labelled or staffed properly, and it leaves with the employee.
- No published prices. Every price question becomes staff time you are not paid for.
- Accepting screenshots as proof of payment. Verify against a bank or provider record.
- Not entering orders into the POS. It corrupts sales, stock and forecasting data at once.
- Leaving the address unconfirmed. Repeat it back with the landmark before dispatch.
- Broadcasting promotions to everyone, often. Customers mute and then block. Message sparingly, with consent, and note that the Business Platform restricts business-initiated messaging to approved templates.
- No escalation rule. Complaints handled slowly by junior staff become public reviews.
- Ignoring consent and data handling. Customer numbers, addresses and order history are personal data under the Nigeria Data Protection Act 2023; keep what you need, secure it, and confirm obligations with the Nigeria Data Protection Commission.
Conclusion
WhatsApp ordering is the highest-margin channel most Nigerian restaurants have, and it fails only because it is run informally. Put it on a dedicated line, publish a catalogue with prices, script the seven details every order needs, take payment through links rather than dictated account numbers, enter every order into the POS as it arrives, and staff the line like any other station. When one person can no longer keep up during peak, move to the Business Platform and, eventually, to a structured ordering system with WhatsApp as the front door rather than the record.
If your WhatsApp line is carrying more orders than it can hold together during service, Linestech can structure the channel, connect it to your ordering and payment systems, and build the ordering flow your repeat customers will move to.
Frequently asked questions
Can we take orders on WhatsApp without a website?
Yes, and many Nigerian restaurants do. A catalogue with prices plus a scripted order flow is enough to trade. A simple menu page still helps, because it is faster to scan, easier to update and gives you something to share in a single link.
How do we stop losing orders during the evening rush?
Three things: a named person on the line with no competing duty during peak, labels used as an order board so nothing sits unattended, and immediate entry of every order into the POS. If volume still exceeds one person, move to the Business Platform so two agents can work at once.
Should we accept payment on delivery?
It is a commercial decision, not a technical one. Many restaurants accept it for repeat customers, below a value threshold, or in zones where their own riders operate. Write the rule down so staff are not deciding it during a rush.
Is it safe to accept a transfer screenshot?
No. Screenshots can be edited. Verify against your bank alert, your payment provider's dashboard, or an automated notification before the food leaves. Using payment links removes the problem almost entirely because payment status is recorded automatically.
How many quick replies do we need?
Around ten covers most traffic: menu, delivery areas and fees, opening hours, payment options, order status, bulk and event orders, pickup instructions, current promotions, allergen and ingredient enquiries routed to a person, and the closing message.
Can a chatbot handle WhatsApp orders for us?
It can handle the repetitive questions and draft structured orders well. It should not confirm an order without the kitchen or the system accepting it, and it should hand complaints, refunds and bulk orders to a person. The AI article linked at the end covers where the boundary sits.
Do we need a separate WhatsApp line for each branch?
Usually yes for multi-branch restaurants, because delivery areas, stock and staffing differ by outlet. Alternatively, run one line on the Business Platform with routing by area. What does not work is one personal phone covering three kitchens.
How do we move customers from WhatsApp to our own ordering system?
Give them a reason and make it easy: a link in the chat, a small first-order benefit, saved addresses and one-tap reorder. Keep WhatsApp available for questions so the change feels like an addition rather than a removal.
Sources and further reading
Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.
