Blog

Challenges in Salesforce CPQ testing - Complexities and Importance of Functional Testing Amidst Automation for CPQ

January 27, 2025
by
Cloud Peritus
Challenges in Salesforce CPQ testing - Complexities and Importance of Functional Testing Amidst Automation for CPQ

Join us as we explore the challenges and complexities of testing Salesforce CPQ with emphasis on the importance of functional testing alongside automation.

Salesforce CPQ (Configure, Price, Quote) is a powerful solution designed to help businesses automate and optimize their quote-to-cash processes. It simplifies the challenging tasks of configuring products, setting accurate prices, and generating precise quotes, all within Salesforce’s CRM platform.

With CPQ, sales teams can efficiently create proposals, contracts, and invoices, reducing errors and boosting productivity. By unifying product configuration, pricing strategies, and approval workflows, CPQ allows sales reps to spend less time on manual tasks and more time focusing on closing deals.

Challenges and Complexity in CPQ Testing

1. Multifaceted Product Configurations:

Challenge: CPQ systems manage offerings with a lot of configurable options, dependencies, and constraints. Testing must encompass all conceivable configurations to ensure the system functions as intended.

Complexity: As the number of options and rules proliferates, the possible configurations multiply exponentially. Verifying that each configuration is valid and that the system behaves correctly under all permutations is an exceedingly arduous task.

Example:

  • Rule-based configurations: Salesforce CPQ relies extensively on sophisticated rules governing products, pricing, and discounts to produce accurate quotations. Testing these rules poses a challenge due to dependencies, conditions, and triggers that may vary between different offerings.
  • Bundled products: Verifying bundled product configurations, including various options and features, necessitates testing multiple combinations to ensure precise pricing and availability. Overlooking edge cases may result in inaccurate quotes.

2. Intricate Pricing Rules and Logic:

Challenge: CPQ systems incorporate intricate pricing models, encompassing discounts, promotions, volume-based pricing, and other dynamic rules.

Complexity: Pricing rules exhibit considerable variability and can interact in complex ways. Testing must confirm that all pricing rules are correctly applied and that calculations are accurate across diverse scenarios.

Example:

  • Advanced Pricing Rules: CPQ pricing mechanisms, such as tiered pricing, volume discounts, and contracted pricing, demand comprehensive validation. These rules often hinge on variables like customer segments, regions, and currencies, complicating the testing process.
  • Discount Approvals: Discount approval processes may differ based on the discount level, each requiring distinct approval workflows. Ensuring the correct approval workflows are triggered presents complexity that necessitates thorough testing.

3. Custom Configurations and Customizations:

Challenge: CPQ systems often support bespoke rules and configurations tailored to meet specific business needs.

Complexity: Custom rules introduce additional layers of intricacy, requiring testers to deeply understand and validate both standard and custom rule sets. This necessitates thorough documentation and a comprehensive grasp of how customizations impact the system.

Example:

  1. Custom Logic: Businesses frequently introduce custom objects, fields, and logic within platforms like Salesforce CPQ. Testing these customizations can be particularly challenging, especially as the system evolves.
  2. Pre-existing Workflow Validations: Workflow validations involve a complex array of rules, including mandatory fields, data formats, and field dependencies, requiring thorough testing to ensure all mandatory fields are accurately populated before any functionality, such as closing an opportunity in CPQ.
    Complex validations or validations that involve multiple conditions slow down the processing time. Each validation needs to be evaluated for every transaction, which adds overhead and leads to performance issues.

4. Approval Workflows:

Challenge: CPQ systems feature multi-tiered, dynamic approval workflows, varying based on factors like deal size, discount levels, or product types.

Complexity: Testing these workflows involves ensuring each stage and condition is processed accurately, and that exceptions are appropriately handled. This requires end-to-end validation to ensure smooth processing.

Example:

  1. Advanced Approvals: Multi-layered approval workflows, especially for discounts or high-value deals, require rigorous testing. Ensuring that all possible scenarios—including edge cases and rejection loops—are covered is vital for system integrity.
  2. Multiple Approvers: Logging in through multiple browsers to test simultaneous actions on approval requests adds to the complexity.
  3. Quote Actions via Email: A significant challenge occurs when testing quote approvals, as the CPQ system sends approval requests via email to designated approvers. The issue arises because the system requires each user to have a unique email address within the organization. If multiple users share the same email, the approval process may fail, making it difficult to accurately track responses—particularly when testing in real-time environments where only unique users can be reliably tested.

5. Auto-Renewal Creation:

Challenge: Complex calculations or validations during the renewal process fail the creation of auto-renewals. Large data volumes can cause performance issues such as slow processing or timeouts, particularly in processes like auto-renewal creation, updates via batch, etc. Addressing these issues is critical for maintaining system efficiency.

Complexity: If the functionality responsible for populating mandatory fields during renewal creation fails, it disrupts the process, thus breaking the custom logic, and preventing renewals from being auto-generated via the batch properly, leading to system failures.

6. Dynamic and Change Currency:

Challenge: Maintaining dynamic strategies in Salesforce CPQ can be cumbersome as products and pricing strategies evolve. Regular updates are needed to keep the rules accurate and relevant.

Real-Time Pricing: Prices may fluctuate dynamically due to real-time factors such as exchange rates, competitor pricing, or market conditions. Testing real-time pricing scenarios adds an extra layer of uncertainty, often necessitating automation to effectively cover all potential cases.

The process of changing currency in Salesforce CPQ involves significant testing challenges, including configuration validation, data integrity checks, integration complexities, and user interface usability.

Complexity: The lengthy process of changing currency in CPQ involves manually deleting each quote line item before using the change currency functionality. While building custom logic can be complex, it simplifies currency changes across opportunities and quotes, including quote line items with minimal clicks, it automatically deletes any line items that mismatch the selected price book or currency. However, a challenge we encountered in the process was with Multi-Dimensional Quoting(MDQ) products. The custom logic created multiple product line items based on segment instead of a single line item in the quote line editor, necessitating the manual interaction of de-segmentation of products in the quote line editor after initiating the currency change.

7. Forecasting Annual Recurring Revenue (ARR):

Challenge:  ARR reflects the annual revenue expected from a business's recurring subscriptions. A key challenge in forecasting ARR in CPQ is accurately monitoring renewals, upgrades, and cancellations. ARR is essential for tracking growth, forecasting revenue, and evaluating long-term customer value.

Complexity: Forecasting ARR is complex due to variable pricing, contract amendments, multi-year terms, and fluctuating subscription renewals. These factors, along with currency changes and product upgrades, make accurate predictions challenging.

Example:

  • Subscription Renewals: Predicting whether customers will renew or churn affects ARR. CPQ systems must factor in renewal probability, which adds uncertainty to forecasts.
  • Currency Fluctuations: For businesses operating in multiple currencies, forecasting ARR is further complicated by currency exchange rate fluctuations that impact revenue projections.

8. Multi-orders:

Challenge: Managing multiple orders simultaneously poses risks of errors in pricing, product selection, and approvals, particularly when each order has varying terms or conditions. Synchronizing these orders across different regions or business units adds complexity, especially when products have different fulfillment timelines or require specific handling.

Complexity: Custom rules and workflows can vary for each order, especially when different products or discount structures are involved, adding complexity to the configuration and management process. Additionally, managing interdependencies between products or services across separate orders, such as bundling or volume-based pricing, requires precise coordination to ensure accurate quotes and contracts across multiple transactions.

Example:

Multi-Order having  MDQ and Non-MDQ Products: When multiple orders are enabled and a quote is created that includes both MDQ and non-MDQ products, there is a CPQ limitation that prevents the contracts from being activated properly.

Need for Functional Testing for CPQ Even Amid Automation

Functional testing is essential in Salesforce CPQ, even with automation, for several reasons:

  1. Validating Business Logic: Functional testing ensures the correct operation of complex rules for product configurations, pricing, and approvals, especially for new or custom features that automation might miss.
  2. Human Oversight: It allows for manual checks of usability and UI issues that automated tests may overlook, such as document generation errors or intricate interactions.
  3. Handling Customizations: CPQ implementations often involve custom workflows, requiring functional testing to verify correct integration, especially for dynamic features like real-time pricing and approvals.
  4. Verifying New Features: Functional testing ensures new features work as expected before updating automation scripts and can uncover bugs automation might not detect.
  5. Quick Validation of Minor Changes: It offers a faster way to confirm small updates, like pricing rule changes, without adjusting automation scripts.
  6. Managing Complex Dependencies: Functional testing ensures smooth interactions between CPQ and external systems like CRM or ERP, which automation may not fully address.
  7. Ensuring Compliance: It verifies adherence to legal requirements and ensures the accuracy of customer-facing documents like quotes and contracts.
  8. Regression Testing: Functional testing catches issues from updates that automated scripts may miss, while also identifying side effects of changes.

In short, functional testing complements automation by addressing areas automation might miss, ensuring accuracy, reliability, and a seamless user experience. We should strategize on which scenarios to automate versus which to handle manually i.e. identifying complex, dynamic configurations for functional testing while using automation for straightforward rule/logic validations.

How CPQ Certification Helps Navigate CPQ Solutions

Salesforce CPQ certification has greatly improved my testing skills, allowing me to efficiently navigate and test CPQ solutions. It provided a solid grasp of core functionalities like product configuration, pricing rules, and quote management, helping me identify issues and validate workflows confidently. The hands-on experience with real-world scenarios, such as setting up product bundles and approval workflows, has been crucial for troubleshooting complex test cases.

Mastering best practices and customization techniques made me proficient in managing custom rules and configurations, ensuring that business needs are properly met. 

Additionally, the certification enhanced my problem-solving abilities and communication with stakeholders, resulting in smoother testing cycles and faster deployments. Overall, it has significantly increased my confidence and effectiveness in testing CPQ systems.

Here are a few problem-solving scenarios I encountered:

  • To create a renewal opportunity for forecasting or reporting, it’s essential to check the “Renewal Forecast” option. When ready to generate a quote, selecting the “Renewal Quoted” checkbox triggers the creation of a quote on the existing renewal opportunity.
  • Ensuring that configurable product bundles only allow valid combinations, especially when dependencies exist between product options, to avoid invalid selections during quoting.
  • At least one subscription product is needed to create a contract.
  • Resolving conflicts between multiple discount rules, ensuring that the right discount is applied based on priority, approval conditions, or sales rep overrides.
  • Troubleshooting issues related to subscription amendments, such as incorrect prorated pricing or overlapping subscription terms.
  • Solving problems with contract renewals or amendments where contract start and end dates do not align, impacting the overall contract duration. Moreover, ensuring that the contract start and end dates are correctly entered is crucial, as these fields typically define the contract's duration and terms.

Salesforce CPQ certification offers significant benefits for professionals by providing in-depth knowledge of key features like product configuration, pricing rules, discount structures, and quote management. It enhances skills in advanced features such as guided selling, dynamic bundles, approvals, and renewals. Certification ensures hands-on experience with real-world scenarios, imparting best practices to optimize system performance while developing problem-solving skills to tackle complex CPQ challenges. Certified professionals can confidently implement solutions, communicate effectively with stakeholders, and make informed decisions on customization, automation, and integration. Ultimately, CPQ certification fosters career growth and successful project execution.

Conclusion

Testing Salesforce CPQ is a complex process due to intricate product configurations, dynamic pricing rules, and custom workflows. While automation is valuable, functional testing remains essential for ensuring system accuracy, particularly with customizations and real-time interactions. Balancing automation with manual testing helps manage CPQ complexities, minimize errors, and enhance reliability.

Gaining Salesforce CPQ certification further strengthens testers' ability to navigate complex scenarios and validate configurations effectively. With thorough testing and certified expertise, CPQ systems can deliver streamlined sales processes, accurate quotes, and greater customer satisfaction.

Cloud Peritus has been at the forefront of innovation since its inception and has since played an integral role in delivering game changing solutions to its clients time and again, resulting in 5 star reviews from across the board.

Feel free to check us out at Salesforce AppExchange.

For more information and to book a free consultation on how we can help transform your business.

Contact us at info@cloudperitus.com

You can also check our other articles on QA and how how AI is changing the landscape.

  1. Enhancing Salesforce testing with AI: How LLMs can supercharge your Salesforce projects
  2. Streamlining Salesforce Test Case Generation Further with Test Case Studio and Generative AI

Authors

Pooja Pimpdae

Pooja Pimpdae

Senior QA Engineer at Cloud Peritus
Praneetha Salihundam

Praneetha Salihundam

QA Engineer at Cloud Peritus