In any CPQ or Billing implementation, the Product Catalog acts as the heartbeat. It defines what you sell, how it’s priced, and how it behaves across quoting, ordering, invoicing, and revenue recognition.
Whether you’re selling a physical product, a service, or a subscription, this chapter will teach you how to design a smart, scalable product catalog in Salesforce Revenue Cloud.
5.1 What is a Product Catalog in Salesforce?
A Product Catalog in Salesforce is a structured list of items and services a business offers to its customers. Each product can have attributes like:
-
Configuration options
-
Pricing models
-
Subscription behavior
-
Billing schedules
In Revenue Cloud, the product catalog isn’t just about sales—it also drives billing, revenue recognition, and even forecasting.
5.2 Core Product Catalog Objects
| Object | Description |
|---|---|
| Product2 | The core object representing each product or service |
| PricebookEntry | Links products with prices through different price books |
| Product Option | Used to define bundles and sub-products |
| Price Rule | Controls dynamic pricing logic |
| Configuration Attribute | Adds variable options to a product |
5.3 Setting Up Products – Step-by-Step
Step 1: Define the Product
Create a new Product2 record:
-
Name: "Premium Support Subscription"
-
Product Code: "PSS-001"
-
Active: True
-
Subscription Term: 12 (months)
-
Subscription Pricing: Fixed / Percent / Usage
Step 2: Add Pricing
-
Create a Price Book (e.g., "Standard Price Book")
-
Create PricebookEntry for your product
-
Set List Price (e.g., ₹10,000/year)
Step 3: Enable for CPQ & Billing
-
Checkbox: "Configurable" (if part of a bundle)
-
Checkbox: "Billing Enabled"
-
Assign appropriate Revenue Recognition Policy (optional)
5.4 Product Types
Revenue Cloud supports various product types:
| Type | Use Case |
|---|---|
| One-time Product | Setup fees, license purchases |
| Subscription | SaaS, memberships, support plans |
| Usage-Based | Cloud storage, API calls, utility consumption |
| Evergreen | Subscriptions without end dates |
| Bundles | Internet + Cable + Installation (packaged) |
5.5 Bundling in CPQ
A bundle groups multiple products into a parent-child structure. For example:
Product: Internet Plan Bundle
Options:
-
100 Mbps Internet
-
Wi-Fi Router
-
Setup Service
Configuration Features:
-
Product Options: Defines the child products
-
Option Constraints: “If Wi-Fi Router is selected, Setup Service is required”
-
Configuration Rules: Enforce compatibility and dependencies
-
Configuration Attributes: Custom inputs like color, size, or storage
5.6 Dynamic Pricing with Price Rules
Price Rules are used to apply custom logic to calculate prices dynamically.
Example:
-
If user selects more than 10 licenses, apply a 20% discount.
-
Lookup discounts from a custom object using Lookup Queries.
-
Populate fields like Additional Discount, Net Total, or Custom Price.
Components of a Price Rule:
-
Conditions: When to apply the rule
-
Actions: What fields to update
-
Lookup Queries: Pull values from related records
5.7 Configuration Attributes
Used when a product needs customization:
-
Color
-
Storage (e.g., 128 GB / 256 GB)
-
Term (e.g., 6 months / 12 months)
Attributes are stored in Product Attribute Values and displayed in the quote line editor during configuration.
5.8 Considerations for Billing-Ready Products
To prepare a product for the billing lifecycle, ensure:
-
Billing Type: One-Time, Recurring, or Usage
-
Billing Frequency: Monthly, Quarterly, Annually
-
Revenue Recognition Rule is defined (e.g., monthly amortization)
-
Enable checkboxes:
-
"Billing Enabled"
-
"Taxable"
-
"Create Asset"
-
5.9 Example: Creating a SaaS Subscription Product
Scenario: A cloud-based CRM tool that charges ₹1,200/month with a free setup.
-
Product 1: "CRM Monthly Subscription"
-
Type: Recurring
-
Price: ₹1,200/month
-
Term: 12 months
-
Billing: Monthly
-
Auto-renew: Yes
-
-
Product 2: "One-Time Setup Fee"
-
Type: One-time
-
Price: ₹5,000
-
Billed: On contract start
-
These two can be bundled under a “CRM Starter Pack” bundle.
5.10 Best Practices
-
Keep product names and codes consistent
-
Avoid hardcoding discounts—use rules
-
For scale, use Lookup Price Rules and Attributes
-
Plan your catalog hierarchy (base product → bundles → services)
-
Think ahead: How will the product behave post-sale?
5.11 Chapter Summary
-
Product Catalog is the foundation for CPQ and Billing
-
Smart configuration enables accurate quoting and billing
-
Use bundles, price rules, and attributes to handle complex scenarios
-
Prepare all products for subscription lifecycle and revenue recognition
No comments:
Post a Comment