The Nine-Figure Upsell Playbook

MERCHANT FIELD GUIDES
OCTOBER 2026

GROWTH01

The nine-figure upsell playbook.

Practical lessons from our work with nine-figure brands.

START HEREChoose one useful pair.

CHOOSE / BUILD / PROVE / DECIDEOCTOBER 2026

The finished result

One named offer, one verified customer journey and one decision based on your own retained additions and costs.

Your six missions

Choose a useful pair · pages 2–8.
Build a draft and place it · page 9.
Make the intended offer win · page 10.
Prove payment and the final order · pages 11–12.
Diagnose what happened · page 13.
Decide what earns its place · pages 14–15.

How to use this guide

Work one offer through the whole sequence. Worked examples are recommendations to adapt, not actual merchant configurations. Product references and dated evidence are on page 16.

revizeMerchant field guide · October 2026

Mission 1 · Define success

A paid result starts with a useful fit.

Write the reason before choosing the incentive.

Your result

Write down

When someone buys [main product and variant], offer [one companion] because [specific reason it fits].

Follow the whole journey

Stage	What counts as proof
Eligible	A controlled order meets the conditions for this page.
Shown	The intended customer actually sees the offer.
Chosen	The customer selects the correct variant and quantity.
Paid	The additional payment is confirmed and the final order contains the addition.
Retained	At the review date the addition has not been refunded or removed; later refunds remain possible.

Done when

The companion fits the exact model, material, size or task.
Stock, included components and existing order contents have been checked.
An acceptance or a click will not be counted as a paid, retained addition.

revizeMerchant field guide · October 2026

Mission 1 · Choose the first recipe

Start with the easiest fit to explain.

Use the product relationship, rather than the store category, to choose your test.

Your result

Choose your starting point

Customer has bought	Useful next step	Page
A main product	A verified-fit companion	4
One part of a collection	The exact missing matching piece	5
Something that needs care or repeat use	A suitable care item, refill or spare	6
Something else after considering an item	An available item from valid browsing history	7
An order with no stronger relevant match	One understandable fallback, or no offer	8

Stop rule

If you cannot explain why this addition belongs with the order in one sentence, choose another product or launch without an offer.

Write down

Original product / variant: __________________
Companion / variant: __________________
Reason it belongs: __________________
Who verifies compatibility: __________________

revizeMerchant field guide · October 2026

Mission 1 · Choose your pair

Complete the setup.

Offer the companion that makes the original purchase easier to use.

Worked example

Use this when

A main product has a verified companion that is not already included. In this worked catalog, Camera A and Case A each have a single compatible variant.

Configure · illustrative, not a historical store setup

Field	Worked configuration
Offer name	Camera A · fitted case
Qualifying purchase	Product: Camera A. This condition matches the product, including any of its purchase variants; it cannot isolate one model variant.
Offer products	Manual picks: product Case A; quantity 1. This example requires its single compatible variant; there is no merchant-selected compatible variant subset.
Exclusions	Hide products already in the order; omit incompatible or unavailable items.
Price / incentive	Normal price: illustrative $24; no additional offer discount.
Surface / priority	Thank you and Order status where configured; priority 10, before broader offers.

Product-level selection · launch prerequisite

Product conditions and Manual picks select products, not variant subsets. Use products with one compatible variant, or verify that every eligible purchase variant and every displayed companion variant fits the promise. If that is not possible, choose another companion or do not launch this recipe.

Customer sees · illustrative copy

Complete your Camera A setup. Protect it with the case made for this model. Case A · $24. Review the addition and complete any payment shown.

Prove it

Camera A order → Case A appears with the intended price and compatible variant.
Different camera product → this offer does not appear.
Same product, different purchase variant → every displayed companion variant must still fit; otherwise do not launch this configuration.
Case A already in this order → it is not offered again.
Accepted addition → final order has one Case A and confirmed additional payment.

If it fails

Wrong fit: pause and choose a product whose displayed variants all fit the eligible purchase variants, or do not launch. Narrowing a Product condition cannot isolate a variant of that same product. No views: use the diagnostic sequence on page 13 before adding a discount.

revizeMerchant field guide · October 2026

Mission 1 · Choose your pair

Finish the collection.

A direct match should feel like the missing piece.

Worked example

Use this when

The order contains one part of a set and the missing piece is an exact match. In this example, Sand linen is a separate product/finish and every displayed size is compatible with the eligible purchase variants.

Configure · illustrative, not a historical store setup

Field	Worked configuration
Offer name	Sand linen · matching pillowcases
Qualifying purchase	Product: Sand linen duvet cover. If other finishes are variants of this same product, this condition also includes them.
Offer products	Manual picks: product Sand linen pillowcase pair. Every displayed finish/size must fit every eligible purchase variant; otherwise use a different companion or do not launch.
Exclusions	Hide products already in the order. Do not assume the Product condition excludes a different finish stored as a variant of the same product.
Price / incentive	Normal catalog price; no additional offer discount.
Surface / priority	Chosen Thank you / Order status pages; priority 20, below more specific setup matches.

Product-level selection · launch prerequisite

Product conditions and Manual picks select products, not variant subsets. Use products with one compatible variant, or verify that every eligible purchase variant and every displayed companion variant fits the promise. If that is not possible, choose another companion or do not launch this recipe.

Customer sees · illustrative copy

Finish your Sand linen set with the matching pillowcase pair. Choose the correct size and review the price before adding.

Prove it

Sand duvet cover without pillowcases → every displayed pillowcase variant fits the promise.
Matching pillowcase product already in this order → duplicate is hidden.
Different finish stored as another product → this offer does not match.
Different finish stored as a variant of the same purchase product → still eligible; all displayed companion variants must fit, or this recipe must not launch.
Final paid order → intended pair and variant, with no unintended extra discount.

If it fails

A Product condition cannot distinguish finishes stored as variants of the same product, and Manual picks does not restrict the companion to a compatible variant subset. Choose products whose eligible/displayed variants all fit, choose another useful companion, or do not launch.

revizeMerchant field guide · October 2026

Mission 1 · Choose your pair

Help with the next use.

Choose care, a refill or an intentional spare.

Worked example

Use this when

The next task is concrete, and the item is suitable for the product and practical to store.

Configure · illustrative, not a historical store setup

Field	Worked configuration
Option A · care	Order contains suede shoes → manually picked suede-approved brush; quantity 1.
Option B · refill	Order contains Roller A → compatible Refill A pack; quantity 1.
Choose one for launch	Name the offer after that task; use its product condition, normal price and no extra discount.
Duplicate handling	Hide products already in the order for care/refills. For a same-item spare, intentionally allow the repeat only after testing existing quantities.
Surface / priority	Chosen pages; priority 30, below exact setup/collection matches.
Required catalog checks	Material compatibility, instructions, shelf life and existing quantity.

Product-level selection · launch prerequisite

Product conditions and Manual picks select products, not variant subsets. Use products with one compatible variant, or verify that every eligible purchase variant and every displayed companion variant fits the promise. If that is not possible, choose another companion or do not launch this recipe.

Customer sees · illustrative copy

Care: Keep your suede shoes ready for their next wear with this suitable brush. Refill: Keep a compatible Roller A refill ready for next time.

Prove it

Qualifying product → selected care or refill variant is available.
Every eligible material/model variant → every displayed care/refill variant is suitable. If not, choose a different companion or do not launch.
Intentional spare → the final quantity matches the promise and is useful.
Paid final order → addition, price and quantity are correct.

If it fails

Remove unsupported health or performance claims. If repeats are accidental, restore duplicate hiding or change to a complementary item.

revizeMerchant field guide · October 2026

Mission 1 · Choose your pair

Revisit a considered item.

Use expressed interest when a stronger companion does not apply.

Worked example

Use this when

Recently viewed tracking is configured, permissions are complete and the store can verify the resulting selection.

Configure · illustrative, not a historical store setup

Field	Worked configuration
Offer name	A second look
Source	Recently viewed; complete the tracking and privacy setup for your store.
Audience / priority	Use the intended audience; priority 40, after direct product companions.
Duplicates / price	Hide products already in the order; start at normal price. This is current-order suppression, not purchase-history-wide exclusion.
No-history behavior	Inspect the configured fallback on real no-history orders. Do not assume the offer is suppressed.
Truthful headline	Use copy that still makes sense if a fallback is displayed.

Customer sees · illustrative copy

One more item to consider. Review the product, available variant and price before adding.

Prove it

Valid history → an eligible, available considered item is shown.
No history → record the actual fallback or absence; copy remains accurate.
Product already in this order, including an accepted addition → not offered again.
Unavailable variant → no unavailable item can be added.
Final order and payment → match what the customer selected.

If it fails

A no-history result is a source/fallback issue, not evidence that browsing interest failed. Correct setup or switch to Manual picks until the behavior is understood.

revizeMerchant field guide · October 2026

Mission 1 · Choose your pair

Use a relevant fallback — or none.

The remaining audience still needs a reason to care.

Worked example

Use this when

No more specific offer applies, and the fallback has a clear purpose for the remaining orders.

Configure · illustrative, not a historical store setup

Field	Worked configuration
Offer name	Gift order · finishing touch
Qualifying purchase	Product or Collection condition identifying the intended gift orders.
Offer products	Manual picks: one coordinated greeting card, quantity 1.
Exclusions	Hide products already in the order; do not show for unrelated remaining orders.
Price / priority	Normal price; priority 90, after all intended specific matches.
Go / no-go	If the remaining audience has no useful shared purpose, keep the fallback in Draft.

Customer sees · illustrative copy

Finish your gift with a coordinated greeting card. Review the card and its price before adding.

Prove it

Gift order with no specific match → card appears.
Gift order already containing the card → no repeat.
Order matching a more specific offer → that intended offer wins for the page.
Unrelated order → this gift offer does not appear.

If it fails

Do not use a broad bestseller selection to hide missing relevance. Narrow the condition or remove the fallback.

revizeMerchant field guide · October 2026

Mission 2 · Build and place

From pair to saved draft.

The draft should make the intended audience and product choice obvious.

Product fact

Do this in Revize

Open Upsell offers and create an offer. Name it for the product relationship; leave Status as Draft while preparing.
Under Trigger conditions, add the qualifying Product or Collection condition. Use ALL / ANY deliberately and check each condition group.
Choose Manual picks for the first test. Add the verified companion; turn on Hide products already in the order unless this is an intentional spare.
Set the intended price, incentive, headline and choice count. Start without an additional discount. Select the intended Thank you and/or Order status surfaces.
For a separate Order status placement, select Standalone block in upsell settings. In Shopify, open Settings → Checkout → Configurations → Edit; select each intended page and add the supported Revize app block. Save.
Preview on mobile. Once placement and ordering are ready, set the offer to Active for controlled tests. Pause it if a critical test fails.

Done when / write down

Offer name and current status: __________________
Trigger condition / source / duplicate handling: __________________
Intended pages and block saved on each: __________________
A real eligible order proves display; preview alone only proves layout.

Product fact · checked October 22, 2026

Draft/Active, condition controls, manual selection and duplicate hiding were checked against current Revize source. Page-specific placement and eligibility still need a test in your store. Primary setup references: page 16.

revizeMerchant field guide · October 2026

Mission 3 · Make the intended offer win

Specific first is your decision.

The first active, live, matching offer for that page wins in ascending priority order, then ID.

Product fact

Worked priority order · illustrative numbers

Priority	Offer	Condition
10	Camera A · fitted case	Order contains Camera A.
20	Sand linen · matching pillowcases	Order contains Sand duvet cover.
40	A second look	Intended audience with configured recently viewed source.
90	Gift finishing touch	Order contains the selected gift product/collection.

Prove the overlap

Controlled order	Expected result
Camera A, also matching the broader audience	Camera offer wins on each configured compatible page.
Sand duvet cover, no camera	Collection match wins before the broader audience.
Gift order with no higher match	Gift fallback wins if it is active and configured for that page.

Product fact · not automatic specificity

Revize does not infer which offer is more specific. Your priority order supplies that decision. A winner that reaches its per-order acceptance cap does not automatically fall through to another offer.

Done when / write down

Order numbers and actual winning offer: __________________
Thank you and Order status results recorded separately.
Broad returning/first-time customer rules cannot unintentionally cover a direct companion.

If it fails

Check active status, schedule, page compatibility and overlapping conditions before changing the offer product. Keep only the rules your test needs. Source checked October 22, 2026; references on page 16.

revizeMerchant field guide · October 2026

Mission 4 · Prove the payment path

The promise must survive the payment step.

Acceptance is one stage of the journey, not a receipt.

Your result

Illustrative offer card

Complete your Camera A setup Case A protects the model you just chose. Case A · $24.00 · quantity 1 Review this addition, then complete any payment shown.

Make every line true

Customer question	Check in your store
Why this?	The case fits the exact ordered model and is not included already.
How much?	Variant price, offer discount, shipping, tax and any other discount effects are correct.
What happens next?	The actual review/payment step matches the wording. Thank you offers can require Review and pay.
Did it finish?	The final order contains the selected line, quantity and price; additional payment is confirmed.

Prove it / write down

Test order #: __________ ; additional payment reference/status: __________
Abandon the additional payment on another controlled order; do not count that as paid.
Verify the already-paid original order total did not conceal an unpaid add-on balance.
Check mobile, retry behavior and the final customer confirmation.

If it fails

Pause the offer. Finance reconciles the balance and final order before any retry; support explains the actual order state. Do not repeatedly add the item to clear an uncertain payment.

revizeMerchant field guide · October 2026

Mission 4 · Acceptance matrix

Run it before you leave it running.

Write an actual order number and result beside every applicable row.

Your result

Test order / expected / record

Action	Observable pass result	Actual / order #
Place an eligible order	Intended offer appears on the selected page.	__________
Place an excluded order	This offer does not appear.	__________
Use another variant of the same purchase product	All displayed companion variants still fit; otherwise do not launch this configuration.	__________
Order the companion already	Duplicate is hidden unless intentionally allowed.	__________
Use valid history, then none	Recently viewed/fallback behavior and headline are correct.	__________
Make companion unavailable	Unavailable variant cannot be added.	__________
Match two offers	Intended first page-compatible offer wins.	__________
Choose the addition on a phone	Product, variant, price and next step are legible and usable.	__________
Complete additional payment	Final line and confirmed paid balance match the selection.	__________
Abandon additional payment	Order is recorded as unpaid/unfinished, not a paid addition.	__________
Revisit or retry once	No unintended duplicate addition; order state is reconciled.	__________

Launch approval

QA owner: __________ ; finance owner: __________ ; date: __________
All critical customer/payment rows pass. Mark non-applicable source rows with a reason.
Support knows the offer name and how to handle an unfinished addition.

revizeMerchant field guide · October 2026

Mission 5 · Diagnose the first result

Fix the broken stage first.

A low paid count can have different causes. Follow the evidence in order.

Your result

Symptom → next action

What you see	Inspect first	Owner / next action
No views	Active status, schedule, eligible traffic, chosen page/block, priority overlap	Administrator places an eligible controlled order and records the displayed offer.
Views, no selections	Stock/variant availability, mobile layout, useful fit, actual copy and price	Merchandising verifies the journey, then changes one product or message.
Accepted, payment unconfirmed	Payment step, abandoned balance, final line, original-total coverage	Finance reconciles test orders; do not count acceptance as paid.
Paid, then removed/refunded	Removal, refund timing, reason, fulfillment and usefulness	Support + finance reconcile the retained count at the review date.
Retained, weak contribution	Discounts, product cost, incremental fulfillment, fees, refunds	Finance recalculates contribution; remove the incentive or change the item.

When to pause

Pause immediately if the wrong variant is offered, price/payment is inaccurate, duplicate additions occur, or a paid result cannot be reconciled. Resume after the relevant acceptance row passes.

Write down

First failing stage: __________
Order / screenshot proving the issue: __________
Owner: __________ ; fix: __________ ; retest date: __________

revizeMerchant field guide · October 2026

Mission 6 · Read your own scorecard

Keep, change one thing, or pause.

Set the decision criterion before looking at the result.

Your result

Scorecard · use one consistent period

Measure	This period
Period / offer name / changed variable	__________
Unique orders shown / accepted orders	__________ / __________
Confirmed paid additions / later removed or refunded	__________ / __________
Paid additions still retained at review	__________
Added product cost / fulfillment / fees / refund allowance	__________
Total added contribution / 1,000 unique orders shown	__________
Merchant-set minimum contribution per 1,000 shown	__________

Example arithmetic · not a benchmark

Added contribution per retained addition = price after discounts − product cost − extra shipping/fulfillment − payment/app fees − refund allowance. Illustrative: $24 − $9 − $3 − $1 − $1 = $10. Total added contribution ÷ unique orders shown × 1,000 = contribution per 1,000 shown.

Decide

Keep: critical tests pass and your recorded contribution meets your own minimum.
Change one thing: product, wording, choice count or incentive. Record the change and review again.
Pause: a critical journey fails or economics are unacceptable. Name the repair owner.

Read the result honestly

Use unique orders, rather than repeat visits, for the denominator. Recheck later refunds. A two-week rhythm is a starting cadence; low traffic needs longer. Before/after comparisons can be confounded and do not prove incremental lift.

revizeMerchant field guide · October 2026

Mission 6 · Your first-offer brief

Make the next action concrete.

One completed example, then the version your team will own.

Your result

Completed brief · all values illustrative

Field	Camera A example
Pair / reason	Camera A → Case A; each product has one compatible variant in this worked catalog.
Conditions / exclusions	Product Camera A; hide Case A already in this order; verify stock and fit. Product conditions cannot isolate variants of that product.
Source / price / priority	Manual picks: product Case A, quantity 1, $24, no extra discount, priority 10. All displayed variants must be compatible.
Surfaces / customer copy	Thank you + Order status where configured; Complete your Camera A setup.
Payment / proof	Review and pay where shown; final line plus confirmed additional payment; record order #.
Owner / decision	Merchandising lead; review date set before launch; keep only if own contribution threshold is met.

Your brief / write down

Purchase / variant: __________ ; companion / variant: __________
Catalog prerequisite: all eligible purchase variants and displayed companion variants fit, or choose another product / do not launch: __________
Reason: __________ ; price: __________ ; incentive: __________
Trigger / exclusions / priority: __________
Source / surface / customer headline: __________
Payment proof and controlled order #: __________
Owner: __________ ; minimum contribution: __________ ; review date: __________

revizeMerchant field guide · October 2026

Evidence · Updated October 22, 2026

What the evidence can tell you.

Product behavior, observed records and your own results answer different questions.

Evidence

Seen in stores · aggregated research notes

September 7–October 6, 2026: a curated-accessory example recorded 1,748 unique orders shown, 30 accepting orders and 27 passing the available payment/retention checks. A recently viewed example recorded 1,801 shown, 33 accepting and 30 passing those checks. Underlying store records are not public. These inherited aggregate observations were not freshly re-audited for this edition.

Limits of the observations

These are recorded observations at the research cutoff, not conversion benchmarks, incremental lift or profit. Historical configurations were not verified and could have changed. The examples cannot rank recipes or isolate a discount effect. Later removal/refund remains possible. No merchant or customer identities are disclosed.

Product fact · checked October 22, 2026

Revize controls reviewed 22 October 2026. Feature availability depends on plan; verify in your store. Worked products, prices, priorities, thresholds and timelines are recommendations or arithmetic, not recorded merchant settings.

Primary product sources

Your result

Only your tested journey, reconciled paid orders, retained additions and actual costs justify your keep/change/pause decision. References need internet access; the guide itself reads offline.