07398 946 380
07398 946 380
Twilio API

Twilio WooCommerce SMS Notifications: How to Automate Order Updates

27 April 2026 7 min read

Email open rates for order notifications hover around 20–30%. SMS open rates are above 90%, usually within three minutes. For ecommerce businesses that want customers to actually see their order confirmations, despatch alerts and delivery notifications, SMS is significantly more effective than email. Adding Twilio SMS to WooCommerce connects to your order events and sends automated messages at each stage of the fulfilment process — without plugins, without limitations, and without ongoing SaaS fees.

What Twilio WooCommerce SMS can automate

Order confirmation. The moment an order is placed and payment is confirmed, an SMS fires: “Thanks for your order, Sarah. Order #12345 for £47.99 is confirmed. We’ll text you when it’s on its way.” This reduces the support queries that come in when customers don’t see their confirmation email.

Despatch notification. When an order status changes to Shipped or Completed (or a custom despatch status), an SMS fires with the tracking number and a link: “Your order is on its way! Track it here: [link]. Expected delivery: tomorrow.” Combined with a Royal Mail or DPD API integration, the tracking number can be populated automatically.

Out for delivery. For businesses using a carrier API that provides tracking events, the integration can trigger an SMS when the carrier marks the parcel as “out for delivery” that day. This significantly reduces customer anxiety and “where is my order” contacts.

Failed payment recovery. When a WooCommerce order has a payment failure — card declined, PayPal issue, pending payment timeout — an SMS prompts the customer to complete the order: “Hi Tom, your recent order couldn’t be completed. Click here to retry payment: [link].” SMS recovery messages have significantly higher response rates than email for abandoned orders.

Back-in-stock alerts. Customers who signed up for stock notifications on an out-of-stock product receive an SMS the moment the product is restocked, often before the email queue processes.

Review requests. A few days after an order is completed, an SMS asks for a review: “How was your recent order? Leave us a quick review here: [link]. It really helps!” SMS review requests typically achieve higher click-through rates than email.

WooCommerce plugin vs custom integration

Several WooCommerce SMS plugins exist. The most common connect to Twilio and send SMS on basic order status changes. They work for simple requirements. The limitations show up quickly when you need anything beyond basic notification triggers.

Custom trigger logic. Plugins fire on WooCommerce order status changes. A custom integration can fire on any event in your system — not just WooCommerce order status, but custom fields, product categories, order values, shipping methods, or logic that combines multiple conditions. “Send an SMS when an order over £100 is placed and the customer hasn’t ordered in the last 6 months” is impossible with a plugin and straightforward with a custom integration.

Dynamic content. Plugins use basic templates with simple placeholder tokens. A custom integration can pull any data from your WooCommerce database or external systems into the message — personalised product names, specific delivery windows from your carrier API, loyalty points balance, next order discount codes.

Two-way SMS. Plugins only send. A custom integration can receive replies and act on them. A customer who replies “CANCEL” can trigger an automated cancellation flow. A customer who replies with a query can have it routed to your team’s SMS inbox.

UK compliance and sender registration. Plugins handle sender configuration crudely. A custom integration includes proper UK A2P SMS registration, correct sender ID setup, and STOP keyword handling in line with PECR requirements.

How the integration is built

The integration hooks into WooCommerce’s order status transition events. When an order moves from one status to another — Pending to Processing, Processing to Completed, any status to On Hold — a WooCommerce action fires. The integration listens for these actions, checks whether the relevant conditions are met (is a phone number stored on the order?), formats the message with dynamic content from the order data, and calls the Twilio API to send the SMS.

The integration is built as a lightweight WordPress plugin or as a functions.php addition — whichever suits the site’s architecture. Phone numbers are read from WooCommerce’s billing phone field, or from a custom field if you collect phone numbers separately. All Twilio credentials are stored in WordPress options or environment variables server-side — never in the code itself.

For businesses using custom post-despatch status workflows — a separate shipping plugin, a custom order management flow, or manual status updates for certain order types — the integration hooks into the specific events that match the actual workflow rather than the standard WooCommerce statuses.

Order management SMS for the team

The same Twilio integration can also send internal SMS notifications to the business team — not just to customers. A high-value order placed triggers an SMS to the owner. An order with a delivery issue triggers an SMS to the operations manager. A low stock warning triggers an SMS to the buyer. Internal SMS notifications have higher urgency and visibility than email for time-sensitive operational events.

Internal notifications use the same Twilio integration with different recipient numbers — the messages go to staff mobile numbers rather than customer numbers. No additional Twilio setup is required; it’s a different trigger and recipient configuration in the same integration.

For the full Twilio service and pricing, see the Twilio SMS API integration service. For appointment reminder automations, see SMS appointment reminders with Twilio. For the complete Twilio API guide, see Twilio SMS API integration guide. For what the build costs, see the Twilio SMS integration cost guide.

Related posts

Handling opted-out customers

PECR requires that customers who reply STOP to an SMS are not sent further messages. Twilio automatically manages opt-outs at the phone number level — once a number has texted STOP, Twilio will not deliver further messages to that number from the same sender. The integration needs to store this opt-out status in WooCommerce against the customer record so that the integration doesn’t attempt to send to opted-out numbers in the first place.

Twilio provides an opt-out webhook that fires when a customer texts STOP. The integration receives this webhook and marks the customer as opted out in WooCommerce. Future send attempts check the opt-out status before calling Twilio, preventing unnecessary API calls to numbers that have opted out.

For the initial launch, existing customers should be sent an opt-in message before being added to the notification system — or the first transactional message should include opt-out instructions (“Reply STOP to stop texts”). This is both good practice and required for compliance with PECR for marketing-adjacent content such as review requests.

Measuring SMS notification effectiveness

Unlike email, SMS doesn’t have a standard open tracking mechanism. Delivery confirmation from Twilio confirms the message reached the carrier, and delivery status callbacks confirm it was delivered to the handset. Click tracking on links included in messages — using UTM parameters or a URL shortener — measures engagement with specific SMS messages.

The most useful operational metrics for a WooCommerce SMS integration are: delivery rate (percentage of sent messages that confirm as delivered), customer service contact rate before and after implementation (a well-functioning notification system should reduce “where is my order” contacts), and for recovery SMS, the payment completion rate on messages sent after a payment failure.

If you need help with a custom API integration for your website or business application, I can help. I build bespoke API integrations for UK businesses. See API integration pricing or get in touch to discuss your project.

Need a custom integration built?

I build custom API integrations — Stripe, Companies House and bespoke data pipelines. Reliable, well-documented, no agency overhead.

Discuss your project →