Post-Purchase Email Flow for Online Stores: Write It With AI

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Post-Purchase Email Flow for Online Stores: Write It With AI.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Post-Purchase Email Flow for Online Stores: Write It With AI.

A post-purchase flow for an online store should include five emails: an order confirmation straight after payment, a shipping notice when the parcel leaves, a delivery check-in a couple of days after arrival, a review request once the product has been used, and a reorder or related-product nudge. AI drafts each one from a brief you supply.

The most common mistake is treating the five as one campaign. They are two kinds of message. The first three are transactional or service messages: they exist because the customer bought something and needs information about it. The delivery check-in sits closest to the line, so it stays free of any sales content. The last two are marketing: they ask for something or sell something. They follow different rules, belong in different places in your tools and carry different tones, so the flow below keeps them apart.

Follow me on Instagram@sagnikteaches

Transactional first, marketing second

Order confirmation, shipping notice and delivery details are sent because of a purchase. Most store platforms have built-in notifications for them, and many email platforms can also send them. Keep these simple, fast and reliable, with the order facts at the top, and avoid stuffing them with promotions. A confirmation that is mostly an advertisement hides the one thing the customer wanted to see, and sending promotional content inside a transactional message can change how it is treated under marketing rules and by mailbox providers. Check what applies to the customers you sell to, and ask a qualified adviser if you are unsure.

Connect on LinkedInSagnik Bhattacharya

The review request and the reorder nudge are marketing. They should go only to customers whose consent covers marketing email in the way the rules where they live require, include a working unsubscribe link, and be sent from your email platform rather than the store's order notification system. Make sure a customer who unsubscribes from marketing still gets their order emails, and the other way round: a person who has not opted into marketing still gets the transactional messages.

Subscribe on YouTube@sagnikteaches

This split also helps in practice. When a delivery problem occurs you need your transactional emails to be plain and dependable, and when you test a new subject line you want to do it on the marketing side only. Keep two sets of templates and two owners if you have a team.

The Complete Excel Course with AI Integration thumbnail

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Timing for each email

EmailTypeTriggerTimingJob of the email
1. Order confirmationTransactionalPayment receivedImmediatelyProve the order, show what happens next
2. Shipping noticeTransactionalLabel scanned or order marked shippedSame day as dispatchGive tracking and a realistic delivery window
3. Delivery check-inTransactional or serviceDelivery confirmed1 to 3 days after deliveryCatch problems before a bad review
4. Review requestMarketingDelivery plus a use periodProduct-dependent, often 7 to 14 daysAsk for honest feedback
5. Reorder nudgeMarketingExpected use-up dateAt roughly 75 to 80 per cent of the expected use timeOffer an easy repeat purchase

The timings are starting points drawn from how products are used, not rules. A candle lasts weeks and a notebook lasts months. Work out how long your product takes to use, and set the review and reorder emails from that, not from the calendar. If your platform triggers only on order date, add the delay yourself, and if it can trigger on delivery, use that, because carriers vary by days.

Timing the flow for a 60-day refill product

The store and its figures here are invented. It sells refill packs of a multi-surface cleaner, 500 ml each, and an average household uses one in about 60 days. The product ships within a day, delivery takes two to four days, and the store has 1,200 customers on its marketing list.

The timing works out as follows. Delivery check-in on day 2 after delivery. Review request around day 14 after delivery, after two weeks of use. Reorder nudge at about 80 per cent of 60 days, so day 48 after delivery, which gives the customer time to reorder before running out. If the flow triggers from the order date and delivery takes 3 days, the reorder email would be set to 51 days after the order.

The store gives the AI this brief for the whole flow.

I run a small online store selling refill packs of a multi-surface cleaner.
Write a five-email post-purchase flow. Facts:
- Brand voice: friendly, plain, no exclamation marks, no hype.
- Order ships within 1 working day; delivery usually 2-4 working days; tracking link
  is [tracking link].
- Returns: unopened packs can be returned within 30 days; contact [support link].
- One pack lasts about 60 days for an average household.
- Reorder offer: free delivery on a repeat order, not a discount.
For each email give: purpose, trigger and timing, subject line (under 45 characters),
preview text (under 90 characters), and body (under 120 words).
Emails 1-3 are transactional: no promotions. Emails 4-5 are marketing: include an
unsubscribe line placeholder. Mark every claim I have not provided as [CHECK].

The model returns a draft. An illustrative version of email 3, the delivery check-in, shows what comes back and what you fix.

Subject: Did your refill arrive safely?
Preview: A quick check, and a way to reach us if anything is wrong.

Hi [first name],

Your order [order number] was delivered on [date]. Everything should be sealed and
ready to use. If a pack arrived damaged or something is missing, reply to this
email and we will put it right.

Unopened packs can be returned within 30 days: [returns link].

Thanks again,
[your name]

Two things needed attention. The draft said "we will put it right", a promise that has to match what your returns policy and your staff time can do, so the owner changed it to "we will help". And "delivered on [date]" depends on the platform sending a delivery event, so the owner checked that the tool had one before keeping the sentence. Note that this email has no sales content at all. The aim is to catch a problem privately.

Writing each email: facts, tone and a template per message

Email 1: order confirmation

This is the most opened email you send, and the best place for clarity. The order summary, delivery address, expected dispatch and delivery window, and a way to get help belong at the top. Add a line on how to change an address and by when. Give the AI a rule: the first three lines must be what was ordered, where it is going and what happens next. If you use a platform's default confirmation, ask the AI to rewrite its wording only, not to change the fields it fills in.

Email 2: shipping notice

Say it has left, who is carrying it, the tracking link and a realistic window. Promise nothing you do not control. A phrase such as "usually arrives in 2 to 4 working days" is better than "arrives Thursday". If the parcel might need a signature or could be left in a safe place, say it here, because that is where customers look when they cannot find the parcel.

Email 3: delivery check-in

This is the email that most stores omit and most customers appreciate. It is short, personal in tone and aimed at problems. The goal is to hear about trouble by reply, not by a one-star review. Make sure a reply goes to a real inbox with someone watching it. The chatbot conversations tutorial shows how order-status questions can be answered automatically if the replies start to pile up.

Email 4: review request

Ask once, make it easy and be honest about what you want. A link straight to the review form beats a link to your home page. Do not offer a reward in exchange for a review, and do not send the request only to customers you think are happy. Google's review policy, for one, bars businesses from offering incentives for reviews and from selectively soliciting positive reviews, and other review platforms have their own rules. Wording such as "tell us how it went, good or bad" is fair. For platform-specific review links and automation see the automated review requests tutorial.

Subject: How is the refill working out?
Preview: Two minutes, and it helps other households decide.

Hi [first name],

You have had your [product] for about two weeks now. If you have a minute, would you
tell us how it is going? Honest feedback, good or bad, helps us and the people deciding
what to buy.

[Leave a review]

If something is not right, reply to this email and we will help.
[your name]
[unsubscribe line]

Email 5: reorder nudge

This one earns its keep. Remind the customer what they bought, say that they may be running low, and make repeat purchase one click. Keep the offer modest and tied to the product. An easy reorder with free delivery costs you less than a discount and still helps the customer. If the customer has already reordered, the flow should stop. Set an exit condition on any new order, or you will send a reorder nudge to someone who has just reordered, which looks careless. In Klaviyo this is a flow filter; its help centre suggests "Fulfilled Order zero times since starting this flow" for the same job on cross-sell flows.

Five more examples of the same flow in different shops

A shop selling one-off gifts

There is no reorder cycle, so replace email 5 with a related-product email at about three weeks, such as a matching accessory, and add a "gift recipient" question to the check-in. Keep it light, with a single product suggestion.

A shop selling items that need assembly or setup

Move a how-to email in between the shipping notice and the delivery check-in. Put the first-use steps and a short video link there, and make the check-in ask whether setup went smoothly. A setup email cuts returns more than any discount does.

A shop with long delivery times

Add a mid-transit update if the delay is longer than a week, so the customer is not left guessing. Ask the AI to write two versions: on schedule and delayed, with the delay email giving a plain apology and a new window. The delayed version needs your approval before it sends.

A shop with high-value orders

Switch the delivery check-in to a human note from the owner, written by AI from a template but sent individually or reviewed. For orders over a value you choose, personal contact is worth the minutes.

A shop with a subscription

Replace the reorder nudge with an "upcoming shipment" notice a few days before each renewal, linking to skip, pause and cancel. It is a transactional message, and making cancelling easy is both fair and, in many places, required, so check the rules that apply to you.

A before and after for the confirmation email

Before, as many default templates read: "Thank you for your order! We are processing your order and will notify you when it ships. Check out our bestsellers below!" followed by six product tiles and, far down, the order lines.

After, edited from an AI draft: "Thanks, [first name]. Order [order number] is confirmed: 2 x refill pack, shipping to [address]. We pack within 1 working day and you will get a tracking email when it leaves. To change the address, reply within 2 hours of ordering. Order details are below." The second version answers the three questions a customer has in the first minute, which are whether the order went through, where it is going and what happens next, and it keeps promotion out of a message the customer will refer back to.

The other two emails in full, and a quick sum

The delivery check-in and review request are shown above. Here are the shipping notice and the reorder nudge from the same brief, as the owner would edit them.

Subject: Your refill is on its way
Preview: Tracking inside, usually 2-4 working days.

Hi [first name],

Order [order number] left us today with [carrier]. You can follow it here: [tracking link].
It usually arrives in 2-4 working days. If nobody is home, the carrier's card will
say where it has been left.

Questions about the order? Reply to this email.
[your name]
Subject: Running low on refill? 
Preview: Reorder in one click, delivery is free.

Hi [first name],

A pack like yours usually lasts around two months, so you may be getting near the
bottom. If you would like another, this link adds the same pack to your basket
with free delivery: [reorder link].

No pressure. If you have switched to something else, we would like to hear why.
[your name]
[unsubscribe line]

The last line of the nudge is deliberate. A reply from a customer who stopped buying is more useful than a click from one who did not. Read those replies for a month and you will learn why people leave.

Now the sum that tells you whether email 5 is worth the effort. Say 1,200 customers on the list, and about 100 new buyers a month reaching day 48. If 8 of those 100 reorder because of the email, each pack is $14 and costs you $6 to make and send, the gain is 8 x ($14 - $6) = $64 a month before the email platform's cost. That is small, but it repeats every month, it costs nothing in discounts, and the same email also gives you the replies from the other 92. These figures are invented; use yours, and if the sum is below the cost of the tool, remove the email.

Subject line variants for a small test

For the review request, ask the model for three subject lines that differ in approach, not just wording: a question ("How is the refill working out?"), a plain statement ("Your two-week check-in"), and a benefit to others ("Help someone choose a refill"). Run the two you prefer against each other for the next batch of customers. Keep each under 45 characters so it is not cut off on a phone, and avoid capital letters and exclamation marks that make a message look like junk mail.

Copy tests that a small list can actually run

With a few hundred or a few thousand customers, you cannot run elaborate experiments. You can learn one thing at a time. The method below works on the marketing emails only.

  1. Pick one email and one element: subject line, first line or call-to-action wording.
  2. Ask the AI for three variants that differ only in that element, and choose two.
  3. Split new customers evenly between versions for two to four weeks, long enough that each version reaches a few hundred people if you can.
  4. Judge by what the email is for: review links clicked for the review email, reorders for the reorder email. Do not judge by opens alone, since some mail apps load images automatically and inflate them.
  5. Keep the winner as the new default and test the next element. Write down the result and the date.

Be honest about what a small test shows. A gap of a few points on a few hundred sends can be luck. If the two versions are close, keep the one that matches your voice. Test only marketing emails. A confirmation or shipping notice is not a place for experiments, since a confusing subject line may mean a customer misses information they need.

Setting it up in the tool you have

Most email platforms for stores offer a flow builder that starts from a trigger, such as "placed order" or "fulfilled order", and lets you add delays and conditions. Klaviyo's help centre, for example, says a cross-sell flow should trigger on either Placed Order or Fulfilled Order, and its built-in review and cross-sell flow goes out 14 days after an order is fulfilled, which is close to the review timing above. Omnisend lists order confirmation, shipping confirmation and cross-sell among its automations, and a store on a platform's own email tool may find similar features with less choice. Free allowances matter at this size. As of November 2026, Klaviyo's free plan covers up to 250 active profiles and 500 email sends a month, and its pricing FAQ says the free plan lets you build automations; Mailchimp's free plan covers 250 contacts and 500 sends a month but does not include marketing automation flows, so this flow needs one of its paid plans there. Paid prices scale with list size, so read the price for your own list on the vendor's pricing page. The comparison of Klaviyo alternatives helps if you are choosing.

Whatever the tool, build in this order. Create the flow with its trigger, add the delay, paste the copy, add the exit condition, then send a test to yourself and open it on a phone. Check every link, merge field and image. Place a real test order if you can, and follow it through the whole flow in a few days, since a sequence can look right in the builder and misfire in life.

The ways these flows go wrong

  • Merge fields showing as brackets. A missing first name becomes "Hi ," or "Hi [first name]". Set a fallback such as "Hi there".
  • Review requests going to people with open complaints. Add an exit condition for customers who have an open support ticket or a refund.
  • Reorder emails after a reorder. Stop the flow when a new order arrives.
  • Delivery claims that do not match the carrier. Link to tracking and keep the wording soft.
  • Marketing sent to people who did not agree to it. Check consent fields and make sure your tool respects them.

Checking the flow a month later

After four weeks, count what happened rather than what felt right. How many replies did the delivery check-in produce, and how many were problems you would otherwise have missed? How many reviews arrived, and did the star average move? What share of customers reordered after the nudge compared with those who were sent no nudge in the past? Compare against your own earlier figures, not against industry numbers.

Look at unsubscribe and complaint rates for the marketing emails too. If either rises after you add an email, shorten the flow or move the timing. Ask the AI to read a spreadsheet export of the flow's results and suggest which email to change first, then decide for yourself. The win-back tutorial picks up where this flow ends, with customers who stop buying, and the abandoned cart tutorial covers the flow that comes before the first purchase.

Finally, keep a one-page document that lists each email, its trigger, its timing, its owner and the date you last reviewed it. Once or twice a year, read the whole flow as a customer would. Policies change, products change, and an email that mentions a 30-day return window after you moved to 14 days is a small mistake that quietly costs money.

Questions about post-purchase email flows

How many emails should a post-purchase flow have?

Five is a sound start: order confirmation, shipping notice, delivery check-in, review request and a reorder or related-product nudge. Add a sixth, such as a how-to-use email, only where the product needs it. More emails without a clear purpose train customers to ignore you.

Can I put offers in the order confirmation?

Keep the confirmation and shipping emails focused on the order. A small, clearly separate suggestion is common, but promotions can change how the message is treated under marketing rules and by mailbox providers. Check the rules that apply to your customers, and keep the order details first and complete.

When should the review request go out?

After the customer has had time to use the product, not on the day of delivery. For a mug that may be a week. For a refill that lasts two months, ask after the first use. Tie the timing to how the product is used and adjust once you see when reviews arrive.

How do I test copy on a small list?

Change one thing at a time, such as the subject line, and run it for two to four weeks until a few hundred people have received each version. Treat the result as a hint rather than proof, and be cautious with open rates, because some mail apps load images automatically.

Should AI write the final emails without review?

No. Let it draft, then check facts, links, promises and tone yourself, and send test emails to yourself on a phone. Anything about delivery dates, returns, refunds or product claims must match your actual policies before it goes live.

Further reads

Sources: Klaviyo pricing page and Klaviyo help article on upsell and cross-sell flows, Mailchimp marketing pricing page, Omnisend automation page and Google's Maps user-contributed content policy, checked November 2026. Rules on marketing consent differ by market; check those that apply to your customers.

Want your post-purchase emails running without the rework?

On a 1:1 call we'll look at the emails you send today, decide which of the five belong in your flow, and set up the drafting and testing routine in the tool you already use.

Book a 1:1 call with me