New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates

  • Release Notes

Getting Started

  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Developer Resources
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee

  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

AI in Chargebee

  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model context protocol)

Product Catalog

  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions

  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers

  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Invoices, Credit Notes and Quotes

  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes

  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities

  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Managing payments with ChargebeeJS
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration

  • Users & Roles
  • Custom Fields & Metadata
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Reports and Analytics

  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations

  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Order Management
  • Mobile Subscriptions (Legacy)
  • Other Integrations
  • Articles and FAQ

Data Privacy & Security

  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations

  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  3. Product Catalog
  4. Product Catalog Upgrade Rollback
  1. Billing
  3. Product Catalog
  4. Product Catalog Upgrade Rollback

Rollback Product Catalog Version Upgrade

Overview

Businesses that upgrade their Chargebee Product Catalog version from 1.0 to 2.0 can initiate a rollback request post upgrade. A successful rollback ensures that the Chargebee test and live sites are reverted back to legacy product catalog version.

Step-by-step rollback process

The following are the steps to perform product catalog version upgrade rollback process:

  1. Initiate a rollback request with the Customer Success Manager, Professional Services Consultant, or Chargebee support stating the reasons for the rollback. 
  2. Chargebee will validate if the test or live site adheres to the limitations mentioned below. If there are any discrepancies, you will be notified. Please note that the below caveats are important to ensure a successful rollback is possible without complexities. 
  3. Chargebee will run an internal API to perform the rollback to Legacy Product Catalog Version. If plan and addon ID updates were performed as part of the upgrade process, you can choose to retain them or revert them to their original format. 
  4. The rollback process will take approximately one to one and half hour(s) depending on the volume of data. 

Limitations

To ensure that a successful rollback can be performed, follow the limitations:

  1. New plans, addons, or charges should not be created on the latest product catalog version site post upgrade. 
  2. Updates in naming convention, price, billing cycle, attached items and more should not be made to the existing plans, addons, and charges post upgrade. 
  3. All operations that are halted/paused on the Chargebee site during the upgrade should continue to be paused until the rollback process is completed. New customers, subscriptions, quotes, invoices, and transactions should not be generated on the site post upgrade. Only existing subscription renewals and subscription activations (future/trial subscriptions) scheduled to run by Chargebee automatically within the same time window as the upgrade and rollback can continue. 
  4. Latest product catalog version specific features should not be enabled and used post upgrade.

Related Articles

  • Upgrade product catalog version using Self Serve Tool
  • FAQs on upgrading product catalog version using Self Serve Tool
  • Latest product catalog version APIs

Was this article helpful?