August 2026

Decommission a subscription from the Billing app

You can now decommission a subscription directly from the Cancel Subscription flow in the Chargebee Billing interface. Previously, this was only possible through the API. Decommissioning keeps a cancelled subscription available for audit and history, but blocks every further action on it except deletion, including reactivation. You can also filter your subscription list to find subscriptions that have been decommissioned.

Why is this important?

Your team can now retire a subscription for good directly from the cancellation screen, without needing an engineer to call the API. You can also separate decommissioned subscriptions from the cancelled ones when you search, report, or clean up your subscription list, making it easier to find subscriptions you've permanently retired after cancellation while keeping their history for audit and reference. See Subscription Cancellation for how decommissioning works.

How can you use it?

To decommission a subscription:

1. In your Chargebee Billing site, open the subscription and click Cancel Subscription.
2. Choose when to cancel it.
3. Turn on Decommission this subscription.
4. Complete the cancellation.

To control whether this option shows up for your team, go to Settings > Configure Chargebee > Billing LogIQ > Customers & Subscriptions > Subscription cancellation and use the Show decommissioned toggle (on by default).

Multi-language support for cancel pages, offers, and surveys (EAP)

Chargebee Growth now supports multi-language cancel and offer experiences. You can add translations for cancel pages, loss aversion cards, offers, and survey reasons, all without duplicating your plays, audiences, or other content objects.

Why is this important?

You can now serve the right language to each subscriber automatically, based on their billing locale or a value you pass in via API or Chargebee.js, instead of building and maintaining a separate play per language.

How can you use it?

Multi-language is currently in early access; contact Chargebee Growth support to have it enabled for your account.

1. Go to Settings > Languages and add the languages you want to support. English is always the primary language and the fallback when a translation is missing.
2. Under Language resolution, choose where Growth reads a subscriber's language from: Billing (for example, customer.locale) or API / Chargebee.js.
3. Set a matching rule for each language to map incoming locale values (for example, en-US vs. en) to the right language.
4. Open each cancel page, offer, loss aversion card, or survey reason, enable the language variant, and translate the copy.
5. Add the content to a play as usual. Growth automatically routes each subscriber to the matching language variant, falling back to the primary language if no match is found or a translation is incomplete.

Pricing tables aren't included in multi-language support.

Introducing Renewal Optimization (EAP)

Renewal Optimization is now available in Chargebee Growth. It lets you update subscription pricing and packaging across large sets of subscriptions, without writing code. Migrate subscribers to a new plan, adjust plan or addon prices, align subscriptions to your current catalog pricing, and more through a guided wizard.

Why is this important?

Growth, monetization, and billing operations teams can now run price increases, catalog migrations, and plan consolidations directly, instead of relying on custom scripts or engineering time. Common use cases include aligning existing subscriptions to a new catalog price after a price increase, migrating customers from legacy per-unit pricing to tiered or volume pricing, applying annual or semiannual price increases, and migrating subscribers off a legacy plan.

How can you use it?

Renewal Optimization is currently in early access; contact Chargebee Growth support to have it enabled for your account.

1. In your Chargebee Growth site, go to Renewal Optimization in the left navigation and click + Create Renewal Optimization.
2. Define your audience: Build filter rules (property, operator, value) to select the subscriptions to target. Paused, cancelled, advance-invoiced, and contract-term subscriptions are excluded automatically.
3. Choose an action: Plan Price Adjustment, Plan Change, Addon Price Adjustment, or Align to Catalog. Each optimization supports one action type; create separate optimizations for more than one.
4. Configure how changes apply: Immediately or at the next renewal, with or without proration, and how to handle subscriptions that already have a scheduled change (skip, discard, or retain existing schedules alongside the new change).
5. Preview then publish: Review a simulation of the exact changes for your audience, export the analysis as a CSV if you need stakeholder sign-off, then publish. The optimization runs in the background, and results show counts of subscriptions modified, skipped, and failed, with a per-subscription audit log.

A published optimization can't be reversed, so always review the Preview Changes tab before publishing.

Self-serve preferences for RevenueStory reporting settings

RevenueStory now exposes some of its data source settings as user-configurable preferences, accessible from a new Preferences section.

Why is this important?

Settings like week formatting previously required you to contact Chargebee Support. These are now user-configurable at runtime and take effect immediately, without a deploy or manual intervention.

How can you use it?

In your Chargebee Billing site, go to RevenueStory > Preferences to view and update details such as Week Formatting, Exclude Currency Symbol in Exports, and so on.

Void uncaptured payments and invoices in one go

You can now void an outstanding delayed-capture authorization and resolve its associated invoice simultaneously, either from the Chargebee UI or using the Void Authorization Before Capture API.

Why is this important?

You can now void or write off an invoice directly while an authorization is active. Chargebee automatically releases the payment hold and resolves the invoice in one step, via the app or API.

• Void or write off the invoice: Chargebee automatically releases the gateway hold first, then closes the invoice in the same step.
• Release the hold only: Cancels the payment authorization while leaving the invoice open.

How can you use it?

The invoice must have an outstanding scheduled-capture authorization.

1. Open the invoice while the transaction is authorized (not captured).
2. Use Void or Write off. Chargebee shows an authorization notice with the linked transaction IDs, voids the authorization, then voids or writes off the invoice. On the payment card, Void authorization voids the transaction only. From the API, call Void authorizations before capture with invoice_action set to void, write_off, or leave_open.
3. Confirm the authorization transaction is voided. leave_open voids the transaction only and leaves the invoice open.

For parameters and samples, see Void authorizations before capture.

Delayed capture for PayPal Commerce

You can now configure delayed capture for card payments processed through PayPal Commerce (Advanced Credit and Debit Cards). Instead of charging instantly at checkout, Chargebee allows you to authorize the payment first and capture the funds after a custom delay.

Why is this important?

Holding funds before final capture gives you greater operational control over order processing while lowering merchant costs:

• Flexible Fulfilment Windows: Hold authorized funds while completing stock checks, manual fraud reviews, or digital asset delivery.
• Reduced Refund and Chargeback Fees: Avoid unnecessary transaction fees and chargebacks caused by immediate captures on orders that are later canceled.
• Automated Payment Voiding: If an order is canceled or paid through another method before the capture window ends, Chargebee automatically releases the payment hold.
• Global Currency Support: Applies across all currencies supported by your PayPal Commerce integration.

How can you use it?

Prerequisite: Contact Chargebee Support to get Delayed Capture enabled for your site if Capture Settings is not visible on your PayPal configuration page.

1. In the Chargebee Billing app, go to Settings > Configure Chargebee > Payment Gateways and select PayPal.
2. Under Advanced Configurations, open Capture Settings and set Capture Type to Manual Capture.
3. Choose a Capture Delay of up to 7 days, then select Apply and Confirm.

Note: Delayed capture applies only to customer-initiated ACDC card payments. It is not for PayPal wallet or Venmo payments, and not for merchant-initiated charges such as renewals, retries, or Dunning. Those still capture immediately.

For delay options, invoice capture-or-void behavior, and limitations, see Capture settings for PayPal Commerce.

"Billing mode" is now "Proration mode"

The Billing mode setting is now called Proration mode, to better reflect what it actually controls: whether prorated charges and credits for your customers' subscription changes are calculated in calendar days or to millisecond precision. You'll see a banner in Configure Chargebee > Billing LogIQ > Billing & Invoices > Proration mode confirming that your existing settings haven't changed.

The old name suggested this setting controlled how you bill customers overall. Proration mode makes it clear that it only affects proration.

Enable free-text input on any survey reason with a custom placeholder

You can now turn on a free-text input for any exit survey reason, not just the built-in "Other", and set a custom placeholder for it.

Why is this important?

This lets you collect detailed feedback on the specific reasons that matter to you, instead of only on "Other".

How can you use it?

In the funnel designer's reason editor, turn on Enable text input for a reason and set its placeholder text. The "Other" reason keeps its text input enabled by default and remains the only reason where text entry is mandatory to submit.

Override cancel timing per experience

You can now override cancel timing for a specific cancel experience, instead of relying only on your global cancel-timing setting.

Why is this important?

If different cancel experiences need different cancellation policies, you no longer need to change your global default to accommodate one funnel.

How can you use it?

In a cancel experience's configuration, use the new Cancel Timing (Chargebee) section. It defaults to Use global default, and you can override it with the same options available at the global level. Clearing the override returns the experience to the global default.

Schedule quantity discounts on Subscription Ramps

You can now apply quantity discounts to per-unit items when creating or updating a Subscription Ramp. It works alongside the existing fixed-amount and percentage discount types, and you can set its duration to one-time, forever, or limited period.

Why is this important?

• Automate negotiated deal terms across ramp stages: Quantity discounts grant a set number of free units without altering the overall billed quantity, a common requirement in custom B2B contracts. You can now schedule these terms directly within your ramp workflows.
• No manual interventions: Schedule unit discounts to trigger automatically on future ramp dates without requiring manual updates when the term takes effect.

How can you use it?

From the Chargebee Billing app

1. Open the subscription you want to add the Quantity discount to.
2. Click Create Ramps.
3. On the Create Ramps modal, click Add manual discount. Select the Discount type, enter the quantity, and choose the duration.

From the API Pass the new discounts_to_add[quantity] parameter on the Create a ramp and Update a subscription ramp endpoints. When you set a quantity, discounts_to_add[type] is automatically set to offer_quantity.

Correct billing and shipping addresses on AvaTax for Sales invoices

If you've configured taxes on your Chargebee Billing site, you can now update the address fields of an invoice, as long as the change doesn't affect the tax already calculated for it.

Why is this important?

You can now fix address typos on invoices taxed through AvaTax for Sales without voiding or regenerating the invoice, preserving its tax details.

How can you use it?

No additional setup is required. For AvaTax for Sales, you can update Address Lines 1-3, City, State, and Zip when:

• The Avalara document is successful and uncommitted.
• A tax re-estimate for the new address matches the tax already calculated on the invoice.

Country and the VAT Number fields can't be edited, since they affect the calculated tax.

Control customer data syncs from Chargebee to NetSuite

You can now turn off outbound customer record updates from Chargebee Billing to NetSuite using the new Sync Updates to Customer setting.

Why is this important?

When customer data is managed directly in NetSuite or imported into Chargebee via external middleware, syncing updates back to NetSuite can overwrite master records. This control ensures your primary customer system remains untouched.

How can you use it?

In your Chargebee Billing site:

1. Go to Apps > NetSuite > Configure Advanced Sync Rules.
2. Turn off Sync Updates to Customer.
3. Click Save to save your changes.

RevenueStory sync now skips faulty records

RevenueStory's data sync is now more agile and transparent. When individual records contain errors, RevenueStory skips those records and continues syncing the remaining valid data, rather than halting the entire sync.

Why is this important?

Previously, a single invalid record could stop the entire sync, leaving the dashboard showing outdated data for a longer duration without a clear explanation. Sync now continues uninterrupted, and administrators receive a clear, actionable view of which records were skipped and why.

How can you use it?

In your Chargebee Billing site, go to RevenueStory to view the following details:

• Sync status for the last 15 syncs, categorized as Healthy, Warning (some records skipped), or Error (sync stopped).
• Skipped Records details, including the specific reason each record was skipped and whether it requires action on the merchant's part.
• A status banner on the dashboard indicating when data is not fully up to date.

Skipped records are automatically retried every 15 minutes.

South Asian currency numbering format in RevenueStory

Currency values in RevenueStory are now displayed using South Asian digit grouping 3:2:2 (for example, 10,00,000) for supported currencies, aligning monetary figures with regional conventions.

Why is this important?

Chargebee Billing previously formatted all currency values using the international digit grouping convention 3:3 (for example, 1,000,000). For customers operating in South Asian markets, this format does not align with the local numbering convention, making large monetary values harder to read and reconcile.

This formatting is applied automatically to currencies configured through a backend setting. By default, this includes:

• Indian Rupee (INR)
• Bangladeshi Taka (BDT)
• Bhutanese Ngultrum (BTN)

How can you use it?

The updated format applies automatically across Chargebee Billing and RevenueStory Dashboards, Report Explorer, Report Builder, and covers both compact notations (K, L, Cr) and full comma-separated figures. Currencies not included in this configuration continue to use the existing international grouping.

List gateway tokens for a payment source

You can now list gateway payment method tokens for a payment source.

Why is this important?

Use this for vaulting and backup-gateway merchant-initiated transactions (MIT), where one customer card can map to more than one gateway token.

• Support and integrations can see which gateway reference is active.
• That matters for card-on-file renewals in any region once you route the same card across more than one gateway, including backup-gateway MIT.

How can you use it?

Call the list API with your site API key. Prerequisite: The payment source must exist, and vaulting or backup-gateway MIT must be in use if you expect more than one token.

1. Call the List gateway payment method tokens for a payment source API.
2. Optionally pass include_deleted if you need deleted mappings.

For parameters and samples, see List gateway payment method tokens for a payment source.

Pix via dLocal is now generally available

Pix via dLocal is now generally available. You can accept Brazil's real-time bank payments in BRL through dLocal.

Why is this important?

Pix is Brazil's preferred instant bank payment method. Card penetration is lower than in the US or Europe, and cross-border cards fail often on fraud checks. Pix lets Brazilian customers pay from a bank app with a QR code or payment key.

• One-time Pix covers checkout QR payments. Recurring collection uses Pix Automático mandates, so renewals debit without a new QR each cycle.
• If you already process Latin America on dLocal, you get Pix on that gateway instead of adding a Brazil-only processor. Chargebee also offers Pix via EBANX and Pix via Stripe.
• Payments are asynchronous and auto-captured. For failed Pix Automático renewals, Dunning supports real-time payment retries (up to 3 attempts within 7 days), separate from card dunning.

How can you use it?

Prerequisite: Configure dLocal in Chargebee Billing, and confirm Pix (and Pix Automático for recurring) is enabled on your dLocal account.

1. Log in to your Chargebee Billing site.
2. Go to Settings > Configure Chargebee > Payment Gateways > dLocal.
3. Turn on Pix and select Apply.
4. Set up Smart Routing so BRL Pix traffic uses the gateway you intend.

For how Pix works, token formats, sandbox amounts, and reconciliation, see Pix via dLocal.

Standalone credit note PDFs now fall back to Account Info for Billed To

When a customer's Billing Address had no company or name, standalone credit note PDFs showed a blank "Billed To" instead of falling back to the company/name from Account Info, the way invoices already do. This is fixed; standalone credit notes now follow the same fallback behavior as invoices.

Fixed phantom Round Off line in invoice receipt emails

The invoice summary embedded in emails using the \{\{invoice.basic_invoice_html\}\} merge field (Invoice Receipt, payment success, and dunning emails, among others) could show a "Round Off $0.00" line even when the invoice had no round-off amount and round-off was disabled for the site. This only affected the email; PDFs and the web invoice page were always correct. This is fixed.

Fixed retention offer coupons with a "%" in the ID failing to apply

Retention offers using a coupon whose ID contained a "%" character silently failed to apply the discount, even though the customer saw a success message and the coupon existed. This is fixed.

Fixed incorrect checkout for cancelled subscriptions on pricing tables

On Growth Pricing Tables, a customer with a cancelled subscription selecting a plan could be shown €0 and routed to a plan-change checkout instead of a reactivation, so completing checkout didn't reactivate the subscription. This is fixed; cancelled-subscription checkouts now correctly reactivate.

Fixed pricing table failing to render for subscribers on an archived item price

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.

Fixed pricing table sync missing catalog price changes

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.

Fixed addon changes not enabling checkout for returning subscribers

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.

Clearer error when a pricing sync would remove all prices

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.

Immediate cancel now refunds FlexPay recoveries

If you cancelled a subscription immediately while FlexPay was still recovering a failed card or wallet payment, Chargebee could complete the cancel before it knew FlexPay had already captured the amount. That left a paid period with no matching Chargebee payment, so you had to refund by hand or handle a dispute. Chargebee now checks FlexPay when you cancel immediately and refunds that recovery if FlexPay has captured it and Chargebee has not yet recorded it. Cancel at term end is unchanged: no refund, because the customer keeps access through the paid period. See Dunning if you also use Chargebee retries alongside FlexPay.

Worldpay Account Updater now saves the new card on renewal

On Worldpay US eCom (Vantiv), a real-time Account Updater response with code 500 (PAN changed) on an approved US card renewal could succeed at the gateway without Chargebee storing the new token and expiry. Later retries then used the old PAN. Renewals now save the updated card details when Worldpay returns that Account Updater result.

Apex test classes no longer fail during scheduled automated test runs [1.77.2 Package]

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 List index out of bounds: 0 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.

Amendment quotes now show the correct contract start date and billing cycles [1.77.3 Package]

When you created an amendment quote in Salesforce for a subscription whose start date differed from its contract term start date, typically an imported subscription, the Quotes and Contract Details section showed the subscription's start date as the Contract Start Date and calculated the number of billing cycles from that date. The result was a contract start that was weeks off and a billing cycle count that did not match the contract term, while Chargebee CPQ showed the correct figures for the same subscription. Amendment quotes now read both values from the subscription's contract term, so Salesforce and Chargebee agree.

Longer phone numbers no longer break quote sync [1.77.3 Package]

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.

Coupons with plan criteria now appear in the Salesforce coupon picker [1.77.3 Package]

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.

Amendment quotes can be created after removing a scheduled change segment [1.77.3 Package]

When you created an Update Subscription quote for a subscription that had a future scheduled change, the quote editor loaded with two segments, the current period and the scheduled change shown as a ramp. If you removed the scheduled change segment and then tried to create an immediate mid-term amendment, quote creation failed with a "Billing cycle cannot be lesser than 1" error, even though the editor showed only the current period. The only workaround was to remove the scheduled change in Chargebee first and wait for the sync. Removing a scheduled change segment in the quote editor now clears the associated end date, so you can create the amendment quote directly from Salesforce.

Renewal quotes converted from Salesforce no longer add an unexpected prorated charge [1.77.3 Package]

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.

Plan discounts now sync correctly to quote reports [1.73 Package]

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.

Trial subscription sync rule description now accurately reflects behavior [1.76.1 Package]

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.

Editing renewal quotes now allows ramps to be added [1.76.1 Package]

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.

Amendment charges are invoiced as expected [1.76.2 Package]

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.

Plan edit on future-dated amendment quotes is fixed [1.76.2 Package]

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.

Discounts no longer double on re-added line items [1.76.2 Package]

While editing a CPQ quote, if you removed a line item that had a discount and then added the same item back, the discount was being applied a second time on the already-discounted amount. The Salesforce Edit Quote screen showed the correct figures, but the same quote in Chargebee, and the PDF generated from it, showed a lower Net Amount. For example, a 15% discount on $199 came through as $169.15 in Salesforce but as $143.78 in Chargebee, and updating the quote from Salesforce did not correct it. Discounts now apply exactly once per line item no matter how many times you remove and re-add it during quote edits, keeping the Salesforce quote, the Chargebee quote, and the PDF aligned.

No more errors when amending quotes with initial charges [1.76.3 Package]

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.

Add plans to ramps on subscriptions with tiered pricing [1.76.3 Package]

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.

Billing cycle changes now wait for the latest data [1.76.3 Package]

When you changed the billing cycle while creating or editing a quote, the system needed a moment to retrieve the updated billing configuration in the background. If you clicked Create or Update before that fetch completed, the quote could be built using outdated billing cycle information. Chargebee for Salesforce now waits for the latest billing configuration before submitting your change, so quotes always reflect the billing cycle you selected.

Billing cycles now calculate correctly regardless of your time zone [1.76.3 Package]

If your Salesforce user time zone was set behind Chargebee's time zone, editing a quote could incorrectly increase the billing cycle due to a date conversion issue. This affected the billing cycle calculation during the edit quote flow. Billing cycles on edited quotes now calculate correctly regardless of the time zone configured for your Salesforce user.

Fixed missing plans when switching billing frequency in Salesforce [1.76.4 Package]

When attempting to change a subscription in Salesforce to a plan configured for a different billing period than the current one—such as switching from a monthly plan to one set up only for yearly billing—the target plan was not appearing as an available option on the Change Subscription page. This occurred even when the plan existed in both Chargebee and Salesforce. This fix ensures that all eligible plans, regardless of their configured billing frequency, now appear correctly when you initiate a subscription change.

Fixed sync stalls caused by ramp pricing workflows [1.76.4 Package]

If your Salesforce workflow includes ramp pricing on opportunities, you may have noticed the Chargebee-Salesforce sync becoming unresponsive, with sync logs showing large gaps or no activity for extended periods. This occurred when subscriptions were created through a checkout link tied to a ramp-based opportunity, causing the sync process to become overloaded and stall. This fix ensures the sync runs reliably so your Chargebee data stays up to date in Salesforce without manual intervention.

Clearer guidance when an opportunity has no account [1.76.5 and 1.77 Packages]

If you tried to use Manage CB Products on an opportunity that didn't have an account associated with it, you previously saw a generic list index error with no clear next step. Now, Chargebee shows a clear message letting you know that the opportunity needs an account before you can proceed, so you can associate one and continue without confusion.

No more freezing when replacing a product or add-on [1.76.5 and 1.77 Packages]

If you tried to modify an existing product or add-on directly on an opportunity using Manage CB Products, the page may have frozen and become unresponsive, even though removing the item and adding a new one worked without issue. This happened when replacing an add-on on an opportunity that already had a product and add-on added through Manage CB Products. You can now modify existing products and add-ons directly without the page freezing, so you don't need to remove and re-add items as a workaround.

Checkbox field values now sync consistently [1.77 Package]

If you updated a checkbox-type custom field from Salesforce, the value may have synced to Chargebee in lowercase, such as "true" or "false," while updates made directly in Chargebee used "True" or "False." This created inconsistent values across customer records depending on where the update originated. Checkbox custom field updates from Salesforce now sync with consistent casing, so your customer records stay uniform regardless of where the change was made.

Test classes no longer fail on non-synced accounts [1.77 Package]

If you ran Apex test classes that inserted test accounts, you may have run into an unexpected error, even though Chargebee sync wasn't enabled for those test records. This affected merchants updating or testing their Salesforce package version. Your test classes now run without this error when Chargebee sync isn't enabled for the account being tested.

Amendment quotes now carry the right start date and ramps [1.77 Package]

If you created a second amendment quote on the same opportunity, you may have noticed the contract start date defaulting to today's date instead of the correct date, along with existing ramps missing from the items and pricing section. This occurred specifically when a subsequent amendment quote was created on the same opportunity as an earlier quote. Amendment quotes now reflect the correct contract start date and carry over any existing ramps on the subscription, so the quote details match what's actually on the account.

Better visibility into ramp sync issues [1.77 Package]

If a ramp created in Salesforce didn't sync to Chargebee, for example when an opportunity was marked Closed Lost before the ramp was needed, it could be difficult to tell whether the ramp was actually synced. You can now more easily identify ramps that haven't synced to Chargebee, helping you spot and address sync issues before they affect a subscription.

Ramps now load correctly on amendment quotes [1.77 Package]

If you used Create Quote for Amendment on a subscription that had ramps, those ramps may not have appeared on the quote. Amendment quotes now correctly load and display any ramps on the subscription, so your quote reflects the actual terms of the account.

Fixed duplicate text in the detailed Quote PDF view [1.77 Package]

If you generated a detailed Quote PDF, you may have noticed the item description appearing twice. The detailed Quote PDF view now shows the description only once, keeping your quotes easier to read for prospects and customers.

Amendment quotes load reliably again [1.76 Package]

When you tried to create an amendment quote for an amendment opportunity in Salesforce, the quote screen loaded indefinitely and never displayed the quote. This affected all opportunities rather than a specific one, making it impossible to complete amendment quoting in the affected environments. This is now fixed, so amendment quotes load as expected every time you open them.

Ramps now sync correctly for subscription IDs with special characters [1.76 Package]

If your subscription ID included special characters such as + or &, ramps created or updated for that subscription in Salesforce did not sync over to Chargebee. The subscription itself would sync correctly, but the associated ramps failed to appear on the Chargebee side, creating a gap between what you set up in Salesforce and what took effect in Chargebee. This is now fixed, so ramps sync correctly regardless of the characters used in your subscription IDs.

Manual discounts are removed from every line you clear [1.71.1 Package]

If you applied manual discounts to both a plan and an addon on a quote and then created a new quote from the same opportunity to take them off, only one of the two discounts was actually cleared. The other stayed on the quote, so the customer saw a lower price than the one you meant to send. This happened on new subscription, upgrade, and change subscription quotes, including quotes that also had coupons applied to the plan and addon. Clearing a manual discount now removes it from each line you cleared it from.

Default billing cycles from access control now apply [1.71.1 Package]

The default value you set for Billing cycles in access control was ignored on the create subscription screen, so your reps had to type it in themselves and could enter something other than the default you intended. This affected users in the Salesforce public group that the access control setting was assigned to. The default now applies when the subscription is created.