#CPQ2 personnes en discutent

Currently we are looking to update our current discount schedules. Can someone confirm the following steps for the updated? Note: we have a Uplift for Renewal Method and Amendment and Renewal Behavior of Latest End Date. 

1. Create new discount schedules that are assigned to the product and the price book.
2. Remove the reference to the product and pricebook on the current discount schedules and the new discount schedule should apply.
   1. Will this affect pricing if a renewal quote or amendment quote is calculated? Or will it continue to use the existing pricing from the subscription being renewed or changed?
3. Renewals will use the original subscription pricing and add the uplift. If a new product is added at Renewal time it will use the new discount schedule.
4. Amendments will use the original subscriptions pricing but if a new product is added then it will use the new discount schedule

Then, if we want to go to Block Pricing eventually from Discount Schedules do the following steps seem right:

1. Clone all products setting the price method as Block (this would mean recreating all bundles as well).
   1. Create Block Pricing Tiers
   2. Should I use the same product code (as we have multi year contracts and we also do monthly billing)
2. Keep the old products with the discount schedules
3. Make the original products inactive or flag them in some way and filter those out of the add products process for new addition of products.
4. For Amendments, it will use the existing subscription pricing, unless a new product is added. It will then use the new block price product.
   1. Not sure how to avoid a reprice possibly on the amendment to the new product with block pricing.
5. Renewals are set for Uplift and will use the historic pricing but may want to move from the old product to the new product at renewal time.
   1. Need a strategy with the business on how this should be accomplished. Should we use the map of the old product to the new product via the Renewal Product field on the product. Will this work cleanly on bundles.

Any thoughts on these processes? 

At Kugamon, we believe successful Salesforce projects start with understanding the customer's goals before a single solution is designed. 

We're grateful for this feedback from Christiaan Feast

, who recently worked with our team during the discovery and scoping phase of a new initiative: 

Early project planning is one of the most important stages of any Salesforce implementation. Taking the time to ask the right questions, understand business requirements, and provide meaningful guidance helps set the foundation for long-term success. 

Thank you, Christiaan, for your kind words and for trusting Kugamon to be part of your journey. 

If you're evaluating solutions for CPQ, Quote-to-Cash, Revenue Operations, or Salesforce transformation projects, we'd love to connect. 

#Kugamon #Salesforce #CPQ #Quotetocash #DigitalTransformation

Hi Kugamoners, 

Kugamon v10.0 and v10.1 are here! 

We’re excited to introduce major enhancements focused on payment processing, operational efficiency, and platform modernization for your Quote-to-Cash workflows inside Salesforce. 

New Features & Enhancements: 

• Copy & PasteAdded Stripe Processor Connection Support 

• Updated the Online Payment Page to support Stripe Payment Processing 

• Added new Lightning Payment Terminal for Orders and Invoices supporting both Stripe and Manual Payments 

• Updated descriptions for all Validation Rules 

• Deleted deprecated object: Custom Payment Source 

🐞 Fixes (v10.1.1): 

• Resolved issue preventing Orders with Service Lines from releasing by updating the creation logic for related Service Delivery records 

•Fixed Payment Terminal cancel return behavior from the new Payment Page 

These updates continue our mission to deliver flexible, modern, and Salesforce-native Revenue Operations solutions. 

Have questions or feedback? Drop us a comment below! 

Cheers, 

Customer Success Team 

#SaaSInnovation

“A new bar for RevOps.” 

We’re incredibly grateful for this thoughtful review from Dave Moudy and proud to share it with the Kugamon community. 

Hearing that Kugamon helped simplify quoting, collections, renewals, and onboarding — while reducing implementation time from months to weeks — is exactly why we do what we do. 

One line especially stood out to us:

We’ve included a screenshot of the full review so you can read it directly in Dave’s own words. 

Thank you to Dave AND every customer who trusts Kugamon to power their Revenue Operations inside Salesforce. 

#Kugamon #CPQ #Quotetocash #Salesforce #RevenueOperations

Kugamon v9.3.4 is now here. 

This release focuses on improving pricing accuracy, service line consistency, and configurator behavior across Quote and Order workflows. 

Fixes and Updates: 

- Resolved an issue where the Quote & Order Import Lines function did not use the Price Book Entry Price for Sales Price when Sales Price was blank and List Price was defined. 

- Fixed an issue where Import Lines did not respect Service Line List Price and Service Term Behavior values. 

- Corrected behavior so Order Service Line List Price and Service Term Behavior now properly inherit values from the Quote during Order creation. 

- Added support for Tiered Pricing on Kit/Bundle members in the Quote and Order Lightning Configurator [Edit Lines]. 

- Updated available values for the Payment Type picklist field. 

These updates ensure greater consistency and reliability across pricing and service configurations. 

Have questions or feedback? Drop us a comment below. 

Cheers, 

Customer Success Team