The default: nothing happens to them
Publish the change and it reaches new subscribers only. Every existing customer stays on the version they received, indefinitely. You don’t opt into that. It’s what happens if you do nothing special, because the alternative — silently repricing people who already paid — is the kind of thing you can’t undo once they notice.Making the change
1
Edit the plan
Change what it includes: flip a feature off, raise a limit, add something new.
2
Publish it as a new version
From that moment, anyone subscribing gets the new terms.
3
Verify against a real customer
Check an existing subscriber and a fresh one for the same feature. They should disagree — that’s
the versioning doing its job.
Moving someone forward, on purpose
Two things move a customer onto current terms, and both are deliberate:- They change plan. Switching plans re-attaches the subscription to the target plan’s current version — including anything that changed since they first subscribed.
- You migrate them. From the dashboard, when you’ve decided the old terms should end.
If the feature is metered
A price is immutable on its amount at the provider, so changing a rate is always “create a new one and point the entitlement at it”. Kerne does that when you replace a rate. Customers already subscribed keep the rate they signed up on. They move onto the current one when their plan changes — same rule as everything else. See Meters & usage.One thing that catches people
An add-on rides the subscription rather than sitting beside it, so a plan change carries it along. If an add-on exists on one plan and not the other, switching plans ends it. Model an add-on you intend to survive a plan change as a feature present on every plan, with a different allowance.Next
Offers & versions
Why versions exist, and what they pin.
Handle customer exceptions
When one customer needs terms your catalog doesn’t sell.

