WooCommerce Order Updates on WhatsApp: 6 Bugs I’d Watch For

Sending a WhatsApp message upon WooCommerce order status changes may seem straightforward, but in practice, six issues can cause problems. Directly calling the WhatsApp API within the woocommerce_order_status_changed hook can hinder checkout speed or the admin order screen. To avoid this, offload the task to Action Scheduler by utilizing as_enqueue_async_action().

Avoid sending the same message twice, especially when moving an order from processing to on-hold and back. To prevent this, store a meta flag, like _wa_sent_processing, and verify it before sending the message.

Customers may enter phone numbers in various formats, such as “098765 43210”, “+91-98765-43210”, or lacking the country code. Standardize inputs by normalizing the billing country, removing non-digit characters, and eliminating the leading zero.

Soliciting consent before sending messages is crucial to maintain a quality rating for your phone number. Include an opt-in checkbox at checkout, store the preference in order meta, and check it before every message send.

WhatsApp templates that exceed a purely transactional tone can be classified as marketing. To keep costs low, ensure order templates remain strictly transactional, such as “Your order shipped! Use code SAVE10 on your next order”.

Lastly, WhatsApp API messages may return a message ID even if delivery fails later. To address this, subscribe to the status webhook, log the result in order notes, and fall back on WooCommerce email for failed deliveries. If building and maintaining this system seems burdensome, consider using Wabbiyo, a WordPress plugin that supports the official WhatsApp Cloud API with a free plan: Click here to learn more.