Selling Subscriptions: The Sale Is Just the Beginning
- 100 Subscribers – And Suddenly Things Get Complicated
- A Subscription Isn't Just an Order on Repeat
- Failed Payments: What Actually Happens
- Not Every Renewal Is Charged Automatically
- Not All Cancellations Are the Same
- What Does This Mean for a WoltLab Community?
- Different Billing Periods for Different Business Models
- Recurring Revenue Isn't Guaranteed Revenue
- Which Payment Methods Work for Automatic Subscriptions?
- Why I Didn't Want the YoureCom Shop to Be Just Another Download System
- Frequently Asked Questions About Selling Subscriptions
- Conclusion: The First Sale Is Just the Beginning
A customer visits your website, chooses a subscription, and pays. The order is complete, the customer is happy, and you have a new source of recurring revenue.
Sounds pretty good so far.
But what happens four weeks later?
What happens when the next payment fails? When a customer cancels even though their minimum contract term hasn't ended? Or when a renewal needs to be paid by invoice instead of being charged automatically?
That's when a simple sale turns into an ongoing management process.
And that's where you find out whether your shop can merely sell subscriptions or is actually equipped to manage them over the long term.
100 Subscribers – And Suddenly Things Get Complicated
Let's imagine someone running an online community.
They offer members additional features for €4.99 per month, such as access to exclusive forum sections or special membership benefits.
The first ten subscriptions sell quickly. Then there are 30, and eventually 100.
On paper, that's €499 in monthly recurring revenue – provided all subscriptions remain active and every payment goes through.
But those 100 customers don't necessarily share the same billing date. One subscribed on the 3rd of the month, another on the 17th, and someone else on the 28th.
Add different payment methods, cancellations, and the occasional failed charge, and things start getting complicated.
Anyone managing all of this manually will eventually discover that recurring revenue also means recurring work.
And that probably wasn't the plan.
A Subscription Isn't Just an Order on Repeat
From a technical perspective, a subscription has its own lifecycle. It begins when the contract is created, moves through billing periods, and eventually ends through cancellation or another termination reason.
Several things need to work together:
- When is the next payment due?
- Which payment method is on file?
- What is the minimum contract duration?
- What cancellation notice period applies?
- How long is the customer entitled to use the services they've paid for?
- What happens if a renewal isn't paid?
That last question is particularly important.
A subscription with a failed payment isn't the same as one that has been cancelled normally. The system needs to recognize that difference.
Failed Payments: What Actually Happens
Back to our community.
Customer number 47 has replaced their credit card but forgotten to update their payment details.
The next charge fails.
Now what?
The YoureCom Shop subscription extension automatically retries failed charges. By default, it allows three payment attempts in total, spaced five days apart.
Both values can be configured globally and overridden for individual subscription offers.
So one failed charge doesn't immediately mean the subscription is over. The customer is notified and has an opportunity to resolve the issue.
Since version 6.2.4, the system also displays the reason for the most recent failed payment attempt, provided the payment provider supplies that information.
Customers with a stored payment method can update it themselves. For example, they can replace an expired credit card without requiring the shop operator to intervene.
What Happens When All Attempts Fail?
This is where things get interesting.
The setting subscription_auto_terminate_on_payment_failure is enabled by default.
If all scheduled payment attempts fail, the subscription is terminated automatically and immediately, with the termination reason recorded as a payment failure.
Any remaining time in the regular subscription period is no longer granted.
That's an important distinction from a normal cancellation.
For our community operator, it means they don't have to monitor every failed payment attempt or manually terminate subscriptions.
At the same time, they need to understand what the automation actually does.
After all, automation is only useful when you understand its consequences.
Not Every Renewal Is Charged Automatically
When people think about subscriptions, they usually think of credit cards or other payment methods that are charged automatically at regular intervals.
But some operators prefer to handle renewals through invoices.
The subscription extension supports that approach too.
This is particularly relevant when a customer doesn't have a payment method on file that can be used for future automatic charges.
The process is different, though.
With an automatic charge, the system attempts to collect the payment itself.
With an invoice-based renewal, the process depends on whether the invoice gets paid.
Both approaches can lead to a subscription being renewed, but they involve different payment workflows.
That also means payment method self-service doesn't apply equally to every subscriber.
Someone paying by invoice doesn't necessarily have a stored credit card they can simply replace.
Not All Cancellations Are the Same
A customer wants to cancel their subscription.
Sounds straightforward.
In practice, though, several questions come up.
Is there a minimum contract duration? Does a cancellation notice period apply? And is this even a regular cancellation?
The subscription extension takes the minimum duration and cancellation notice period configured for each offer into account.
Here's an example:
A customer signs up for a subscription with a twelve-month minimum term and a one-month cancellation notice period.
After three months, they decide to cancel.
That doesn't mean the contract ends immediately.
The system calculates the earliest possible termination date based on both conditions and aligns it with the appropriate end of a billing period.
An extraordinary cancellation follows different rules.
It's handled as a separate cancellation type and may require approval from the responsible team.
So it isn't simply treated as a cancellation at the end of the next billing period.
For operators, this distinction matters.
Knowing that a customer has cancelled doesn't necessarily tell you when their subscription will actually end.
What Does This Mean for a WoltLab Community?
If you run a community using WoltLab Suite, you already have a user management system in place.
The YoureCom Shop manages products, orders, and customers within that same environment, while the subscription extension adds recurring sales models.
Additional extensions can connect this foundation to community features.
For example, a paid membership might grant access to specific permissions or user groups.
There are two responsibilities that need to remain clearly separated:
Subscription management determines the contractual and payment-related status.
The relevant integration applies the resulting permissions within the community.
This distinction matters because a failed payment, a regular cancellation, and an extraordinary cancellation can have different consequences.
A system that treats all three situations identically would quickly run into problems.
Different Billing Periods for Different Business Models
Not every subscription should renew based on the individual purchase date.
A software provider might prefer monthly billing starting from the subscription date.
An association, on the other hand, might want fixed annual membership periods.
Version 6.2.3 introduced fixed billing periods to the subscription extension.
This allows subscriptions to follow a defined billing period regardless of when the customer originally subscribed.
Billing based on the individual subscription date remains available as well.
It's not the kind of feature that looks particularly exciting on a sales page.
But for operators working with fixed contract periods, that flexibility can make all the difference.
Recurring Revenue Isn't Guaranteed Revenue
Subscriptions make revenue easier to predict.
But predictable doesn't mean guaranteed.
Customers cancel, invoices remain unpaid, and automatic charges can fail permanently.
One important metric is Monthly Recurring Revenue (MRR).
It represents the calculated monthly recurring revenue generated by active subscriptions.
Here's an example:
50 customers each pay €10 per month.
That's €500 in MRR.
Another ten customers subscribe, increasing the figure to €600.
If five subscriptions subsequently end, the calculated MRR drops to €550.
The YoureCom Shop subscription extension provides corresponding statistics and converts different billing intervals into monthly values.
However, it's important to distinguish calculated recurring revenue from payments that have actually been received.
Having €500 in MRR doesn't necessarily mean you have €500 in your bank account.
Which Payment Methods Work for Automatic Subscriptions?
A payment method that works for a one-time purchase isn't necessarily suitable for recurring charges.
The payment provider must support storing a payment method and using it for future transactions.
In the YoureCom Shop, the shop_offsession_payment_methods setting determines which payment methods are available for these charges.
By default, Stripe and PayPal Checkout are configured.
For PayPal, Reference Transactions must be enabled for this type of recurring payment.
So just because PayPal is available as a payment option in your shop doesn't automatically mean recurring charges will work.
The payment provider's requirements must also be met.
That's why you shouldn't judge a subscription system solely by the payment logos displayed at checkout.
What matters is which payment workflows it actually supports.
Why I Didn't Want the YoureCom Shop to Be Just Another Download System
When I started developing the YoureCom Shop, my goal wasn't simply to put a price tag and a Buy button on products.
There are already plenty of solutions for that.
What interests me is what happens after the purchase.
How are orders managed? What happens with licences, updates, and support entitlements? How do recurring payments work?
And what happens when something doesn't go according to plan?
Subscriptions are a good example of why these questions matter.
A successful payment is easy enough to understand.
Things get interesting when a charge fails, an invoice remains unpaid, or a customer cancels a subscription with a minimum contract term.
That's why the subscription extension isn't just another Buy button.
It extends the shop's existing management features with subscription contracts and payment workflows.
Of course, not every website needs every feature.
Someone selling individual downloads has different requirements from an operator managing several hundred active memberships.
What matters is choosing a system that fits your business model.
Frequently Asked Questions About Selling Subscriptions
Can I Sell Subscriptions on My Own Website?
Yes. You need a shop system that supports recurring payments and the associated contract management.
With the YoureCom Shop and its subscription extension, you can offer subscriptions directly on a WoltLab-based website.
How Many Times Will a Failed Payment Be Retried?
By default, the system allows three payment attempts in total, spaced five days apart.
These values are configurable and can be overridden for individual subscription offers.
What Happens When All Payment Attempts Fail?
With the default subscription_auto_terminate_on_payment_failure setting enabled, the subscription is terminated immediately due to the payment failure.
Any remaining time in the regular subscription period is no longer granted.
Can Customers Cancel Their Subscriptions Themselves?
Yes. Customers can cancel subscriptions through the subscription management section of their user account.
The effective termination date depends on the minimum contract duration and cancellation notice period.
Extraordinary cancellations may require approval.
Can Subscriptions Be Renewed by Invoice?
Yes. Renewals can also be processed through an invoice-based workflow.
This differs from automatically charging a stored payment method.
Can I Use PayPal for Recurring Payments?
That depends on the PayPal integration and the capabilities enabled for your merchant account.
In particular, automatic future charges require support for Reference Transactions.
Conclusion: The First Sale Is Just the Beginning
From a customer's perspective, subscribing usually takes just a few minutes.
For the operator, the real work starts afterwards.
Payments need to be processed, cancellation notice periods respected, and contract durations managed.
And sometimes, a payment simply doesn't go through.
That's why the question you should ask before introducing subscriptions isn't just:
How can I offer recurring payments?
It's also:
What happens when my customers don't pay, cancel their subscriptions, or change their payment methods?
Those are exactly the situations I developed the YoureCom Shop subscription extension to handle.
Not because every operator needs a complicated shop system, but because managing recurring payments should create as little additional work as possible.
After all, you'd probably rather spend your time working on your website, your products, or your community.
Instead of figuring out why customer number 47's credit card has expired.
Learn more: YoureCom Shop – Subscriptions