Plan Ecommerce Retention Around the Customer Journey
A retention workflow is a planned sequence of messages or tasks that starts from a real customer event. Before building one, write down six things: the trigger, who is eligible, who is excluded, what stops it, who owns it and which outcome you will check. Test consent and suppression cases before launch. Judge the result against a holdout group, not platform-attributed revenue alone.
A flow is only as reliable as the event that starts it.
Before writing a single message, confirm which system records each event, how quickly it arrives and what can make it wrong.
If “order placed” arrives an hour late, a checkout reminder can reach someone who has already bought. If unsubscribes live in one tool and sends go out from another, a suppressed contact can still get messages. Fix the data path first. Then design the journey.
| Event | Usually recorded in | Used to | Watch for |
|---|---|---|---|
| Consent given or withdrawn | Signup forms, checkout, preference centre | Decide who may receive marketing, per channel | Consent not synced to every sending tool |
| Checkout started | Store platform | Start a checkout reminder | Guest checkouts with no known contact |
| Order placed | Store platform or order system | Stop reminders; start post-purchase | Delays between store and CRM |
| Order fulfilled or delivered | Fulfilment or carrier feed | Time the follow-up correctly | Split shipments, missing tracking |
| Refund, cancellation or return | Store platform, support desk | Stop review and cross-sell messages | Refunds processed outside the store |
| Support ticket opened | Help desk | Pause promotional messages | No link between ticket and CRM profile |
| Bounce or spam complaint | Sending platform | Suppress the address | Suppression not shared across tools |
Six common flows, written down before they are built.
Each spec answers the same questions. These are starting templates for discussion. Adjust the timing, audience and owners to your business, and have the permission rules reviewed for your markets.
Welcome
Introduce the store after someone subscribes and set expectations for what they will receive.
- Trigger
- Contact subscribes and permission is confirmed (double opt-in where you use it).
- Audience
- New subscribers with marketing permission for the channel used.
- Exclusions
- Existing customers already on a welcome series; unsubscribed or bounced addresses; test and staff accounts.
- Stop rules
- Unsubscribe; first purchase (switch to post-purchase); hard bounce or complaint.
- Channel and permission
- Email. SMS only if separate SMS permission was given.
- Human owner
- Marketing lead approves content; CRM admin owns the trigger and suppression.
- Outcome to check
- Delivery, unsubscribe rate, first purchase compared with a holdout group.
Checkout reminder
Remind a known contact about a checkout they started but did not complete.
- Trigger
- Checkout started by an identified contact, with no order after a set wait (for example, one hour).
- Audience
- Contacts whose permission covers this message and channel in their market.
- Exclusions
- Anyone who has since ordered; unsubscribed contacts; items now out of stock; contacts with an open support ticket.
- Stop rules
- Order placed (checked immediately before every send); unsubscribe; cart emptied.
- Channel and permission
- Email first. SMS only with explicit SMS permission and within local sending hours.
- Human owner
- Ecommerce manager owns timing and offer rules; CRM admin owns the order-event check.
- Outcome to check
- Completed checkouts against a holdout; complaints and unsubscribes per send.
Post-purchase
Help the customer use what they bought, then ask for feedback once it has arrived.
- Trigger
- Order delivered (not just shipped), with product-specific timing where it helps.
- Audience
- Customers with a delivered order. Usage tips and feedback requests follow your permission rules.
- Exclusions
- Refunded, cancelled or returned orders; open support tickets; customers who already left feedback.
- Stop rules
- Refund or return started; ticket opened; feedback submitted.
- Channel and permission
- Keep order and shipping notices strictly transactional. Promotional content follows marketing permission.
- Human owner
- Customer service lead reviews replies and negative feedback; marketing lead approves content.
- Outcome to check
- Support contacts after delivery, feedback volume, repeat purchase against a holdout.
Replenishment
Prompt a reorder for consumable products, timed from real usage patterns.
- Trigger
- A set number of days after delivery of a consumable item, based on your own reorder data.
- Audience
- Buyers of that item with marketing permission.
- Exclusions
- Customers who reordered already; subscription customers; discontinued items.
- Stop rules
- Reorder placed; unsubscribe; item discontinued or out of stock.
- Channel and permission
- Email, or SMS with SMS permission.
- Human owner
- Merchandising owns timing per product; CRM admin owns the product-to-flow mapping.
- Outcome to check
- Reorder rate and timing against a holdout; unsubscribes.
Win-back
Decide what to do with customers who have gone quiet: message, pause or remove.
- Trigger
- No purchase within a window based on your typical buying cycle.
- Audience
- Past customers with current marketing permission.
- Exclusions
- Recent complaints or refunds; open tickets; contacts who have not engaged in a long period (review for suppression instead).
- Stop rules
- Purchase; unsubscribe; no engagement after the final message (move to suppressed).
- Channel and permission
- Email. Avoid switching channels just to reach someone who stopped engaging.
- Human owner
- Marketing lead decides offer rules; CRM admin applies the suppression outcome.
- Outcome to check
- Reactivated customers against a holdout; unsubscribes; list health.
Service follow-up
Make sure a customer request gets an owner and a response. This is a task flow, not a campaign.
- Trigger
- A customer question, complaint or failed delivery is logged.
- Audience
- Internal team member assigned by request type.
- Exclusions
- Requests already assigned or resolved.
- Stop rules
- Request resolved and customer informed.
- Channel and permission
- Internal task or alert. Customer replies are service messages, not marketing.
- Human owner
- Customer service lead.
- Outcome to check
- Time to first response, overdue requests, reopened requests.
Transactional messages, such as order confirmations and shipping notices, are usually treated differently from marketing. Don’t add promotional content to a transactional message to reach someone who has unsubscribed. Consent rules differ by country, state and channel. This guide is not legal advice.
Change the customer. Watch which messages still send.
A fictional three-step checkout reminder. Every step checks eligibility again immediately before sending, not only when the contact entered the flow.
Twelve cases to run before you activate.
Create a test contact for each case, run it through the flow and record the result. Mark each one as you go. Your selections stay on this page only and are cleared when you leave.
| ID | Scenario | Expected result | Result |
|---|---|---|---|
| T01 | Contact unsubscribed, then starts a checkout | No reminder sent. The skip is logged with the reason. | |
| T02 | Email permission yes, SMS permission no | Email steps send. SMS step is skipped. | |
| T03 | Unsubscribed contact places an order | Order confirmation and shipping notices still send, with no promotional content. | |
| T04 | Contact re-subscribes after unsubscribing | Eligible again from the new consent date only. Earlier history is kept. | |
| T05 | Email address hard-bounces | Address suppressed in every sending tool. No retries. | |
| T06 | Contact marks a message as spam | Suppressed from all marketing email. Complaint recorded on the profile. | |
| T07 | Order refunded before the feedback request | Feedback and cross-sell steps stop. | |
| T08 | Support ticket opened mid-flow | Promotional steps pause until the ticket closes. Owner is notified. | |
| T09 | Customer orders between trigger and first send | Contact exits before the first reminder. | |
| T10 | Same person has two profiles | One message only. Duplicate flagged for merge. | |
| T11 | Customer in a different time zone | SMS arrives within allowed hours in the customer’s local time. | |
| T12 | Contact qualifies for two flows on the same day | Priority rule applies. One message sends; the other waits or is skipped. |
Attributed revenue is not the same as extra revenue.
Sending platforms usually credit a purchase to a message if it happens within a set window after an open or click. Some of those customers would have bought anyway.
To estimate what a flow actually adds, hold back a random share of eligible contacts from receiving it. Compare purchases between the two groups over the same period. The difference is your estimate of incremental effect. Keep the holdout long enough, and large enough, to be meaningful for your volumes.
- Delivery health Bounces, complaints and unsubscribes per send.
- Flow behaviour Entries, exits by stop rule, skipped sends and why.
- Customer outcome Purchases in the flow group compared with the holdout.
- Service load Replies and support contacts the flow creates.
Credits every purchase in the window to the flow.
Only the difference against the holdout.
A launch sequence for each flow.
Launch one flow at a time, so you can tell which change caused what.
- 01Confirm the spec
Trigger, audience, exclusions, stop rules, owner and outcome agreed in writing.
- 02Test the events
Trigger each event with a test contact and confirm it reaches the CRM on time.
- 03Check permissions and suppression sync
Unsubscribes, bounces and complaints reach every tool that sends.
- 04Run the test cases
Record pass or fail for each case. Fix failures before going further.
- 05Approve the content
The named owner signs off copy, offers and links.
- 06Start small, with a holdout
Activate for a limited audience first, and keep a holdout group from day one.
- 07Review on a schedule
Check delivery health, exits and customer replies weekly, then outcomes once the holdout period ends.
CRM retention questions
Including what to measure and what not to assume.
A planned sequence of messages or internal tasks that starts from a customer event, such as a purchase or a period of inactivity. It includes rules for who is eligible, who is excluded and what stops it.
One or two, where your event data is reliable and the customer need is clear. Adding flows before the first ones are tested makes it hard to see what is working and easy to over-message customers.
No. Only to identified contacts whose permission covers that message and channel in their market, and only if they have not ordered in the meantime. Rules vary by location, so have them reviewed.
Transactional messages complete something the customer started, such as an order confirmation or shipping notice. Marketing messages promote products or offers. They are usually governed by different permission rules, so keep them separate.
Compare customers who received it with a random holdout who did not, over the same period. Also watch unsubscribes, complaints and support contacts. Platform-attributed revenue alone overstates the effect.
We can help map the events, write the flow specs, build and test the flows in your CRM and set up reporting, once your platform, data access and consent rules are confirmed during scoping. Consent requirements should be reviewed by your own legal adviser.
Bring one flow. We’ll write the spec with you.
Share your CRM, the events you have and the journey that needs attention. We map the trigger, exclusions, stop rules and owner before anything is built.