Some of them only wanted next month off

Why this lands on your desk

Look at the reasons people give when they cancel a subscription box, a coffee plan or a monthly refill. A lot of them aren't about the product. Going away for a month. Still have two bags left. Money is tight until the new year. Moving house.

Those people didn't want to leave. They wanted a break, and the only button on the account page was Cancel. Some of them come back later and sign up again from scratch, if they remember. Some don't.

If your subscription has no pause or skip, adding one is one of the most sensible small projects you can hand a developer. Here's the message to send, then what it's really asking for.

The message

Copy this, change the bits in brackets, and send it.

Hi [name], I'd like to add pause and skip options to our subscriptions. Here's what I'm after: >1. On the account page, next to Cancel, add Skip next delivery and Pause. Cancel stays where it is and works exactly as it does now.2. Pause lets the customer choose how long: [1, 2 or 3 months], or pick a resume date up to [3 months] out.3. While paused, no charges and no shipments. The account page clearly shows "Paused until [date]" with a Resume now button.4. Send a reminder email [7 days] before the first charge after a pause, with links to resume as planned, extend the pause, or cancel.5. In the cancel flow, offer pause once, as a single option on one screen. If they still choose cancel, cancel immediately.6. Track how many people pause, skip, resume and cancel, by month. >Can you tell me what this would take with our current subscription setup, and anything I haven't thought of?

That last line matters. A good developer will have questions, and they're the right ones. Expect a reply with a few of them before any estimate.

What the message is really asking for

Underneath, you're asking for a new state. Today a subscription is probably active or cancelled. Pause adds a third state with a date attached: active, paused until a day, cancelled. Everything that touches subscriptions has to understand that state: billing, the account page, the fulfillment export, the reports, the emails.

You're also asking for honest timing. A reminder before billing restarts is the difference between a customer who's glad they paused and one who is surprised by a charge in February and asks for a refund. Make the reminder plain: when, how much, and how to change it.

It helps to keep skip and pause distinct. Skip is one delivery: the next box doesn't come, the one after does. Pause is a stretch of time with an end date. Customers understand the difference instantly, and offering both means fewer people pick a long pause when they only needed to miss one box.

And you're asking for numbers you probably don't have yet. Pauses that turn back into active subscriptions are good news. Pauses that turn into cancellations at the end are useful too, because they tell you the break wasn't the real reason.

The questions your developer will ask back

Have answers ready for these, or at least a first opinion.

What about an order that's already being packed? If someone pauses the day after the charge, does that box still ship? Usually yes, and the pause starts after it. Say so on the screen.

What happens to their price? If they joined at an introductory price or you've raised prices since, does the old price survive a pause? Decide before someone asks support.

Prepaid plans and gifts. A three-month prepaid plan or a gift subscription can't simply stop charging, because nothing is being charged. Most stores either move the end date out or don't offer pause on those. Pick one.

How long is too long? An open-ended pause turns into a forgotten account. A limit, with a choice to extend from the reminder email, keeps things tidy.

Forecasting. Your warehouse or roaster plans from the number of active subscriptions. Paused subscriptions with resume dates are future demand. Make sure the export they use shows them.

What does support see? Your team needs to see that a subscription is paused, since when, until when, and who paused it. They'll also get asked to pause on someone's behalf by phone or email, so the admin needs the same button the customer has.

Which emails stop? Paused customers shouldn't get "your box ships soon" messages or payment reminders. Check every automated email that keys off the subscription, including the ones a marketing tool sends.

What the platform already does. Many subscription apps already support pause or skip. Your developer may tell you it's a setting plus some work on emails and the account page, which is good news.

Don't make pause a trap

There's a version of this that goes wrong. Pause gets placed in front of cancel, then a discount offer, then a survey, then a "are you sure," and cancelling takes five screens. Customers notice, and they talk about it.

Pause is an offer. The moment it becomes a maze in front of cancel, it stops being one. Show it once. Respect the answer. Making it easy to leave is part of what makes it comfortable to stay, and it keeps the door open for coming back.

Put this into practice

Before you send the message, read your last few months of cancellation reasons, if you collect them. Count how many sound like a break rather than a goodbye. That count, not a guess, is your case for the work.

Then send the message, and ask for the reminder email and the account page wording to be shown to you before launch. Once it's built, pause a test subscription yourself, read every email you receive, and check the fulfillment export on the next ship day to be sure your paused box isn't on it.

Our ecommerce work joins the storefront, billing and fulfillment so changes like this don't break the box that ships on Tuesday. If you want help scoping pause for your store, talk to us.

Related work: Paddle8.