Customer Retention Automation: Start With the Delivery Date
What to automate first for retention: the flows tied to dates your store records, like the order and the delivery. Predicted dates come last, once your own orders show when people reorder.

Michal Hlavacek, founder of WDNN · LinkedIn
10 years building retention systems for US ecommerce brands.
Customer retention automation means emails that fire on what a customer did, with no one pressing send. Automate the flows tied to dates your store records first: the order and the delivery. Leave predicted dates until you have reorder data.
Customer retention automation means emails that fire on what a customer did, with no one pressing send. Automate the flows tied to dates your store records first: the order and the delivery. Leave predicted dates until you have reorder data.
Most guides on this topic tell you to start with whatever the writer sells. We sort it a different way: by how sure you are of the date that starts each flow.
What is customer retention automation?
It is a set of flows. A flow is a series of emails that starts when a customer does something, like placing an order. Each flow has a trigger, a job and an exit. Once it is live, it runs without you.
Retention automation starts after the first order. Cart and checkout recovery catch people who have not bought yet. Run them, but they do not bring a buyer back for order 2. Our abandoned cart flow article covers that side.
The question this article answers is the next one. You have a first order. What do you automate first to get the second?
What do the guides say to automate first?
We read the 6 pages that rank for this term. Each one answers differently.
Source What it sells What to automate first Mailchimp Email platform Sync your store, then a thank-you "within 24 hours" Joy Loyalty app "Onboarding, loyalty, and win-back" Manago Customer data platform "At-Risk VIP Reactivation (priority one)" Chatty Support and chat app "Start with one flow, not ten," at your worst friction pointLook at the second column next to the third. The loyalty app puts loyalty near the top. The support app says to start with support if that is your problem. The data platform starts with a flow that needs a prediction.
They also contradict each other. Mailchimp starts with a thank-you email. Manago says a basic "thanks for your order" email "does nothing."
Manago also attaches percentages to its picks. It gives no source for them, so we leave them out.
Our call: automate by how sure the date is
Every flow starts from a date. Some dates are facts. Some are guesses. Build the facts first.
Order Trigger date Flows from the guide Why here 1st A date your store records: the order, the delivery First purchase welcome, delivery follow-up, product education The date cannot be wrong 2nd A fixed number of days after delivery Review request, cross-sell, returns recovery The date is a fact plus a setting you choose 3rd A date you estimate, or a 3rd order Replenishment, win-back, VIP Needs your own reorder data, or repeat buyers to rewardA known date cannot fire at the wrong time. An estimated one can. Say you assume a bottle lasts 30 days, and most people make it last 50. Your replenishment flow then nags people with a full bottle. Your win-back flow treats happy customers as lost.
That is why we disagree with Manago's priority one. At-risk VIP reactivation needs 2 things a young store may not have yet: enough VIPs, and a reliable idea of when each one is late.
What should you build in week 1?
These 3 flows all start from the first order or its delivery. Here are the send times from the guide.
Flow Emails When they send Job First purchase welcome 5 Right away, day 2, on delivery or day 5, day 10, day 14 Turn a first buyer into a fan Delivery follow-up 2 48 hours after delivery, day 5 after delivery Catch problems before they turn into returns Product education 3 On delivery, day 5 after delivery, day 10 after delivery Get the product usedNow look at day 5. All 3 flows can send that day. Pick one email for day 5 and move or drop the others. The guide's rule is simple: if a customer is in one flow, overlapping emails from another wait or get skipped.
If your store does not track delivery, count from the day the order ships. Add your usual shipping time.
Our post-purchase flow article covers the order-to-delivery window in detail. For subscription brands, our subscription retention strategies article shows how these flows carry a subscriber to charge 2.
What comes second?
Flows that start a set number of days after delivery. You pick the number, so the date is still yours to control.
- Review request: 7 to 14 days after delivery. Use 7 for things people use up and 14 for things that last. Our review request email article explains why the start date matters.
- Cross-sell: 14 days after delivery, then day 21 and day 28. One product, not a grid of 8. See our cross-sell flow.
- Returns recovery: starts when a refund or return comes in. It pauses every other flow for that customer. Build it before you have so many flows that a refunded customer gets a sales email.
What should stay manual?
The reply. Automate the question and let a person answer it.
The delivery follow-up asks if the order arrived in good shape. If the customer says no, send it to a person on your support team. Chatty puts it plainly: "Do not send promo messages while a support issue is open." We agree.
Manago gives one more case: for your best customers, "Pick up the phone." We agree with that too. A flow can tell you who your best customers are. It cannot have the conversation.
Keep one more thing manual at first: the predicted date. Set it by hand from your own orders before any app sets it for you.
When do you add the predicted flows?
When your own orders tell you when people reorder. Group first-time buyers by the month they first bought. That group is a cohort. Then check when each cohort places order 2. Our repeat purchase rate article shows the method.
Once you have that date, the 3rd row opens up:
- Replenishment: 5 days before the run-out date, on the day, and 7 days after. Set the date from how many units they bought, not one delay for everyone.
- Win-back: 14 days after the predicted reorder date, then 3 more emails spaced out.
- VIP: right after the 3rd order. Our VIP email flow explains why order 3 beats a top 5% cutoff.
For how all of this fits the rest of your retention work, start at the ecommerce customer retention hub.
Get the whole system
Every flow in this article is in the guide, with every send time written out.
12 flows, 37 emails, one job: repeat purchases. Every trigger, every send delay, every exit condition, written out so you can build them this month.
