The email that arrives every month
'I cancelled on the 3rd and you still took money from me. Please refund immediately.' You check. The renewal charge ran on the 1st, for the box that ships on the 12th. The cancellation on the 3rd stopped next month's charge, as it should. From the subscriber's point of view, though, they cancelled and then saw a payment, and nobody explained that the payment was for a box they have not received yet.
Some of these become refunds, some become angry replies, and a few become chargebacks, which cost a fee even when you have done nothing wrong.
Three dates that subscribers never see together
A subscription box runs on at least three dates: when the card is charged, when changes stop affecting this month's box, and when the box is dispatched. Your team knows these by heart. Subscribers see only fragments.
- The charge appears on a bank statement with your company name and nothing else.
- The cut-off date is mentioned on an FAQ page, not in the subscriber's account.
- The dispatch date moves slightly each month depending on stock arrival.
- The cancel button does not say whether a box is already paid for and on its way.
When the dates are invisible, a correct charge looks like a mistake.
What the confusion costs
Each of these emails takes time to investigate, because someone has to look up the charge, the cancellation time and the dispatch plan before replying. Chargebacks carry a fee and a dispute process. Refunds given to calm things down mean a box shipped for nothing. And subscribers who feel caught out leave reviews that mention it, which puts off people deciding whether to sign up.
There is a reputational side too. 'Hard to cancel' and 'charged after cancelling' are exactly the phrases people search for before trusting a subscription.
How we make the dates visible
- A timeline for each subscriber, built from your subscription app: last charge, which box it paid for, this month's cut-off, planned dispatch date and next charge.
- The timeline appears on the manage-my-box page and in every charge receipt, in plain words: 'This payment is for your October box, which ships around the 12th.'
- The cancel flow shows what happens next before the subscriber confirms: whether this month's box is already paid for and will still arrive, and that no further charges will be taken.
- The bank statement descriptor is reviewed with you, where your payment provider allows changes, so it names the box rather than a company name subscribers do not recognise.
- Support sees the same timeline next to each email, with a draft reply that explains exactly what happened for that subscriber.
- Disputes and chargebacks are logged with the timeline attached, so the evidence is ready if your payment provider asks for it.
| Moment | What the subscriber sees | What support sees |
|---|---|---|
| Charge taken | Receipt naming the box it pays for | Charge linked to the box month |
| Before cut-off | Days left to make changes this month | Cut-off status per subscriber |
| Cancelling | Whether a paid box is still coming | Time of cancellation against charge |
| Dispatch | Shipping notice with tracking | Dispatch date and courier reference |
The wording of what happens when someone cancels is your policy. We make sure it is shown clearly at the moment it matters; your own adviser decides what the policy should say.
A month with the timeline in place
Subscribers who cancel after the charge see, before confirming, that this month's box is paid for and still coming. Most of them are happy with that. Those who still email get a reply that shows their timeline, drafted in seconds. Chargebacks, when they happen, go in with the evidence already attached.
Your team stops re-explaining the same three dates, and the reviews stop mentioning surprise charges.
Signs you have this problem
- You get 'charged after cancelling' emails every month.
- Your cancel flow does not say whether a box is already paid for.
- Receipts do not name the box month the payment covers.
- Support looks up three systems to answer a billing question.
- Chargebacks are fought without a clear record of dates.