Subscriptions
A customer's ongoing commitment to pay for a product on a recurring basis. Captured as discrete events that drive every subscription report.
A subscription is a customer's ongoing commitment to pay for a product on a recurring basis. SaaSFlow doesn't store subscriptions as a single "active" record — it stores every change to a subscription as a discrete subscription event, and reconstructs the current state by replaying those events.
Where subscription data comes from
| Source | What lands as subscription data |
|---|---|
| Stripe | Every Subscription, SubscriptionItem, and Invoice event becomes a SaaSFlow subscription event. |
| HubSpot | Commerce subscriptions and contracts. |
| Manual | You can add subscription events from the customer's detail page — useful for off-Stripe contracts (annual deals, special pricing). |
A subscription event is always attached to a customer and a plan item (the priced variant under a product).
Event types
| Type | Meaning |
|---|---|
| New | The customer started paying for the first time. |
| Expansion | A paying customer's recurring revenue went up: an upgraded plan, more seats, an add-on, or an additional subscription. |
| Contraction | A paying customer's recurring revenue went down but stayed above zero: a downgraded plan, fewer seats, or one of several subscriptions ending. |
| Churn | The customer cancelled everything. Their recurring revenue dropped to zero. |
| Reactivation | A churned customer started paying again, on the old subscription or a new one. Counts separately from "new" so you can analyse win-back. |
Types follow the customer, not the single subscription. A customer who already pays and starts a second subscription is expansion, not new business.
The Subscriptions report groups events by period and shows the net impact of each type.
Two timestamps per event
Each event carries two dates that matter for analytics:
- Effective time — the date the change took financial effect (when revenue recognition begins / ends).
- Committed time — the date the customer or counterparty committed to the change (when the contract was signed).
These are usually the same date. They differ when there's a gap between booking and go-live — for example, a customer signs an annual contract on Jan 1 that starts Feb 1. The distinction drives the MRR vs CMRR split — see MRR & subscriptions for what that means in the reports.
Editing events
Editing a single event is supported (correct an amount, change the type, attach to a different plan item) but rare in practice. Most events come from integration sync and re-running a full sync is usually the right answer when the underlying data was wrong.
You can also delete an event from the customer's event log if it was clearly created in error — for example, a duplicate after a manual entry that crossed with an integration sync.