A customer waiting for their size to come back in stock doesn't need a long sales pitch. They need to know it's available and have a quick way to buy it.
Push notifications are well suited to moments like this. A short alert can reach a subscribed customer while they're away from your store and take them directly to the product or information they wanted.
For an ecommerce brand, that creates a useful way to continue the relationship between visits. The challenge is choosing messages worth receiving and making the journey after the tap feel effortless. Here's how push works and what a practical program looks like.
What are push notifications?
Push notifications are messages delivered to a device from an app or subscribed website. They can appear on a lock screen, in a notification center or as a banner, depending on the device and the customer's settings.
The customer doesn't need to be actively browsing your store when the notification arrives. Tapping it can open a product, order update, account page or another relevant destination.
A typical notification contains an icon, a short title and a brief message. Some formats also support images and action buttons. The exact presentation varies across operating systems and devices.
Unlike SMS, push uses an app or browser subscription rather than a phone number. Unlike an in-app message, it can reach the customer when they aren't currently using the app.
App push vs web push
Ecommerce brands can send push through a mobile app or through the web. The messages may look similar, but the way you build the audience and bring customers back is different.
| App push | Web push | |
|---|---|---|
| What customers need | Your app installed and notifications enabled | A supported browser or web app with notification permission |
| Where a tap leads | A screen in your app, when configured | A page on your website or web app |
| Useful starting audience | People already using your shopping app | Visitors who want alerts from your store |
| Main setup work | Connect push to the app and relevant customer events | Add web push support and a subscription flow to your store |
App push makes sense as part of an app customers have reasons to keep using, such as convenient reordering, saved preferences or access to relevant products. Notification performance depends on that underlying experience as well as the message.
Web push can give you a notification channel without developing a native app. There are still device requirements to consider. On iPhone and iPad, customers need to add your web app to their Home Screen and grant permission on supported versions starting with iOS and iPadOS 16.4.
That extra step matters when assessing how much of your traffic you can realistically turn into subscribers.
How push notifications reach your customers
Behind a push campaign is a connection between your store or app, a messaging service and the customer's device. Your team usually works through a marketing platform that handles the sending process.
The basic flow is straightforward:
- A customer enables notifications for your app or website.
- The app or browser registers a subscription that can receive messages.
- A campaign or customer event triggers an eligible notification.
- The push service routes it to the device.
- The customer taps through to the destination you've configured.
Delivery and visibility are affected by permissions, connectivity and device settings. A sent notification isn't a guarantee that someone saw it.
Permissions are a real part of the setup on both major mobile platforms. Apple provides authorization controls for alerts, sounds and badges, while newly installed apps on Android 13 and later have notifications off until permission is granted.
Your subscriber count should therefore reflect reachable devices, with invalid subscriptions removed as the program runs.
Useful push notification examples for ecommerce
The strongest reason to send a notification is something relevant happening for the customer. That gives you a more useful starting point than filling a fixed number of campaign slots each week.
These illustrative examples show several roles push can play.
Back-in-stock and saved-product alerts
A customer who asked about a specific product has already told you what they want to hear. The message can be direct:
Your size is back
The linen shirt is available in medium again. Shop your size.
Link to the correct product and variant where possible. If availability changes quickly, make sure the destination shows the current stock position clearly.
Replenishment reminders
A reminder can help customers return to a familiar product near the point when they're likely to need more.
Ready for your next bag?
Reorder your usual house-blend coffee in a few taps.
Timing should reflect the quantity purchased and the customer's previous buying pattern. Someone with a scheduled subscription order or a recent refill may need a different message, or no reminder at all.
Relevant product launches
New products can give existing customers a reason to return, especially when they're connected to something the customer already likes.
A new color in your favorite fit
The everyday tee now comes in forest green. Take a look.
The relevance is doing the work here. A customer who has bought that fit is a more natural audience than every person who has ever installed your app.
Cart reminders
Push can help an eligible customer resume an unfinished order with minimal effort.
Still thinking it over?
Return to the items you were considering and pick up where you left off.
The link should restore the appropriate cart, and the flow should stop when the customer purchases. Avoid suggesting that stock is reserved or a cart will expire unless that is how your store works. A well-designed recovery sequence also makes room to answer the questions that caused hesitation.
Order and account updates
Some of the most useful notifications support a purchase that's already happened. An order ready for collection, a delivery change or a reply to a service question gives the customer information they may be waiting for.
These updates help the app or website remain useful beyond promotions. Keep their purpose clear so customers can distinguish essential order information from an invitation to shop again.
How to build a push program customers want
Choosing the use cases is only part of the work. The permission request, sending rules and shopping journey determine whether those messages become a welcome part of the experience.
Ask when the benefit is clear
A customer who has just requested a restock alert understands why notifications would help. Someone who has only opened your app for the first time may have no reason to agree yet.
Explain what they'll receive before presenting the system prompt. Keep that explanation specific and give them an easy way to continue if they decline. Preferences for product alerts, offers and order updates can make the choice more useful as the audience grows.
Set frequency around relevance
There isn't a universal daily or weekly quota that makes a push program effective. Frequency should reflect how often you have something useful to say to that customer.
A product-drop audience may welcome regular announcements. A customer who only wants a refill reminder has a different expectation. Segmenting by those needs lets the program serve both without imposing the same cadence on everyone.
Coordinate with email and SMS as well. Receiving the same promotion through three channels still feels like repeated contact, even if each channel is within its own sending limit.
Make the destination match the promise
A notification about a specific item should open that item. A collection reminder should lead to the right collection, and an order update should show the relevant order.
Test the journey from a locked phone, with the app closed and with the customer signed out. Make sure authentication or an app update doesn't lose the destination. If the product becomes unavailable, the customer should see a clear explanation and an appropriate next step.
Account for the full cost
Push can have a low additional cost per send, but the program still needs software, integration, content and maintenance. App push also depends on an app worth operating and promoting.
Consider those costs alongside the audience you can reach and the contribution from additional purchases. An active shopping app may already provide much of the foundation; starting from scratch is a different investment decision.
How to measure push notification performance
Start with whether people can receive and act on your messages. Subscription growth, delivery information where available and tap-through rates help you understand the immediate response.
Then follow the customer beyond the tap. Are they finding the product, completing a purchase or getting the order information they needed? Those outcomes are more useful than app opens alone.
For promotional notifications, track orders, contribution after incentives and notification opt-outs. Where you have enough subscribers, compare a randomly selected group receiving the notification with a group held out from that message to estimate the additional effect.
App subscribers may already be among your more engaged customers, so their higher spending alone doesn't establish what push caused. The comparison helps you judge which messages deserve a place in the program.
For a broader view of the customer experience, include push in your plan for coordinating email, SMS and notifications. That makes it easier to see how one message contributes to the whole relationship.
Final thoughts
Push notifications give you a convenient way to reconnect customers with something they care about. A useful alert, delivered at an appropriate moment, can make the next visit or purchase much easier.
The lasting value comes from making that experience dependable. When the messages remain relevant and the destination delivers what they promise, customers have a reason to keep notifications enabled and continue shopping with you.
