Subscription Software Where Churn Is Something You Can Act On.
A subscription business is won and lost on two moments: the card that failed and the customer who went quiet. Here a declined renewal is retried and followed up automatically, and the rest is a flow that fires within minutes rather than a report you read on Monday.
What Recurring Revenue Needs
The signup is the easy part. Everything here is about month four.
Plans
Recurring On The Variant
Cards
Stored Properly
Recovery
Failed Payment Is Handled
Retention
Journeys, Not Blasts
Boxes
Curated Contents
Truth
Revenue On One Record
Involuntary Churn Is The Winnable Kind.
A meaningful share of subscription cancellations are not decisions. They are expired cards, replaced cards and declines nobody followed up quickly enough.
Here a declined renewal falls back to the customer's other saved cards before it counts as failed, and when every card is declined the customer is emailed straight away with a way to update it, then retried 2 days later. That is a retention lever most stacks technically have and practically never wire up.
And What You Should Check.
Subscribers skip, pause, swap and cancel from their own account, and every delivery is a real order against real stock: a sold-out delivery is skipped with no charge, with a heads-up email before the day, rather than billed and refunded.
Two things to check before you plan a launch. Renewals charge a card saved with Authorize.net, so that has to be your processor today. And the account pages are built in your storefront against the SDK rather than dropped in as a hosted portal, so budget for those screens.
It Reads From The Same Records
Questions People Ask
How do subscriptions work here?
A recurring plan attaches to a product variant and a stored payment profile sits against the customer, so renewals run without asking anybody to re-enter a card. The subscription, the orders it produces and the customer are all one record.
What happens when a card fails?
A renewal tries the subscription's card, then the customer's other saved cards. If every card is declined, the customer is emailed a link to update their card and the charge is retried 2 days later; a second failure stops the subscription and emails them a way to re-enable it. Involuntary churn is usually the largest recoverable slice of cancellations and it depends entirely on speed.
Can subscribers pause or swap their box themselves?
Yes. From their account, subscribers can skip the next delivery, pause and resume, change flavor, size, quantity or frequency, update their card, cancel, and subscribe again, with changes applying from the next order. Those actions are storefront API and SDK calls, so the account pages live in your own storefront and look like the rest of it.
Can we build retention sequences?
Yes, as flows with delays and branching on real events: welcome, second box, a nudge at month three, win-back after a cancellation. Every run keeps a per-step record, so a sequence that quietly stopped is something you find rather than something a customer reports.
Where do retention numbers come from?
The orders themselves, because the subscription, the order and the traffic share a database. That is a different thing from an analytics tool's idea of your recurring revenue, and the two rarely agree.
Start With The Failed Card.
Sign up, put a subscription on a variant, and see how a declined renewal is handled before anything else.