How to Automate Shopify Order Follow-Ups With Flows and Tags

October 17, 2026

Build three automated follow-ups: an order confirmation with tracking, a delivery check-in two days after delivery, and a review request seven days later. Tag every customer by product category at purchase so you can segment later. Skip the abandoned cart sequence until the post-purchase messages are working, because repeat buyers are worth more than recovered carts.

Most Shopify stores automate the front of the funnel and ignore the back. That is backwards. Post-purchase messaging reaches people who already trusted you enough to pay, and the marginal cost of sending it is close to zero once the automation exists.

The failure mode is over-sending. Five emails about one order trains customers to ignore everything from your domain, including the delivery notification they actually needed.

What should the three messages actually say?

The confirmation goes out immediately and contains the tracking number only if it exists. Sending a tracking link that resolves to “label created” for two days is worse than sending the number later, because the first experience of tracking your shipment becomes a dead end.

The delivery check-in goes out two days after the carrier marks the order delivered. Ask one question: did it arrive as expected. Not a survey, not a rating scale, one question with a reply that reaches a human. This catches damage and wrong-item issues before they become chargebacks.

The review request goes out seven days after delivery, once the customer has used the product. Requests sent on delivery day collect reviews about shipping speed, not about the product.

How do you set this up in Shopify Flow?

Flow is included on most Shopify plans and runs on triggers. Use Order created for the confirmation, Fulfillment event created with a delivered check for the check-in, and a scheduled delay from the delivery date for the review request. Each flow needs a condition so it does not fire on refunded or cancelled orders.

Add a tag action at the end of the first flow that records the product category on the customer. That tag is the asset. Eighteen months from now it lets you send a launch email to people who bought a specific category, without exporting anything.

Keep each flow small. One trigger, two or three conditions, one action. Flows that try to handle five scenarios become impossible to debug when a customer says they received nothing.

Why tag customers at purchase instead of after?

Because order history gets messy over time. A customer who bought a coat in 2025 and a phone case in 2026 ends up with two unrelated records once you factor in returns, exchanges and bundles. The tag written at the moment of purchase is a clean signal that survives all of it.

Use a consistent naming scheme from day one. cat:outerwear and cat:accessories sort and filter cleanly. Outerwear, outer wear and Jackets will not.

What about abandoned carts?

Do it second. Cart recovery converts at 5 to 10 percent on a good day, while post-purchase messages drive repeat purchases at a much higher rate over twelve months. If you only have time for one automation, do the post-purchase one.

When you do build cart recovery, keep it to two emails: three hours after abandonment and twenty-four hours later. The third and fourth emails mostly generate unsubscribes.

How do you know it is working?

Track reply rate on the delivery check-in and repeat purchase rate at ninety days. Open rates are unreliable now that inbox providers pre-fetch images, and click rates on transactional messages are low by design because the message is informational.

If the delivery check-in gets replies, it is working. If it gets none for a month, the message is either not arriving or not asking a question a human would answer.

Key Takeaways

  • Three post-purchase messages: confirmation, delivery check-in two days after delivery, review request at seven days.
  • Tag customers by product category at purchase; the tag is the asset that makes future segmentation possible.
  • Only send tracking once it resolves, or the first tracking experience becomes a dead end.
  • Build cart recovery second; post-purchase automation drives more revenue over a year.
  • Judge success by reply rate and ninety-day repeat purchase rate, not open rate.
Tags: