The email automations every small shop should consider

• Browse abandonment. Catches interest before the basket exists. Lower intent than a cart, higher volume.
• Winback. Lapsed buyers already know and trust you. Segment by what they bought and how long ago.
• Back in stock. The highest-intent email you can send, because the person asked to be told.

Beyond those, replenishment matters if your product runs out on a predictable cycle, and birthday emails are cheap and warm and very easy to overdo. The full set of ten is on the flows hub.

The reason automated emails sound automated is that most of them were never written. They were assembled out of a platform template and a merge tag, and it shows.

A flow email should read as though you wrote it that morning, because from the recipient’s point of view you did. Same voice as your campaigns, same standard of copy, same restraint. The only difference is that you wrote it once.

Timing carries as much of the effect as words. Right message, wrong hour, is a worse email.

• No testing. Wrong branch, wrong email, wrong customer. Always a testing failure, never bad luck.
• No exit rules. Continuing to sell to someone who has already bought is the most common flow error there is.
• Too many flows. Someone abandons a basket, browses two products and hits a birthday in the same week, and receives five emails from you in two days.
• Set and forget. Flows drift as products, prices and stock change. They need checking against the numbers monthly.

That last one is why reporting and automation belong together.

Less than most shops expect. The content mostly exists already, in your product pages, your FAQs and the answers you type into messages every week. The work is deciding the order, writing it properly, branching the logic and testing it before it goes anywhere near a customer.

Every platform on the platforms list can run these. If your current tool genuinely caps what a flow needs to do, I will say so rather than sell you a migration.

Which automation should I build first?

Welcome or abandoned basket. Which one depends on whether you get more signups or more traffic that leaves without buying.

How many flows does a small shop need?

Three to six. Ten is available and rarely necessary at the start.

Will automation replace my campaigns?

No. Flows handle behaviour, campaigns handle news. A list that only ever hears from automation forgets there is a person behind it.

How long does a flow take to build?

A welcome flow is normally days rather than weeks, including copy and testing. The automation service page covers the process.

Do flows need maintaining?

Yes. Products, prices and stock change, and a flow that references something you no longer sell is worse than no flow at all.