This scenario applies when Products, Customers, and Transactions are all present with stable identifiers. It describes the baseline data condition, why it matters for Agent design, and how to get started.
Data
-
Products are available with a stable unique Product Id, Product Name, Hierarchy, and relevant attributes.
-
Customers are available with stable IDs at the pricing-relevant level, together with hierarchy and geography where applicable.
-
Transactions are available at line-item level and link product and Customer Ids. Typical fields include:
-
Date
-
Quantity
-
Currency
-
UOM
-
Price
-
Discounts
-
Costs
-
Margin
-
-
The Pricefx Quick Start - Template and Sample Data (Pricefx Quick Start - Template and Sample Data.xlsx) provides the reference structure.
Why it Matters
This is the baseline Pricefx data model. Products, Customers, and Transactions are the primary contexts required in most deployments. Stable identifiers allow Agents to join and aggregate data by:
-
Product
-
Customer
-
Segment
-
Geography
-
Business Unit
This is also the best starting point for the Curated Agents. They provide predefined analytical use cases such as:
-
Margin Variance
The Curated Agents are available without requiring each customer to design a fully custom Agent from scratch.
Advice
-
Start with the Curated Agents that match the available measures and business objectives.
-
Load the mandatory/core Analytics fields first.
-
Add business-context and waterfall fields incrementally.
-
-
If multiple currencies or units of measure are used, normalize them or provide valid conversion data.
-
Keep the Product/Customer/Transaction identifiers consistent across all data contexts.