LUCENTCOMMERCEGET A FREE STORE AUDITFREE AUDIT

SUBSCRIPTIONS · RETENTION · CRO · 26 MARCH 2026 · 7 MIN READ

Subscription pause, skip and swap: the retention levers

Three of the four reasons people cancel are not "I want to stop buying this". Give each one its own button and most of them stop being cancellations.

A wholesale order form beside its negotiated price list

You reduce subscription cancellations by making the smaller action easier to reach than the big one. Most people who cancel are not rejecting the product — they have too much of it already, the timing has gone wrong, or they want a different variant. Skip absorbs the first, pause the second, swap the third, and none of them ends the agreement. Build those three properly before you spend anything on save offers, because a discount offered to someone whose cupboard is full is answering a question they did not ask.

IN SHORT

  • Four reasons account for most cancellations: too much stock, wrong timing, wrong product, and failed payment. Only the last is a technical problem.
  • Shopify models pause as a first-class contract state — `PAUSED` is documented as "temporarily paused and is expected to resume in the future", distinct from `CANCELLED`, "ended by an unplanned customer action".
  • Skip operates on a single billing cycle rather than the contract: `subscriptionBillingCycleSkip` and its inverse `subscriptionBillingCycleUnskip` both take one cycle as input.
  • `subscriptionBillingCycleContractEdit` edits "the contents of a subscription contract for the specified billing cycle" — which is what makes "change just this box" possible without touching the standing agreement.
  • Shopify’s first-party Subscriptions app documents resume, skip and cancel as customer-facing actions; product swapping is not among them, so a swap flow means a platform or a build.
  • The retention surface is the email before the charge, not the cancellation page. By the time someone opens the cancellation page they have already decided.

Four reasons, four different answers

It is worth separating these, because a single "are you sure?" screen treats all four as the same event and answers none of them.

"I have too much." The commonest reason, and the most avoidable. Someone signed up for coffee every four weeks and drinks it every six. Every delivery widens the gap until the cupboard is the argument against the subscription. The answer is a skip that takes one tap, and a frequency change offered by name — not buried in a settings page called *Manage plan*.

"Not right now." Travel, a house move, a tight month, a hospital stay. The customer has no complaint and no intention of leaving permanently; they need the charges to stop for a while. If pause is not obvious, they will cancel, because cancel is the only control they can find that definitely stops the money.

"I want a different one." They like the programme, they are bored of the variant. This is the reason most often misread as churn, and the one most stores have no mechanism for at all — so it surfaces as a cancellation followed, sometimes, by a new subscription to a different SKU, and usually not.

The card failed. Involuntary churn, and it belongs in a separate report. Fixing it is dunning and card-updater work, not messaging, and mixing it into the churn number will have you redesigning a cancellation flow to solve an expired Visa.

The platform already thinks in these terms

This is not a set of behaviours you have to invent on top of Shopify. The data model has opinions about them, and they are the right ones.

A subscription contract carries a status, and Shopify’s documented values distinguish exactly the outcomes you care about: ACTIVE is "active and continuing per its policies"; PAUSED is "temporarily paused and is expected to resume in the future"; CANCELLED is "ended by an unplanned customer action"; EXPIRED means it ran its full course; FAILED means "billing failed and no further billing attempts are expected". Pause is not a cancellation with a nicer label — it is a different state with a different expectation attached, and your reporting should honour that distinction rather than lumping paused subscribers in with lost ones.

Skip is finer-grained still. subscriptionBillingCycleSkip "skips a Subscription Billing Cycle" and takes a single billing cycle as input, and subscriptionBillingCycleUnskip reverses it. The unit is one delivery, not the agreement. That is the whole point: a customer who skips has not changed anything about what they buy, and a customer who un-skips after reconsidering has left no trace of an aborted cancellation.

Swap is the interesting one. subscriptionBillingCycleContractEdit is documented as editing "the contents of a subscription contract for the specified billing cycle", and it returns a subscription draft — so a one-off substitution is modelled as an edit scoped to a cycle, separate from editing the contract itself. That distinction is the difference between "send me the dark roast next month" and "change my subscription to dark roast forever", and a swap interface that cannot tell those apart will get it wrong in whichever direction annoys the customer more.

What you get out of the box, and what you have to build

Shopify’s own Subscriptions app documents what a customer can do from their account: resume, skip or cancel their subscriptions, and manage their payment methods and shipping address. Merchants can modify, skip, pause and cancel plans and contracts from the admin.

Read that carefully, because there are two gaps. Customer-initiated pause is not listed alongside skip and cancel in the same way resume is, and product swapping is not a documented customer-facing action at all. So if your retention plan leans on either of those, you are choosing between a subscription platform whose product includes them and building the portal yourself against the APIs above.

That is a legitimate reason to pay for a platform, and one of the few honest ones — the billing machinery is the same underneath either way. But price it against the alternative. A store selling four SKUs on one frequency does not need a swap engine; it needs a skip link that works on a phone. We have seen more retention lost to a portal that takes four taps to skip than to any missing feature.

The cancellation page is the wrong place to fight

By the time somebody has navigated to the cancellation page, they have made the decision. Everything that happens there is damage limitation, and most of what stores put there makes it worse.

The discount save offer is the reflex, and it is the weakest lever of the four. It costs margin on exactly the customers who were going to stay anyway once they found the skip button, it teaches a segment of your base that threatening to cancel is how you get a better price, and it does nothing for the person whose problem is that they have six bags of coffee. Offer it last, if at all, and never before you have offered pause.

What does work on that page is honest ordering. Put the three smaller actions above the cancel button, labelled in the customer’s words — *Skip my next delivery*, *Pause for a while*, *Change what I get* — and leave cancel visible and functional underneath. Hiding it is a bad trade: you keep a handful of subscribers who resent you and they tell their card issuer instead, which costs you a chargeback and a payment dispute rather than a churn event.

Ask for a reason, one tap, five options, optional. Reasons captured at cancellation are the only direct read you get on which of the four problems you actually have, and a programme that cannot tell "too expensive" from "too much product" will spend the next quarter discounting its way into the wrong one.

Move the fight earlier: the pre-billing email

The real retention surface is the notification that goes out before a charge. It arrives at the exact moment the customer is thinking about the subscription, and it is the only moment they are thinking about it while nothing has gone wrong yet.

That email should contain the skip link, the swap link and the pause link as buttons, not a "manage subscription" link to a portal login. Every step between the thought and the action is a chance for the thought to become "actually, cancel". A customer who skips from an email has had a good experience with your brand; the same customer, having failed to find the skip button on a phone, has had a bad one and will remember it at the next renewal.

The same logic applies to the second skip in a row. Two consecutive skips is not a retention success, it is a cancellation that has not happened yet, and the right response is to offer a frequency change rather than wait for the third. A subscriber on the wrong cadence is a subscriber with an expiry date.

Measure it as four numbers, not one

A single churn percentage hides everything you would act on. Split it.

  • Voluntary versus involuntary churn, separated cleanly. Failed-payment losses are a dunning and card-updater problem, and improving them will not show up in any messaging test.
  • Pause-to-resume rate. The number that tells you whether pause is a retention lever or a polite exit. If almost nobody resumes, your pause has no end date and no reminder.
  • Skip depth. How many consecutive skips before a cancellation. This is your cadence report, and it usually says your default frequency is too fast.
  • Swap rate among retained subscribers. If swapping is available and nobody uses it, either the range is too narrow to be worth swapping within, or the control is not findable.
  • Time to first cancellation, by cohort. A cluster right after delivery two means the product is not landing; a cluster after delivery five is usually cadence or boredom.

The honest position

We build and maintain subscription programmes, and the work that moves retention is rarely the work clients arrive expecting to pay for. It is a skip button that is findable on a phone, a pause with a return date attached, an email that arrives before the charge rather than after it, and a cancellation page that does not insult the person reading it.

The expensive machinery — build-a-box, swap engines, multi-tier save-offer trees — is worth it for a range deep enough that a subscriber could plausibly want something else next month. If your catalogue is four SKUs, that is not your problem, and the honest advice is to spend the money on the cadence instead.

Questions this raises

How do you reduce subscription cancellations?

Make the smaller actions easier to find than cancelling. Most cancellations are caused by having too much product, bad timing, or wanting a different variant — skip, pause and swap answer those three without ending the agreement. Put all three above the cancel button and, more importantly, in the email that goes out before the next charge.

Is pausing a subscription better than cancelling?

Materially, yes, and Shopify treats them as different states. A contract with status `PAUSED` is documented as "temporarily paused and is expected to resume in the future", while `CANCELLED` is "ended by an unplanned customer action". Report them separately: a paused subscriber is someone to bring back with a reminder, a cancelled one is someone to win back from scratch.

Can a customer skip a single subscription delivery on Shopify?

Yes. Skipping is modelled per billing cycle rather than per contract — `subscriptionBillingCycleSkip` takes a single billing cycle as input, and `subscriptionBillingCycleUnskip` reverses it. Shopify’s first-party Subscriptions app lists skip as an action customers can take from their account.

Can customers swap products in a Shopify subscription?

Not through the first-party app, which documents resume, skip and cancel as customer-facing actions along with managing payment method and shipping address. The API supports it — `subscriptionBillingCycleContractEdit` edits the contract contents for a specified billing cycle — so a swap flow means either a subscription platform that ships one or a custom portal built against those mutations.

Do discount save offers reduce churn?

Less than people expect, and they carry a cost. They give margin away to subscribers who would have stayed once they found the skip button, and they teach a segment that threatening to cancel gets a better price. They also do nothing for the most common cancellation reason, which is having too much product already. Offer pause first and the discount last, if at all.

Should failed payments be counted as churn?

Count them, but separately. Involuntary churn from expired or declined cards is a dunning, retry and card-updater problem with an entirely different fix from voluntary cancellation. Blending the two produces a churn number that moves for reasons nobody can attribute, and sends teams redesigning a cancellation flow to solve a payments issue.

NEXT STEP

Free store audit

A senior Shopify engineer reviews your storefront, theme performance and checkout, then sends a prioritised list of fixes.