Skip to main content
Add-ons are plans that can be purchased alongside a customer’s existing plan, rather than replacing it. They’re used for top-ups, extra feature packs, or supplementary services.
Example
A customer on the Pro plan can purchase a “Storage Add-On” for an extra 100GB/month, or a one-time “Credit Top-Up” of 500 credits.

Setting up

Set addOn: true on the plan:
autumn.config.ts
Push changes with atmn push.

How add-ons work

Without the add-on flag, attaching a new plan replaces the customer’s current plan (within the same group). With the add-on flag:
  • The plan is added alongside the customer’s existing plans
  • Multiple add-ons can be active at the same time
  • Add-ons don’t participate in upgrade/downgrade logic

Balance stacking

When an add-on provides the same feature as the customer’s main plan, the balances stack. Each source is tracked separately in the breakdown array.
Example
A customer’s Pro plan grants 1,000 credits/month. They purchase a one-time top-up of 500 credits. Their total balance is 1,500 credits, tracked as two separate sources.
Autumn uses deduction order to consume shorter-interval balances first (monthly before lifetime).

Purchasing add-ons

Add-ons use the same checkout/attach flow as regular plans:
For prepaid add-ons (like a credit top-up), pass the quantity:
TypeScript

Cancelling add-ons

Cancel an add-on using the same cancel flow:

Common add-on patterns