Nigerian Restaurant WhatsApp: NAFDAC, FCCPC, Paystack Stack

The five rulebooks a Nigerian restaurant actually meets when it turns on WhatsApp for reservations, pre-orders, and payment

The day a Nigerian restaurant switches reservations, pre-orders, catering enquiries, or delivery-follow-up onto the WhatsApp Business Platform, five separate rulebooks come into play. NAFDAC (National Agency for Food and Drug Administration and Control, nafdac.gov.ng) governs food safety, labelling, and any packaged-food product the restaurant sells to consumers. FCCPC (Federal Competition and Consumer Protection Commission, fccpc.gov.ng) governs restaurant advertising, menu representation, refund and complaint handling. NDPA 2023 (Nigeria Data Protection Act 2023, enforced by the Nigeria Data Protection Commission at ndpc.gov.ng) requires a written Data Processing Addendum with any messaging vendor and controls how customer personal data (name, phone, address, order history) flows through the WhatsApp workflow. CBN (Central Bank of Nigeria, cbn.gov.ng) regulates the payments layer — Paystack, Flutterwave, Remita, Interswitch — that the restaurant hands off to at deposit or full payment. And the delivery-platform commission economics on Chowdeck, Bolt Food, and Glovo (Jumia Food ceased Nigerian operations in November 2023) drive the whole business case for direct-order WhatsApp workflows. Every section below picks one of these five threads.

Nigerian delivery platforms, commission economics, and the WhatsApp direct-order counter-move

The Nigerian food-delivery market has consolidated significantly across 2023-2025.

Active Nigerian food-delivery platforms:

• Chowdeck (chowdeck.com) — Nigerian-origin, Y Combinator-backed, dominant in Lagos and expanding across Abuja, Ibadan, Port Harcourt.
• Bolt Food (bolt.eu/food) — Estonian ride-hailing group's food-delivery arm; strong Lagos presence.
• Glovo (glovoapp.com) — Spanish-origin; Nigerian operations in Lagos and select cities.
• FoodCourt (foodcourt.ng) — Nigerian-origin cloud-kitchen and delivery platform.
• Jumia Food — ceased Nigerian and other African market operations in November 2023.

Delivery-platform commission structure:

• Commission on the menu subtotal typically sits in the 15-30% range depending on the restaurant tier, platform, and negotiated agreement.
• Additional fees on delivery time-slot promotion, in-app menu placement, and payment processing.
• Marketing-in-platform (banner, in-app promotion) is often a separate paid tier.
• Platforms provide the customer-acquisition, the rider network, and the payment collection — the restaurant provides food and packaging.

The WhatsApp direct-order counter-move:

A Nigerian restaurant that builds a WhatsApp customer base can serve repeat customers directly:

• Customer messages the restaurant's WhatsApp Business number — the number the restaurant already publishes on menus, receipts, packaging.
• Restaurant confirms availability and shares Paystack or Flutterwave payment link in-chat.
• Customer pays in naira on the payment provider's hosted page.
• Restaurant arranges delivery either through its own rider(s), an on-demand courier (Kwik Delivery, GIG Logistics, Gokada, or a specific rider partnership), or a delivery-platform 'own-fleet' arrangement.
• Restaurant retains the full menu subtotal minus payment-gateway transaction fee (typically 1.5-2.5% for Nigerian cards).

The economics comparison for a mid-size Lagos restaurant with 30% repeat-customer rate:

• Delivery-platform-only orders: 100% of orders processed through platform; commission takes 15-30% of every order subtotal.
• Hybrid direct + delivery-platform: 30% of orders through WhatsApp direct (commission = payment-gateway fee only, ~2%); 70% through delivery platform. Blended commission drops materially.
• Direct-order dominant: 60-70% of orders through WhatsApp direct; delivery-platform used for customer acquisition and new-customer onboarding. Blended commission drops further.

Where direct-order via WhatsApp doesn't work as well:

• Discovery-phase customer acquisition — new customers find the restaurant through the delivery platform's app, not through the restaurant's WhatsApp.
• Rider logistics at scale — Chowdeck's rider network is a real operational advantage the restaurant cannot cheaply replicate.
• In-app rating and social proof — customer trust in a new restaurant is often built on the platform's ratings before they attempt direct order.
• Payment dispute handling — the delivery platform absorbs chargeback and refund friction that the restaurant would otherwise handle directly.

Realistic operational pattern: use delivery platforms for new-customer acquisition and one-off orders; migrate repeat customers to WhatsApp direct order for scale efficiency. The WhatsApp workflow needs to be reliable enough that a repeat customer prefers it to the delivery-platform app.

NAFDAC food safety, menu representation, and the WhatsApp allergen or ingredient claim a restaurant must not fabricate

NAFDAC (National Agency for Food and Drug Administration and Control, nafdac.gov.ng) governs food safety, product registration, and labelling across the Nigerian food and beverage sector. For a restaurant, NAFDAC's role is most visible in three areas:

• Packaged-food product registration — if the restaurant sells packaged food products (branded pepper sauce, packaged pastries for retail, meal kits), those products need NAFDAC registration and labelling per the appropriate NAFDAC guidelines.
• Food safety and hygiene — general food-handler standards; state-level agencies (Lagos State Ministry of Health, similar in other states) run inspection and licensing regimes.
• Allergen and ingredient claims — while Nigeria does not currently have the same allergen-declaration regime as the EU or UK, NAFDAC's general labelling and misleading-claim standards apply to any packaged product, and FCCPC's misleading-advertising authority extends to menu representation.

Where WhatsApp workflows create NAFDAC-adjacent and FCCPC exposure:

• Menu representation in a WhatsApp broadcast: a restaurant that broadcasts 'nut-free, halal, gluten-free' claims via WhatsApp needs those claims to be accurate for every dish in the promotion. A customer allergy incident traced back to an inaccurate WhatsApp claim is exposure under both NAFDAC labelling standards (if the food is a packaged product) and FCCPC's misleading-advertising authority.
• Photo representation: WhatsApp broadcasts using stock or heavily-styled food photography that doesn't represent what the customer actually receives — a documented misrepresentation.
• Ingredient-source claims: 'locally-sourced', 'organic', 'imported' claims need substantiation. FCCPC has taken action on unsubstantiated marketing claims in adjacent sectors.
• Halal certification claims: verify the specific certification body (NSCIA — Nigerian Supreme Council for Islamic Affairs, or JIBWIS certification body) and reference it accurately.
• Portion and price representation: menu prices shared via WhatsApp must be honored at checkout; bait-and-switch pricing exposes the restaurant to FCCPC complaint.

Safe patterns for a Nigerian restaurant using WhatsApp:

• Menu confirmation via WhatsApp reply rather than pre-broadcast static menu — allows real-time ingredient and availability check.
• Allergen-question routing to a human staff member during service hours; automated 'we accommodate all allergies' auto-reply is exposure if the kitchen cannot in fact isolate every allergen.
• Photos: use actual dish photography from the restaurant, not stock. Update seasonally.
• Price integrity: WhatsApp-broadcast promotional pricing must match the payment-link amount and the checkout total.

State-level restaurant licensing: each Nigerian state has its own restaurant licensing regime (Lagos State Ministry of Health, FCT Health and Human Services Secretariat, etc). Compliance with state licensing is a precondition to operating, and the WhatsApp customer-facing communication reflects the operating status.

FCCPC consumer protection, refund handling, and complaint escalation on a Nigerian restaurant WhatsApp

The Federal Competition and Consumer Protection Commission (FCCPC) at fccpc.gov.ng was established under the Federal Competition and Consumer Protection Act 2018 (FCCPA). Its enforcement powers cover unfair trade practices, misleading advertising, consumer-contract terms — including restaurant menu representation, service delivery, and complaint handling.

Where FCCPC rules touch a Nigerian restaurant WhatsApp workflow:

• Misleading advertising in WhatsApp broadcasts — 'Lagos best jollof' claims, 'authentic pepper soup' representations, promotional pricing that hides material terms.
• Menu representation — the dish delivered must match the description at order.
• Delivery timeline representations — 'delivery within 30 minutes' promises that systematically break create FCCPC exposure.
• Refund handling — a customer complaint about food quality, missing items, or delivery failure needs a reasonable response and a defined escalation route.
• Complaint handling — FCCPC expects an internal escalation route; a customer complaint that gets ignored on WhatsApp is exposure.
• Prepaid order deposit — a customer who prepays for a catering order or table reservation retains rights to a fair refund if the restaurant fails to deliver.

Common Nigerian restaurant WhatsApp complaint patterns:

• Missing item from delivery order — customer received part of the order, missing item was paid for.
• Food quality below expectation — customer received the ordered dish but reports quality issue.
• Delivery time significantly exceeded promise — customer received order late enough to be unusable.
• Wrong item delivered — customer received a different dish than ordered.
• Table reservation confusion — reservation confirmed via WhatsApp not honored on arrival.

Compliant handling patterns:

• Acknowledge complaint within a working day — even a template acknowledgement that the concern is being reviewed.
• Refund process aligned with payment method: for Paystack card refunds, typically 5-10 business days; for bank transfer, prompt-return via same account; for delivery-platform-mediated orders, refund runs through the platform's own process.
• Missing-item resolution: refund the missing item's cost via Paystack refund API or credit against next order.
• Repeated-issue pattern: track complaints in the WhatsApp thread and escalate to the restaurant operations lead where a customer has had multiple issues.
• FCCPC signposting: for unresolved complaints, signpost fccpc.gov.ng/complaints as the external escalation route.

Delivery-platform-mediated complaint handling: for orders placed through Chowdeck, Bolt Food, or Glovo, the platform mediates the refund process. The restaurant should not resolve platform-mediated complaints off-platform (violates the platform's terms) but can acknowledge on WhatsApp and route to the platform's dispute resolution.

NDPA 2023, the Nigeria Data Protection Commission, and the restaurant customer data on WhatsApp

The Nigeria Data Protection Act 2023 (NDPA 2023) at ndpc.gov.ng, enforced by the Nigeria Data Protection Commission, applies to the customer personal data a Nigerian restaurant collects and processes via WhatsApp.

What restaurant customer data typically flows through a WhatsApp workflow:

• Customer name, phone number, delivery address.
• Order history, preferences, dietary requirements.
• Payment reference (via Paystack or Flutterwave — the payment provider is a separate data controller for its own KYC data).
• Booking history, party size, table preferences.
• Complaint threads and resolution records.

NDPA 2023 core requirements for a Nigerian restaurant:

• Lawful basis for processing — typically contract-performance basis for order-processing, consent for marketing broadcasts.
• Data processing agreement (DPA) — Section 29 requires a written contract between the restaurant (controller) and any WhatsApp platform vendor (processor). Vendors that cannot produce an NDPA-compatible DPA are not a defensible choice.
• Cross-border data transfer — Section 41 restricts transfer outside Nigeria unless adequacy applies, binding contract with safeguards is in place, or the data subject consents. Most WhatsApp platform vendors host outside Nigeria.
• Data Protection Officer (DPO) — applies to larger restaurant chains per NDPC guidance thresholds.
• Breach notification — the restaurant must notify NDPC and affected customers of a personal data breach within statutory timelines.
• NDPC registration and compliance audit — larger data controllers register and undergo periodic audit.

Where restaurant WhatsApp workflows create NDPA issues:

• Personal WhatsApp on a manager's phone with customer numbers and addresses — no formal DPA, no data-residency arrangement, no incident-response capability. High-risk pattern.
• Marketing broadcast to a customer list without documented opt-in — Section 69 NDPA (direct marketing) exposure.
• Photos of prepared food-for-delivery containing the customer's address label shared in staff WhatsApp Groups — inadvertent personal data disclosure.
• Complaint threads shared with third parties for advice without customer consent.
• Retention of complaint threads and customer data indefinitely — Section 25 NDPA storage-limitation principle expects a defined retention period aligned to purpose.

Safe patterns for a Nigerian restaurant:

• WhatsApp Business Platform via a BSP rather than personal WhatsApp Business App — centralised account, exportable audit trail, DPA in place.
• Documented consent for marketing broadcasts, captured at the point of contact (opt-in link, in-store QR code, delivery receipt reference).
• Retention policy for customer WhatsApp data — active order flow + defined post-purchase window + longer for complaint records + statutory-required retention for tax records.
• BYOD policy for staff who use personal phones for restaurant WhatsApp — encryption, phone lock, no forwarding to personal accounts.
• DPA in place with the WhatsApp platform vendor covering Section 29 requirements + Section 41 cross-border basis.

CBN, Paystack, Flutterwave — direct-order payment collection inside the restaurant WhatsApp workflow

The Central Bank of Nigeria (CBN) at cbn.gov.ng regulates the payments layer that a Nigerian restaurant WhatsApp direct-order workflow hands off to. CBN's Payment System Vision framework licenses Nigerian fintech: Payment Solution Service Providers (PSSP), Mobile Money Operators (MMO), Switching and Processing Companies.

The main Nigerian payment integrations for restaurant direct-order:

• Paystack (paystack.com) — CBN-licensed PSSP; acquired by Stripe in 2020. Card, bank transfer, USSD, mobile money. Widely used by Nigerian restaurants. API at paystack.com/docs.
• Flutterwave (flutterwave.com) — CBN-licensed PSSP with pan-African footprint. API at developer.flutterwave.com.
• Remita (remita.net) — long-established Nigerian payments platform.
• Interswitch (interswitchgroup.com) — Nigeria's oldest payment processor.
• OPay, Kuda, PalmPay — challenger fintechs with wallet + card acquisition.
• In-restaurant POS: Nomba, Moniepoint, Opay POS, Baxi, Yello card readers.

Restaurant WhatsApp payment flow patterns:

• Deposit for catering or reservation: WhatsApp confirms booking, generates Paystack/Flutterwave payment link, customer pays deposit, WhatsApp confirms deposit receipt.
• Pre-order full payment: WhatsApp captures order, generates payment link, customer pays full amount, WhatsApp confirms and passes order to kitchen.
• Post-service payment for dine-in: less common on WhatsApp; in-restaurant POS handles.
• Delivery order full payment: WhatsApp captures delivery order, payment link, customer pays, restaurant dispatches through its own rider or on-demand courier.
• Split payment: multiple customers on same table settle via multiple Paystack payment links against the same order reference.

Payment-gateway transaction fees for Nigerian restaurants:

• Card payment: typically 1.5-2.5% + a small flat fee per transaction (verify with the specific PSSP).
• Bank transfer via PSSP: often lower percentage or capped fee.
• USSD payment: variable fee per transaction.
• In-person POS: separate fee structure from online.

Restaurant WhatsApp platform + payment integration reality:

• WATI, Respond.io, Freshchat: no native Paystack/Flutterwave integration; middleware path (Zapier, Make.com, custom webhook) required to trigger payment link from WhatsApp flow.
• Purpose-built WhatsApp-CRM (BossBot and equivalents): first-party Paystack/Flutterwave integration bundled — WhatsApp flow generates payment link and processes webhook confirmation without middleware.
• DIY approach: manager manually sends Paystack payment link via WhatsApp after each order confirmation — works at small scale, breaks at volume.

CBN compliance implications:

• KYC/AML: the payment provider carries the CBN's KYC obligations at merchant onboarding; the restaurant inherits obligations on the settled funds (record-keeping for tax, source-of-funds documentation for large transactions).
• Consumer complaint route: CBN Consumer Protection Framework should be signposted for payment-specific disputes; restaurant's WhatsApp complaint template routes payment issues to the payment provider's process.
• Refund handling: 5-10 business days typical for Nigerian card refunds via Paystack or Flutterwave; bank transfer refunds are faster; the restaurant's WhatsApp template should reflect the realistic timeline.
• BVN and NIN: required at PSSP merchant onboarding, not collected inside the customer WhatsApp flow.
• VAT: FIRS 7.5% VAT applies to restaurant sales; the Paystack or Flutterwave transaction record + restaurant's own accounting record support FIRS filing.

FCCPC advertising, NDPA marketing consent, and NCC DND — Nigerian restaurant WhatsApp broadcast discipline

The FCCPC (fccpc.gov.ng), the NDPA 2023 direct-marketing rules (Section 69), and the NCC do-not-disturb (DND) directive all apply to a Nigerian restaurant's WhatsApp broadcast activity.

Transactional versus marketing distinction:

• Transactional messages (order confirmation, dispatch alert, table reservation confirmation, deposit acknowledgement, invoice, receipt): do not require FCCPA or NDPA-marketing consent — contract-performance basis covers them.
• Marketing messages (menu-launch broadcast, seasonal promotion, restaurant reopening notification, loyalty-program invitation, birthday offer): require documented opt-in specific to WhatsApp marketing.

Restaurant-specific marketing patterns and compliance:

• Menu-launch broadcast to past customers: requires opt-in captured at earlier point of contact (delivery receipt, in-restaurant WiFi signup, loyalty programme enrolment).
• Seasonal promotion (Detty December, Eid, Christmas, Independence Day, New Year): same opt-in requirement.
• Birthday offer — captured customer birth date needs documented consent and specific marketing purpose disclosure.
• 'We've missed you' win-back to lapsed customers: soft opt-in exception under NDPA Section 69(3) may cover past customers of similar service; specific consent for the marketing channel still preferred.
• Referral request ('share with friends, get discount'): asks the customer to share the restaurant's WhatsApp with named third parties who have not consented — exposure.

Compliant Nigerian restaurant WhatsApp broadcast patterns:

• Documented opt-in at point of contact — delivery receipt reference, in-restaurant QR code, loyalty programme enrolment with distinct WhatsApp-marketing checkbox.
• 'Reply STOP to opt out' text in every marketing message, honoured within a working day.
• Timestamped consent records the NDPC can inspect on complaint.
• Segmentation by consent scope — order-confirmation contacts have not opted in for marketing without a separate consent moment.
• Broadcast list via WhatsApp Business API broadcast list function, not WhatsApp Group — Groups reveal customer numbers to each other (a separate NDPA breach).
• Promotional broadcast frequency reasonable — aggressive daily promotions create NCC DND complaints even where consent is technically valid.

Patterns to avoid:

• Pre-ticked marketing checkbox at delivery receipt sign-up: invalid consent under NDPA.
• Adding every past customer's WhatsApp number to a broadcast list without a consent moment: Section 69 breach.
• Referral-share broadcasts that ask customers to share the restaurant's WhatsApp with named third parties without those third parties' consent.
• Marketing to a customer number captured only for a specific complaint thread: purpose-mismatch consent.

Enforcement patterns:

• FCCPC has published enforcement decisions at fccpc.gov.ng.
• NDPC has begun publishing NDPA enforcement decisions at ndpc.gov.ng.
• NCC's Consumer Affairs Bureau handles DND-related complaints.

The Nigerian restaurant WhatsApp stack — from personal WhatsApp Business to purpose-built platform

Realistic Nigerian restaurant WhatsApp stack options (all pricing pointers to be verified on the vendor's live pricing page before commitment).

Tier 1: Personal WhatsApp Business App (free)

• Best for solo or 1-2 staff restaurants with modest order volume.
• Free from Google Play or App Store.
• 256-contact broadcast list limit.
• No centralised control if staff phones change.
• No formal NDPA DPA — the restaurant is directly the data controller for the personal-account data.
• No first-party payment integration — Paystack or Flutterwave payment links pasted in manually.
• Adequate until order volume outgrows single-phone coordination.

Tier 2: WhatsApp-first BSP platform (WATI, purpose-built WhatsApp-CRM)

• Best for restaurants with 3+ staff needing shared inbox + broadcast + basic chatbot.
• WATI Growth: USD $49/month, 3 users, 1,000 contacts.
• Purpose-built WhatsApp-CRM: USD $49/month, unlimited users, first-party Paystack/Flutterwave integration.
• Meta WhatsApp conversation fees pass through — often within free service-tier for restaurant volume.
• NDPA DPA available.

Tier 3: Multi-channel platform (Respond.io, SleekFlow)

• Best for restaurants with real Instagram DM + WhatsApp customer volume (fashion-forward or influencer-marketed restaurants).
• Respond.io Team: USD $79/month.
• SleekFlow Pro: USD $79/month.
• Broader channel coverage; higher price.

Tier 4: Enterprise-tier integration (Twilio, Bird, direct BSP)

• Best for restaurant chains with 10+ locations and integrated ordering system.
• Requires developer resource.
• Consumption-billed at scale.

Purpose-built WhatsApp-CRM value for a Nigerian restaurant specifically:

• First-party Paystack and Flutterwave integration removes middleware layer for direct-order payment collection.
• Booking / reservation calendar included with WhatsApp intake.
• Customer record retention aligned to Nigerian restaurant workflow.
• Complaint tracking with WhatsApp thread export for FCCPC evidence if needed.

Meta directory at business.whatsapp.com/partners is the source of truth for approved BSPs.

Evaluation checklist for a Nigerian restaurant:

• NDPA-compatible DPA available before signup.
• First-party Paystack / Flutterwave integration — native, Zapier, or manual.
• Booking / reservation calendar integration.
• Chowdeck / Bolt Food / Glovo webhook integration if the restaurant runs a hybrid direct + delivery-platform model — most WhatsApp platforms don't have this natively.
• Naira budgeting posture — flat-rate USD subscription.
• Complaint thread export for FCCPC evidence.
• Staff BYOD policy covering personal-phone use for restaurant WhatsApp.

Total-cost model for a Nigerian restaurant running WhatsApp direct-order plus delivery-platform hybrid

Realistic monthly total-cost pattern for a Nigerian restaurant at three profiles (all figures should be verified on live vendor pricing pages; naira estimates use directional rates and should be updated at the point of budgeting).

Profile A: Single-location Lagos casual restaurant, ~500 orders/month, mostly walk-in and delivery-platform:

• WhatsApp platform: personal WhatsApp Business App = USD $0/month.
• Paystack transaction fees on ~150 direct-WhatsApp orders: ~1.5-2% × average order value.
• Delivery-platform commission on 350 orders: 15-30% × subtotal — the material cost.
• Total WhatsApp-specific software cost: USD $0/month; delivery-platform commission is the bigger economic lever.

Profile B: Mid-size Lagos or Abuja restaurant, ~1,500-3,000 orders/month, 30-50% WhatsApp direct-order rate:

• WhatsApp platform (WATI Growth or purpose-built WhatsApp-CRM Starter): USD $49-99/month.
• Meta WhatsApp conversation fees: mostly within free service-tier for inbound customer questions; occasional marketing broadcast fees.
• Paystack transaction fees on ~500-1,500 direct-WhatsApp orders: percentage × average order value.
• Delivery-platform commission on remaining orders: material cost that migrating repeat customers to WhatsApp reduces.
• Total WhatsApp-specific software cost: USD $49-99/month; savings on delivery-platform commission scale with WhatsApp direct-order rate.

Profile C: Chain or high-volume single-location restaurant, ~5,000+ orders/month, 50%+ WhatsApp direct-order rate:

• WhatsApp platform (WATI Pro, purpose-built WhatsApp-CRM Growth, or enterprise BSP): USD $99-300+/month.
• Meta WhatsApp conversation fees: growing above free service-tier; marketing broadcasts add cost.
• Paystack / Flutterwave transaction fees on 2,500+ direct-WhatsApp orders: material line item on the revenue side but far below equivalent delivery-platform commission.
• Delivery-platform commission on remaining orders: still meaningful but now the minority of revenue.
• Total WhatsApp-specific software cost: USD $150-500+/month; annualised savings on delivery-platform commission commonly exceed the platform software cost by 10-100x for restaurants successfully migrating repeat customers.

The core economic argument for a Nigerian restaurant investing in WhatsApp direct-order:

A restaurant paying 20% commission on a NGN 10,000 order gives up NGN 2,000 to the delivery platform. Migrating that same order to WhatsApp direct with Paystack payment (1.5-2% fee = NGN 150-200) recovers ~NGN 1,800 per order. Even with modest customer-migration success rates, the annualised recovery on repeat customers materially exceeds the WhatsApp platform cost.

The catch: WhatsApp direct-order only works if the restaurant handles the delivery logistics (own rider, on-demand courier, or a platform 'own-fleet' arrangement). For restaurants without a delivery-logistics capability, the delivery platform's rider network is a real operational value the restaurant is paying commission for.

Naira budgeting implications:

• Any USD-billed WhatsApp platform is FX-exposed at settlement.
• Delivery-platform commission is naira-denominated (the platform settles in naira to the restaurant) — no FX exposure on that cost line.
• Paystack and Flutterwave transaction fees are naira-denominated.
• The naira budget question is 'which platform subscription' versus 'which commission percentage'.

Migration considerations for a restaurant moving to WhatsApp direct-order dominant model:

• Delivery logistics: own rider, Kwik Delivery, GIG Logistics, Gokada partnership, or delivery-platform 'own-fleet' arrangement.
• Payment reconciliation: Paystack/Flutterwave settlement into restaurant bank account matched to WhatsApp order records for accounting.
• Customer-acquisition: continued use of delivery platform for new-customer discovery even while shifting repeat customers to WhatsApp.
• Complaint handling: WhatsApp direct-order complaints are the restaurant's direct responsibility, not the platform's — needs staff bandwidth.

Reservation Deposit + No-Show Recovery + Peak-Window Slot Discipline for Nigerian Restaurants

Reservation deposits, no-show recovery, and peak-window slot management are the operational layer that compounds every other rulebook and payment discipline discussed above — a restaurant that fills the diary on Friday night without holding deposits leaves 20–40% of capacity to no-shows during Detty December, wedding season, and Sallah windows.

Reservation deposit norms in the Nigerian restaurant sector:
- Weeknight standard-cover reservation (2–6 pax) — deposit optional; a strong confirmation-message discipline with a reply-YES ask 24 hours ahead typically holds no-show under 15%. Casual dining and mid-market restaurants operate this way.
- Weekend prime-time reservation (Friday–Sunday dinner, 4–10 pax) — non-refundable reservation deposit ₦5,000–₦15,000 per booking, credited against final bill on attendance. Cuts no-show to 5–8% typical.
- Group bookings (10+ pax private-dining or partial-room) — non-refundable deposit ₦25,000–₦100,000 depending on room capacity and menu-set commitment; balance settled on the day.
- Full-room private events (birthday, corporate dinner, engagement) — 30–50% deposit of the event minimum spend, with a defined cancellation window (typically 7 days pre-event for partial refund; 72 hours for no refund).
- Peak-window premium — Detty December, Sallah, Valentine's, and Mother's Day carry surcharge and higher deposit requirements; some restaurants require full pre-payment for Christmas Eve, New Year's Eve, and Valentine's Day covers.

WhatsApp deposit-collection workflow:
- Booking confirmation with Paystack link — reservation confirmed only once deposit lands via Paystack (webhook-verified) or via direct bank transfer with proof-of-payment screenshot; verbal / voice-note holds do not survive the peak-window pipeline.
- Deposit-terms disclosure at booking — the deposit amount, refundability, and credit-against-bill rule communicated in writing before payment link is sent; surprise-at-the-door surcharges damage trust and trigger FCCPC-adjacent consumer-protection review.
- Reservation-cancellation policy — clearly stated cancellation window; policy sent as part of the booking confirmation for the record.
- 48-hour and 24-hour confirmation asks — 'confirming your Friday 8 p.m. booking for 6 pax — reply YES to hold or reply RESCHEDULE to move'; no-response after 24 hours releases the slot to the waitlist per stated policy.

No-show recovery pattern:
- Same-day no-show WhatsApp — polite check-in within 30 minutes of missed booking; captures the whether-still-coming signal and closes off table for waitlist.
- Post-no-show follow-up — next-day WhatsApp 'we held your table last night — hope everything's okay; would you like to rebook?' opens the recovery conversation without shaming; deposit-forfeit customers already have their financial signal.
- Repeat-no-show discipline — a customer with 2+ no-shows in a rolling period gets a polite one-time note that future bookings require full pre-payment or deposit at 100% of booking value; the customer either upgrades their commitment or self-selects out.

Peak-window slot management:
- Detty December waitlist opening — early November opt-in broadcast to the opted-in customer list ('Detty December Friday and Saturday dinner slots opening this weekend — reply YES for priority-booking access before public release'). Lifts deposit-locked booking density in the shoulder weeks before general availability opens.
- Sallah and Valentine's peak — separate opt-in and deposit workflow for these concentrated demand windows.
- Wedding-block reservations — reservations from wedding parties (rehearsal dinner, post-wedding brunch, family visitor group) route to a dedicated events-coordination WhatsApp thread with the primary booker; deposit and menu-set commitment coordinated as a package.
- Corporate lunch and dinner reservations — Tier-1 bank / oil-and-gas / consulting recurring bookings route to corporate-billing account rather than deposit; monthly invoice with 30-day terms and PO-referenced.

FCCPC-adjacent discipline: the FCCPC has periodically reviewed hospitality-sector deposit and refund practices under consumer-protection principles. Restaurants should maintain: (1) written deposit terms shared before payment; (2) clear cancellation-window with proportionate partial-refund tiers where applicable; (3) documented no-refund circumstances (no-show, no-notice cancellation within the retention window); (4) FCCPC-compliant complaint-handling process for disputed deposits.