The flow that turns a first order into a second one. Order confirmation, thank-you, cross-sell, and review request, all firing after the buy, all aimed at retention.
At a glance
A KPI summary of the post-purchase automation, the sequence that fires after a customer places an order. Depending on how the merchant has built it, this covers order confirmation, a thank-you, education or onboarding, cross-sell and replenishment prompts, and a review request. Where the abandoned-cart flow wins back lost sales, the post-purchase flow does the quieter, higher-margin work of turning buyers into repeat buyers and harvesting reviews. The panel surfaces the flow’s entries, sends, conversions, and revenue so you can judge whether your post-purchase programme is actually driving repeat purchase or just confirming orders. Conversions follow Klaviyo’s default 5-day click, 1-day view attribution.
| What it counts | The post-purchase automation’s funnel for the period: entries (orders that triggered it), sends, conversions, and attributed revenue, summarised as KPI tiles. |
| API endpoint + statistics field | POST /api/flow-values-reports over recipients, conversions, and revenue, scoped to the flow triggered on the placed-order event (identified via GET /api/flows). |
| Trigger type | Fires on the placed-order trigger, so an entry corresponds to a completed order rather than an abandoned cart. |
| Attribution model | Klaviyo default: 5-day click plus 1-day view. A buyer who clicks a cross-sell or review email and orders again within the window is credited to the flow. |
| Email vs SMS aggregation | If the flow includes SMS steps (common for shipping or review nudges), both channels are summed into the panel. |
| What it drives | Repeat purchase, review generation, and retention, the levers behind customer lifetime value rather than first-order acquisition. |
| Chart type | KPI summary (tiled metrics). |
| Time window | Selected period, compared to the prior period. |
| Alert trigger | Read alongside flow status; a post-purchase flow stuck in draft silently stops the repeat-purchase engine. |
| Roles | owner, marketing |
Calculation
Calculated automatically from your Klaviyo data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A coffee subscription brand on Shopify running a post-purchase flow: order confirmation, a brewing-guide email at 3 days, a review request at 14 days, and a replenishment cross-sell at 25 days. The 30-day window covers 14 Mar 26 to 12 Apr 26. All figures are illustrative.| Metric | This period | Prior period |
|---|---|---|
| Flow entries (orders) | 4,500 | 4,200 |
| Sends | 15,300 | 14,100 |
| Conversions (repeat orders) | 405 | 360 |
| Attributed revenue | £23,800 | £20,900 |
| Conversion rate (per entry) | 9.0% | 8.6% |
- Repeat-purchase conversion rose to 9.0 percent. Of every 100 first orders entering the flow, nine led to another purchase inside the attribution window. For a subscription-adjacent brand this is the metric that compounds, because each repeat order seeds future repeats.
- Revenue per entry is modest at £5.29, and that is fine. Post-purchase revenue per entry is lower than cart-recovery revenue per entry because the goal is long-term retention, not immediate rescue. The value shows up over the customer’s lifetime, which is why this flow pairs naturally with the predicted-CLV view.
- Sends per entry of 3.4 against a four-step flow is healthy. Most entrants receive the confirmation, the guide, and the review request; the replenishment cross-sell at day 25 reaches a slightly smaller set inside a 30-day window. A figure far below 3 would suggest later steps are not firing.
- The review request step is doing double duty. Beyond any direct conversions, the 14-day review email generates social proof that lifts conversion elsewhere on the site. This panel will not capture that downstream value, so judge the review step partly on review volume in your reviews tool, not only on its attributed revenue here.
- A static or zero panel is a silent retention leak. Unlike the cart flow, a broken post-purchase flow does not produce an obvious revenue cliff, it quietly stops nurturing buyers. Check that the flow is live, that the placed-order trigger is firing, and that the cross-sell logic still references in-stock products before assuming low numbers mean low opportunity.
Sibling cards merchants should reference together
Post-Purchase Flow is a retention engine. Pair it with these:| Card | Why pair it with Post-Purchase Flow |
|---|---|
| Welcome Flow Status | The other bookend of the lifecycle. Welcome onboards the relationship; post-purchase deepens it after the first order. |
| Flow Status Breakdown | Confirms the post-purchase flow is live rather than sitting in draft, the most common reason this panel reads low. |
| Flow Trigger Types | Shows whether placed-order triggers are covered across the account, including post-purchase variants. |
| Top 10 Flows by Revenue | Portfolio context. Post-purchase usually ranks behind cart recovery and welcome but should still feature. |
| Predicted CLV Tiers | The long-term payoff. A strong post-purchase flow lifts customers into higher predicted-value tiers over time. |
Reconciling against Klaviyo
Where to look in Klaviyo:- Flows → [the post-purchase flow] → Analytics shows entries, recipients, conversions, and revenue for the flow, the direct comparison to this panel.
- Flows → [the post-purchase flow] → individual messages for the per-step figures behind the totals, including the review-request and cross-sell steps.
- Analytics → Reports → Flow Performance, filtered to the post-purchase flow, for a period-bounded view.
| Reason | Direction of divergence |
|---|---|
| Time-zone. Klaviyo runs on the account time zone; Vortex IQ runs on UTC. Boundary days differ, shifting a period’s tiles slightly. | Usually small on the headline. |
| Which flow is “post-purchase”. Accounts often run several placed-order flows (thank-you, cross-sell, replenishment) as separate flows. Vortex IQ may aggregate them, while Klaviyo’s per-flow view shows one. | Vortex IQ can run higher. |
| Long delays vs short window. A replenishment step at day 25 or later may convert outside a 30-day window, so its revenue lands in a later period than the entry. | Revenue can appear delayed against entries. |
| Attribution window. A mid-period change to the attribution window can make a live read and a Klaviyo snapshot disagree. | Small drift on changed-window accounts. |
| Custom trigger names. If the flow triggers on a custom event rather than the standard placed-order event, detection may miss it. | Card can under-report. |