How a post-purchase flow works
The trigger is an order. Depending on the platform it can fire when payment is taken, when the order is marked fulfilled, or when the courier reports delivery — and which one you choose decides whether the whole sequence lands sensibly or arrives out of step with the parcel.
What follows is a short run of messages with different jobs. An early one confirms what happens next and how to reach a human. A middle one helps the customer get value from what they bought: how to set it up, how to care for it, what people commonly get wrong. A later one asks for a review, and a later one still suggests a sensible companion purchase or a refill.
None of these are receipts. Order confirmations, dispatch notices and tracking updates are transactional emails, sent because the customer needs them and delivered even to people who never joined a marketing list. The post-purchase flow sits alongside them and must not duplicate them.
Why it matters
Selling again to somebody who has already bought is cheaper than finding a new buyer, and this is the sequence that decides whether there is a second order at all. A customer who is helped through the first few weeks remembers the shop; one who hears nothing until the next sale announcement does not.
It also lowers costs elsewhere. Most support questions after an order are the same handful, and answering them before they are asked reduces both the messages your team handles and the returns that come from a product being used wrongly. The review request in the sequence is usually the cheapest source of genuine reviews a small business has, which feeds straight back into how the shop looks to the next buyer.
Where it goes wrong
Selling too early is the common one. An upsell that arrives before the parcel does reads as greed, and a review request sent while the customer is still waiting invites a bad one about delivery rather than the product.
Timing is where this bites hardest. Delivery inside the Kathmandu valley, delivery to a district town and delivery abroad can take very different lengths of time, and a flow with a fixed wait built for the fastest case will reach the slowest customers at the wrong moment entirely. The other frequent fault is one sequence for every product: refill advice for a consumable makes no sense to somebody who bought a one-off item.
How to get it right
Base the timing on delivery rather than on payment, and where the courier data is available, trigger the later steps from the delivery event itself. Where it is not, set the waits around the slowest realistic case rather than the fastest.
Split the sequence where the message genuinely differs — first-time buyer against returning customer, consumable against durable — and keep the number of paths small enough that you can read every one. Then judge the flow on repeat purchase rate and review volume rather than on the opens of any single message.
