Salesforce CPQ – What The Future Holds When RLM is on Horizon

1 Salesforce CPQ Fundamentals

Salesforce CPQ (Configure, Price, Quote) offers a robust solution for complex product configuration and pricing, providing technical architects with compelling reasons to choose it over custom development. From its native integration with Salesforce core objects to advanced features like product configuration and complex pricing, CPQ addresses critical enterprise needs while reducing technical complexity and maintenance overhead.

In this post, I share my perspective on the CPQ landscape and its evolution. But before we look ahead, let's recap CPQ (Steelbrick) basics one last time.

Core CPQ Objects

• Account
• Opportunity
• Product
• Pricebook
• Pricebook Entry
• Quote (Package)
• Quote Line (Package)
• Opportunity Product

Additional objects that play crucial roles in CPQ functionality include:

• Custom Action: Used to perform specific actions on Quotes in the Quote Line Editor (QLE).
• Custom Action Condition: Defines conditions for when Custom Actions should be executed.
• Search Filter: Helps narrow down product selection based on specific criteria.
• Product Bundle: Represents a group of related products sold together.
• Product Feature: Defines characteristics or components of a Product Bundle.
• Product Option: Represents individual items within a Product Bundle that can be selected or configured.
• Configuration Attribute: Allows for customization of products with specific characteristics.
• Product Rule: Enforces business logic for product selection and configuration.

Detailed object information can be found in the Salesforce CPQ documentation.

2 Product Bundles & Attributes

Product Bundles and Configuration Attributes are key features in Salesforce CPQ that enable businesses to create complex product offerings and customize them to meet specific customer needs.

Product Bundles

• Product Bundles are groups of related products sold together as a package
• Three types of bundles in Salesforce CPQ:
  1. Static Bundle: Pre-packaged, fixed bundle with no customization allowed
  2. Configurable Bundle: Allows customers to select or modify components
  3. Nested Bundle: A bundle that contains other bundles
• Benefits include simplified quoting process and increased cross-selling opportunities

Configuration Attributes

• Allow for customization of products with specific characteristics
• Can be auto-mapped to Quote Lines for efficient data transfer
• Two types:
  1. Configuration Attributes: Related to a single bundle
  2. Global Attributes: Can be associated with multiple products

Product Rules

• Enforce business logic for product selection and configuration
• Can be used to:
  • Select or deselect products
  • Hide or show options
  • Validate user selections in the Quote Line Editor

By leveraging Product Bundles and Configuration Attributes, sales teams can create tailored solutions that meet complex customer requirements while maintaining pricing accuracy and streamlining the quoting process.

3 Twin Fields & Multi-Dimensional Quoting

Twin Fields and Supported Objects

Salesforce CPQ provides out-of-the-box support for Twin Fields and auto-mapping between specific objects, enhancing data consistency and streamlining the quoting process. This feature is particularly useful for maintaining data integrity across related objects without the need for custom code or additional automation. Below are some of the major and commonly used Twin fields. For the full list, visit the Salesforce CPQ documentation.

MDQ – Multi-Dimensional Quoting

Multi-Dimensional Quoting (MDQ) in Salesforce CPQ is a powerful feature that allows sales teams to create complex, segmented quotes for subscription-based products. MDQ enables the breakdown of a single product into multiple time-based segments, each with independent pricing, quantities, and discounts.

Key aspects of MDQ include:

• Segmentation: Products can be divided into monthly, quarterly, or yearly segments, with custom periods also possible.
• Independent pricing: Each segment can have its own pricing structure, allowing for introductory rates or yearly increases.
• Flexible quantities: Sales reps can adjust quantities for individual segments, accommodating scenarios like ramped user adoption.
• Granular discounting: Discounts can be applied to specific segments rather than the entire subscription.
• Quote line representation: Each MDQ segment appears as a separate quote line, providing detailed visibility and reporting capabilities.

MDQ is particularly useful for businesses offering complex subscription models, enabling them to create more accurate and tailored quotes for their customers. However, it's important to note that MDQ products cannot be bundles themselves, though they can be part of a larger bundle.

4 From the Lens of CTA or Technical Architect

Why should I bring CPQ into my solution if it's just some product combination and bundle selling? Can it be done with LWC or Flow or AI tools to write code for me?

Salesforce CPQ offers numerous technical advantages that make it an attractive solution for businesses seeking to streamline their quoting processes. Here's a list of key technical benefits:

• Native Salesforce Integration: As a native Salesforce application (AppExchange), CPQ seamlessly integrates with existing Salesforce data and processes, reducing implementation complexity and maintenance overhead.
• Scalability: CPQ is designed to handle complex product catalogs and high-volume quoting, making it suitable for businesses of all sizes and industries.
• Customization and Extensibility:
  • Custom Fields: Easily add custom fields to CPQ objects to capture unique business requirements.
  • Apex Triggers: Leverage Apex to create custom logic and automations.
  • All other platform capabilities like Flows, LWC etc. can be leveraged.
• Advanced Pricing Capabilities:
  • Tiered and volume-based pricing models.
  • Contract-based pricing.
• Automated Calculations:
  • Real-time quote calculations reduce errors and improve quote accuracy.
  • Complex pricing rules and discounting logic can be implemented without custom code.
• Performance Optimization:
  • Large data volume (LDV) considerations built into the product architecture.
  • Efficient querying and data retrieval mechanisms for faster quote generation.
• Security and Compliance:
  • Inherits Salesforce's robust security model, including field-level security and sharing rules.
  • Supports compliance with various industry standards due to Salesforce's certifications.
• API Access:
  • Out-of-box and CPQ-specific RESTful APIs allow for integration with external systems and custom applications.
• Reporting and Analytics:
  • Built-in reporting capabilities leverage Salesforce's powerful analytics tools like Salesforce reports or CRMA.

These technical advantages contribute to reduced development time, lower maintenance costs, and improved system reliability compared to custom-built quoting solutions. The platform's flexibility and robust feature set enable businesses to adapt quickly to changing market conditions and scale their quoting processes efficiently.

5 Most Common Errors Faced by Customers in CPQ

However, as we all know from experience, what we see in documentation is not always true at the customer side because of many other reasons and decisions implementation partners or clients make.

Here's a list of the most common errors customers face when using CPQ, along with their causes and potential solutions:

1. Apex Heap Size Limit Exceeded:
   • Salesforce enforces an Apex Heap Size Limit of 6 MB for synchronous transactions and 12 MB for asynchronous transactions.
2. Performance Issues with Quote Line Editor:
   • Slow loading and saving of products, even with a small number of items.
3. Over-Complicated Configuration:
   • Excessive customization leading to time-consuming setups and maintenance.
4. Data Inconsistencies:
   • Using irrelevant or incorrect data in CPQ processes, especially if Product MDM is not in Salesforce. It's not just simple integration that syncs products from SAP to Salesforce. It has to be well thought through and planned.
5. Constraint Rule Evaluation Errors:
   • Incorrect setup of product rules and constraints.
6. Quote Generation Failures:
   • Complex pricing calculations or large volume of quote lines. CPQ being complex, there are processes to create quotes, calculate prices, create orders, subscriptions, etc. There are many places where silent errors can erode business trust in systems.
7. User Adoption Challenges:
   • Insufficient training or overly complex price configurations and their handshake with external systems like enablement or fulfillment.

6 Revenue Lifecycle Management (RLM)

CPQ and RLM Evolution

The future of Salesforce CPQ has become significantly clearer since this article was first published. With the introduction of Revenue Lifecycle Management (RLM) – now rebranded as Revenue Cloud Advanced (RCA) – Salesforce has charted a definitive course for the future of revenue management on its platform.

Salesforce RLM (now Revenue Cloud Advanced) is designed to streamline and automate the entire quote-to-cash process, incorporating CPQ functionality while extending its reach across the complete revenue lifecycle.

This solution addresses some of the limitations of traditional CPQ systems, particularly in areas such as scalability for large quotes and managing complex, subscription-based business models.

Key aspects of RLM/RCA that will impact the future of CPQ include:

1. Enhanced Scalability: RCA is built to handle larger volumes of data and more complex pricing scenarios, addressing a known gap in the current Salesforce CPQ solution.
2. Subscription Management: With a focus on recurring revenue models, RCA provides improved tools for managing subscriptions throughout their lifecycle.
3. AI-Driven Automation: At Dreamforce 2025, Salesforce introduced Agentforce Revenue Management, embedding AI agents directly into revenue processes for optimized pricing, reduced errors, and improved forecasting accuracy.
4. End-to-End Revenue Management: Unlike CPQ, which primarily focuses on the quoting process, RCA extends to cover billing, revenue recognition, and customer success aspects of the revenue lifecycle.
5. Improved User Experience: RCA provides a more intuitive and efficient interface for sales teams, addressing some of the user adoption challenges faced with CPQ.
6. Usage-Based Pricing: New support for usage-based products using Rate Cards, offering flexible billing models beyond traditional subscription pricing.
7. Commerce Cloud Integration: Pricing is now integrated with Commerce Cloud, creating a seamless connection between product catalog and e-commerce platform.
8. Advanced Approval Workflows: Serial and parallel approvals within approval chains allow for more flexible and efficient deal approval processes.

With the official CPQ End of Sale, the transition is no longer optional for long-term planning. Salesforce is positioning Revenue Cloud Advanced as the definitive evolution of CPQ, not just an alternative. For organizations currently using Salesforce CPQ, planning the transition should now be a strategic priority.

For organizations currently on CPQ, the transition path involves:

• Continued support for existing CPQ implementations (through estimated 2029-2030)
• Migration tools available from multiple ecosystem partners
• New implementations should use Revenue Cloud Advanced
• Increased focus on subscription and recurring revenue management within the Salesforce ecosystem

7 CPQ vs RLM/Revenue Cloud Advanced – Feature Comparison

8 Migration Strategy & Best Practices

A Word of Caution on Migration

While migration tools from partners offer a straightforward path from Salesforce CPQ to Revenue Cloud Advanced, simply mapping data between old and new objects may not fully leverage the potential of this transition. Instead, organizations should view this as an opportunity to reassess and optimize their entire quoting and revenue management processes.

Key Migration Best Practices

1. Audit & Assess First: Review your existing CPQ configuration. Identify every custom script (QCP) and trigger – these won't port over and must be rebuilt using RCA's native tools. Look for "Ghost Products" and "Zombie Rules" that can be eliminated.
2. Rationalize Your Data: Examine SKUs from the last 24 months. If a product hasn't been quoted, don't migrate it. Legacy CPQ often required five different Price Rules to do one job; RCA's new engine can likely handle these through a single Constraint or Pricing Procedure.
3. Product Catalog Rationalization: Simplify and standardize your product offerings, eliminating redundancies and streamlining configurations.
4. Process Redesign: Reevaluate existing workflows to align with RCA's enhanced capabilities, focusing on automation and efficiency.
5. Handle Existing Contracts Strategically: Keep active contracts in Legacy CPQ. When a contract is up for renewal, use automation to bridge data into an RCA Renewal Quote. This allows gradual retirement of the legacy system.
6. Data Cleansing: Use this transition to clean and normalize data, ensuring accuracy and consistency in the new system.
7. User Experience Optimization: Design intuitive interfaces and guided selling processes that leverage RCA's improved UI capabilities.
8. Integration Assessment: Review and optimize integrations with other systems (ERP, billing, fulfillment) to create a cohesive revenue management ecosystem.
9. Use a Phased Approach: A phased rollout minimizes disruption. Migration typically takes 4-12 weeks depending on complexity.

By taking a holistic approach to the CPQ-to-RCA migration, organizations can not only preserve existing functionality but also unlock new efficiencies and capabilities that drive revenue growth and improve customer satisfaction.

9 Frequently Asked Questions

Related Reading

Continue your Salesforce architecture learning journey with these related guides:

• 10 Differences Between Salesforce Solution and Technical Architect - Understand the key distinctions between Solution and Technical Architect roles in the Salesforce ecosystem.
• 10 Salesforce Integration Design Considerations from Architect POV - Essential integration design patterns and considerations for enterprise Salesforce implementations.
• 5 Steps to Increase Your CTA Certification Chances - Practical advice for preparing for the Salesforce Certified Technical Architect exam.
• 7 Ways to Secure Experience Cloud - Security best practices for Salesforce Experience Cloud implementations.

11 Abbreviations & Glossary