Example
A customer on a plan with 1,000 credits/month only uses 600 in January. With rollovers enabled, the remaining 400 credits carry over — giving them 1,400 credits available in February.
Setting up
- CLI
- Dashboard
Add a Push changes with
rollover config to a plan item:autumn.config.ts
atmn push.Rollover configuration
How rollovers work
At the end of each billing cycle, when a feature’s balance resets:- Autumn checks how much unused balance remains
- If rollovers are configured, the unused balance is saved as a rollover balance
- The feature resets to its granted amount, and the rollover is added on top
- If a
maxcap is set, the oldest rollover balances are trimmed first (FIFO) - Expired rollover balances are removed automatically
Viewing rollover balances
Rollover balances appear in thebreakdown array when you retrieve a customer’s balances. Each rollover entry has its own expiry date:
Deduction order
Rollovers are deducted before a customer’s main balances for the same feature. Within the rollover pool, balances are consumed inexpires_at order: soonest-expiring first, with rollovers that never expire going last. Only once all rollover balances are drained does Autumn fall through to the regular deduction order over the main entitlements.
This means carried-over balance is used up before fresh monthly allocation, so rollovers you’re about to lose to expiry get spent first.
Example
A customer has a 1,000 credits/month balance that just reset, plus a 400 credits rollover from last month. They use 300 credits.
Autumn deducts all 300 from the rollover, leaving 100 credits in rollover and the full 1,000 credits monthly untouched.
Rollovers are only available on
consumable features with a reset interval. Non-consumable features (like seats) don’t reset and therefore don’t support rollovers.