Why WhatsApp Commerce Is the Next Big Channel
WhatsApp has over 2 billion active users. In Nigeria, it's often the primary business communication tool — more used than email, more trusted than web forms. For businesses, this is an enormous opportunity: meet customers exactly where they already spend their time.
The WhatsApp Business Platform (Cloud API) makes this programmable. You can build automated order flows, appointment booking, customer support, payment confirmation, and shipping alerts — all inside WhatsApp.
How the Cloud API Works
The Cloud API is Meta's hosted version of the WhatsApp Business API. Instead of managing your own servers or partnering with a BSP for basic access, you can call Meta's APIs directly.
Key concepts:
Phone number: Each business has a WhatsApp Business phone number linked to a Meta Business account. This is the sender identity for all messages.
Webhooks: Incoming messages from users arrive as HTTP POST requests to your webhook URL. Your server processes these and responds.
Message templates: Proactive messages (notifications, reminders, marketing) must use pre-approved templates. Conversational replies within a 24-hour window can be free-form.
Interactive messages: Buttons (up to 3), list menus (up to 10 items), and product catalog messages enable structured flows without free-text parsing.
Building a Commerce Flow
A typical order flow:
1. User messages your business number with a product enquiry
2. Your bot responds with a product list (interactive list message)
3. User selects an item; bot confirms selection and asks for delivery details
4. User provides address; bot sends an order summary with Confirm/Cancel buttons
5. On confirmation, bot initiates payment link (Paystack, Flutterwave) via a CTA button
6. On payment, bot sends confirmation template with order ID and tracking link
This entire flow runs without a human agent and can handle hundreds of concurrent conversations.
Handling the 24-Hour Window
WhatsApp distinguishes between two types of messages:
- Session messages: Sent within 24 hours of the last user message. These can be any format — text, media, interactive. No template required.
- Template messages: Required for proactive outreach or messages outside the 24-hour window. Must be pre-approved by Meta.
For commerce, this means: if a user places an order and you need to send a shipping update 48 hours later, you need a pre-approved shipping update template. Plan your template library early — approval takes 24–72 hours.
Integrating with Your CRM
WhatsApp conversations are valuable customer data. Sync them to your CRM:
- Map WhatsApp phone numbers to customer records
- Store conversation history with message IDs
- Trigger CRM workflows on intent signals (e.g., "interested in X product")
- Sync order status back to WhatsApp for proactive notifications
HubSpot, Salesforce, and most modern CRMs have REST APIs that make this straightforward.
What You Need to Get Started
1. A Meta Business Account (verified)
2. A WhatsApp Business Account with a dedicated phone number
3. A server with a publicly reachable webhook endpoint
4. Node.js or Python to handle the webhook logic
5. Pre-approved message templates for your proactive use cases
The technical setup takes a day. The product design — figuring out the right conversation flows, templates, and error handling — takes longer. Invest in that upfront.
Want to build WhatsApp automation for your business? Let's get started →