Alerts the customer asked for
Every other flow in a shop is the business deciding to write. These two start with the shopper asking, which is their strength and the source of their obligations. The shopper asked about one product, often one size or colour, and on the terms the request button described. The alert has to keep to those terms: about that item, sent when it can actually be bought, telling the truth about price and stock, and stopping when the question has been answered.
| Alert | The shopper asked | Trigger | What the email must say | Ends when |
|---|---|---|---|---|
| Back in stock | Tell me when this variant can be bought | The variant is purchasable on the site | The product, the variant, the price, a direct link; limited quantity only if true | The shopper buys, the request expires, or the item is discontinued |
| Price drop | Tell me if this gets cheaper | The variant's price falls below the price when the request was made | The new price, the price it is compared with, a direct link; any end date only if real | The shopper buys, the request expires, or the item is discontinued |
The abandoned cart flows tutorial builds the flows a shop sends without being asked, and this tutorial reuses its pattern: identified shoppers, events from the shop, exits checked before every send, a frequency rule across flows and an honest measure. The difference is the request itself, which creates a promise and a record.
Before you start
- A working abandoned cart flow, or at least its plumbing: shop events reaching the email platform, a contact record for each identified shopper, and exits evaluated before each send.
- Stock and price events per variant: when a variant becomes purchasable, when it sells out, and when its price changes, sent to the email platform as they happen rather than in a nightly batch.
- A developer or the shop's settings for the request form on the product page, at variant level.
- A price history per variant, so that a price drop can be checked against prices customers were actually charged.
- A consent position, decided with whoever owns compliance, for the alert and for any marketing choice offered beside it.
- A rule from merchandising on how restocked units are allocated: online first, to the alert queue first, or no priority at all.
The steps
Add the request to the product page
Put the request where the shopper meets the problem: next to the variant selector, shown when the selected size or colour is unavailable, and for price drops beside the price. The product page optimisation guide keeps out-of-stock variants visible and clearly unavailable, with a notify-me option, rather than letting them vanish. Make the request variant-level, because a shopper waiting for one size does not want to hear that another size returned. Word the button and the confirmation to say exactly what will be sent: one email when this size is back, or one email if this price falls. Offer any ongoing marketing as a separate, unticked choice beside it, because a request for one alert is not a newsletter subscription, just as the list building and consent guide warns against treating a download as one.
Record what was requested and on what terms
Store each request as a record, not just a tag on the contact: the product and variant, the date and time, the type of alert, the channel, the wording the shopper saw and, for price drops, the price displayed at the moment of the request. The time matters because it sets the shopper's place in the queue in the fourth step; the price matters because it is what the alert will be compared against in the fifth. Decide with whoever owns compliance whether the alert itself is treated as marketing. The promotional versus transactional comparison describes the UK regulator's direct marketing guidance as deciding by the content and purpose of a message, and treats the unclear case as marketing; the cart tutorial does the same for its reminders. The default here follows them: an unsubscribe in every alert, and a check against the suppression listA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. before each send.
Decide the stock rule
Send the back-in-stock alertA message a shopper asked to receive when an unavailable item, size or colour returns, sent as soon as stock is live and with urgency only where it is true. when the variant can be bought, which is not the same as when goods arrive at the warehouse. Trigger from the event that makes the variant purchasable on the site, and check that the product page, the basket and the stock figure agree before the first email goes, or the alert sends shoppers to a page that still says unavailable. The flows guide is clear that the alert should go as soon as stock is live; delay hands the stock to whoever happens to browse first. Decide what counts as a restock worth announcing, such as more than a single returned unit, and what happens to pre-ordersAn order and payment taken before the stock is ready, with terms that state what the buyer commits to, when dispatch happens and what if the date slips. or back-orders, which are a different promise from stock on the shelf.
Notify in request order when stock is short
When the quantity returning is smaller than the queue, telling everyone at once turns the alert into a race that most recipients lose, and those who lose remember it. As general practice, compare the returning quantity with the number of open requests for that variant. Where the queue is longer, notify the earliest requests first, in a batch no larger than the stock can serve, give that batch a fair chance to buy, and send the next batch only if stock remains. When the stock runs out, close the alert: tell anyone who was notified and could not buy that the variant has gone again, and tell the rest of the queue where they stand and whether their request stays open for the next restock. The batch size and the wait between batches are the shop's own decisions, set from how quickly the first batch buys.
Set the price-drop rule from real prices
A price-drop alert is a price statement, so the rules on price claims apply to it. The pricing and packaging guide records that in the UK the Competition and Markets Authority enforces consumer protection law covering misleading pricing practices, including reference prices that were never genuinely charged, urgency claims that are not true and fees revealed late, and that the Advertising Standards Authority's codes cover price statements, including claims about savings. The guide to planning promotions turns that into working checks: a "was" price must have been a real price, a deadline must be real, and the advertised price must be the price people can pay. Trigger the alert only when the variant's price falls below the price the shopper saw when they asked, and that price was one customers were actually charged. Never raise a price in order to lower it, and have whoever handles compliance review the rule. Nothing here is legal advice.
Write the alert
Keep the alert short and specific to the request: the product name and image, the variant the shopper asked for, the current price and, for a price drop, the price it is compared with and the saving calculated from the two. Link straight to that variant on the product page, selected, so that one tap reaches the add-to-basket button. Say how many are available only if the number is real, and mention an end date only if the price really ends then. Put a line reminding the shopper why they are receiving it, an unsubscribe link and a way to manage their other alerts. If several requested items return on the same day, send one email listing them rather than one email each. Where the shop also offers alerts by text message, send them only to shoppers who chose that channel for it, because the SMS and WhatsApp automation guide treats each channel's consent as separate. If the shop has an app that sends the same alert as a push, the tutorial on writing push notifications applies these habits to a message read in a glance on the lock screen.
Set exits, expiry and frequency limits
Check the exits before each send, as the cart tutorial does. A shopper who has bought the variant since asking, through any channel, receives nothing. A request older than an expiry period the shop sets lapses quietly, because a reminder about a product someone wanted long ago reads as noise; state the period on the request confirmation so the shopper knows. A price-drop request ends once it has been answered, unless the shopper asks for further drops. Put the alerts inside the same per-person cap as the cart and browse flows, and decide the priority between them: an alert the shopper requested usually outranks a browse email about the same product, which should then not send at all.
Handle discontinued items
When an item will not return, the open requests are a promise the shop can no longer keep, so release them once and plainly: the variant is discontinued, the request is closed, and, if the alert is handled as marketing and the shopper's record allows it, the nearest alternative. Then remove the request button from that product page so new requests stop arriving. Keep the email platform and the advertising feed in step: the product lifecycle guide for Shopping and Performance Max explains that discontinued products should leave the feed and that availability must match the landing page, and the same product status should close the alert queue at the same time.
Test with real products
Run the email automation flow launch checklist, then test with real products and test contacts. Request a variant as a guest and as a signed-in customer and check the record. Restock it and confirm the alert sends only once the page shows it purchasable, with the right variant selected behind the link. Create a short restock against a long test queue and confirm the batches go in request order and stop at sell-out, with the closing message. Lower a price and confirm the alert compares it with the price on the request record; raise it and confirm nothing sends. Buy the variant before the alert and confirm the exit. Let a test request reach its expiry, mark a test product discontinued, and check that unsubscribing from alerts never stops order emails.
Measure and review
The flow's main measure is conversion per alert sent: orders of the requested variant, or of anything, within a stated window after the alert, divided by alerts sent, which the conversion rate calculator turns into the rate (CVRShare of visits or clicks that convert.). Read click-through (CTRShare of impressions that result in a click.) and the add-to-cart rateShare of sessions in which a product was added to the cart. from the alert as diagnostics: clicks without baskets usually point to the page, the price or stock that ran out. Read back-in-stock and price-drop alerts separately. Report the requests closed as sold out and the requests per variant to buying and merchandising, because an alert queue is a measure of unmet demand that no other report holds. Review monthly beside the cart flow, and compare the average order valueAverage revenue per order. of alert orders with the shop's usual figure to see whether shoppers add to the item they waited for.
A trainer resale shop's restock alerts (illustrative)
Solecairn Sneakers tells a long queue about a short restock
Solecairn Sneakers, an online trainer resale shop, had 420 open back-in-stock requests for one popular model in a single size when 36 pairs arrived. Instead of emailing all 420, it notified requests in the order they were made, in batches, giving each batch two hours before the next, and closed the alert when the size sold out.
| Batch | Requests notified | Alerts sent | Orders | Pairs left after batch | Requests closed as sold out |
|---|---|---|---|---|---|
| 1 | Earliest 50 | 50 | 19 | 17 | 0 |
| 2 | Next 50 | 50 | 14 | 3 | 0 |
| 3 | Next 30 | 30 | 3 | 0 | 27 |
| Not notified | Remaining queue | 0 | 0 | 0 | 290 |
The 130 alerts produced 36 orders, a conversion of 28% per alert sent. The 27 shoppers in the last batch who did not buy received a sold-out note within the hour, and the 290 still in the queue received one message saying the size had sold out and their request was closed, with one click to rejoin the queue for the next restock; 171 did. The request count went to the buying team, which ordered a larger allocation of that size for the next drop.
When a restocked product still sells less than it did before the gap, the diagnosis page for sales not recovering after a restock checks the alert queue alongside the page, the feed and the ads.
Alerts sent, not site visits, are the base when the conversion rate calculator is set up for email flows, which gives restock alerts and price-drop alerts a rate each.
Common mistakes
- Treating a request as a subscription. One alert about one product is not consent to the newsletter.
- Alerts at product level. A shopper waiting for one size hears about every other size.
- Sending before the stock can be bought. The link opens a page that still says unavailable.
- Telling a long queue about a short restock. Most recipients arrive to find it gone.
- Price drops against prices nobody paid. The reference price must be real, and so must any end date.
- No exit on purchase. The shopper who bought in store receives the alert anyway.
- Requests that never expire. An alert about something wanted long ago reads as noise.
- Leaving discontinued items open. Requests wait for a product that will never return.
The post-purchase flow tutorial takes over once an alert turns into an order, and the automation hub sets out the priorities and governance that keep these flows from colliding with the rest.
