Skip to main content

#CPQ16 personnes en discutent

We’ve updated the Kugamon website!

 

We’re excited to share a refreshed online experience designed to make it easier to explore Kugamon and discover how we help businesses streamline CPQ, Quote-to-Cash, Billing, and Revenue Operations — all natively in Salesforce. 

 

Whether you’re new to Kugamon or have been following us for years, we invite you to take a look around and see what’s new. 

 

Visit the updated Kugamon website and let us know what you think: https://www.kugamon.com/

 

#Kugamon #Salesforce #CPQ #Quotetocash #SalesforceApps #SAAS

0/9000

I have two items related to reconfiguring bundles and how to handle existing subscriptions and assets. 

First Bundle

 

Currently we have a bundle configured as below:

  1. Bundle Header (Parent) - Product A (renewable subscription that has a price associated with it)
    1. Child Product (product option) - Product B (one-time asset that has a price associated with it).

When added to a quote, since the child is not flagged as Bundled, pricing sits at both lines. The business now wants to re-design the bundle. They want it to look like the following:

  1.  Bundle Header (Parent) - Product C (renewable subscription that has a $0 price)
    1. Child Product (product option) - Product A (renewable subscription that has a price associated with it).
    2. Child Product (product option) - Product B (one-time asset that has a price associated with it).

Pricing would sit at each child product line. I was thinking I could just reconfigure the bundle by creating the bundle header and adding Product A as a child and then Product B as a child. And remove the child option (product B) from from Product A (basically breaking the original bundle apart).  

But my concern is existing data that was sold under the current configuration. Do I create subscription bundle headers and then realign the current subscriptions and assets to the new bundle header (adding the Root ID, Required By ID, adjust the product option information on each subscription and asset)? If so, what are the possible risks to amendments and renewals? If this is not the best approach what would you suggest? I can’t create new product codes so I need to use the current products and product codes. 

 

Second Bundle

We have a one time subscription Service product that is part of two bundles. We want to break this apart from the bundles to make it standalone and have it only added on new sales quotes. This Service product is a one-time subscription product.  

For new sales, I need to hide the options within the two bundles and have the product auto added. For amendments, I need the options available for the products being revised but if we are adding one of the two bundles for the first time we need the option for the Service product hidden in both bundles.  

How would i build this? For new sales I am thinking a product selection rule to add the standalone product. For new sales a product selection rule to hide the options. For amendments, how would I approach this? 

 

Thank you. 

 

#Salesforce CPQ & Billing  #CPQ  #CPQAskAnExpert

1 réponse
  1. 27 sept., 13:11

    Hi Rachel,

    For the first bundle, I’d be cautious about manually changing the existing Subscription/Asset hierarchy (Root ID, Required By ID, Product Option, etc.). Those relationships are used by CPQ/Billing during amendments, renewals, and asset/subscription management, so manually realigning historical records could introduce issues later. 

     

    A safer approach is generally to keep the existing sold structure intact for historical subscriptions/assets and use the new bundle configuration for future sales. Since you need to retain the existing product codes, I’d validate the impact on amendments and renewals in a full sandbox before changing any existing subscription hierarchy. 

     

    For the second bundle, your approach of using Product Selection Rules for new sales makes sense. For amendments, I’d make the rule criteria aware of whether the quote is an amendment versus a new sale, and whether the bundle already exists on the customer's subscription/assets. That way, the Service product can remain available when amending an existing bundle while being excluded when the bundle is being added for the first time. 

     

    Because this involves existing subscription/asset relationships, I’d test several scenarios—new sale, renewal, amendment of the existing bundle, and adding the bundle for the first time—before deploying the configuration. If you can share the CPQ package version and how your amendment quotes are currently configured, it would help determine the exact rule conditions. 

0/9000

I'm struggling with a flow. I have a new product, MCP which can be added to 2 different existing products my company sells. I have created this new product and made it an option for the existing product. Our design has both the Lead Product and its options bundled under one master product.  

 

-Bundle Product 

---Lead Product 

---Add On 1 

---Add On 2 

---Add On 3 (New Add On) 

 

Only the Lead product creates a subscription object, so I want to note on the Lead Product Quote Line (so that it easily flows through to the subscription) that Add-On 3 is also on the quote. 

 

In the bundle, the Lead Product is required, but the Add Ons are not. 

 

I created a flow that says when a quote line is created and the product is Add On 3 then use the SBQQ Required By field to identify the parent. Then get all the other quote lines on the quote for which the Bundle Parent is the same and filter for the one named Lead Product. Update a field on Lead Product to say "Add On 3 present" = True. 

 

If the whole of it is added at one time, the flow works as expected. If however the quote is for a renewal and we are just looking to add only the add on, it is not updating the existing Quote Line. 

 

Steps to take: Open Existing Quote Line Editor, configure the Bundle Parent, check the new add on and save the Quote Line Editor. 

 

When you run it in the debug and identify the newly created quote line as the "run as though this was created" it works as expected in all situations. 

 

#Flow  #CPQ

1 réponse
  1. 26 sept., 14:57
    Interesting! If I were troubleshooting this flow, I would check failed flow interviews just to make sure it's not failing without notifying me for some reason. Then, I would try modifying the flow to run on create OR update. I'm not sure what all is happening on the backend in your instance, but if it's not triggering the flow on create, maybe it is created first and then updated to match criteria, which would not trigger your flow.
0/9000

Hello, 

Currently our system is built that upon the creation of a quote for a new sale they set a custom Contract Term field on the quote to the length they want the term to be (for example, 36) and then on the quote they set the Subscription Term to 12. They have automation that then creates a Master Agreement that is a high level agreement that contains the full length of the contract (for example, start date of 1/1/2026 through end date 12/31/2029) and on the master agreement the contract term says 36. And then there is a child agreement that is related to the master agreement (a child to this agreement) that has a contract term of 12 and a start date of 1/1/2026 through 12/31/2026. Then on 12/30/20206 they create a new Subscription Agreement via an auto renewal process for Year 2 with dates of 1/1/2027 through 12/31/2027. Then do the same thing at Year 3 for dates of 1/1/2028 through 12/31/2028. Then on 1/1/2029 they complete what is called a contract renewal where the above starts over again with a new master agreement then child subscription agreements. 

 

Now with a new sales they want to move to a quote with the custom contract term of 36 months and subscription term of 36 months but within the quote are quote line groups for Year 1, Year 2, Year 3 of 12 months. When the contract creates they want one contract containing the whole contracts information. Then at the end of the 3 years the "contract renewal" occurs for the 36 months for the contract term and Subscription Term. 

 

The issue is existing contracts on the old structure. How do we handle the interim subscription agreements before the contract renewal if we remove the master agreement. And then how do we move to the new contract renewal process at the end of the compete term. I am assuming some sort of data migration but not sure what that would be or would look like. 

 

Has anyone else had to go through this? And nope they do not want MDQ. 

Thank you. 

 

#Salesforce CPQ & Billing  #CPQ  #CPQGurus  #CPQAskAnExpert  #Salesforce Developer  #Architects

2 réponses
  1. 20 sept., 14:32

    @Sai T

     

    Thank you for your response. This is the recommendation I gave as how to move forward with this change. 

    If you had to have some mechanism to determine the existing current structure versus the new what would you use? For example we have a Year in Contract field for the current structure which is a formula field but that doesn't say whether a contract is new or existing. I wonder if we should create a field on the backend that we update via an upload that flags a contract as "Legacy"/"Existing" new. Just trying to think of the best approach so that the automation will know that a contract is existing or new so we don't accidentally take the interim renewal and try to convert it to the new structure. We do have a field called Upcoming renewal type that says Subscription Renewal or Contract Renewal. I think we can use that to say basically exclude subscription renewal and look at the ones that are contract renewal.

0/9000

Customer success is at the heart of everything we do at Kugamon. 

 

We’re grateful to Christian Gennerman for sharing his experience with Kugamon and highlighting what matters most to us — delivering exceptional support alongside powerful Quote-to-Cash solutions. 

 

“Kugamon works exactly how we need it. The real bonus is the customer service.” 

 

Christian shared how our team provides responsive support, meaningful answers, and a willingness to connect directly when help is needed. 

 

We believe great technology is only part of the solution — having a dedicated team that understands your goals and is there when you need us makes the difference. 

 

Thank you, Christian, for trusting Kugamon and sharing your experience with our community! 

 

#Kugamon #Salesforce #CPQ #Quotetocash #SAAS

  

Customer success is at the heart of everything we do at Kugamon.

 

 

0/9000

We’re continuing to enhance the Quote-to-Cash experience with improvements designed to provide a more seamless and reliable Salesforce-native workflow. 

 

🐞 Fix: 

• Resolved an issue where the Sidebar Filter Panel feature did not support Purchased Assets, Contract Assets, and Contract Subscriptions in the Quote and Order Lightning Configurator [Add Lines] function. 

 

This update improves flexibility when managing customer assets and subscription-related products, helping teams create and manage quotes and orders with greater confidence. 

 

Have questions or feedback? Drop us a comment below! 

 

Cheers, 

Customer Success Team

#CPQ #Quotetocash #Kugamon #SalesforceApps #SaaSInnovation #ReleaseUpdate 

0/9000

Kugamon v10.5 is here! 🚀 

 

We’re continuing to enhance your Quote-to-Cash experience with new configuration flexibility and improved online order workflows. 

 

✨ New Features & Enhancements: 

• Added a new Hide Kit/Bundle Member setting to the [Manage Kit/Bundle] function. 

• Updated the Quote and Order Lightning Configurator [Edit Lines] function to support the new Hide Kit/Bundle Member setting. 

• Added an Order Acceptance Banner to the Online Order Confirmation Page. 

• Added an E-Sign Consent Checkbox to the Online Order Page. 

 

These updates provide greater control over product visibility, improve customer-facing order experiences, and help streamline digital acceptance workflows. 

 

Have questions or feedback? Drop us a comment below! 

 

Cheers, 

Customer Success Team 

#CPQ #Quotetocash #Kugamon #SalesforceApps #SaaSInnovation #ReleaseUpdate 

0/9000

Hi Everyone, 

while doing the trailhead challenge i'm facing the error. i've attached the reference image below. Could anyone please help 

 

 

 

Facing the There was an unhandled exception. Please reference ID: XRSJHNFB. Error while attempting the trailhead challenge

 

 

 

 

There was an unhandled exception. Please reference ID: XRSJHNFB.

 

 

#Trailhead Challenges #CPQ

1 réponse
0/9000
Supriya Joshi a publié du contenu dans #Job Postings

🚨 HIRING | SALESFORCE CPQ DEVELOPER 🚨

🚀 Looking for a Salesforce CPQ Developer to join a Leading Global Consulting & Professional Services Organization.

📍 Hyderabad | Gurgaon

 

🏠

Hybrid Work Model

 

💼

Experience:

4+ Years 

⚡

Immediate Joiners / Serving Notice Period

🔥 Key Requirements

✅ Strong Salesforce & Salesforce CPQ

experience 

✅ Hands-on

CPQ implementation

experience 

✅ Experience delivering end-to-end CPQ projects 

✅ Strong CPQ configuration & development skills

🌟 Exciting opportunity to work on impactful Salesforce CPQ projects with a global organization!

📩 Share your CV: supriyah@wen-jobs.co.in

 

📞

Contact:

7892999581 

 

#Job Postings  #Salesforce CPQ & Billing  #CPQ  #Salesforce

0/9000

PLEASE ANSWER ONLY IF YOU ACTUALLY KNOW 

WHAT YOU ARE TALKING ABOUT.  ChatGPT and Google did not help. DO NOT PASTE THAT JUNK HERE. Get Answer Leaderboard "points" on someone else's time. 

 

I have the System Admin profile with View All Data and Modify All Data permission.  I cannot see the New Quote button in the header on Opportunity Lightning Pages.  I have a user with a Business profile who also cannot see the button.  I have a different user with a Sales profile who CAN see the button.  In my Sandbox, I switched the blocked user to the Sales profile, logged in as him, and still cannot see the button.  When I log in as the Sales user I can see the button.  I checked different record types in different apps.  The Sales user always sees the button the Business user and Sys Admin never see the button. 

 

All three profiles see the same page layout for each Opportunity Record type.  "New Quote" is a custom create record action on the Opportunity object.  It works for the Sales user with no issues or errors.   

 

"New Quote" is an Action on the Opportunity object.  It is not a Global Action.  I checked the fields on the Action Layout and the predefined fields in the Action.  All three profiles have View permissions on all fields and none of the fields are Read Only for anyone.  The Object of the Action is Opportunity and the target is Quote.  The Record Type is Master.  The Sales and Business profiles have Master as the default Record Type for Quotes.  Sys Admin has Standard as the default Record Type.

 

All three users are Flow users.  All three users are Marketing users.  We all have the Salesforce CPQ User (or Admin) permission set.  We all have the CPQ permission set license.  We all have the CRM permission set license. 

 

The Lightning Page we are seeing i the org default.  When I view the page in the Lightning Editor, I still don't see the "New Quote" button in the header.  There is no filter on the header component.  The same Compact Layout is assigned to all Record Types. 

 

The only CPQ plug in we have is a Product search.   We do not put Quotes in Queues.  We do not use Roles and Hierarchy.

 

What am I missing? 

 

#CPQ  #CPQGurus  #Quotes  #Opportunities  #Pagelayouts  #Lightning App Builder  #User Profiles  #Quick Actions

2 réponses
  1. 11 sept., 06:48

    I added this to the original post as well, in case someone who knows how to do this reads it:  The Object of the Action is Opportunity and the target is Quote.  The Record Type is Master.  The Sales and Business profiles have Master as the default Record Type for Quotes.  Sys Admin has Standard as the default Record Type.

0/9000