The Klaviyo post-purchase flow: one order in, three paths out
One thank-you goes to every order. But a first-time buyer, a repeat consumable buyer, and a high-value regular just did three different things, and a single thank-you treats them all the same.
One flow cannot speak to three buyers
Send one sequence to every order and each buyer gets the wrong email.
Three questions the order already answers.
First order or repeat?
The order count on the profile answers this. One order means the branch must teach: onboarding, confidence, the path to a second purchase. More than one order means continuation, because a pattern already exists. This is the first conditional split, and it decides everything downstream.
What did they buy?
The items on the order answer this. Category decides what the follow-up teaches: the care routine, the setup, the first-use trick. Category also decides what pairs with the order next. A flow that reads the order can point at the product in the box. A flow that does not can only point at the store.
What are they worth?
The rfm_recency, rfm_frequency, and rfm_monetary properties answer this, once the list is scored. Value tier decides how much of the branch is automation and how much is human warmth. A first-timer can run on templates. A high-value regular deserves a sentence a person wrote. The RFM teardown, linked below, teaches the scoring.
The branches: three buyers, three flows.
First-time buyers
One order is a trial. This branch earns the second order. It sends a check-in after delivery to make sure the first order worked. It sends a how-to that makes the product better. Then it nudges toward the product that pairs with the first. The order count split routes buyers here automatically. The full cadence, send by send, is laid out on its own page.
the second-purchase playRepeat buyers of consumables
A second order of the same consumable is a schedule announcing itself. This branch stops pitching and starts timing. The follow-up becomes a refill reminder, set to the gap between their orders instead of a calendar the account picked. It teaches nothing and pushes no cross-sell. The right product simply lands in the inbox before the last one runs out. How to build that timing has its own page.
the replenishment flowHigh-value regulars
This branch has one hard rule: no coupon, ever. A customer who keeps ordering at full price needs no bribe. A discount only teaches them their loyalty was overpriced. This branch gives access instead: the early look, the first-to-know note, the thank-you a person clearly wrote. The rfm properties route buyers here. Why the branch is guarded this carefully is spelled out on its own page.
protecting your ChampionsNothing sells before the product works
Every branch obeys the same clock. The confirmation and the shipping notice build confidence, and they carry no ask. The check-in after delivery makes sure the purchase actually worked, and it carries no ask either. Only after the product has arrived and done its job does any branch earn the right to suggest what comes next. No branch skips ahead.
The branch decides what to say next. The rule decides when anyone gets to say it.
Two numbers, read against the old flow.
Repeat rate by branch
This is the share of customers in each branch who come back for another order. Read each branch against the single flow it replaced, not against the other branches. First-timers and high-value regulars will never repeat at the same rate, so comparing them tells you nothing. Ask whether each branch beats the sentence it replaced.
Next-order value by branch
This is what the next order is worth when a branch drives it. It shows whether the branch teaches the right next step or just any next step. A refill timed to the cycle reads differently than a random cross-sell. If repeat rate climbs but order value sinks, the branch is nudging the wrong thing.
Branching only works when the flow knows who it is talking to. That means the list is scored into buckets first. The RFM teardown puts the value tier on every profile, as properties the splits can read. The segment migration view shows whether the branches move anyone up: first-timers into repeat buyers, repeat buyers into regulars. Score first, then branch.
One flow for everyone: the most common finding
When we read a post-purchase program cold, the most common finding of all is one generic flow sent to every order. That read is part of every Blueprint. We map your flows and your splits on your data. Book the fit call if you want it run for you. Build the branches from this page if not. Yours either way.
What operators ask
Do I need an app to branch a Klaviyo flow?
No. Conditional splits on profile properties and order data are native to Klaviyo flows. The trigger and every branch in this play run on data the platform already reads. The work is not building the splits. The work is deciding them: which questions the order answers, and which branch each answer deserves.
How many branches is too many?
Start with three. Every branch is a flow you must keep true: current copy, correct timing, a reason to exist you can still name. Ten branches are maintenance debt wearing a personalization costume. Add a fourth branch when the first three are measured and working, and when a segment is clearly getting the wrong emails.
Does this replace the welcome flow?
No. The welcome flow runs before the purchase and speaks to subscribers who have not ordered yet. This play begins at the order, the moment the welcome flow's job ends. The two hand off rather than overlap. Welcome earns the first purchase; the branches decide what happens after it. An account needs both, doing different jobs.
Build the branches, or bring us the whole program
Everything here is enough to build the three branches in your Klaviyo this week. Or book the fit call, and we read your post-purchase program as part of the Blueprint: $2,500, credited, built in your account, and yours if we ever part ways.
More from this series: the lifecycle playbook the RFM teardown segment migration the second-purchase play
Sources
- Concomitant: the full lifecycle playbook (the hub this play hangs off)
- Concomitant: the second-purchase play (the first-timer branch, taught in full)
- Concomitant: the RFM scoring teardown (the properties the value split reads)
This page carries no benchmark figures by design: the play is method, and the numbers worth trusting here are the ones your own order data produces. The linked plays hold the attributed benchmarks where they exist.