When Engage has received a stock level update, these conditions have to be met to trigger a Back in Stock automation per subscription:

When Engage has received a Back in Stock subscription, i.e. a request from the contact, this will trigger a Back in Stock Subscription Created automation.

Locale – If you only want to trigger SKUs with a certain locale. Locale can also be used as a condition in a value split, see further down for more details.

Quantity – Find a threshold that makes sense for your business. Set the quantity to more than 1 to not trigger an automation when the SKU is restocked with for example a single return.

SKU – If you only want to trigger the automation for certain SKUs

Subscribed on – If you only want to trigger the automations for subscriptions that are more recent (e.g., last 30 days) or the opposite, start with the oldest subscription since they were first in line.

ExternalId – An optional ID that can provide information such as warehouse location or a unique ID for a SKU and warehouse combination.

Product data – Filter the trigger based on any data from the product feed, such as price, URL, category and spare fields

Suppose there are other ways to purchase the product that isn’t covered in your stock update, like a physical store with a separate warehouse. Then you can tick the box The contact has not purchased the product last 5 days which will block any contacts that have a receipt containing the SKU from the last 5 days.

The trigger can be filtered based on any contact attributes. Read more about the filtering tool here.

The Back in Stock automations support value splits on locale.

You can add an email to the automation. The event that triggered the automation could be utilized in an email sent out to the subscribers. To get started, order a back in stock email module from your Voyado contact.

The standard module will dynamically present the following for each SKU that is back in stock and therefore included in the trigger:

Once the automation has started (passed all trigger conditions) the subscription will be deleted no matter if the automation includes communication to the subscriber or not.