WhatsApp Shipping Updates for Online Stores

Ask any small online store owner what eats their afternoon and the answer is rarely marketing. It's 'where is my order?' People ask it by phone, by Instagram DM and on WhatsApp, usually while the parcel is sitting at a hub in the next city.

Most of those messages are avoidable. A customer who has been told what's happening doesn't need to ask. The trick is knowing which updates actually matter and which ones are just you talking.

The five updates worth sending

1. 1Order received: the items, the total and the expected dispatch date.
2. 2Dispatched: the courier name and a tracking link, if the courier provides one.
3. 3Out for delivery: a heads-up that someone should be at the address or reachable by phone.
4. 4Delivered: a short thank-you and a way to reach you if something is wrong.
5. 5Delayed: sent whenever you know about a problem, not after the customer notices.

That's it. We'd resist the urge to send a message for every internal status such as packed, labelled or picked up. The customer doesn't care that the parcel has a label. They care about three things: did you get my order, is it on its way, and is it going to arrive.

Delay messages are the ones people remember

Anyone can send 'your order has shipped'. What builds trust is writing 'your order is delayed by two days because the courier missed the pickup, and here is the new date'. It's slightly uncomfortable to send, and that's exactly why customers notice.

Don't hide behind vague wording. 'Your order may be slightly delayed' makes people panic. A date, a reason in one clause, and an apology in one sentence is enough.

Cash on delivery needs its own thinking

COD orders that get refused at the door are expensive. You pay for shipping both ways and the stock is stuck in transit. A short confirmation message before dispatch, asking the customer to reply to confirm the address and the order, filters out a good share of the orders placed on impulse or by mistake.

Don't promise that it works for every store, because it depends on your customers and your products. Try it for a month, compare refused orders before and after, and decide from your own numbers.

Templates, windows and who the message is from

On the official WhatsApp Business API, a business-initiated message outside a customer-initiated conversation generally needs an approved template. Shipping updates are a classic template use case, because you want to send them whenever your system says so, not only when the customer happens to message you first. Read our post on the 24-hour window and check Meta's current rules and categories before you design the templates.

Variables are what make a template feel personal: the customer's name, the order number, the courier, the tracking link. Keep the fixed text short and let the variables do the work. Vague or promotional wording is a common reason for rejection, which we cover in why templates get rejected.

Connecting your store to WhatsApp

Whatever platform your store runs on, the idea is the same. When the order status changes, your store system makes a request to a messaging API, and the API delivers the message. With WA Getway, that's a REST API call authenticated with an API key, and sending goes through a paced queue, so a sale day with 300 dispatches doesn't turn into one giant burst.

Keep that API key on your server and never in your website's front-end code. Our note on keeping API keys safe explains why, and if your store's developer is new to this, the guide to your first message through a REST API is a good starting point.

You should also be able to see what happened to each message. Delivered and read marks mean different things, and our post on message statuses explains what you can and can't conclude from them. If a customer says they never got the update, the delivery record is the first thing to look at.

Where this goes wrong

• Sending updates to a number the customer typed incorrectly. Validate the number at checkout.
• Messaging customers who haven't agreed to WhatsApp updates. Ask at checkout, and record it.
• Sending the same update twice because your system retried. Make your integration safe to retry.
• Ignoring replies. People will answer 'delivered' with 'I never got it', and someone has to read that.
• Forgetting to test. Use staff numbers first, as in our guide to testing without spamming customers.

If your store runs on a custom or unusual platform and you'd like the status changes wired to WhatsApp properly, that's what our services team does. Begin with two updates, dispatched and out for delivery, and watch how the support calls change.