The subscription engine is the platform component that handles recurring billing: charging cards on schedule, retrying failures, dispatching renewal notifications, and updating feature access on plan changes. Enable it once your packages are defined.
Pre-Flight Checklist
- Stripe (or PayPal/GoCardless) integration is connected and tested.
- Subscription packages are defined with prices and feature sets.
- Email templates for renewal reminders, failed-payment, and cancellation confirmation are reviewed.
- Webhook endpoint
/api/stripe/webhookis receiving events successfully. - Dunning flow is configured (see “Handling Failed Payments”).
Turning On
- Open Site Settings → eCommerce → Subscription Engine.
- Toggle the master switch on.
- Configure renewal reminders — typical pattern: 14 days, 3 days, 1 day before charge.
- Enable prorations on plan change (recommended).
- Set the “grace days” before service suspension on failed payment.
- Save.
Worked Examples
- SaaS launch: Engine on, single 14-day reminder, 5-day grace, prorations enabled — vanilla setup.
- Annual-only product: Reminder cadence 30/14/7/1 days — annual customers need more lead time.
- Donation platform: Engine on, no renewal reminders (donations are silent), 1-day grace before pause.
- Beta period: Engine off — all tenants are on “Beta” feature set free of charge until launch.