Why make bulk updates to product information in CPQ configurations?
Product codes, SKUs, product families, and names are central to CPQ configuration. However, product information often changes due to:
Product discontinuations
Code or SKU standardization efforts
Rebranding or restructuring of product families
Pricing strategy adjustments requiring consistent product data
Failing to update product references across CPQ configurations can lead to:
Inaccurate pricing or discounting
Broken product bundles or configurations
Approval processes referencing outdated products
Increased maintenance effort due to inconsistent product data
Bulk updates ensure product references remain consistent, reducing configuration errors and improving quote accuracy.
When to perform bulk updates to product information?
Use this solution guide when:
Products are discontinued or replaced
Product codes or SKUs change due to business decisions
The organization restructures product families
There’s a need to report on all pricing-affecting configurations for a product family
Audit findings reveal inconsistencies in product references
Avoid making bulk changes during critical sales periods without proper validation and approval.
Prerequisites
Before proceeding, ensure you have:
Access to the Elements.cloud platform with a connected Salesforce Org.
Revenue Cloud (SBQQ) Add-on license
Space admin permission to create MetaFields
Perform Bulk Updates to Product Information
Step 1: Search for product references using code search
To identify where products are referenced across your CPQ configuration:
Navigate to the Code Search feature in Elements, by right-clicking on the Org name at the top of the Metadata Dictionary.
Select "Find a specific string".
Type in a string corresponding to any of the following attributes from Product2 record:
Product Name
Product Code
SKU
Product Family
The results will include references across the following Salesforce objects:
Product feature, product option, product action, option constraint
Configuration rule, block price, price rule, price dimension
Contracted price, discount schedule
In addition to metadata, the search will return references within:
Flows
Apex classes and triggers
Other custom code that references product attributes
Step 2: Analyze and select impacted configuration records
Review the search results to identify records needing to be updated. You can see which objects the records belong to, and filter the list down to specific type (e.g. price rules).
As you are reviewing records that show references to product name, code, SKU or family, consider:
Should discontinued products be removed from configurations?
Do updated SKUs or product codes require amendments to price rules or options?
Are product family restructures reflected in block prices or discount schedules?
You can open the right panel for each record and click on the Salesforce icon to open it in Salesforce and investigate the logic directly. You can then make a decision on how to proceed with the record.
Step 3: Raise user stories for updates or deletions
From the results, bulk-select the configuration records that you have decided to either delete completely or update.
Then bulk-create user stories from the selected record to capture the work required. Add context to each user story, specifying:
The reason for the change (e.g., “Product discontinued” or “SKU update”)
Desired future state (e.g., “Replace references with new product code XYZ”
Assign captured stories to the appropriate team members and link them to Jira if needed, using Elements.cloud's integration capabilities. You can then pick up those stories for development from your backlog and deliver it when there is capacity.