Chargebee Release Notes

Pricing tables sometimes failed to load for a customer whose subscription referenced an item price that had since been archived in the product catalog, even though the subscription itself was still active. This is fixed.

On pricing tables with large catalogs or many price variants, syncing catalog changes could silently miss price updates (for example, a new currency price added to a plan), reporting no differences even though the catalog had changed. This is fixed.

A customer staying on their current plan could add, remove, or change the quantity of an addon, but the checkout button on the pricing table stayed disabled because the change wasn't detected. This is fixed; addon changes on the current plan now correctly enable checkout.

Accepting a pricing table-catalog sync that would remove every remaining item price showed a confusing, technical validation error instead of an explanation. This is fixed; the error now explains that all item prices on the pricing table have been removed from the product catalog and suggests checking your configuration.

If you run Apex test classes on a schedule across your Dev, UAT, and Test environments, tests that touch Chargebee customer records could fail with a error pointing to the managed package. The same tests passed when run manually as an admin or an API user, so the failures showed up only in the automated run and skewed the org health metrics reported from it. Deployments, releases, and day-to-day Salesforce activity were not affected. These test classes now complete successfully in scheduled automated runs, so your org health reporting reflects the true state of your environments.

If a quote's billing or shipping address carried a phone number longer than 20 characters, common with international numbers or numbers that include an extension, the quote synced to Chargebee but failed to sync back to Salesforce, and the sync logs reported a character limit error. The only way around it was to shorten the number in Chargebee, which is not always an option when the number is the customer's real contact detail. The Billing Phone and Phone fields on CB Quote records now accept up to 50 characters, matching the equivalent field on subscriptions, so quotes with longer phone numbers sync without errors.

When you applied a coupon restricted to specific item families, the coupon could be missing from the Salesforce coupon picker even though it was active in both Chargebee and Salesforce and the selected plan belonged to an eligible family. Reps working entirely from Salesforce had no way to apply the coupon to new or existing subscriptions and no indication of why it was unavailable. Eligibility is now matched consistently regardless of how the family name is capitalized, so every coupon that applies to the selected plan appears in the picker.

When you converted a renewal quote from Salesforce for a subscription in a non-renewing state, the resulting subscription could include an extra prorated charge that was not part of the quote. Because the charge appeared only on conversion, it was easy to miss until the invoice was reviewed. Renewal quotes converted from Salesforce now produce charges that match the quote.

When a coupon or manual discount was applied to plan line items on a quote, the discount percentage stopped appearing on the CB Quote Product record for that plan. This occurred on quotes containing both plans and add-ons, regardless of whether the discount was entered as a percentage or a fixed amount, and it also left the discounted unit price out of sync. Since these fields feed downstream dashboards and reports, the gap could affect the accuracy of quote reporting. This is now fixed: discounts applied to plan SKUs sync correctly to CB Quote Products, keeping reporting accurate.

When configuring sync rules for trial subscriptions, the help text in the Chargebee Salesforce integration stated that the opportunity stage would update to the specified stage only when the trial subscription became active. In practice, the opportunity stage updated to whatever stage was set in the sync rules at the time the trial subscription synced, not at activation. This discrepancy caused confusion when validating or troubleshooting sync rule behavior. The help text has been corrected to accurately describe when the update occurs.

When editing a Renewal Quote created after converting a New Subscription quote with Fixed Billing Cycles, the quote editor always displayed in "quote on acceptance" mode, regardless of the intended configuration. This prevented ramps from being added to the renewal quote during editing, blocking a key step in the renewal workflow. The editor now respects the intended configuration, allowing ramps to be added as expected.

When you created an amendment or renewal quote in Salesforce and manually added a charge, the charge event defaulted to On Subscription Creation, an option that does not apply once the subscription already exists. As a result, those charges were attached to the subscription but never invoiced, and your sales team had no easy way to spot the mistake. With this release, the On Subscription Creation option is hidden for amendment and renewal quotes, and newly added charges default to Immediately, so the charges your team adds get billed the way they expect. The option continues to behave as before for brand new subscription quotes.

When you created an amendment quote with a future Amendment effective on date, or with a ramp that started on a future date, clicking Edit on the plan left the screen on a loading state with no error and no way to continue. Your team had to discard the quote and start again, even though all the inputs were valid. You can now open the plan edit screen on these amendment quotes as expected and make changes to the plan, including on quotes that use ramps.

Previously, when you tried to create an amendment quote for a subscription that included a charge configured to bill only at subscription creation, you could run into an error blocking you from completing the quote. This happened because the initial charge's discount reference was incorrectly carried over into the amendment flow, even though that charge no longer applied. You can now create amendment quotes for these subscriptions without interruption.

If your subscription included tiered or stairstep priced items, adding a new plan to a ramp during an amendment quote in Salesforce previously did nothing, even though the same action worked as expected on the initial term or in native CPQ. You can now add plans to ramps on these subscriptions without any issue, giving you full flexibility to build out ramp structures regardless of the pricing model on the subscription.