Subscriptions in an online store: what the apps do and what breaks
How subscriptions work on the platform, what a subscription app actually handles, and the operational and legal details that decide whether they pay.
The short answer
Subscriptions on the platform run on native subscription contracts billed through the platform’s own checkout; an app sits on top to sell the subscription on the product page, manage schedules, give customers a portal, retry failed payments and report. The model pays when the product is genuinely consumed on a rhythm and the customer can adjust that rhythm easily. It breaks in predictable places: failed payments not retried intelligently, customers who cannot skip or pause so they cancel, stock not reserved for renewals, tax and shipping recalculated wrongly on renewal, and churn that nobody measures until revenue dips. Consumer law in many markets adds requirements on disclosure, cancellation and reminders, and the portal is where those are met or missed.
What the platform does and what the app does
| Concern | Platform | App |
|---|---|---|
| Subscription contract and recurring billing | Native, through the checkout | Creates and manages contracts |
| Selling widget on the product page | Yes, and its weight matters | |
| Schedules, frequencies, discounts for subscribing | Contract supports | Interface and rules |
| Customer portal: skip, pause, swap, change address or frequency, cancel | Yes, the most important feature | |
| Failed payment retries and reminders | Billing attempts | Retry schedule and emails |
| Stock reservation for renewals | Partly | Depends on app and configuration |
| Tax and shipping on renewals | Recalculated | Must be configured correctly |
| Reporting: active, churn, lifetime value | Basic | Better in the app or a reporting tool |
Setting up subscriptions that last
- Choose products that are consumed on a rhythm; do not force one-off products into subscriptions.
- Choose the app for the portal, the dunning and the page weight, and measure the product page before and after installing it.
- Offer flexibility: skip, pause, change frequency, swap product, update address and card, cancel, all self-service.
- Disclose clearly before subscribing: price, frequency, term, cancellation. Make cancelling as easy as subscribing.
- Configure retries and reminders, and test a failed payment end to end.
- Reserve or forecast stock for renewals, and reconcile with the back office.
- Test tax and shipping on a renewal for each market.
- Measure active subscribers, voluntary and involuntary churn, and revenue recovered by dunning, monthly.
Measuring whether it pays
Active subscribers and their monthly value. Voluntary churn: people who cancelled, and why, from the cancellation reasons in the portal. Involuntary churn: failed payments not recovered, and the recovery rate. Average subscription length. Revenue per subscriber compared with the same customers’ one-off buying before. Those numbers, monthly, say whether the model works for your products and where to adjust frequency, portal options or dunning.
What this means for you
Run subscriptions on the native contracts with an app chosen for its portal, dunning and page weight. Offer real flexibility, disclose clearly, make cancelling easy, configure retries, reserve stock, test renewals per market and measure churn monthly. Subscriptions pay when they fit the product and respect the customer; the app is the smaller part of that.
Frequently asked questions
Do we need an app for subscriptions?
Yes, in practice: the platform provides the underlying subscription contracts and billing through its checkout, and an app provides the selling widget, schedules, the customer portal, dunning for failed payments and reporting. Choose the app for its portal, its retry logic and its weight on the product page, in that order.
What causes subscription churn that we can control?
Failed payments not recovered, inability to skip or pause so people cancel instead, deliveries that arrive too often or too seldom for the product's real consumption, and surprises in price or shipping. A flexible portal with skip, pause, swap and frequency change, plus good retry and reminder emails, addresses most of it.
What must we tell customers legally?
Clearly, before they subscribe: the recurring price, frequency, minimum term if any, how to cancel and how easily, and renewal reminders where required. Requirements differ by market and are tightening; check them for each country you sell to with an advisor and make cancellation as easy as signing up.
Sources
- EUR-Lex: Directive 2011/83/EU, Article 6 (information requirements, including duration and termination) (accessed 2026-09-14)
- Shopify Help Center: Subscriptions (accessed 2026-09-12)