Mandatory Data (PO) | Pricefx Knowledge Base

warning 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:

Sample_Data_Structure.xlsx

Type	Data	Fields	Use Case
Transaction Data	Sales Data (Transactions)	Unique Id (String) Product Id (String) Customer Id (String) – mandatory if customer master is deployed Pricing Date (Date) Invoice Price (Money/Number) Gross Margin (Money/Number) Gross Margin Rate (needs to be added as a calculated field in Datamart after deployment. It is “Gross Margin / Invoice Price”) Quantity (Quantity/Number) Optional: Currency (you need filled Ccy Datamart when using currency) UoM	Transaction data is essential for price optimization process. Product/Customer master data should be provided in a separate data structure if it is to be used in segmentation and deal guidance.
Master Data	Product	Product Id Product Name Up to 30 custom attributes	Product and Customer master data is used to drive the segmentation process. Good examples for Product Dimensions are: Product: Product hierarchy Brand Product performance markers Competitive / Captive Product Lifecycle Basic / Premium Products Customer: Regional Data / Org Data Country Region Sales Office Sales Org Customer performance markers Loyalty Size / Classification 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	Customer Id Customer Name Up to 30 custom attributes

Type

Data

Fields

Use Case

Transaction Data

Sales Data (Transactions)

Unique Id (String)
Product Id (String)
Customer Id (String) – mandatory if customer master is deployed
Pricing Date (Date)
Invoice Price (Money/Number)
Gross Margin (Money/Number)
Gross Margin Rate (needs to be added as a calculated field in Datamart after deployment. It is “Gross Margin / Invoice Price”)
Quantity (Quantity/Number)

Optional:

Currency (you need filled Ccy Datamart when using currency)
UoM

Transaction data is essential for price optimization process.

warning Product/Customer master data should be provided in a separate data structure if it is to be used in segmentation and deal guidance.

Master Data

Product

Product Id
Product Name
Up to 30 custom attributes

Product and Customer master data is used to drive the segmentation process.

Good examples for Product Dimensions are:

Product:

Product hierarchy
Brand
Product performance markers
- Competitive / Captive
- Product Lifecycle
- Basic / Premium Products

Customer:

Regional Data / Org Data
- Country
- Region
- Sales Office
- Sales Org
Customer performance markers
- Loyalty
- Size / Classification

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

Customer Id
Customer Name
Up to 30 custom attributes