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

Docschargebeedocs

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. Entitlements
  3. Features Overview
  1. Billing
  2. Entitlements
  3. Features Overview

Features Overview

The Features module helps you define the various features offered as part of your product line. It also allows you to define the entitlements that catalog items and subscriptions can have towards said features.

This results in a better customer experience for your users, and greater operational efficiency for your business.

image

There is a many-to-many relationship between features and product catalog items such as plans, addons and charges. An item can be assigned multiple features, and a feature can belong to multiple items.

All Features in Chargebee carry a name, description, and ID. Features can be created, updated, activated, archived, and deleted.

Entitlement levels

Levels determine the extent to which a feature can be diversified when associating them with product catalog items. With a feature having three entitlement levels, you can assign each level to a catalog item-higher value entitlement levels to premium plans, and basic entitlement levels to starter plans.

This is explained more in the following section on Feature Entitlement Types. This section, along with Managing Product Entitlements will help you understand the implementation of levels.

Feature Entitlement Types

Entitlement type defines the nature of entitlement levels that are available to users for a feature. The different feature entitlement types are as listed below:

Switch: For features that are either Available or Not Available to a user. Also called feature flags or toggles in other systems.

Quantity: For features that are offered with pre-defined numerical limits to users.

Range: For features that can be offered with numerical limits within a certain range.

Custom: For features and benefits that have various entitlement levels, but aren't numerical by nature.

Switch-type

With a switch-type feature, you can restrict the feature access to a set of applicable product catalog items.

Switch-type features have available/ not available options as entitlement levels.

See also

Adding Switch-type feature entitlements

Example: Let's consider Analytics as a premium feature, for which only the Platinum and Gold plan users are entitled. You can select Switch as the entitlement type and configure it as available only for the premium plans.

image

Quantity-type

Quantity-type allows you to create numerical value-based features.

If the consumption of a feature entitlement can be tracked and measured against a limit using numerical values, then using a quantity type is recommended.

Applicable when you intend to closely control the entitlement levels by setting specific limits for each level. You can add any number of entitlement levels, including Unlimited for the maximum level.

See also

Adding Quantity-type feature entitlements

Example: Let's say you are running a streaming service and need to restrict the number of movies a user watches in a month based on their plan. Quantity-based entitlements would be the best fit here. You can set the Entitlement unit as movies/month, and set the levels as 20, 30 and 50 movies/month.

image

Range-type

Range-type feature is applicable when you do not intend to closely control the entitlement levels. Unlike predefined values, you cannot set several limits but rather only a minimum and maximum value.

Range can also be used when you want to experiment with a range to understand the levels that your customers will respond to.

See also

Adding Range-type feature entitlements

Example: Let's consider that you sell your SaaS product in two countries - country A and B. Since API traffic in country A is usually high compared to the B, you intend to provide an API limit based on that. The plans you provide are A-basic, A-premium for country A and B-basic, B-premium for country B.

To tackle this use case, you can set a range from 100 to 1000 and configure API limits for each plan and country within that range. A-basic : 500 requests/min, A-premium : 800 requests/min, whereas B-basic : 150 requests/min and B-premium : 400 requests/min.

image

Custom-type

Custom-type features help define service levels effectively. For example, onboarding, implementation, support, and success service levels.

It also allows you to configure any feature that doesn't come essentially under switch or quantity types. You can define several levels of entitlement using custom text or labels.

See also

Adding Custom-type feature entitlements

Example: Let's say that you have various service levels for the Support you offer. You can set Email Support, Chat Support, Phone Support and Priority Phone Support as the Entitlement levels from lowest to highest.

image

Roles and Permissions

Based on your role in Chargebee, you can perform various operations on the entitlements. Since entitlements directly impact the end-user, there is a need to limit access to who can view and make changes to it.

Given below is a table that lists out the possible roles and their permissions.

RolesCreate FeaturesEdit FeaturesChange Item EntitlementsOverride Entitlements on SubscriptionsChange/Delete Entitlements on SubscriptionsView Entitlements
Adminimageimageimageimageimageimage
Sales Agentimageimageimageimageimageimage
Customer Supportimageimageimageimageimageimage
Sales Managerimageimageimageimageimageimage
Tech Supportimageimageimageimageimageimage
Analystimageimageimageimageimageimage
Finance Executiveimageimageimageimageimageimage

See also

Features API

Articles & FAQs

How to add a custom field to a feature

Was this article helpful?