How to Use Recharge to Save Subscribers Who Try to Cancel

The short answer: if subscribers cancel from the portal with nothing in their way, the Cancellation Prevention flow is on Recharge's Starter plan at $149 a month plus 1.50% + 20¢ per transaction, so build it there before paying for Scale (pricing page, checked on 5 November 2026): pick the template under Churn tools, branch by shipping country so customers in regions with strict cancellation rules can leave without an offer, give each cancellation reason one offer with a limit on how often money is claimed, build the landing page, activate and test it from the portal, read the saves after a full month, and let Claude pull the cancellation reasons through the Analytics MCP connector while a person sets the offers.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

A cancellation is the one moment a subscriber tells you why. Recharge's flow catches that moment with a survey and an offer tied to the answer, and the save rate is readable in the same place (Cancellation Prevention overview). Plans, fees and the rest of the product are in the Recharge entry.

Before you build it:

1. Price the offer against the order. For example, 300 cancellations a month and a 20% discount on a $40 next order cost $8 per save; if the flow keeps 45 of the 300, the discounts cost 45 x $8 = $360 and the retained next orders are worth 45 x $40 = $1,800, before any order after that. The default 365-day limit on monetary offers caps how often one subscriber can take the same discount (overview).
2. Start from the reasons you already have. Support tickets and portal cancellations from the last quarter tell you which survey answers deserve an offer; the basic template ships with no incentives and the suggested-offers template with one per answer (build guide).
3. Set the baseline. Last month's cancellations and active subscribers, written down, because flow metrics refresh once a day at 1:30 AM ET and the Insights tab shows only the previous calendar month (Flows guide, overview).

What you need

• Recharge on the Shopify Checkout Integration, the platform the feature is listed for (overview).
• A customer portal on a standard theme. A custom portal gets a link to the standalone landing page through the SDK but cannot alter the survey, per the same overview.
• A view from counsel on cancellation law in each country you ship to. Recharge's own guide tells you to consult one (regional laws guide).

Step 1: Pick the template

Churn tools, then Cancellation Prevention, then Create from template. There are six: basic, basic with suggested offers, two A/B versions and two with rewards reminders; Get started opens the canvas, and the flow triggers whenever a customer starts cancelling (build guide). The pricing page lists subscriber-journey A/B testing under Scale, so check your plan before choosing an A/B template (pricing page).

Step 2: Branch by country

Drag a Conditional branch from the Conditions tab ahead of the survey, choose Shipping address, then Country, and order the branches from most to least specific, because only the first branch whose conditions pass runs. Recharge's example offers North American customers an incentive and lets European customers cancel without seeing one (regional laws guide). A second branch on Subscription being cancelled, by product or collection, can route high-value lines to a stronger offer; use that object rather than Line item, which checks the next queued order instead of the one being cancelled (overview).

Step 3: Add a deflection page, if there is something to show

A Deflection Page placed before the survey presents one offer and the subscription's benefits; a customer who accepts never sees the survey (build guide). Skip it if the only thing to show is a discount.

Step 4: One offer per reason

Open the Cancellation survey node and edit the offer behind each answer: contact support, delay and change frequency, delay, discount, discount code, free gift, skip, swap, swap to a specific product, swap and discount, or no offer. Reasons cannot be reordered once added, so write the list in order first; the shuffle setting randomises the order per customer to blunt the first-option bias. Set the gaming prevention window; a subscriber who already claimed money inside it gets a skip instead (build guide). Two limits from the overview: swaps fail on prepaid subscriptions, and a swap cannot change what is inside a bundle, only replace the whole bundle (overview).

Step 5: Build the page

Customize landing page opens the Site Builder for the survey page and for each response page. The free gift and credit balance sections show only to customers who hold one, and the page looks the same across portal themes (customisation guide).

Step 6: Activate and test

Save, Activate, Confirm: activate flow, then cancel a test subscription through your own portal. A live flow cannot be edited, even after it is deactivated; a change means Duplicate, edit the copy, activate it and deactivate the original (Flows guide).

Step 7: Read the saves

On the Customer Details page, Customer Flows shows each customer's path as completed, cancelled or in progress (build guide). The bar graph icon on the flow opens its metrics, and Refresh metrics now is allowed once an hour per flow (Flows guide). After a month with more than 50 unique cancellation notes, the Insights tab shows up to five AI-generated reasons by product or by reason (overview).

Step 8: Let Claude read the reasons

Add the Recharge Analytics MCP from the Claude connector directory, which takes a Claude owner for an organisation and the Analytics permission in Recharge for each user, then ask: "What are the top 3 reasons customers are cancelling their subscriptions?" and "How does my active churn rate compare with my vertical over the past 6 months?" (MCP article). The connector returns aggregate metrics only, never a list of who churned, and cannot write to the store, so the human check is built in: a person reads the answer, changes an offer in a duplicated flow and activates it. The feature is in early adopter status. Remi, the AI agent inside the dashboard, is listed under Scale on the pricing page (pricing page), while Recharge's July 2026 launch post said it was live for every merchant (Remi post); look for the chat icon in the bottom right corner of the dashboard before paying for it.

Step 9: Follow with a win-back

For the ones who leave anyway, the Win Backs: Through Recharge template emails an offer 30 days after a customer cancels every subscription, then two more if the first goes unclaimed, and each message carries an unsubscribe link that cannot be removed (Win Backs guide).

Where the guides say it goes wrong

• Editing a live flow. Not possible; duplicate it (Flows guide).
• A Line item condition on a product branch. It reads the next queued order and shows the wrong survey (overview).
• A discount offer that vanishes. Discount offers, unlike discount codes, are removed when the customer changes the next charge date, per the same overview.
• A reason nobody sees. A reason whose offer needs a portal setting, such as swaps or discount codes, is hidden until that setting is on (build guide).

The suggested offers are Recharge's defaults, not your margin. Every discounted order a template offer saves is still a transaction Recharge processes at 1.50% + 20¢, so a save at any price is a win on the platform's ledger before it is one on yours; set each offer's value from the product's margin and the gaming window from your own repeat rate (pricing page).

FAQ

Is Cancellation Prevention on the Starter plan?

Yes. The Starter card on the pricing page lists Smart Cancellation Prevention; subscriber-journey A/B testing and Remi are listed from Scale (pricing page).

Does the flow work for prepaid subscriptions?

Partly. Reasons with swap or skip offers are hidden from a customer cancelling a prepaid subscription, and a swap configured for one fails (overview).

Can I change a flow after it is live?

No. Duplicate it, edit the copy, activate the copy and deactivate the original; the Flow timeline records who changed what and when (Flows guide).