Skip to content
All changes

Change your prices without changing what customers bought

Plans, add-ons and credit packs have versions, and you choose who moves to a new one, with a preview first: gains apply at once, losses only after notice. Buyers of a one-time or lifetime add-on keep what they bought or upgrade for the difference.

Added
4
  • BillingWhen you publish a new version of a plan, you decide whether its customers move. You can keep them where they are, move the customers who only gain, or move everyone. Anything taken away comes with 7 to 365 days' notice (30 by default). The console shows who moves, when and at what price before you confirm. A gain applies at once, while a loss is emailed first and applies at the customer's renewal. A move started with an API key or a blueprint (your setup file) waits for a confirmation in the console.
  • BillingAdd-ons and credit packs have versions too, with a history and a draft editor in the console. Customers with a recurring add-on, and auto top-ups, can be moved to a newer version. A buyer of a one-time or lifetime add-on keeps the version they bought, and can upgrade to the one on sale for the difference. A lifetime add-on can also include every later version at no charge.
  • WebhooksYour app hears about each version move through webhook events: subscription.version_move_scheduled, subscription.version_moved, subscription.version_move_withdrawn, version_move.completed and version_move.cancelled. For an upgraded add-on, addon.purchased carries the cause upgrade. When you read a subscription, it includes scheduledVersionChange. Blueprints now cover add-ons, coupons, versioned credit packs and a plan's move setting.
  • ConsoleYou can see billing that went wrong in one place: Billing > Billing health. It lists where a subscription and Stripe disagree, billing operations left part way, plan credits that could not be granted and version moves delayed past their window. In settings, a Billing versioning card lets you turn each part of versioning off for one organization.
Improved
1
  • BillingBehaviour change: to change what a published plan version, pricing group version or add-on sells, publish a new version. Editing it now answers 409 VERSION_REQUIRED, where it answered 400. A published version's trial can no longer be edited, so that needs a new version too. Changing a catalog item or feature that customers hold answers 409 CATALOG_ITEM_SOLD. Deleting a credit pack in use answers 409 CREDIT_PACKAGE_IN_USE instead of 400.

Use what shipped this week

Everything in this release is already in the console and the SDK.

Free plan7-day free trial on paid plansNo credit card required