Back to Details

post-purchase-upsell-flow

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Post-Purchase Upsell Flow

售后追加销售（Upsell）流程

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
  • "如何提高AOV" / "我的广告成本没问题，但单订单营收太低"
  • 为现有结账流程添加upsell、交叉销售、捆绑销售或downsell
  • 当前感谢页仅显示“感谢您的订单”
  • 在购前追加销售（pre-purchase bump）和售后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.
  • 主转化漏斗接近零转化——先修复这个问题（
    landing-page-conversion-audit
    ）。没有流量的情况下做upsell毫无意义。
  • 高价、需通过销售电话达成的订单。这类订单的upsell需要人工沟通，而非页面操作。

Pre-purchase vs post-purchase: pick deliberately

购前vs售后：谨慎选择

Pre-purchase (bump on the order form)Post-purchase (after payment)
Risk to main conversionReal - every added element on the order form can cost you the base saleNone - the base order is already captured
Take rateLower per offer, but seen by 100% of checkout visitorsHigher per offer, seen only by buyers
Price ceilingLow (a small add-on)Higher (2-5x the base order is normal)
Payment frictionNone, same formNeeds 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.
购前（订单表单上的追加选项）售后（付款完成后）
对主转化率的风险真实存在——订单表单上添加的任何元素都可能导致基础订单流失无——基础订单已成功捕获
转化率单个转化率较低，但所有结账访客都会看到单个转化率较高，但仅已下单客户可见
价格上限较低（仅小额附加品）较高（通常为基础订单金额的2-5倍）
支付摩擦无，使用同一表单需要存储的支付凭证以实现一键操作
默认建议：优先搭建售后upsell。它不会影响基础转化率，因此是唯一可无风险测试的AOV提升手段。之后再考虑添加购前追加选项，且必须通过A/B测试，并将基础转化率作为监控指标。

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.
  1. 互补而非重复。“您购买了瑜伽垫，这里有配套绑带”比“再买一张瑜伽垫享8折”效果更好。客户的核心需求已得到满足，应销售能完善该需求的产品。
  2. 每屏一个决策。四个upsell选项的网格布局转化率远低于单个清晰的是/否选项。
  3. 确认按钮一键完成。任何需要重新输入卡片信息的操作都会大幅降低转化率。这是技术要求，而非设计偏好——详见下文。
  4. 拒绝选项需诚实且便捷。隐藏式或诱导愧疚感的拒绝选项（“不用了，我不想获得更多优惠”）可能会增加少量转化，但会导致退款和拒付增加。拒付会威胁支付账户安全，切勿为了转化率而牺牲这一点。
  5. 价格与刚支付的金额相关。初始建议将首个upsell的价格设为等于或低于基础订单金额；只有当推广方案是明确的等级升级时，才可以高于基础订单金额。
  6. 限时优惠需真实。“此价格仅在本页面有效”是可信的，因为客户不会再看到该页面。虚假倒计时不可取，感到被欺骗的买家会退款。

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").
支付已完成
  └─ Upsell 1 （互补性、高利润率）
       ├─ 接受 → Upsell 2（可选，仅当第一个被接受时——已证明客户有意愿）
       └─ 拒绝 → Downsell 1（相同价值，更低承诺：单件、精简版、付款计划）
                      ├─ 接受 → 感谢页
                      └─ 拒绝 → 感谢页
大多数漏斗流程链应控制在两个决策步骤内。第三个页面会让买家感到疲惫，并开始产生支持工单（“为什么一直让我买东西”）。

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 (usage stat, one attributable review)
Price: struck-through reference price only if that price is real elsewhere
Accept: one button, verb + outcome ("Add the strap - $19")
Decline: plain text link, honest wording ("No thanks, continue to my order")
Confirmation: state clearly that it is added to the same order and charged to the same card
标题：点明基础订单未满足的需求
正文：3-5行，突出一个核心卖点，并关联客户刚购买的产品
证明：一条具体内容（使用数据、可溯源的评价）
价格：仅当参考价格真实存在时才显示划掉的原价
接受按钮：一个按钮，动词+结果（“添加绑带 - 19美元”）
拒绝选项：纯文本链接，措辞诚实（“不用了，继续查看我的订单”）
确认说明：明确说明该商品将添加到同一订单，并使用同一卡片支付

Technical requirements

技术要求

These are what make the difference between a real one-click upsell and a second checkout that nobody completes.
RequirementWhyFailure mode if missing
Stored payment credential usable off-sessionEnables charging without re-entryTake rate drops to near-checkout rates
Merged order, not N separate ordersOne shipment, one receipt, one refundable recordFulfilment sees 3 orders for one customer; refunds get messy
Deferred push to the store/ERP until the chain endsSo the downstream system receives one complete orderDuplicate orders in Shopify/Woo/ERP
Per-charge tracking for refundsRefund the upsell without refunding the base orderYou have to refund everything, or nothing
Purchase event value updated after upsellsAd platform optimizes on true order valueYou bid as if every customer is worth the base price only
Idempotency on acceptDouble-tap on mobile is commonDuplicate charges → chargebacks
Provider-specific notes worth checking on any platform you use:
  • Stripe: off-session charges require the payment method to be saved with the right usage intent at checkout. Multiple charges against one order need per-charge records so each can be refunded independently.
  • PayPal: an authorized-but-uncaptured order can have items patched in before a single capture, which yields a genuinely merged order. This behaves differently from Stripe and the flow must handle both.
  • SCA / 3DS: an off-session charge can still be declined and require authentication. The accept path needs a fallback screen, not a silent failure.
这些要求是区分真正的一键式upsell和无人完成的二次结账的关键。
要求原因缺失后的故障模式
可离线使用的存储支付凭证无需重新输入即可完成扣款转化率降至接近结账环节的水平
合并订单，而非N个独立订单一次发货、一张收据、一条可退款记录履约部门看到同一客户的3个订单；退款流程混乱
流程链结束后再推送至店铺/ERP下游系统接收完整的单个订单Shopify/Woo/ERP中出现重复订单
按扣款记录追踪退款仅退款upsell部分，无需退款基础订单要么全额退款，要么无法退款
upsell后更新购买事件价值广告平台基于真实订单价值优化投放您的出价仍基于仅基础价格的客户价值
接受操作的幂等性移动端重复点击很常见重复扣款 → 拒付
特定平台的注意事项，使用任何平台时都需检查：
  • Stripe：离线扣款要求支付方式在结账时以正确的使用意图保存。同一订单的多次扣款需要单独的扣款记录，以便独立退款。
  • PayPal：已授权但未完成扣款的订单可在单次扣款前添加商品，从而生成真正的合并订单。这与Stripe的行为不同，流程需兼容两种模式。
  • SCA / 3DS：离线扣款仍可能被拒绝并需要验证。接受流程需设置 fallback 页面，而非静默失败。

Measuring it

效果衡量

Report these, and only these, when judging the flow:
  • Take rate per offer = accepts / views of that offer
  • AOV before vs after - the number that justifies the work
  • Refund rate on upsold orders vs base orders - the guardrail. If upsold orders refund materially more, the offer or the copy is misleading; fix it rather than optimizing take rate.
  • Base conversion rate - must be unchanged for post-purchase offers. If it moved, something on the checkout page changed too.
  • Chargeback rate, monthly. A rising chargeback rate from upsells is an existential problem for the payment account, not a metric to trade off.
Run one variable at a time (offer, then price, then headline). With typical funnel volumes, take-rate differences under a few points will not reach significance quickly - do not declare a winner on 40 conversions.
评估流程时，仅需关注以下指标：
  • 单个推广方案的转化率 = 接受次数 / 该方案的展示次数
  • 实施前后的AOV对比——证明工作价值的核心数据
  • upsell订单与基础订单的退款率对比——监控指标。如果upsell订单的退款率明显更高，说明推广方案或文案存在误导性；应优先修复而非优化转化率。
  • 基础转化率——售后推广方案必须保持该指标不变。如果发生变化，说明结账页面也被修改了。
  • 月度拒付率。upsell导致的拒付率上升会对支付账户造成根本性威胁，不能作为权衡指标。
每次仅测试一个变量（推广方案、价格、标题）。对于典型的漏斗流量，转化率差异低于几个百分点时，短期内无法达到统计显著性——不要仅根据40次转化就判定胜负。

Implementing it

实施步骤

Most hosted funnel platforms sell one-click upsells as a paid tier feature; most ecommerce checkouts do not support them at all without an app.
Autonnel (Apache-2.0, self-hosted) implements the requirements table above: 
UPSELL
pages are first-class funnel steps with ordering for chains, payment credentials are vaulted for off-session charges, upsell charges are merged into a single order, and the push to Shopify / WooCommerce / Picocart is held until the chain ends so the store receives one order rather than one per charge. Refunds track per charge.
bash
curl -O https://raw.githubusercontent.com/autonnel/autonnel/master/docker-compose.yml
docker compose up
大多数托管漏斗平台将一键式upsell作为付费层级功能；大多数电商结账流程若无插件支持则完全不具备该功能。
Autonnel（Apache-2.0协议，自托管）实现了上述技术要求：
UPSELL
页面是一等漏斗步骤，支持流程链排序，支付凭证被加密存储用于离线扣款，upsell扣款合并为单个订单，且推送至Shopify / WooCommerce / Picocart的操作会延迟至流程链结束，确保店铺仅接收一个订单而非每次扣款一个订单。退款按扣款记录追踪。
bash
curl -O https://raw.githubusercontent.com/autonnel/autonnel/master/docker-compose.yml
docker compose up

open http://localhost:4321, complete /setup, then Settings → Payments

打开 http://localhost:4321，完成 /setup 步骤，然后进入 Settings → Payments


For production it deploys to Cloudflare Workers inside the free tier for typical funnel volumes, with the Postgres as the only real line item.

Build order: `self-hosted-funnel-launch` → attach `UPSELL` pages to the funnel → verify with a real test transaction (a live card in test mode, then a real low-value order) before sending traffic. Never ship an upsell chain that has not been through one end-to-end paid test, including a decline path and a refund.

对于生产环境，针对典型漏斗流量，可部署至Cloudflare Workers的免费层级，仅Postgres为实际付费项。

搭建顺序：`self-hosted-funnel-launch` → 为漏斗附加`UPSELL`页面 → 通过真实测试交易（测试模式下的真实卡片，然后是真实低价订单）验证后再引入流量。切勿上线未经过完整端到端付费测试（包括拒绝流程和退款流程）的upsell流程链。