It’s used for products that have a predictable lifespan, and the customer is expected to make another order.
If you sell shaving cream, you can expect at some point a new order for that product again. It varies from customer to customer, but we can give the extension a default value. Let’s imagine the product lasts for six weeks.
How do we know how long the product will last?
If it’s the customer first order, we just can't know based on customer information. But if he made more than two orders, we already know the number of days he takes to make another order, and we calculate the number of days from there.
But for the cases where we don't know the number of days, each product can have an attribute that holds that information. Add a new product attribute called "Number of Days," or anything else. In that product field, add the number of days for the product lifespan. Then go to "Marketing/Email & SMS Marketing/Configuration" and in the "Expected Reorder Time Attribute" option, choose the attribute that holds the number of days.
Continuing with the example, six weeks * 7 days = 42 days.
If the customer makes an order now, it's expected that within 42 days he will need to buy another one.
Let's create the autoresponder.
We choose the product cycle option, and in the "Number of Days" field, we define the number of days before the event to trigger the autoresponder. If the day the customer is expected to make another purchase is in 42 days, we want to send him the first notification ten days before (we insert 10 in the field). Ten days before, we will start executing the chained actions from the autoresponder.
Note: We only use data from orders with status "complete."