Overview
Transactional Pricing is split through the following stages :
- Product manager defines in pVelocity whicg prices to apply to which Sold-To/Material
- Sales Reps commits in Salesforce for the price they have negociated with their customer
- Product Manager need to Approve or Reject the committed price if it is below the asked
Target Price
General Process | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Table of content
Without transactional pricing, price increases are often focused on | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Transactional Pricing aims at reducing price dispersion amongst | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Transactional pricing is a 5-step approach | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Why in pVelocity? | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Commitments records are created by pVelocity directly in Salesforce from the scatterplots defined by the Product Manager. Sales Reps commit for prices and Product Managers approve or reject commitments directly in Salesforce. When a Commitment is updated in Salesforce, those modifications are sent back to pVelocity |
pVelocity and Salesforce | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
