Order Updates via WhatsApp: Confirmations, Shipping, Delivery
Answer 'where is my order' before anyone has to ask it.
A customer who just placed an order checks their inbox obsessively for the next two days — and if they don't hear anything, they message you asking "where is my order," which is the single most repeated support ticket in ecommerce.
WhatsApp order updates solve this before the question gets asked: a short, automatic message the moment an order is placed, again when it ships, and again when it's delivered, all sent to a channel customers already check dozens of times a day.
What WhatsApp order updates customers actually want
Not every internal status change deserves a message. Customers care about four moments:
- Order confirmed (with what they bought and the total)
- Order shipped (with carrier and tracking link)
- Out for delivery / arriving today
- Delivered
Skip the internal-only states — "processing," "picking," "packed" — customers don't act on these, and extra pings train people to ignore your messages entirely.
The goal isn't more messages. It's fewer "where is my order" replies, because the answer already arrived before the question did.
Connecting your store
WaSMS listens for events from your store rather than you sending updates by hand. Connect your store's webhook (Shopify, WooCommerce, or a custom cart via API) so an order-created or fulfillment-updated event triggers the matching WhatsApp message automatically.
curl -X POST https://api.wasms.net/v1/webhooks \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"event": "order.shipped",
"target": "whatsapp",
"template": "order_shipped_v1"
}'
Because WaSMS runs on your own WhatsApp number through your own gateway, there's no per-message platform fee to plan around — you're limited only by your own send volume and WhatsApp's normal usage rules.
Templates that reduce "where is my order"
A good shipping update answers the question before it's asked: what shipped, when it's expected, and a live tracking link. A store called Northwind Supply sends something like:
"Hi Amara — your order #5521 (2 items) has shipped via national courier. Expected by Thursday. Track it here: [link]. Reply if anything looks off."
That last line matters. Inviting a reply, rather than sending a dead-end notification, is what turns the message into a channel instead of a broadcast — and it's a big part of why order updates on WhatsApp tend to get read (and acted on) far more than the same update sent by email. You can also attach a photo of the packed order or the product itself directly in the update — see Sending WhatsApp Media for size and format limits.
For stores that also want customers to browse and reorder inside the same chat, pair this with a Product Catalog in WhatsApp.
Post-delivery check-in
The update sequence doesn't have to stop at "delivered." A short check-in a day or two later — "how did the linen dress work out?" — catches sizing or damage issues while they're still easy to fix, and it's a natural place to ask for a review. See AI Follow-Up Automation for how to chain this without writing a new message for every order.
Keep this message optional-feeling: one line, easy to ignore, easy to reply to. A check-in that reads like an ad gets muted.
Reporting
Every update sent, delivered, read, and replied to shows up in your WaSMS dashboard, broken down by template. If your "shipped" message has a low reply rate but your post-delivery check-in has a high one, that tells you customers read updates but only engage when there's something to say back to. Use that to trim templates that aren't earning their place in the sequence, and to see whether questions about a product (from AI for E-commerce Support) tend to come in right after a particular update.