Here you can find a list of mandatory and optional data for Accelerator Packages. It helps you identify what data you need from the customer to set up and configure the packages.
Accelerate Price Setting Package
For this package you could start with requirements for Core (Product Data) and at least mandatory data for one pricing strategy.
Type | Data | Fields | Mandatory for Use Case |
|---|---|---|---|
Master Data | Products |
| Core Technically SKU could be SKU, but this would probably make no sense - you could completely “skip” the lookup key concept by defining SKU as the only Lookup Key Dimension and configure everything with the “*” value |
Product Cost | Mandatory:
Optional
| Cost+ Pricing Strategy Margin Calculation / Margin Checks | |
Advanced Cost Definition | Per Advanced Cost type:
| Advanced Cost Module | |
Discount Structure | Discount Groups and Discount Values | Pricing on List Price → Net Price level | |
Exchange Rates | Currency and Conversion Rates | Dependent pricing in different currencies | |
Competition Data | Mandatory:
Optional:
| All Competition Based Pricing Strategies | |
Pricelist Data |
| Initial Prices All checks and KPI regarding price increase Pricing Strategy: Price Increase | |
Stock Data |
Optional:
| KPI Days of Cover (DoC) DoC related Pricing Strategies | |
Product References |
| Pricing Strategies: Anchor Pricing, Attribute Based Pricing | |
BoM (Kit List) |
| Pricing Strategy: Kit Pricing | |
Business Data | Plus for Product |
| Cost+ based Pricing Pricing Strategy |
Price Increase |
| Price Increase Strategy | |
Pricing relevant Attributes |
| Attribute Based Pricing Strategy | |
Pricing Level Adjustment |
| Dependent Pricing of Independent (e.g. Global Reference Pricelist → Country Pricelist) | |
Sales Forecast |
Optional:
| Lookup Based Forecast (optionally, we can use Lookup Based or Transaction Based Forecast) | |
Transaction Data | Sales Data (Transactions) |
Optional:
| All KPI regarding “Sales History”
|
Accelerate CPQ Package
Type | Name | Fields | Mandatory |
|---|---|---|---|
Master Data | Product | Core data | |
Customer | Core data | ||
Product Extension | ProductCost | Mandatory:
Optional:
| Core data |
Price List | Core data | ||
Product Extension |
| Mandatory:
Optional:
| Mandatory if the price of the product is not in the price list |
Model Record | PriceOptimizer model | Mandatory:
Optional:
| Optional |
Product Extension | PriceGuidance | Mandatory:
Optional:
| Optional |
Product Extension | PriceCompetitors | Mandatory:
Optional:
| Optional |
Customer Extension | CustomerCashDiscount | Mandatory:
| Optional |
Price Parameter | StandardDiscount | Mandatory:
Optional:
| Optional |
ExceptionDiscount | Mandatory:
Optional:
| Optional | |
Transaction Data | Sales data | Mandatory:
Optional:
| Optional |
Accelerate Sales Insights Package
Type | Data | Fields | Use Case |
|---|---|---|---|
Transaction Data | Sales Data (Transactions) |
Optional:
| You can add additional fields for your waterfall definition. Basically you can add every field that follows your pricing journey starting from the List Price and ending at the pocket price.  You can have different price points as well as adjustments. Note that in the example below the price points are in bold and have adjustments in between. Typically you have items like:
|
Master Data | Product |
| The Product / Customer Masterdata is used for two scenarios: Filtering and Dimensions. Filtering allows you to define the Products/Customers you want to include in your analysis.  Typically you can include following fields for this reason. Product:
Customer:
The second use case is to define the Product/Customer aggregation to have a view on your portfolios from different angles. You can find this aggregation in chart types like Pie Charts (definition of the “pieces” or Scatter Charts (band by).   |
Customer |
|
Accelerate PO Package
Please note: Accelerate PO Package has very similar data requirements as Sales Insights Package. Just pay attention to the slightly different purpose of the Product/Customer attributes in the two packages. It is encouraged to deploy Accelerate Sales Insights Package first and include all Product/Customer fields that you will need for the segmentation right away.
You can use this Excel Template to get an idea what the data could look like:
Type | Data | Fields | Use Case |
|---|---|---|---|
Transaction Data | Sales Data (Transactions) |
Optional:
| Transaction data is essential for price optimization process.
|
Master Data | Product |
| Product and Customer master data is used to drive the segmentation process. Good examples for Product Dimensions are: Product:
Customer:
These Dimensions are used in the Optimization model to drive the segmentation of the model. Each segment will be optimized separately.  Try to add as many product attributes as possible to make sure the Machine Learning Algorithms can evaluate the most optimized segmentation tree.  |
Customer |
|
Accelerate Customer Insights Package
Type | Data | Fields | Use Case |
|---|---|---|---|
Master Data | Customer | Custom attributes (optional) |
|
Product | All the dimensions in the relevant Product Data Source (optional) | Customer Products Portfolio: Pricing and Selling Opportunities by Product Attribute:
| |
Transaction Data | Sales Data (Transactions) |
| Core. |
PricefxPlasma
Type | Data | Fields | Use Case |
|---|---|---|---|
Transaction Data | Sales Data (Transactions) |
Optional:
| Transactions data is essential for Plasma Transactions core functionality. |
Quotes | Quotes Data |
Optional:
| Quotes data is essential for Plasma Quotes core functionality. Selling To, SellingFrom and Unique ID are necessary in case Plasma Quotes Enrichment is applied. |