---
title: "How to use web push notifications for ecommerce"
author: "Performetic Ekibi"
url: "https://www.performetic.com/en/blog/web-push-notifications-for-ecommerce"
published: "2026-02-17T08:00:00.000Z"
updated: "2026-10-05T02:41:58.431Z"
---

# How to use web push notifications for ecommerce

> Web push notifications let you send short browser messages to visitors who opted in, even when your site is not open. In ecommerce they work best for timely, personal alerts such as back in stock, price drops and order status. Ask for permission when the value is clear, not on arrival; on iPhone only Home Screen web apps support them.

## How should ecommerce stores use web push notifications?

Web push notifications let you send short browser notifications to visitors who opted in, even when your site is not open. In ecommerce they perform best as timely, personal alerts: an item back in stock, a price drop on a saved product, an order status update. The key to success is asking for permission when the visitor sees the benefit, not the moment they land.

For ecommerce brands without a mobile app, web push offers something close to app notifications. It works with a one-click permission, without asking for an email address or phone number. That low friction is both an advantage and a risk: permission is easy to give, and just as easy to revoke after irrelevant notifications.

## What are web push notifications and how do they work?

According to MDN, the Push API lets web applications receive messages pushed from a server whether or not the web app is in the foreground, or even currently loaded. This happens through a service worker running in the background in the browser. As web.dev explains, push is the technology for sending messages from your server to users, and notifications are the technology for displaying that information on the device. In practice they are used together.

The flow has three steps:

1. Your site asks the user for notification permission; web.dev says this should be triggered by a user gesture, such as clicking a button.
2. If granted, the subscription details created by the browser are stored on your server or with your push provider.
3. When you want to notify, your server sends the message and the browser displays it on the device.

Most ecommerce brands use a push notification service that integrates with their store platform rather than building this from scratch.

## Do web push notifications work on iPhone?

Yes, with one condition. According to WebKit's announcement, iOS and iPadOS 16.4 added Web Push support for web apps added to the Home Screen. That means an iPhone user has to add your site to their Home Screen from Safari's Share menu. A Home Screen web app can request notification permission only in response to a direct user interaction, such as tapping a subscribe button. These notifications also work with iOS Focus modes.

If a large share of your mobile traffic comes from iPhones, your web push audience will grow mostly on desktop and Android. Plan the channel accordingly.

## When and how should you ask for permission?

web.dev's permission UX guide says the worst thing you can do is show the permission dialog as soon as users land on your site: they have no context for why they are being asked, and the prompt gets in the way of what they came to do. It also notes that if the user blocks the request, your site cannot ask again; the user has to change the permission in browser settings. Nielsen Norman Group likewise recommends providing value before asking and telling users what the notifications will be about.

Natural moments to ask in ecommerce:

- On an out-of-stock product page: "Want a notification when it is back?"
- When a product is added to a wishlist: "Should we tell you if the price drops?"
- After checkout: "Want shipping updates as notifications?"

The double permission pattern web.dev describes also works well: first show your own short prompt explaining the benefit, and only if the user says yes, trigger the browser's real permission dialog. That way uninterested users never block you at browser level.

## Which web push use cases drive sales?

| Use case | Trigger | Why it works |
|---|---|---|
| Back in stock | A followed product is available again | Purchase intent is already high |
| Price drop | A saved product got cheaper | Personal and timely |
| Order and shipping status | Order shipped, out for delivery | Improves the customer experience |
| Cart reminder | Items left in the cart | Can recover abandoned sales |
| New collection or limited drop | Launch time | Creates fast interest among loyal fans |

web.dev warns that using push for content users do not find timely, relevant and precise will annoy them and reduce engagement. Prioritize behavior-triggered alerts like those above over frequent generic sale announcements. To combine cart reminders with your email flow, see our [cart abandonment guide](/en/blog/reduce-cart-abandonment).

## How is web push different from email and SMS?

- **No identity required:** visitors can stay anonymous, so the opt-in barrier is low.
- **Short-lived:** a notification is seen in the moment or lost; it is not suited to long content.
- **Tied to device and browser:** if a user switches browsers or clears data, the subscription may be lost.
- **User-controlled:** permission can be removed in browser settings at any time.

So think of web push as a complement to email and SMS, not a replacement. Rules for promotional messages differ by country; check with legal counsel how commercial messaging rules apply to web push in your markets.

## How do you write an effective web push notification?

The notification area is small and users give it a few seconds. Each notification should carry one message:

- **Concrete headline:** something like "An item you liked is back in stock" that tells users immediately why they got it.
- **Short body:** a personal detail such as product name, size or color, plus any deadline.
- **Right landing page:** open the relevant product or order page, not the homepage.
- **Image:** product images help in browsers that support them, but the message must work without one.
- **Timing:** send stock and price alerts when the event happens, and campaign pushes when users are typically active.

## How do you measure web push performance?

- **Opt-in rate:** what share of users asked actually accept, and which trigger works best?
- **Click-through rate:** what share of notifications sent are clicked?
- **Unsubscribes and blocks:** users who remove permission after each send.
- **Revenue:** add UTMs to notification links and track web push sessions and sales separately in GA4.

There is no fixed rule for frequency; NN/g advises against sending notifications in bursts and recommends making them easy to turn off. Test each new notification type on a small segment and watch the block rate.

If you want to position web push alongside email, SMS and paid channels in one growth plan, you can request a free growth analysis through our [contact page](/en/contact).

## Key takeaways

- Web push lets you notify opted-in visitors through the browser even when your site is closed.
- Ask for permission at a moment of clear value, such as stock, price or order updates, not on arrival.
- If a user blocks permission, your site cannot ask again; the double permission pattern reduces that risk.
- On iPhone, web push only works for Home Screen web apps and requires a user interaction.
- Prioritize timely, personal, behavior-triggered alerts and track the block rate after every send.

## FAQ

### Do I need a mobile app for web push?

No. Web push runs through the browser and a service worker on your site; no separate app is needed. On iPhone and iPad, however, only web apps the user has added to the Home Screen can receive notifications. Android and desktop browsers do not have that requirement.

### Can I ask again if a user blocks notifications?

No. As web.dev notes, once a user blocks the permission request, your site cannot ask again; the user has to change the setting in the browser. Using a double permission pattern, where your own prompt explains the benefit first, reduces the risk of being blocked.

### How often should I send web push notifications?

There is no fixed rule. Behavior-triggered alerts such as back in stock, price drops and order status are welcomed more often because users asked for them. Keep generic campaign pushes limited, avoid bursts and adjust frequency based on the unsubscribe rate after each send.

### Can web push replace email marketing?

No, it complements it. Web push collects subscribers with a low barrier because no identity is needed, and it is strong for instant messages. But it depends on the device and browser, cannot carry long content and can be lost when users clear browser data. Your email list is an owned, durable and richer channel.

## Sources

- [Push notifications overview (web.dev)](https://web.dev/articles/push-notifications-overview)
- [Permission UX (web.dev)](https://web.dev/articles/push-notifications-permissions-ux)
- [Web Push for Web Apps on iOS and iPadOS (WebKit)](https://webkit.org/blog/13878/web-push-for-web-apps-on-ios-and-ipados/)
- [Push API (MDN Web Docs)](https://developer.mozilla.org/en-US/docs/Web/API/Push_API)
- [Five Mistakes in Designing Mobile Push Notifications (Nielsen Norman Group)](https://www.nngroup.com/articles/push-notification/)