CPQ

I've audited a lot of CPQ orgs over the years, and there's one pattern I see almost every time: a price rule built to patch a problem from three reorgs ago, still firing in production, that nobody remembers the reason for. Same story with bundle/option logic that's quietly drifted away from how Sales actually sells today. 

I've been experimenting with an AI agent that scans an org's CPQ/Revenue Cloud metadata, flows, and price waterfall to flag exactly this kind of drift and tech debt before it causes a quoting mess. Still refining it, but it's already surfaced things in test orgs I wasn't expecting. 

Curious if this is a familiar headache for others here, or if your orgs are cleaner than the ones I usually get called in on. What's the strangest "nobody knows why this is here" logic you've found in a CPQ org?

When we create a quote we add  start date and subscription term on the basis ot that end date calculates automatically and reflect on quote page as well as order form but not its not happening how to fix this and what to check ? 

Hello, 

My org currently uses discount schedules with products and price book values completed. They now want to go away from Discount Schedules all together and move to Block Pricing. We use Renewal Method of Uplift and for Amendments we use an Amendment and Renewal Behavior of Latest End Date. 

I have not worked at an org where they moved completely off of one to the other. I am trying to understand any gotchya or things to be aware of. Also, trying understand the best practice for this move and steps to complete. For example, steps to complete: 

1. Add all block price tiers to affected products
2. Change the Pricing Method to Block from List for those products.
3. Since we have many discount schedules for each product (based on price book) remove the reference to the product and price book from the current discount schedules.

What happens when we renew or amend with products that used a discount schedule before? What can I do to avoid any pricing issues/errors?  

Thank you. You are always so helpful.

Hi Everyone, 

We have a requirement where certain product options in a bundle should no longer be selectable. These options should remain available as stand-alone products, but not as part of the bundle. 

Apart from creating a Product Rule with the Hide action, is there any alternative approach that can achieve this without relying on Product Rules, while also ensuring that existing in-progress transactions are not impacted?

Appreciate your guidance and suggestions. 

Thank you!

Sukumar 

Hello Everyone, 

We have a requirement to batch re-calculate all existing CPQ Quotes whenever the related Account record transitions to a specific stage. The solution should ensure that:

• No Quote records are skipped or missed during the re-calculation process.
• No record locks occur, preventing conflicts or failures during execution.

Tried an Approach by creating  a cross reference formula field on Quote and use the Same in Quote "Calculating Fields" field set which resulted in few of the Quotes are failed during re-calculation. 

Thanks in Advance ! 

Is it possible to reference a quote quantity range in the body of CPQ quote terms. 

For instance, if the quantity on the line item is 50, we want the quote term to reference 25-50 licenses available  

Hi everyone,

In Salesforce CPQ (managed package, Production), I have an approval process for Quotes. 

When a Quote is approved and set to

. 

Before, this triggered the Quote → Opportunity product sync, but now the sync isn’t happening.

Is there a version of Agentforce Quote Automation that works with CPQ+, or does it only work with Revenue Cloud Advanced?  If it does work with CPQ+, can you point me to any documentation with how to set it up?  (I tried a few searches within Trailhead and didn’t find anything).