WhatsApp automation for WooCommerce stores

Almost everything in WhatsApp automation is platform-agnostic: keyword flows, the knowledge base, Google Sheets lookups, the shared inbox and broadcasts work identically wherever your store runs. Only one part differs for WooCommerce — how a store event starts a flow.

That single difference is why WooCommerce merchants find far less written for them than Shopify merchants do, and it is smaller than the coverage gap suggests.

What works without any integration at all

Flow	Needs the store connected?
Welcome message and menu	No
After-hours auto-reply	No
Keyword flows — returns, wholesale, stock	No
AI answers from your own website	No
Order-status lookup from a Google Sheet	No
Shared team inbox	No
Broadcasts and segments	No
Click-to-WhatsApp ad flows	No
Order confirmation, shipping, cart recovery	Yes

Eight of those nine need nothing from WooCommerce. A store that builds only those has most of the value, and can start this afternoon.

The one part that is different

Shopify sends store events directly. WooCommerce does not have that connection, so an order event has to reach the automation builder another way — through the External Event trigger, which starts a flow when your own software posts an event.

The developer task is small: when an order is placed, post to /api/external/event with your account API key, an event name you choose, the customer's phone number, and whatever fields the flow needs. Those arrive in the flow as {{event.field_name}}. The full brief is in starting a flow from your own system.

In WooCommerce terms that is a hook on order status change and an HTTP request — an hour of work for someone comfortable with the platform, and it is the only part of this that needs one.

Three routes, ranked

1. A small custom hook. Cleanest and most reliable. Fires on the order statuses you care about, sends exactly the fields you need.
2. An automation tool as the middleman. If you already run something that watches WooCommerce orders and can make an HTTP request, it can post the event without anyone writing code.
3. A Google Sheet. Export or sync orders to a sheet, and let flows read it. This does not give you real-time triggers, but it does give you order-status lookups immediately — using a Google Sheet as your automation's database.

Most WooCommerce stores should start with route three for lookups and add route one when they want proactive order messages.

Which events to send

You control the list, which is an advantage over a fixed integration. The ones worth wiring, in order of value:

• Order placed — the confirmation flow, and the highest-value one in cash-on-delivery markets.
• Order shipped — with carrier and tracking, if you have them.
• Payment failed — a recovery conversation while intent is live.
• Abandoned cart — if your setup captures them.
• Anything specific to your business that Shopify would never send: a made-to-order stage completing, a subscription renewal, a booking confirmed.

That last bullet is the genuine upside. A Shopify store is limited to seven events; a WooCommerce store posting its own can trigger a flow on anything its software knows about.

The rules do not change

Whatever platform you run, Meta's constraints are identical:

• A flow starting from a store event lands on a chat outside the 24-hour customer service window, so the first message needs an approved template — per Meta's sending messages documentation.
• That template is charged; everything after the customer taps is free.
• Your messaging tier starts at 250 unique recipients per rolling 24 hours, per Meta's messaging limits documentation.
• Marketing templates cannot reach US numbers.

So the design advice is the same too: lead with utility, ask rather than announce, and let the customer's tap open the free window.

Writing back to the order

Here is an honest limitation. The Shopify-specific steps that tag or cancel an order do not apply to WooCommerce, so a flow cannot write back to your store directly.

Two workarounds, both fine in practice. A Call External API step can post the customer's answer to your own endpoint, which updates the order — the same developer who wired the trigger can wire this. Or the flow can tag the contact and leave an internal note, and a person updates the order. For lower volumes the second is entirely reasonable.

A realistic first week

1. Day 1. Connect your number, build the welcome menu, the after-hours reply and the cancel-pending-question flow. None needs WooCommerce.
2. Day 2. Add keyword flows for returns, stock and wholesale, and a knowledge base from your existing policy pages.
3. Day 3. Put your orders into a Google Sheet and build the order-status lookup.
4. Week 2. Get the order-placed event posting, and build the confirmation flow.
5. Later. Shipping, then cart recovery.

By the end of day three you have most of the support-deflection value with no developer involved at all, which is a better starting position than most Shopify guides imply is available to you.

Why so little is written for WooCommerce

Worth saying plainly, because it can look like the platform is unsupported. The WhatsApp tooling market grew up around the Shopify App Store, where a listing is a distribution channel — so vendors write Shopify content because that is where their installs come from.

None of that reflects a technical limitation. A WooCommerce store with one hook in place has the same automation capability as a Shopify store, plus the freedom to trigger on events Shopify does not send.

Deciding which order statuses matter

WooCommerce carries more order statuses than Shopify exposes as events, which is an advantage if you choose deliberately rather than firing on all of them.

Status change	Worth a message?	Why
Pending → Processing	Yes	The confirmation — highest value
Processing → Completed	Yes	Usually your dispatch signal
Any → Cancelled	Yes	Confirming a cancellation prevents a support message
Any → Refunded	Yes	Money moving deserves a message
On hold	Depends	Only if the customer needs to act
Failed	Yes	A recovery conversation while intent is live

Send one event per status you care about, with a distinct event name, and build one flow per event. Do not send a single generic "order updated" event — a rule with a blank or shared event name fires on everything, which turns one flow into a catch-all messaging people about the wrong thing.

Testing without a real customer

Have whoever wires the hook post one test event with your own phone number before you publish anything. It proves three things at once: the API key works, the event name matches what your rule expects, and the template renders with real values rather than blanks.

That last point matters more on WooCommerce than on Shopify, because you control which fields are sent — and a template variable that resolves to an empty string is rejected outright by Meta, so the customer receives nothing. Testing protocol is in testing an automation safely.

Templates you will need

The same set as any store, and no more: an order confirmation, a shipping notification, and — if you take cash on delivery — a delivery-day notice. Three templates, each with variables, covers a whole catalogue.

Meta caps templates at 250 per WhatsApp Business Account for an unverified business portfolio and 6,000 once verified, per its template documentation, so there is no pressure to economise — but there is every reason not to build one per product, which is how stores end up maintaining dozens of near-identical messages.

Plugins versus your own hook

Plenty of WooCommerce plugins advertise WhatsApp integration, and it is worth knowing what you are choosing between.

A plugin that connects through the official Cloud API is doing the same thing a custom hook does, with a settings page instead of code. That is a reasonable trade if the events you need are the ones it sends.

A plugin that works by linking a device — typically set up by scanning a QR code with your phone — is a different product entirely. It needs no template approval and charges no per-message fee, which is exactly why it looks better, and it carries a structural risk to your number that the official route does not. If setup involves a QR code, that is the tell. See what to do when your account is restricted.

What to ask before you commit

1. Does it use the official Cloud API, or link a device?
2. Which order statuses can it fire on?
3. Can it send the fields your templates need, including tracking?
4. Can it write anything back to the order?
5. What happens if it stops being maintained?

The last question is the one WooCommerce merchants learn to ask. A hook you own keeps working; a plugin that stops being updated eventually does not.

Where to start today

Build the flows that need nothing from WooCommerce first — the welcome menu, the after-hours reply, keyword flows for your commonest questions, and a knowledge base from your existing policy pages. That is an afternoon's work, no developer, and it removes most of your repetitive support volume.

Add the order-placed event when you have someone available to wire it. By then you will know from your own inbox which order messages customers actually want, which is a better basis for the flow than copying a Shopify guide.