post-purchase-upsell-flow

The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.

---
name: post-purchase-upsell-flow
description: Design and implement one-click post-purchase upsells and downsells that raise average order value without hurting the main conversion rate. Use when asked to increase AOV, add an upsell, cross-sell or downsell after checkout, build a one-click upsell flow, monetize the thank-you page, or when someone asks how to make more revenue per customer from the same ad spend.
---

# Post-Purchase Upsell Flow

The step after payment is the cheapest revenue in a funnel: the customer has already converted, the payment method is already captured, and the offer costs nothing in ad spend. This skill covers designing that step and the technical requirements that make it actually work.

## When to use

- "How do I increase AOV" / "my ad costs are fine but revenue per order is too low"
- Adding an upsell, cross-sell, bundle or downsell to an existing checkout
- The thank-you page currently says only "thanks for your order"
- Deciding between a pre-purchase bump and a post-purchase upsell

## When not to use

- Main funnel converts near zero - fix that first (`landing-page-conversion-audit`). An upsell on no traffic is arithmetic on zero.
- High-ticket, sales-call-closed offers. The upsell there is a human conversation, not a page.

## Pre-purchase vs post-purchase: pick deliberately

| | Pre-purchase (bump on the order form) | Post-purchase (after payment) |
|---|---|---|
| Risk to main conversion | Real - every added element on the order form can cost you the base sale | **None** - the base order is already captured |
| Take rate | Lower per offer, but seen by 100% of checkout visitors | Higher per offer, seen only by buyers |
| Price ceiling | Low (a small add-on) | Higher (2-5x the base order is normal) |
| Payment friction | None, same form | Needs stored payment credentials to be one-click |

**Default recommendation**: build the post-purchase upsell first. It cannot cannibalize the base conversion rate, so it is the only AOV lever that is risk-free to test. Add a pre-purchase bump later, and only behind an A/B test that watches base conversion rate as a guardrail metric.

## Designing the offer

### Rules that decide take rate

1. **Complementary, not bigger.** "You bought the mat, here is the strap" beats "buy a second mat at 20% off". The customer's need is now solved; sell the thing that completes it.
2. **One decision per screen.** A grid of four upsells converts worse than one offer with a clear yes/no.
3. **Yes must be one tap.** Any re-entry of card details collapses take rate. This is a technical requirement, not a design preference - see below.
4. **No must be honest and easy.** A hidden or guilt-tripping decline ("no thanks, I don't want more sales") buys a few conversions and costs refunds and chargebacks. Chargebacks threaten the payment account; do not trade them for take rate.
5. **Price relative to what they just paid.** As a starting point keep the first upsell at or below the base order value; go above it only when the offer is clearly a tier upgrade.
6. **Time-bound only if true.** "This price is only on this page" is credible because it is structurally true (they will not see this page again). Fake countdown timers are not, and buyers who feel tricked refund.

### The chain

```
Payment captured
  └─ Upsell 1  (complementary, highest-margin)
       ├─ accept → Upsell 2 (optional, only if the first was accepted - willingness is proven)
       └─ decline → Downsell 1 (same benefit, smaller commitment: single unit, lite version, payment plan)
                      ├─ accept → thank-you
                      └─ decline → thank-you
```

Keep the chain at two decisions for most funnels. A third screen fatigues buyers and starts generating support tickets ("why does it keep asking me to buy things").

### What to write on the page

```
Headline: names the gap the base purchase left open
Body: 3-5 lines, one benefit, referencing what they just bought
Proof: one specific line (usag