# How do you change pricing or packaging for existing customers?

By Sean Everett · October 6, 2026

Design the transition around current commitments, customer impact and billing behavior, then verify that the promised change matches the first affected invoice.

Topics: Pricing · Subscription products · Customer experience

## Treat the existing customer base as a separate decision

A new offer can be clear for a first-time buyer and confusing for someone with an established plan. Inventory current prices, discounts, included features, usage units, renewal dates and outstanding quotes. Identify which customer groups would experience a material change.

Chargebee’s documentation provides a useful example: changing a plan price applies to new subscriptions, while existing subscriptions retain their old price unless separately updated. The distinction is a product decision as well as a billing-system behavior.

Decide which existing arrangements should continue and which need a transition. Make the additional value or changed scope understandable. Have the commercial and legal owners establish what current agreements allow and which notice or consent requirements apply before scheduling customer changes.

## Make the timing and invoice consequences explicit

Specify whether a change takes effect immediately, on the next bill date or at renewal. Then examine credits, partial-period charges, discounts, add-ons and quantities. The same headline price can produce different first invoices for customers in different states.

Recurly’s subscription-change documentation separates these timing options and offers invoice previews for immediate changes. Use the relevant platform’s preview or test capability to inspect representative cases before applying a migration broadly.

Check the access experience alongside the invoice. A customer should know when features or allowances change, how the bill was calculated and what choices remain available. Reconcile the account screen, notification and support explanation with the configured behavior.

## Verify the transition through its first affected cycle

Choose test cases from the actual variation in the installed base, including scheduled changes and nonstandard arrangements. Record the expected plan, access and invoice before testing. Do not assume that a successful change to one subscription covers the rest.

Use a controlled rollout with a clear owner for exceptions. Retain the previous state and the intended new state so support can explain discrepancies. Decide in advance how an incorrect transition will be corrected without creating additional surprise charges or access changes.

After the first affected cycle, inspect actual billing and customer questions against the planned behavior. Separate a system defect, an unclear explanation and a rejected value proposition. Each points to a different next action; a completed migration job alone cannot distinguish them.

## Related reading

- [Chargebee: New prices and existing subscriptions](https://www.chargebee.com/docs/billing/2.0/kb/product-catalog/will-a-new-plan-price-affect-the-existing-subscriptions)
- [Recurly: Subscription changes and invoice previews](https://docs.recurly.com/recurly-subscriptions/docs/change-subscription)
- [Explaining an offer at the purchase decision](https://evergences.com/insights/pricing-presentation-purchase-decisions/)

Source: https://evergences.com/insights/existing-customer-pricing-transitions/