You are here:
Salesforce Pricing Limits
Review the default limits for Salesforce Pricing’s components and their usage. To modify the set default values, ask your Salesforce administrator to raise a support ticket.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions of Revenue Cloud where Salesforce Pricing is enabled |
Discovery Procedures
| Value | Default | Minimum | Maximum |
|---|---|---|---|
| The number of discovery procedures in an org | 2000 | 1 | 10000 |
| The duration that a discovery procedure can remain active | 10 seconds | 1 second | 60 seconds |
Pricing Procedures
| Value | Default | Minimum | Maximum |
|---|---|---|---|
| The number of pricing procedures in an org | 2000 | 1 | 10000 |
| The duration that a pricing procedure can remain active | 1 minute | 1 second | 2 minutes |
Pricing Elements
| Value | Default | Minimum | Maximum |
|---|---|---|---|
| The number of pricing elements in a discovery procedure | 50 | 2 | 100 |
| The number of pricing elements in a pricing procedure | 130 | 2 | 200 |
| The duration that a pricing element can remain active | 60 seconds | 4 milliseconds | 80 seconds |
| The number of mappings the Map Line Item element can have | 70 | - | 100 |
| The number of context tag mappings the Assignment element can have | 20 | - | 50 |
Price Impacting Attributes
| Value | Default | Minimum | Maximum |
|---|---|---|---|
| The number of price impacting attributes that can be associated with a product in an org | 25 | 1 | 50 |
Contributing Products or Assets
| Value | Default | Minimum | Maximum |
|---|---|---|---|
| The number of products that can be associated with a contributing product in an org | 40 | 1 | 50 This limit is the total number of contributors for a derived product. Both Transactional and Non Transactional |
| The number of assets that can be associated with a contributing asset in an org | - | - | 50 |
Other Limitations
- Pricing procedures don't support the children of sibling nodes for any context definition. For example, in the Sales Transaction context, children or descendants of a sibling node, Sales Transaction Item aren’t supported.
- Pricing element functionality is restricted to context tags at the Transaction Item and Transaction Header levels. Descendant and sibling node attributes are unsupported.
Did this article solve your issue?
Let us know so we can improve!

