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
  • 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)

Developer Resources


  • Developer Resources Overview
  • Articles and FAQ

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

Entitlements


  • Entitlements Overview
  • Features Overview
  • Feature Management
  • Managing Product Entitlements
  • Subscription Entitlements
  • Customer Entitlements
  • Grandfathering Entitlements
  • Articles and FAQ

Usage Based Billing


  • Understanding Usages
  • Setting up Usage Based Billing
  • Usage Alerts
  • Metered Billing
  • Articles and FAQ

Chargebee CPQ


  • Chargebee CPQ
  • Chargebee CPQ for Salesforce
  • Chargebee CPQ for HubSpot

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
  • Pricing Table
  • Managing Payments with Chargebee.js
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Approvals
  • 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

Multi Business Entity


  • Multi Business Entity Overview
  • Customer Transfer Overview
  • Articles and FAQ

Mobile Subscriptions


  • Overview
  • Omnichannel Subscriptions
  • Omnichannel One-Time Orders
  • Mobile Subscriptions (Legacy)

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
  • Ecommerce Management
  • 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
  2. Product Catalog
  3. Articles and FAQ
  4. Product Catalog Overview
  1. Billing
  2. Product Catalog
  3. Articles and FAQ
  4. Product Catalog Overview

What are the best practices for naming subscription products and tiers?

Problem Statement

You want to know the best practices for naming subscription products and tiers in Chargebee.

Related Scenarios

  • How should I name my subscription products to ensure clarity and consistency?
  • What naming conventions should I follow for product tiers in Chargebee?
  • How can I audit my current product names to align with future launches?

Solution

Naming your subscription products and tiers effectively is crucial for maintaining clarity, consistency, and scalability as your business grows. Here are some best practices to follow:

  1. Consistency: Ensure that your naming conventions are consistent across all products and tiers. This helps in maintaining a uniform brand identity and makes it easier for customers to understand your offerings.

    • Example: Use similar structures or patterns, such as "Basic Plan," "Standard Plan," and "Premium Plan."
  2. Clarity: Choose names that clearly describe the product or tier. Avoid using jargon or overly complex terms that might confuse customers.

    • Example: Instead of "Pro Max," consider "Professional Maximum Features."
  3. Scalability: Design your naming conventions to accommodate future products or tiers. This ensures that new offerings can be integrated seamlessly without disrupting the existing structure.

    • Example: If you plan to introduce more tiers, consider using numbers or letters to indicate hierarchy, such as "Tier 1," "Tier 2," etc.
  4. Customer-Friendly Terms: Use terms that are easy for customers to understand and relate to. This enhances the customer experience and reduces confusion.

    • Example: Use "Starter" instead of "Entry-Level."
  5. Audit and Review: Regularly audit your current product names to ensure they align with your business goals and customer expectations. Consider arranging a call with an implementation specialist for a detailed review and personalized advice.

Additional Information

  • Consider the cultural and regional implications of your product names if you operate in multiple countries.
  • Test your product names with a small group of customers to gather feedback before a full launch.

Important Notes

  • Ensure that your product names are unique to avoid confusion with competitors.
  • Regularly update your naming conventions as your business evolves.
  • Keep a documented naming convention guide for internal use to maintain consistency across teams.

Was this article helpful?