Order-status notifications pay for the app

By Abdalla Kamesh · Published September 21, 2026 · 4 min read

Every store owner knows the message. Some version of “hi, any update on my order?” — arriving by email, chat, Instagram DM and WhatsApp, usually about an order that is moving along perfectly normally.

That message exists for one reason: nothing told the customer. The information was in your system the whole time. It just never reached them.

Why the notification works where email does not

You already send order emails. WooCommerce sends them by default. So why does the question keep coming?

Email arrives where people are not looking. Order confirmations land in Promotions tabs, get filtered, or sit unread for a day. A push notification arrives on a lock screen within seconds.

Email requires effort to act on. Find the email, open it, find the tracking link, follow it to a carrier site, decode the carrier’s language.

Email does not survive. Nobody can find last week’s shipping email. An app’s order history is always two taps away, permanently.

The comparison is not “notification versus nothing,” it is “notification versus an email the customer cannot find.”

Which statuses to notify on — and which to skip

WooCommerce has more statuses than a customer needs to hear about. Notifying on all of them is how a useful channel becomes noise.

Notify:

Shipped / completed — the one people are waiting for. Include the tracking number itself, not a promise of one.
Out for delivery, if your carrier data supports it. High value: it changes what someone does with their afternoon.
Delivered — closes the loop, and it is the correct moment to think about a review prompt later.
Refunded — silence after a refund request generates anxiety and a second message.
Cancelled — especially if you cancelled it. Never let a customer discover this on their own.
Failed payment — a recoverable order, and the customer usually does not know.

Do not notify:

Processing. Means nothing to a customer, and fires immediately after the order confirmation they just saw.
On hold, usually. Internal state. If it will delay them, send a human message explaining why, not a status code.
Pending payment, for offline methods where the customer already knows.
Any custom internal status your fulfilment plugin sets.

The test: would this change what the customer does or feels? If not, stay quiet.

What a good one contains

Title: the event. “Out for delivery.” Not your store name — the OS already shows that.

Body: the specifics. The product and the timing. “Trailhead Jacket — arriving today by 8pm.”

Deep link: that order. The tap should open the order in the app’s history, with the tracking number visible. A notification that opens the home screen has wasted the interruption. More on that in push copy that converts.

How this works with your existing tools

The important architectural detail: these notifications should fire from the order status changing in WooCommerce, not from a separate system you have to maintain.

In StoreToNative, order-status notifications are on every plan and flow through WooCommerce’s own webhooks. That means whatever sets the status — you in wp-admin, a fulfilment plugin, a shipping integration, a 3PL pushing updates via the API — triggers the notification. You do not integrate anything twice, and you do not have to change your fulfilment process.

Keep your emails. Some customers prefer them, and not everyone will have the app. The notification is a faster, better-placed copy of information you are already sending.

What to expect

I am not going to quote you a percentage reduction in tickets, because any number I gave you would be from someone else’s store with a different carrier, category and customer base. What is worth doing is measuring your own:

Before you turn it on, count “where is my order” messages for two weeks — across every channel, including DMs. Note the average time from dispatch to the first such message.

After, count the same thing for two weeks, and split it by whether the customer has the app.

The second cut is the one that matters, because it compares app customers to non-app customers in the same period rather than comparing two different months.

The second-order effects

Fewer tickets is the obvious benefit. Three less obvious ones:

Fewer WISMO-driven refund requests. A meaningful share of “cancel my order” messages are anxiety about a package with no visible progress.

Better review timing. If you know when something was delivered, you can ask for a review two days after — when the customer has actually used the product — rather than the day they ordered. That is the difference between a five-star review and an annoyed one. See the review prompt approach.

A reason the app stays installed. Order tracking is the most-cited functional reason customers keep a store app, which makes it the foundation everything else — campaigns, back-in-stock, reorders — is built on. Uninstalled apps send no marketing.

Set it up this week

Turn on order-status notifications.
Enable only: shipped, out for delivery, delivered, refunded, cancelled, failed payment.
Confirm the tracking number appears in the notification body, not just in the app.
Confirm the tap opens that order.
Place a real order, ship it to yourself, and read every notification as a customer would.
Count your WISMO messages for two weeks and compare.

Step 5 is the one people skip, and it is where you find out that your carrier integration posts “out for delivery” at 4 a.m.

Related reading