Uncategorized
24 min read

How to Send WooCommerce Order Notifications to WhatsApp

  • David
    Author David
  • Published

WhatsApp has become the fastest lane to customer attention, and WooCommerce is the engine of millions of online stores. Put them together and you can deliver instant order confirmations, shipping updates, and proactive service directly in a channel customers actually read. In this comprehensive guide for the Watsspace Digital Marketing Blog, you’ll learn exactly how to send WooCommerce order notifications to WhatsApp—covering plugins, the WhatsApp Business Platform (Cloud API), Business Solution Providers (BSPs), compliance, message templates, code examples, analytics, and ROI.

Why send WooCommerce order notifications to WhatsApp?

Customers expect immediate, clear updates about their purchases. Email alone often gets lost, while SMS can feel intrusive or costly. WhatsApp sits in the sweet spot: high visibility, conversational tone, and global reach.

  • Massive reach: WhatsApp is used by more than 2 billion people globally, exchanging over 100 billion messages per day. Meta
  • Higher engagement: Messaging channels consistently outperform email on read and response rates. Many brands report read rates above 90% for WhatsApp order updates, and quick replies due to the conversational interface. Twilio Messaging Engagement Report
  • Customer preference: 64% of people say they prefer messaging to calling or email for simple queries and updates. Facebook IQ Messaging Survey
  • Conversion and loyalty: Fast, transparent order communications reduce WISMO (“Where is my order?”) tickets and improve satisfaction. Companies with faster response times see higher CSAT and repeat purchases. Zendesk CX Trends 2023
  • Cart recovery potential: Checkout friction drives ~69.99% cart abandonment. Proactive messaging and transactional clarity can mitigate post-purchase anxiety and improve lifetime value. Baymard Institute

Bottom line: WhatsApp order notifications create a low-friction customer experience that builds trust and reduces support workload.

How the WhatsApp Business Platform works (and what it means for WooCommerce)

Before you wire WooCommerce events to WhatsApp, it’s critical to understand the rules and structure of WhatsApp’s business messaging.

Key concepts

  • Business accounts and phone numbers: You’ll message from a WhatsApp Business number connected to a WhatsApp Business Account (WABA). WhatsApp Business Platform Documentation by Meta
  • Session vs. template messages:
    • Session (customer-initiated): Free-form messages within a 24-hour window after the customer last messaged you.
    • Template (business-initiated): Pre-approved message templates required to initiate conversations or message outside the 24-hour window. Templates can be Utility (e.g., order updates), Authentication, or Marketing.
  • Opt-in: Customers must consent to receive WhatsApp messages. The opt-in must be clear and granular (e.g., “Order updates on WhatsApp”).
  • Quality rating and limits: Message quality and phone number tiers affect throughput. High-quality, relevant notifications protect your sender reputation.
  • Pricing: WhatsApp charges per 24-hour conversation window by category and region. Rates vary. Meta

WooCommerce triggers events like “order created,” “payment complete,” and “status changed.” Your job is to transform those events into properly formatted WhatsApp messages that respect opt-in and template rules.

Three ways to send WooCommerce notifications to WhatsApp

You can integrate WhatsApp with WooCommerce using plugins, Meta’s Cloud API, or via a Business Solution Provider (BSP). Each path balances speed, control, and cost differently.

Approach Best For Setup Time Cost Control Scalability Dev Effort Examples
WooCommerce plugin + WhatsApp provider Non-technical teams wanting speed Fast Plugin license + messaging fees Medium Medium–High Low WooCommerce WhatsApp Notification plugins, AutomateWoo add-ons, WATI, Zoko
WhatsApp Business Platform (Cloud API) direct Teams needing flexibility and lower vendor lock-in Medium Meta conversation fees + infra High High Medium–High Meta WhatsApp Cloud API
BSP (Twilio, 360dialog, MessageBird, Vonage) Enterprises needing reliability, support, dashboards Medium BSP fees + conversation fees High High Medium Twilio, 360dialog, MessageBird, Gupshup, Vonage

Prerequisites and compliance checklist

  • WooCommerce installed and configured; admin access to WordPress.
  • Clear opt-in for WhatsApp order updates at checkout, account signup, or on product pages. Store the customer’s WhatsApp number and consent.
  • Privacy policy updated to cover WhatsApp communications and data handling.
  • WhatsApp Business Account (WABA), a verified phone number, and either:
    • Access to WhatsApp Cloud API, or
    • An account with a BSP supporting WooCommerce or webhooks.
  • Approved message templates for order confirmation, shipping, out-for-delivery, delivered, and COD reminders (if applicable).
  • Data minimization: Never send full PANs or sensitive PII via WhatsApp. Keep it transactional, not confidential.
  • Opt-out handling: Provide a simple way to stop messages (e.g., “Reply STOP to unsubscribe”) and maintain a suppression list.

Option 1: Use a WooCommerce WhatsApp notification plugin

Plugins are the fastest way to go live, especially if you want a low-code path with pre-built triggers.

Typical setup steps

  1. Choose a plugin: Look for “WooCommerce WhatsApp notifications,” “WhatsApp for WooCommerce,” or AutomateWoo/Flow Builder style plugins with WhatsApp connectors. Verify it supports your provider (Cloud API, Twilio, 360dialog, MessageBird, WATI, Zoko, etc.).
  2. Install and activate the plugin in WordPress.
  3. Connect your provider:
    • For Cloud API, you’ll paste your WhatsApp Business Account ID, phone number ID, and access token.
    • For BSPs, provide API keys, phone number, and sender ID.
  4. Map WooCommerce events: Select events like “Order created,” “Payment completed,” “Order status changed to processing/shipped/completed,” “Refunded,” etc.
  5. Assign templates: Choose the approved WhatsApp template for each event. Insert variables like {{1}} for order number, {{2}} for name, etc.
  6. Test in sandbox or with a test number. Verify formatting, variables, and delivery.
  7. Enable opt-in logic: Ensure only users who consented receive messages. Many plugins add a checkout checkbox (“Send WhatsApp updates”).

Pros and cons

  • Pros: Quick launch, minimal code, UI for templates, built-in mapping of WooCommerce events.
  • Cons: Less flexibility for custom flows, potential plugin conflicts, and reliance on the plugin’s update cycle.

Option 2: Use the WhatsApp Business Platform (Cloud API) directly

Using the Cloud API gives you maximum flexibility and often the most predictable cost structure. You’ll own the integration and can tune it for performance and scale.

Cloud API setup: Quick overview

  1. Create a Meta app and enable the WhatsApp product. Get a test business number.
  2. Verify your business (Business Verification in Meta Business Manager).
  3. Add a phone number to your WABA. Complete number verification.
  4. Generate a permanent access token or set up App tokens with secure rotation.
  5. Register your webhook endpoint to receive delivery receipts and incoming messages.
  6. Create and submit message templates for approval (Utility for order updates).

Once you have the Phone Number ID and access token, you can call the Cloud API’s /messages endpoint from your server whenever WooCommerce fires an event.

Example: Sending an order confirmation via Cloud API

The snippet below listens for the WooCommerce “processing” status (paid) and posts a WhatsApp template message.

add_action('woocommerce_order_status_processing', 'watsspace_send_whatsapp_order_confirmation', 10, 1);

function watsspace_send_whatsapp_order_confirmation($order_id) {
    $order = wc_get_order($order_id);
    if (!$order) { return; }

    // Only send if customer opted-in and phone is present
    $opt_in = get_post_meta($order_id, '_whatsapp_opt_in', true);
    $phone  = preg_replace('/D+/', '', $order->get_billing_phone()); // E.164 clean
    if (!$opt_in || empty($phone)) { return; }

    $customer_name = $order->get_billing_first_name();
    $order_number  = $order->get_order_number();
    $total         = $order->get_total();
    $tracking_url  = home_url('/account/orders/'); // replace with real tracking page

    $phone_number_id = getenv('WS_WHATSAPP_PHONE_NUMBER_ID');
    $access_token    = getenv('WS_WHATSAPP_ACCESS_TOKEN');

    $payload = array(
        'messaging_product' => 'whatsapp',
        'to' => $phone,
        'type' => 'template',
        'template' => array(
            'name' => 'order_confirmation',
            'language' => array('code' => 'en'),
            'components' => array(
                array(
                    'type' => 'body',
                    'parameters' => array(
                        array('type' => 'text', 'text' => $customer_name),
                        array('type' => 'text', 'text' => $order_number),
                        array('type' => 'text', 'text' => wc_price($total)),
                        array('type' => 'text', 'text' => $tracking_url),
                    )
                )
            )
        )
    );

    $response = wp_remote_post(
        "https://graph.facebook.com/v18.0/{$phone_number_id}/messages",
        array(
            'headers' => array(
                'Authorization' => "Bearer {$access_token}",
                'Content-Type'  => 'application/json'
            ),
            'body' => wp_json_encode($payload),
            'timeout' => 20
        )
    );

    // Optional: log response for auditing
    if (is_wp_error($response)) {
        error_log('WhatsApp send error: ' . $response->get_error_message());
    } else {
        error_log('WhatsApp send status: ' . wp_remote_retrieve_body($response));
    }
}

Note: Template placeholders must match the approved template sequence, and numbers must be in E.164 format (e.g., 15551234567).

Option 3: Use a Business Solution Provider (BSP)

BSPs are official partners offering WhatsApp APIs, dashboards, and support. They often simplify template management, compliance, and analytics.

  • Examples: Twilio, 360dialog, MessageBird, Gupshup, Vonage.
  • Integration model: Your server or plugin calls the BSP’s API; the BSP bridges to WhatsApp. Many have native WooCommerce connectors or Zapier/Make scenarios.
  • Pros: Robust reliability, tooling, support, fallbacks (SMS), QA sandboxes.
  • Cons: Additional platform fees and possible vendor lock-in.

BSP integration steps

  1. Create an account and add your WhatsApp sender.
  2. Request template approvals via the BSP console.
  3. Use a WooCommerce plugin supported by the BSP or implement a webhook/REST integration.
  4. Test delivery, localization, and failover options.

Crafting high-converting WhatsApp order messages

Design messages that are clear, concise, and actionable. Stick to Utility category templates for transaction updates.

Best practices

  • Personalize with name, order number, and item count.
  • Front-load the value: “Order confirmed,” “Shipped,” or “Delivered.”
  • One action: link to order details or tracking page.
  • Compliance: Avoid promotional language in Utility templates.
  • Language: Offer templates matching customer locale.

Template examples

order_confirmation (Utility):

Hi {{1}}, your order {{2}} is confirmed.
Total: {{3}}
Track or manage your order: {{4}}
Reply STOP to unsubscribe.

order_shipped (Utility):

Good news, {{1}}! Your order {{2}} has shipped.
Carrier: {{3}}
Tracking: {{4}}
Need help? Reply here. STOP to opt out.

order_delivered (Utility):

Delivered: {{1}}, your order {{2}} has arrived.
How did we do? {{3}}
Support: {{4}}
STOP to opt out.

cod_reminder (Utility)

Reminder: Cash on Delivery for order {{1}} is {{2}} due today.
If you need to reschedule, reply HELP.
STOP to opt out.

Technical implementation: mapping WooCommerce events to WhatsApp

WooCommerce exposes many hooks for your notification logic. You will typically listen for status transitions and send the relevant WhatsApp template.

Common hooks and what to send

  • woocommerce_thankyou: After checkout success. Send order confirmation.
  • woocommerce_order_status_processing: Paid and processing. Send confirmation or “we’re preparing your order.”
  • woocommerce_order_status_completed: Fulfilled or delivered. Send delivery confirmation.
  • woocommerce_order_status_refunded: Refund notice. Send refund confirmation.
  • custom shipment events: If you use a shipping plugin, hook into its update actions to send “shipped” with tracking info.

Webhook-first architecture

For reliability, consider a small service layer between WooCommerce and WhatsApp. Queue events to avoid blocking the checkout and to retry on failures.

// Pseudo-architecture
WooCommerce --> Event Queue (e.g., database table) --> Worker Cron
Worker Cron --> Sends WhatsApp via API --> Logs status
Webhook Receiver <-- Delivery receipts, updates quality metrics

Testing, QA, and launch

High-quality messaging starts with rigorous testing. This protects your sender quality and customer experience.

  • Use a test number: Add your own numbers to a test user list and simulate all order paths.
  • Validate templates: Ensure variables are safe, trimmed, and localized (currency, decimal separators, date formats).
  • Check opt-in gates: Attempt orders with and without consent; confirm suppression works.
  • Delivery receipts: Verify you receive “sent,” “delivered,” and “read” statuses via webhook or provider dashboard.
  • Fallbacks: If WhatsApp fails, optionally fall back to email. Make this explicit in your policy.
  • Load test: Simulate peak order volume (e.g., sales) and measure queue latency and API throttling.

Analytics and optimization

Strong measurement turns notifications into a growth lever. Instrument your flow end to end.

  • Core metrics:
    • Sent, delivered, read rates (by template and locale).
    • Click-through to order detail or tracking page.
    • Customer replies and resolution time in the 24-hour session window.
    • WISMO ticket volume pre/post WhatsApp rollout.
    • Refund rates and delivery attempts (for COD).
  • Revenue impacts:
    • Repeat purchase rate within 30–60 days post-delivery.
    • Average time-to-first-response for support queries.
    • CSAT/NPS after delivery messages. Zendesk CX Trends 2023
  • A/B testing ideas:
    • Short vs. detailed order confirmation.
    • Inclusion of a “Need help?” prompt vs. purely informational.
    • Localized tone and emoji usage by market.

Cost modeling and ROI

WhatsApp charges per conversation window, and your provider may add platform fees. To estimate ROI, compare incremental customer experience gains and reduced support load to the cost of messaging.

Component Example Input Notes
Monthly orders 10,000 All orders eligible for WhatsApp updates
Conversation windows per order 1–2 e.g., confirmation + shipping
WhatsApp conversation cost Varies by country/category Check Meta pricing; Utility usually lower than Marketing
BSP/platform fees $0–$0.02 per message Depends on vendor
WISMO ticket reduction 20–40% Observed by many brands after proactive messaging Zendesk CX Trends 2023
CSAT improvement +5–15 pts Faster, clearer updates
Repeat purchase lift +2–5% Better post-purchase experience

Simple ROI formula:

ROI = (Support cost savings + Incremental gross margin from retention) - (WhatsApp + platform fees)

Advanced tactics for different order types

Not all orders are equal. Tailor your messages for the scenario.

  • Cash on Delivery (COD):
    • Send a polite payment readiness reminder and delivery window confirmation.
    • Offer rescheduling or cash change confirmation to reduce failed attempts.
  • Backorders/pre-orders:
    • Set expectations with clear ETA and periodic status updates.
    • Offer alternatives if delays exceed thresholds.
  • Subscriptions:
    • Notify upcoming renewals, successful charges, and shipment cycles.
    • Provide a one-tap path to pause or change frequency.
  • International shipments:
    • Localize language, currency, and duty/tax info.
    • Include carrier tracking that works in the destination market.
  • BOPIS/Click-and-Collect:
    • Send “Ready for pickup” with store location and hours.
    • Remind after 24–48 hours if not collected.

Messaging must respect privacy and security standards while delivering value.

  • PII minimization: Send only what’s needed: first name, order number, masked email if necessary. Avoid sensitive data or full addresses unless critical.
  • Payment data: Never transmit card details via WhatsApp. PCI-DSS prohibits sending PANs in cleartext.
  • Opt-in records: Store timestamp, method, and consent text per user. Be able to prove consent on request.
  • Opt-out: Honor STOP/UNSUBSCRIBE signals and provide alternative channels.
  • Data retention: Define how long you store message logs and why; include in your privacy policy.
  • Regional laws: Comply with GDPR, CCPA, LGPD, and local telecom rules where you operate.
  • Meta policies: Use the correct template category, avoid spammy language, and monitor quality rating to avoid restrictions. WhatsApp Business Platform Documentation by Meta

Troubleshooting common issues

  • Messages not delivering:
    • Check opt-in and E.164 formatting of phone numbers.
    • Confirm template approval and language code.
    • Monitor provider status and phone number limit tiers.
  • Template rejections:
    • Remove promotional or ambiguous text from Utility templates.
    • Use placeholders consistently; provide realistic sample content in submissions.
  • Quality rating drops:
    • Reduce frequency; ensure content relevance and clarity.
    • Add opt-out copy and limit off-hours messages in certain markets.
  • Duplicate messages:
    • De-duplicate events using order ID + status hash keys.
    • Implement idempotent send logic with a message log table.
  • WooCommerce conflicts:
    • Disable other plugins one by one to identify conflicts.
    • Use action priorities and avoid blocking calls on checkout threads.

Implementation blueprint: end-to-end example

This blueprint aligns WooCommerce events with WhatsApp templates, ensuring compliance and reliability.

  1. Checkout opt-in:
    • Add a checkbox “Send me order updates on WhatsApp.”
    • Save to order meta and user meta for future orders.
  2. Template catalog:
    • order_confirmation (Utility)
    • order_shipped (Utility)
    • out_for_delivery (Utility)
    • order_delivered (Utility)
    • cod_reminder (Utility)
    • refund_processed (Utility)
  3. Event mapping:
    • Thank you page or processing → order_confirmation
    • Shipment created → order_shipped
    • Carrier status “Out for delivery” → out_for_delivery
    • Status completed → order_delivered
    • Refunded → refund_processed
  4. Send service:
    • Use Cloud API or BSP SDK. Abstract send logic into a single function with retries.
    • Log message ID, order ID, template, timestamp, and result.
  5. Inbound handling:
    • Route replies to support inbox. Auto-reply with office hours when out-of-session.
    • On STOP/UNSUBSCRIBE, toggle suppression flag.
  6. Monitoring:
    • Dashboard for delivery, read rates, and template quality metrics.
    • Alert on error spikes or API throttling.

Code snippets: adding opt-in to WooCommerce checkout

The following adds a WhatsApp opt-in field to checkout and saves it to order meta for later use in your send function.

// 1) Add checkbox to checkout
add_action('woocommerce_after_checkout_billing_form', function($checkout) {
    woocommerce_form_field('whatsapp_opt_in', array(
        'type'  => 'checkbox',
        'class' => array('form-row-wide'),
        'label' => __('Send me order updates on WhatsApp'),
        'required' => false,
    ), $checkout->get_value('whatsapp_opt_in'));
});

// 2) Save to order meta
add_action('woocommerce_checkout_update_order_meta', function($order_id) {
    $opt_in = isset($_POST['whatsapp_opt_in']) ? 'yes' : 'no';
    update_post_meta($order_id, '_whatsapp_opt_in', $opt_in);
});

// 3) Persist on user profile for future orders (optional)
add_action('woocommerce_checkout_update_user_meta', function($customer_id, $posted) {
    if (isset($_POST['whatsapp_opt_in'])) {
        update_user_meta($customer_id, 'whatsapp_opt_in', 'yes');
    }
}, 10, 2);

Cloud API: cURL example for quick testing

If you want to test outside WordPress, here’s a basic cURL example to send a template message.

curl -X POST 
  https://graph.facebook.com/v18.0/PHONE_NUMBER_ID/messages 
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" 
  -H "Content-Type: application/json" 
  -d '{
    "messaging_product": "whatsapp",
    "to": "15551234567",
    "type": "template",
    "template": {
      "name": "order_confirmation",
      "language": { "code": "en" },
      "components": [{
        "type": "body",
        "parameters": [
          { "type": "text", "text": "Alex" },
          { "type": "text", "text": "#1245" },
          { "type": "text", "text": "$49.90" },
          { "type": "text", "text": "https://yourstore.com/account/orders/1245" }
        ]
      }]
    }
  }'

Localization and accessibility

Global stores must align messages to customer preferences and local regulations.

  • Language: Maintain template variants per locale (en, es, pt, ar, hi, etc.). Store the user’s language in WooCommerce and map to templates.
  • Currency and units: Format amounts and dimensions per locale.
  • Time windows: Respect local messaging times if culturally sensitive.
  • Accessibility: Keep messages clear, provide human support on request, and avoid heavy emoji if they harm legibility.

Team workflows and ownership

Make WhatsApp notifications a cross-functional effort.

  • Marketing: Defines tone, templates, and localization.
  • Product/Engineering: Owns integration, reliability, and metrics.
  • Support/Operations: Handles replies and edge cases (address changes, reschedules).
  • Legal/Compliance: Reviews opt-in flows and template categories.

Create a quarterly review cadence to audit templates, monitor quality ratings, and refresh content.

Frequently asked questions

Can I send promotional messages about new products via WhatsApp?

Yes, but you must use Marketing category templates, and customers must have opted in to receive them. Keep this separate from Utility messages like order updates.

Do I need business verification to send notifications?

Yes, to scale beyond testing and to use your own number, you must complete Meta Business Verification. Meta

What if a customer responds to my order message?

The reply opens a 24-hour session; during that window, you can send free-form messages to resolve the issue. Always keep it relevant to their query.

What if I migrate from a BSP to the Cloud API?

It’s possible to port your phone number between providers. Plan downtime, template re-registrations, and webhook changes carefully.

How many templates should I create?

Start lean: confirmation, shipped, delivered, refund, and one COD reminder (if needed). Expand with localization once stable.

Final checklist and next steps

  • Opt-in implemented at checkout and stored to order/user meta.
  • WhatsApp number verified and connected (Cloud API or BSP).
  • Templates approved for confirmation, shipping, delivery, refund.
  • Event mapping completed for WooCommerce status changes.
  • Send logic centralized with retries, logs, and idempotency.
  • Monitoring for delivery, read rates, and quality rating.
  • Security and privacy checks: data minimization, opt-out honored.
  • QA completed across locales, currencies, and payment types.

WhatsApp notifications are one of the most impactful, low-lift improvements you can make to your WooCommerce customer experience. Whether you plug in a ready-made extension, go direct with the Cloud API, or partner with a BSP, the framework above will get you from concept to reliable, compliant, and high-performing notifications. If you need a strategic partner to plan templates, implement the integration, and build analytics, the team behind the Watsspace Digital Marketing Blog specializes in turning messaging into measurable business outcomes.

Sources cited: Meta, WhatsApp Business Platform Documentation by Meta, Twilio Messaging Engagement Report, Facebook IQ Messaging Survey, Zendesk CX Trends 2023, Baymard Institute.

Check out other posts