Release Notes
Updates, changes, and improvements at Chargebee
Release Notes
Updates, changes, and improvements at Chargebee
Your pricing pages can now automatically display in each visitor's local currency, letting them see prices they're familiar with. This is ideal if your product catalog supports multiple currencies but you want to eliminate foreign exchange friction and better align with local purchasing power. By presenting prices in the visitor's currency, you can create a more inviting purchase experience and potentially reduce cart abandonment.
We are thrilled to introduce the Feature Availability Metrics (FAM) feature in entitlements, offering insights into feature distribution across plans, addons, and subscriptions as well as the count of overrides for a feature. Use FAM to make data-driven decisions on trial management, packaging experimentation, and revenue growth. FAM primarily offers four essential metrics.
We are excited to introduce an update to our filters on the index pages that aims to provide users with a more intuitive interface while simultaneously reducing the load on the system. These improvements will streamline the process of refining search results and enhance overall system performance.
Key enhancements include:
We are confident that these changes will positively impact the user experience, and we encourage you to explore our updated filter UI to take advantage of these new features.
The following enhancements have been made to the full-page layout of Checkout:
Note - This feature is in early access. Submit a request to enable this feature.
In our current accounting integrations, discounts are mapped as a single consolidated line item, rather than being broken down by individual line items. This means that discounts are synchronized at the invoice level, rather than at the line-item level. You can now reach out to our support team to enable this feature. With this enhancement, when multiple coupons are applied to an invoice in Chargebee, each coupon will be created as a separate Discount item (or Non-Inventory Sale) within NetSuite. This improvement ensures that discounts are accurately reflected at the line-item level in your accounting system, providing greater clarity and precision in your financial records.
Previously, when a synchronization process failed due to a server quit, the sync message erroneously displayed 'Sync started' instead of accurately reflecting the failure. We are pleased to announce that we have addressed this issue. The sync message has been updated to provide more accurate information. In the event of a synchronization failure due to a server quit, the message will now correctly indicate, 'Sync Failed, Please retry manual sync or wait for auto sync.' This change ensures that you receive the appropriate notification when sync failures occur, enabling you to take the necessary steps for resolution.
Previously, when attempting to map records based on external IDs, NetSuite would raise an exception stating, 'Transaction type specified is incorrect' if the same external ID was used for different entities. We are pleased to announce an improvement in how this situation is handled. Instead of the generic error message, we have refined the error handling process. Now, when entities with the same external ID exist in NetSuite, the system will display a more informative error message: 'This record already exists.' This enhancement will provide you with clearer and more actionable information when dealing with duplicate external IDs during mapping, leading to a smoother and more intuitive experience.
The following issues were fixed and enhancement was released:
A scheduled change upon subscription renewal was moved to the next term instead of the originally scheduled date.
While editing an addon to change its billing cycle, the associated price point currency was found to change erroneously.
Schedule Change sub response in retrieve and list API was not returning the changes_scheduled_at parameter. Fixed!
While creating a new subscription record, clicking any option from the floating menu at the left-hand side removed the customer ID from the URL, which in turn threw an error while clicking on the Create button. This has been fixed!
We've introduced the ability to remove the non-recurring add-ons from a subscription record while editing the subscription.
With this release, we have added support for a new payment method called Venmo via Braintree. Venmo is a US-based peer-to-peer (P2P) payment solution that allows users to transfer and receive money easily and quickly via a smartphone application. This is a beta release, you can contact Chargebee Support to learn more.
Customers can now seamlessly purchase our usage-based products through full page layout of Checkout. This update includes support for new checkouts, existing customer checkouts, and one-time checkout processes, enhancing the overall shopping experience and expanding our product accessibility.
Note: This feature is in early access. Submit a request to enable this feature.
The following issues were fixed with this release:
While adding usage to an invoice generated in the previous month, the usage was getting removed upon page refresh.
While importing Credit Notes, since the ref-item-id for credit note line items are not populated in the database, though the credit notes get mapped to respective invoices, the credit note line items were not mapped to relevant invoice line items.
Invoice number under Promotional Credits tab for a subscription that was cancelled was found to be invalid, and the invoice link was leading to a broken link.
Attempting to schedule advance invoices for two billing cycles on specific dates was throwing an error. One billing cycle was getting missed and an extra billing cycle was getting included in the subscription.
Inability to add links in invoice payment instructions wherein the links were found to get distorted.
This update introduces a new feature that allows users to set a manual trigger for e-invoicing when creating a new customer profile. This enhancement provides greater control and flexibility in managing E-invoicing processes, enabling users to initiate E-invoicing for specific customers at their discretion during the customer creation process.
Note: This feature is in early access. Submit a request to enable this feature.
You now have the ability to override the default unit of measure that applies to addons during the checkout process. This override will be reflected in the Checkout interface.
If translations are provided for the unit of measure, they will be taken into account during the checkout process.
If a product in the catalog has an explicitly mentioned unit of measure, that unit of measure will be used for that specific product during checkout.
When the checkout is rendered in a non-primary language, translations provided in the language pack will be prioritized over the unit of measure provided in the catalog. If no translation is available, the fallback will be the unit of measure provided in the catalog.
Resolved Limited-Time Coupon Error: Fixed an issue in version 1.57 where subscriptions with limited-time coupons encountered errors. This is resolved in version 1.57.1.
Fixed Duplicate Entries in Amendment Log Sync: Fixed the issue where the amendment log functionality created duplicate entries when syncing from Chargebee to Salesforce.
Addressed Test Site Unlinking Issue: Addressed an issue preventing the unlinking of test sites from the Salesforce integration.
Fixed Scheduled Cancellations Issue: Fixed an issue that prevented scheduled cancellations on specific dates from working correctly.
Previously, for our One-time purchase API, there was a limit of 70 characters for product[id] and 20 for product[name] as the product[type] was appended to the product[id] and `product[name]`. Now that we are not appending the product[type] to these fields, the character limit for product[id] and product[name] gets increased. product[id] can now be 96 characters, and product[name] 46 characters.
Previously, Play Store one-time purchases required acknowledgment within three days to prevent automatic refunds and purchase revocation. Acknowledgment was SDK-based, potentially causing issues for non-SDK users. We've improved the system to automatically acknowledge one-time purchases through Google's APIs, if not already acknowledged.
In previous versions, when Google's APIs returned a 410 error, it was not handled appropriately, causing a 500 error to be thrown instead. In this release, we have resolved the issue by ensuring that when a 410 error is received, the error is now properly represented with the correct error details, rather than throwing it as a 500 error. This ensures more accurate error handling in our application.
We are pleased to announce an enhancement to the MRR History Builder. In the current version, the tool may generate inaccurate subscription histories when line items end at non-standard intervals, such as random hours that do not align with the typical 24-hour cycle.
In this release, we have addressed this issue. The MRR History Builder will now take into account those additional hours in line items, ensuring the accurate generation of subscription histories. This improvement will contribute to better data accuracy and reporting for your subscription-based services.
The following issues were fixed with this release:
The transactions split in Chargebee from NetSuite were incorrectly updated in NetSuite upon re-sync. We have introduced the imported_payment property for transactions. Transactions with this property won't sync back to third-party systems like NetSuite, preventing overwrites and conflicts.
Previously, the 'Ignore Entity API' was unavailable in the NetSuite Leap UI. In response to this issue, we have introduced a new "Ignore Entity API" to address this gap in functionality. It's important to note that this fix applies to the NetSuite Leap UI and the Multi-Business Entity (MBE) integration, ensuring comprehensive functionality across both platforms.
The Tax Registration Number Field was not displayed in the customer creation page even though the option to 'Collect Tax Registration Number from customers for countries not configured for tax'(under Configure Taxes) was enabled, until atleast any one country tax is configured. This is now fixed!