Skip to main content
This flow automatically notifies customers when a product from one of their personal lists (for example, Favorites, a wishlist, or a “notify me when available” list) returns to stock. It triggers individually for each customer and each product, so the message always feels personal and timely.

​
Before you start

Set up an automated campaign in the channel you plan to use:
  • Email
  • SMS
  • Viber
  • Mobile push
  • Web push
The campaign should pull product details using the ProductListItem parameter, or use the new content constructor that displays product information without manually specifying parameters.
Plan the channel ahead of time. The flow uses a single channel per branch, so if you want to reach customers across multiple channels, plan to add separate branches with subscription checks for each one.

​
How to configure the flow

​
Step 1. Set the trigger event

Start the flow with the event Product in customer’s list changed — Product is back in stock. This event has a few important behaviors:
  • It fires when a product that was previously out of stock becomes available again.
  • It re-fires every time the product cycles between out of stock and back in stock, so customers can be notified on each return to availability.
  • If several products from a customer’s list become available at the same time, the event fires separately for each product.
  • If your catalog uses regional availability zones and the customer has regional data, the event respects regional stock information when deciding whether the product is available for that customer.

​
Step 2. Limit how often the flow runs per customer

Add a frequency limit so the same customer does not receive too many back-in-stock messages in a short period. This protects the customer experience and keeps your sending reputation healthy. A common starting point is to allow no more than one back-in-stock message per customer per day, but tune the limit to match your catalog size and how active your customers’ lists are.

​
Step 3. Restrict sending hours

Add a time window so the flow does not send campaigns during nighttime hours. Match the window to your customers’ time zones — for example, only allow sends between 9:00 AM and 9:00 PM local time.

​
Step 4. Add product validation checks

Insert conditions that confirm the product is actually worth sending a message about. Typical checks include:
  • The product is in stock in the customer’s region.
  • The price meets your minimum threshold (for example, above $10).
  • The product is not excluded from marketing communications (no “do not promote” flag).
  • The product belongs to a category you actively promote.
Adjust the checks to match your merchandising rules.

​
Step 5. Check the customer’s subscription and contact details

Before sending, confirm that the customer:
  • Has an active subscription for the channel you are using.
  • Has valid contact information for that channel (a deliverable email address, a valid phone number, an active push token, and so on).
This step prevents wasted sends and keeps engagement metrics clean.

​
Step 6. Send the campaign and clean up the list

Send the prepared campaign to the customer. After the send, optionally remove the product from the customer’s list (for example, from a “notify me when available” list) so the customer is not notified again about the same item.
If the list is Favorites or a wishlist that the customer maintains themselves, do not remove the product — let the customer manage the list manually. Only auto-clean lists that are specifically meant for one-time back-in-stock alerts.

​
Step 7. Add a final frequency cap

End the flow with one more frequency limit to prevent multiple back-in-stock campaigns from being sent to the same customer at nearly the same moment (for example, when several products in the customer’s list become available within seconds of each other).

​
Make the message work harder

You can enrich the campaign with recommendations so a single back-in-stock message also drives discovery of related products:
  • Related products for the same item. Use the parameter ProductListItem.Product.Recommendations.{algorithm name} to show products related to the one that came back in stock.
  • Personalized recommendations for the customer. Use Recipient.Recommendations.{algorithm name} to show products tailored to the individual customer.
Replace {algorithm name} with the name of the recommendation algorithm you have set up.

​
Test and optimize

Run an A/B test on the campaign to find the variant that drives the most engagement and revenue. Common things to test:
  • Subject line and preview text
  • Hero image versus product grid
  • Single product focus versus product plus recommendations
  • Call-to-action wording
  • Send time inside your allowed window
Once you have a winner, promote it to the default and keep iterating.