Browser Push for E-commerce: Cart Abandonment, Price Alerts, Back-in-Stock

Browser push is the most direct re-engagement channel in e-commerce: one click on Allow, no newsletter opt-in, no smartphone app required. This guide covers four use cases with real data: winning back cart abandoners, price alerts from wishlists, back-in-stock notifications, and re-engagement pushes. With timing, copy, segmentation, and a worked example that shows why the channel pays for itself from the first month.

Why e-commerce and browser push fit so well together

In an online shop, the next hour decides whether a full basket becomes an order or quietly disappears in a browser tab on another device. That is exactly the time window in which browser push shows its strength. A push notification arrives in seconds, it requires neither a stored email address nor a phone number, and it works on the device the customer is already using.

Behind the notification sits an official browser interface: the Web Push API and a service worker running in the background — even when the shop page has long since been closed. The customer says Yes to the permission once, and from that moment the message lands directly in the operating system, with no detour through an inbox that is already overflowing.

For e-commerce this has four consequences. Push is faster than email. Push is cheaper than SMS. Push reaches visitors who would never have subscribed to a newsletter. And push carries real content today: a product image and a price; one click on the notification takes the customer directly to the destination. The notification looks like a miniature product card, not a text line from the 1990s.

The four push occasions in e-commerce at a glance

Not every push justifies the effort. Four occasions have become standard practice in online shops because they measurably recover or generate revenue.

• Cart abandonment recovery. Someone adds items to their cart and does not check out — they get a gentle reminder, a concrete nudge, and if necessary a discount.
• Price alert. Someone who adds a product to their wishlist is notified as soon as the price drops.
• Back-in-stock. Someone who clicked on an out-of-stock product finds out immediately when it is available again.
• Re-engagement and sale push. Someone who has not been back for a while is targeted with a sale, new arrivals, or loyalty status updates.

Each occasion works with a clear trigger from your shop system and a defined message. That is exactly what makes push predictable. In the campaigns and analytics view you see delivery and dispatch rates per send; click rates are measurable as soon as click-tracking is active (via SendSeven short URLs or your own UTM parameters). Direct revenue attribution per push is not something the analytics module provides — for that you combine click data with the conversion reporting in your own shop.

Use case 1: Cart abandonment recovery

Around seven in ten shopping baskets are abandoned in English-speaking e-commerce before the order is placed. The reasons are rarely dramatic. A colleague calls, a tab is closed, the price is compared with a second shop and forgotten. Push catches exactly that gap.

The sequence consists of two or three well-timed notifications that your shop backend triggers itself via the SendSeven REST API. Control lies with your shop, not with SendSeven: once a basket is left behind, the shop backend calls the REST API after roughly one hour and sends the first push. After 24 hours the shop checks its own order status and sends a second push if the order is still pending — after 72 hours, optionally, a third. The shop starts each push individually via a separate API call, so it controls the timing completely.

A one-hour wait has proven to be the sweet spot. Earlier feels intrusive; later and the impulse has faded. In tests across online shops the click rate of this first reminder runs between 12 and 18 %, and post-click conversion between 8 and 12 %. Email recovery, by comparison, achieves median click rates of around 4–6 %.

The tone shift across the steps is worthwhile. The first push sounds like a friendly nudge: You left your trainers in the basket. Shall we hold them for you? The second makes a concrete offer: We are rounding down to a 5 % discount — valid for 24 hours. The third is more direct and should only go out if the margin supports it.

One rule: keep the discount ladder short. Three pushes per basket is the maximum. Anyone who sends more trains their customers to wait for the next discount and erodes margin permanently.

Use case 2: Price alerts from wishlists

Wishlists are a goldmine that many shops use too timidly. Someone who adds a product to their wishlist has interest — but not yet the impulse to buy. Price alerts turn that interest into a purchase the moment the trigger is right.

The trigger is straightforward. When a product's price drops and that product is on a wishlist, your shop detects it. Its backend cross-references the affected push subscribers and calls the SendSeven REST API to send each of them a personalised notification. In tests click rates for these pushes run between 20 and 30 %. The combination of explicit intent and a concrete price advantage is hard to beat.

The copy lives on the before-and-after contrast. Rather than a cliché, the notification shows both prices side by side: Your trainers just dropped in price: €129 instead of €159. The product image shows the item; one click takes the customer straight to checkout. No waiting time is needed: the sooner the push reaches the customer, the higher the likelihood the click becomes an order.

Shops without wishlist functionality can build a lightweight equivalent using product bookmarks or a simple Watch price button. Both follow the same pattern: the customer presses once, registers an interest, and receives a push as soon as the price changes.

Use case 3: Back-in-stock notifications

Out-of-stock products are not a loss — they are a list. Someone looking for a limited-edition trainer or a scarce clothing size who cannot find it is usually happy to sign up to be notified as soon as stock returns. A small restock notify form on the product detail page captures that intent.

The moment availability returns, the push goes out immediately. Every minute counts here because limited editions can sell out again within hours. The post-click conversion rate for this occasion sits at around 25 %. The reason is obvious: someone who requests a back-in-stock notification has already made the purchase decision and is merely waiting for the opportunity.

The copy stays plain and direct. Back in stock: Air Pulse 5, size 8, in Black. One click leads straight to the product. Shops offering multiple sizes or variants should try to make the push as variant-specific as possible — otherwise customers land on a product page and have to search again.

A practical tip: pair restock pushes with a scarcity note in the content, such as Only 23 pairs remaining. Scarcity works when it is genuine — not when it is manufactured. A push that communicates real scarcity honestly builds trust rather than burning it.

Use case 4: Re-engagement and sale push

The fourth occasion is broader and requires more care. Customers who have not visited the shop in a while can be activated with well-timed pushes — especially around sales, new product drops, or loyalty status changes.

Segmentation is key. A push to all push subscribers is broadcast marketing from decades past and permanently damages the push subscriber list. Meaningful segments follow four axes: last-purchase date (more than 90 days inactive), average order value (address top buyers separately), product-category affinity (sneaker fans get sneaker drops), and wishlist content (anyone who saved shoes gets shoe sales).

The best time windows for re-engagement pushes are Tuesday to Thursday between 5 pm and 7 pm. Weekend sounds like shopping time but is flooded with competitor campaigns. A Tuesday evening push finds a quieter notification centre and gets more attention.

In terms of copy: sale pushes have a clear occasion, a short deadline, and a personalised message. 3 new pieces from your favourite brand. Sale starts today at 6 pm. Pairing the sale push with a product image from the customer's preferred category adds extra attention.

Comparison: push vs SMS vs email for recovery

Each channel has a job. Push is the most immediate, SMS the most reliable, email the most detailed. For e-commerce recovery this creates a clear order.

In practice the order usually looks like this: push as the first touch after one hour, email as the second touch after 24 hours with detailed arguments, SMS as the third touch after 48–72 hours when the basket is large enough to justify the SMS cost. Anyone who wants to dig deeper into the direct comparison of push and email newsletter will find the detailed arguments there.

Timing, copy, and segmentation

Three levers decide whether a push gets clicked or ignored: timing, copy, and segmentation.

Timing. For cart abandonment the first hour is the sweet spot; for price alerts immediately at the change; for restock the moment availability returns; for sale pushes Tuesday to Thursday between 5 and 7 pm. Sending pushes at night costs subscribers when they turn off the browser's notification permission.

Copy. In DTC e-commerce the informal second-person tone is industry standard. Title and body stay short: 65 characters maximum in the title, 240 in the body. Specific content (product name, price, size) beats clichés (Come and take a look). Personalisation in the title lifts click rates measurably.

Segmentation. Four axes carry far: last-purchase date for re-engagement, average order value for top-buyer pushes, product-category affinity for targeted drops, and wishlist content for price alerts. Starting with these four axes covers 80 % of worthwhile push occasions.

Testing pays off once the push list exceeds a few thousand subscribers. Important caveat: browser push in SendSeven has no built-in A/B test module — you split your segment manually into two random halves and send two separate campaigns. Useful tests run along three variables: title personalisation (first name vs generic), discount level (5 % vs 10 %), and image (product hero vs lifestyle photo). Testing without a plan collects only noise.

Worked example and stack integration

Let us run the numbers on a typical online shop. Starting point: 100,000 browser push subscribers, of whom around 20,000 abandon their cart each month. The assumptions sit at the lower end of the ranges cited above to keep the calculation conservative.

• Push sends: 20,000 cart-abandonment pushes per month
• Push 1 click rate: 15 % → 3,000 clicks back into the shop
• Post-click conversion: 10 % → 300 recovered orders
• Average basket value (AOV): €60
• Recovery revenue: €18,000 per month
• Push costs: channel fee from €9 per month plus usage-based send costs for the 20,000 pushes
• Revenue relative to channel costs: a multiple of the push costs

The point of the calculation is not a spectacular headline metric but the ratio: push costs (channel fee + usage-based send) remain low while the recovery revenue scales with the size of your push list. Even a single-digit share of recovered orders covers the push costs many times over. Important: this is a model calculation using assumed click and conversion values — not a guaranteed return. Your real figures depend on your product range, margin, and how well you maintain the list.

Stack integration means push rarely stands alone. In a considered recovery stack, push delivers the first touch, email and WhatsApp handle the follow-ups. This creates multi-channel recovery stacks where each channel does what it does best: push for instant reminders, email for the detailed argument, WhatsApp for the personal close. You trigger push itself via a REST API call or a campaign. The follow-up email and WhatsApp touches can then be orchestrated in the Flow Builder — because those are flow channels.

GDPR, opt-in, and setup with SendSeven

Browser push is more GDPR-friendly than many assume because the browser itself makes consent a mandatory step. Two things remain the shop's responsibility.

First: the double opt-in equivalent. Before the native browser dialog, the shop shows a soft-ask explaining what the push permission will be used for. Skipping the soft-ask loses roughly half your potential push list because many visitors reflexively reject the native dialog. Adding it gains subscribers who genuinely want pushes. The soft-ask should not appear immediately after the page loads — it belongs at a moment where the customer has shown interest: after adding to cart, after a first purchase, or after adding to the wishlist.

Second: the purpose mapping. Cart abandonment, price alerts, and restock fall under the same purpose: service relating to an ongoing order or observation process. Re-engagement and sale pushes are classic marketing. Both purpose categories can technically be covered by the same push permission, but they should be clearly named separately in the privacy policy and ideally be individually toggleable in account settings.

SendSeven provides the infrastructure that makes this practical. The push channel handles sending and subscription management; the REST API accepts event-triggered sends from your shop; broad sale and re-engagement pushes run as scheduled campaigns via Reach. Incoming replies to pushes land cleanly in the unified inbox. The GDPR-compliant foundation is provided by EU hosting with a DPA; the official API interface ensures neither the service worker nor tokens end up in a questionable location. As SendSeven GmbH, headquartered in Augsburg, we operate exclusively via official interfaces.

Technical setup runs in three steps. First, activate the push channel and embed the code snippet in the shop. Second, your shop backend connects to the SendSeven REST API and responds to its own events — add_to_cart, order_placed, wishlist_add, and price_change — with an API call that sends the appropriate push. Third, the broad re-engagement and sale pushes are configured as scheduled campaigns via Reach targeting the relevant segments, tested, and switched live. On a Shopify, WooCommerce, or Magento setup this is live within a day.

Frequently asked questions

How do e-commerce shops use browser push for cart abandonment, price alerts, and back-in-stock?

Browser push is used in e-commerce across four occasions: cart abandonment recovery (click rate 12–18 % in online shops), price alerts from wishlists (click rate 20–30 %), back-in-stock notifications (conversion around 25 %), and re-engagement pushes for sales and new drops. Event-triggered pushes are initiated directly by your shop via a REST API call; broad re-engagement and sale pushes run as scheduled campaigns via Reach to segments. Push carries a product image and price; one click leads directly to the destination.

How quickly should the first push go out after cart abandonment?

After roughly one hour. Earlier feels intrusive; later and the purchase impulse fades. The second push follows after 24 hours; an optional third after 72 hours with a discount. Three pushes per basket is the maximum — otherwise you train customers to wait for the next discount.

What click rates and conversions does push deliver compared with email in e-commerce?

Cart-abandonment pushes achieve click rates of 12–18 % and post-click conversions of 8–12 % in online shops. Price alerts from wishlists run at 20–30 % click rate. Back-in-stock pushes convert at around 25 % post-click. Email recovery, by comparison, sits at 4–6 % click rate.

Do I need a separate push opt-in for each use case?

No. Cart abandonment, price alerts, and restock fall under the same purpose (service relating to ongoing order and observation processes). Re-engagement and sale pushes are classic marketing. Both purpose categories can be covered by the same push permission but should be clearly named separately in the privacy policy and ideally be individually toggleable in account settings.

How is push best combined with email and WhatsApp?

Push is the first touch after one hour, triggered via REST API call from the shop. Email follows as the second touch after 24 hours with detailed arguments; WhatsApp as the third after 48–72 hours for larger baskets. The follow-up email and WhatsApp touches can be orchestrated in the Flow Builder — those are flow channels. That way each channel does what it does best.

Does browser push make sense for small shops with only a few thousand visitors?

Yes. Even with a few thousand push subscribers, cart abandonment in particular generates measurable revenue, because push costs are low: a channel fee plus a small usage-based send cost per push, with no carrier fees like SMS. A clean soft-ask before the browser dialog is important — without it you lose roughly half of your potential subscribers.

What events does my shop system respond to with a push?

Control lies with your shop, not with SendSeven: your shop backend detects the event itself and then calls the SendSeven REST API to send the appropriate push. For the four occasions these are typically add_to_cart for cart abandonment, wishlist_add combined with price_change for price alerts, back_in_stock for restock, and the customer profile (last-purchase date) for re-engagement. Shopify, WooCommerce, and Magento provide these events natively or via standard extensions. An incoming shop event does not start a flow in SendSeven — push sending happens via your shop's API call.

What does browser push cost at SendSeven?

The entry point starts from €9 per channel per month on the pay-as-you-go plan. Incoming replies are always free. You will find the exact terms and further plans on the pricing page.