Order status notifications over WhatsApp: the three requirements
What it takes to send an order status update over WhatsApp
Three things, and none of them is the wording of the message.
Order status notifications over WhatsApp need a template approved by Meta, a payment method configured in Meta, and a rule that understands it fires on status changes. Any guide that starts with how to word the message is skipping what makes it arrive.
That the channel works is not in dispute. Meta reports that 43% of shoppers track their seasonal orders through messages, and that 55% of millennial and Gen Z seasonal shoppers say messaging a business makes them feel more connected.
Requirement 1: a template approved by Meta
Outside the conversation window you cannot write free text. A template goes out, and Meta approves it.
Meta classifies order status updates under utility messages, which it defines as conversations that keep the customer informed with timely updates. Picking that category correctly is half the approval.
The other half is writing it without ambiguity. A template that looks like a promotion, or that is nothing but variables with no context, comes back rejected.
Requirement 2: a payment method configured in Meta
Template messages are billed by Meta, not by us. With no payment method registered on Meta's side, they do not go out.
And there is a date worth noting: from 1 October 2026 Meta starts charging for service messages and also for utility templates sent inside the 24-hour window, which until now were free.
Which means the "your order has shipped" update starts carrying a per-message cost even when the customer wrote to you a moment ago. Worth reviewing how many updates per order you send before that date.
Requirement 3: the rule fires on status changes
This is the one that surprises most people: the notification does not go out when the order is created.
Rules are defined over transitions. You pick which status to which status, and that combination is what fires. Each rule is switched on and off on its own, without touching the others.
If you want to announce creation, the practical way out is having a first status and moving the order into it. It is not an elegant detour, but it is how it works today.
| What you want to announce | How it is configured |
|---|---|
| "We received your order" | Rule from the initial status to the next one |
| "It is being prepared" | Rule from pending to in preparation |
| "It is out for delivery" | Rule from preparation to dispatched |
| "It was delivered" | Rule from dispatched to delivered |
Who receives each update
It depends on the channel, and they do not work the same.
- Over WhatsApp, it always goes to the order's contact. There is no recipient list.
- By email, it goes to the addresses you type, to the contact's email, or to both.
That is a practical distinction: the internal heads-up for your team goes by email; the one the customer sees goes over WhatsApp.
Email and WhatsApp do not cover for each other
There is no automatic fallback between channels.
If the WhatsApp does not arrive, the email does not go out by itself. If you want the update to arrive no matter what, you enable both channels on the same rule and accept that sometimes the customer gets two.
Worth saying because intuition says the opposite, and intuition gets paid for with customers who never found out.
The email goes out with your brand, not ours
The customer sees your name and your logo on the notification.
It is a small detail that changes how the message reads. An order update signed by a provider your customer has never heard of creates exactly the doubt the update was meant to prevent.
What to write inside the template
Write it once and reuse it in every rule that needs it.
Templates pull in your order's fields, the contact's details and the names of your statuses. So the same text serves three different rules without being rewritten.
And this is not plan-gated: both notification channels are available on every plan.
Key takeaways
- Sending updates over WhatsApp needs an approved template, a payment method in Meta, and a status-change rule.
- Meta classifies these updates as utility messages, and that is the category to pick when creating the template.
- From 1 October 2026 utility templates inside the 24-hour window start being charged.
- Rules fire on status transitions, not on order creation.
- WhatsApp always goes to the order's contact; email goes to the addresses you choose.
- There is no automatic fallback between channels: if you want redundancy, enable both.
Frequently asked questions
- Can I notify the customer as soon as the order is created?
- Not directly: rules fire on status changes. The practical approach is having the order start in an initial status and moving it to the next one, which is the transition that fires the update.
- How much do these notifications cost?
- Template messages are billed by Meta at its own rates, which is why a payment method has to be configured on Meta's side. From 1 October 2026 utility templates sent inside the 24-hour window are charged too.
- What if Meta rejects my template?
- You rewrite it and submit it again. The most common causes are picking the wrong category, ambiguous text, variables with no context around them, or a template that is nothing but variable fields.
- Can I send the update by email and over WhatsApp at the same time?
- Yes, by enabling both channels on the same rule. What does not exist is automatic fallback: if one does not arrive, the other does not go out on its own.
- Are these notifications on every plan?
- Yes. Order notification channels are not plan-limited. What you do need for WhatsApp is the approved template and the payment method registered with Meta.
Related posts
Get twice the output from your team without asking more of them
It answers WhatsApp, Instagram and web. It learns your business, takes the orders, and hands off to a person when it matters. You see every action noted in the chat.
Free Pro trial. No credit card required.