Recurring revenue depends on a scheduler nobody watches. When it drifts, the symptom is not an error page — it is renewals that quietly did not happen.
Everything that decides whether a subscription business works happens without a visitor on the site.
Every active subscription schedules its own future events. On a large store that is tens of thousands of pending actions, and where they are stored decides whether the site stays quick.
A failed card is retried on a schedule, and a payment provider outage means thousands retrying together. That burst gets absorbed rather than taking the storefront down with it.
Each renewal creates an order, so a subscription store generates orders faster than a normal one and never stops. Order queries are indexed for that growth rather than for a launch-day catalogue.
Dunning and retry sequences run predictably, so a customer whose card expired gets the emails at the right intervals rather than whenever cron caught up.
Subscription state and order history are tied together. Backups cover both, so a restore does not leave customers billed for something the site forgot.
A subscription store fails silently. The site stays up, the shop works, and the only sign is a renewal batch that did not complete a week ago.
The measure here is not page speed. It is whether the scheduler can work through a queue that grows with every subscription you sell.
Subscriptions turn a store into a scheduler with a shop attached, and every row here is about the scheduler.
| Setting | What we do | Why |
|---|---|---|
| Scheduled action storage | Kept in indexed tables rather than the options table | Tens of thousands of pending events in autoloaded options are read into memory on every single request, which slows the whole site down for reasons nobody connects to billing. |
| Retry bursts | Absorbed within plan limits | A payment provider outage causes thousands of subscriptions to retry in the same window, which is the largest concentrated write a store ever sees. |
| Renewal batches | Own execution ceiling, run to completion | A partially completed renewal run means some customers were billed and others were not, which is worse than none of them being billed. |
| Order indexing | Tuned for continuous order growth | A renewal is an order, so a subscription store's order table grows on a schedule forever rather than in proportion to traffic. |
| Dunning sequence | Driven by the platform scheduler | Retry emails at the wrong intervals turn a recoverable expired card into a cancellation. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Move the store across — migration is free, subscriptions and schedules included.