On a subscription, cancellation is rarely a definitive rejection. A customer goes on holiday, has a difficult month, still has three unopened boxes at home. In those situations they do not want to stop, they want to suspend. Without a pause option, they cancel.
Why a pause beats a cancellation
The economic difference is clear and easy to measure.
A subscriber who cancels is lost: winning them back will take a marketing action, at an acquisition cost close to that of a new customer. A paused subscriber stays in your base, keeps their saved payment method, and resumes without friction.
Resumption happens in a significant share of cases, especially when the pause has an announced end date and a reminder before it resumes.
A second, less obvious effect: offering a pause improves the perception of the service even among those who never use it. A customer who knows they can suspend commits more easily at the start.
The rules to define
Four parameters to settle before implementation.
Maximum duration. One to three months depending on your cycle. An unlimited pause is no longer a pause, it is a cancellation that will not say its name and that pollutes your metrics.
Frequency. How many times a year can a subscriber suspend? Twice is a reasonable benchmark. With no limit, some subscribers alternate one active month and one paused month, which amounts to halving the price.
Notice. The pause must be requested before the next due date, with a few days of margin. A request the day before the charge creates a technical and accounting problem.
Resumption. Automatic on the planned date, or on customer action? Automatic is preferable: it avoids subscribers who stay paused through forgetfulness, and it is more honest about the commitment made.
DataFirefly Subscriptions — Subscriptions and Stripe Recurring Payments for PrestaShop 8 & 9The subscription module for PrestaShop 8 and 9: Stripe card-on-file, dunning, self-service customer area.€169.00
The effect on billing
A technical point to handle properly, on pain of disputes.
A pause shifts the due date, it does not cancel it. A monthly subscriber who suspends for two months sees their next billing pushed back by that much, and their anniversary date shifts accordingly.
Two things to check in the implementation. No charge must occur during the suspended period, which means the payment platform has to be informed and not just your shop. And the payment method must remain valid: a three-month pause can span a card expiry, hence the value of a check on resumption.
On a subscription with a minimum term, also state whether the pause extends that term. Both answers are defensible, the absence of an answer is not.
The customer-side interface
Three elements in the customer account.
A suspend button visible in the subscription detail, at the same level as modification and cancellation. Burying it in a submenu amounts to not offering it.
A choice of duration among short options: one month, two months, three months. A free date picker complicates the decision without adding much.
A clear summary before confirmation: suspension date, resumption date, next charge, and what stays accessible during the pause.
That last point deserves attention on subscriptions that give access to content: the customer must know whether they lose access during the pause or keep it. Both models exist and the answer must be explicit.
The pause offered at cancellation
This is where most of the effect comes from, and where the most care is needed.
A customer who clicks cancel can be offered the pause as an alternative. That is legitimate: you are showing them an option they may not have known about.
It must never obstruct cancellation, though. The principle is clear: cancelling online must stay as simple as subscribing. Offering an alternative is acceptable, on three conditions.
A single alternative screen, not three successive steps.
The cancel button stays visible and at the same visual level as the pause button. A discreet link facing a large coloured button is an obstruction.
No obligation to make contact. Redirecting to a form or a phone number to cancel, while allowing a pause in one click, is exactly what consumer rules target.
The right implementation looks like this: a screen with two equivalent buttons, one “suspend my subscription”, the other “cancel permanently”, with one sentence each on what it implies.
What the pause reveals
Collect the reason at the moment of suspension, with a short list: temporary absence, enough stock at home, budget constraint, other.
These reasons are richer than cancellation reasons, because the customer is not in a breaking-off mindset and answers more sincerely.
The “enough stock” reason is the most instructive: it signals that your delivery frequency is too fast for that customer. Offering a change of frequency rather than a pause then treats the cause.
Measuring
Three indicators.
The resumption rate after a pause, which validates or invalidates the whole thing. Below 50%, your pause mainly delays cancellations.
The cancellation rate before and after it goes live, watching that it actually falls rather than turning into pauses that never resume.
The average subscriber lifetime, which is the final figure. If it rises, the mechanism creates value; if it stalls, you have moved a problem without solving it.
The Subscriptions module for PrestaShop handles this on PrestaShop 8 and 9: suspension from the customer account with a limited duration and automatic resumption, due dates shifted on the payment platform side, reason collection and a cancellation path that stays accessible without obstruction.