CPQ Master Data Model

This layer defines the static, reusable data that forms the backbone of your product catalog and pricing structure. Key components include:

• Products (Product2): Represents the items or services being sold. Products can be standalone, bundles, or options.
• Attributes and Attribute Groups: Define product characteristics (e.g., color, size) and organize them for reuse.
• Price Lists and Price List Items (PLI): Price Lists act as containers for pricing strategies, while PLIs link products to specific price lists with details like list price, charge type, and effective dates.
• Catalog Structure: Organizes products into categories and subcategories for easy navigation.
• Product Groups: Logical collections of products used for applying rules or pricing strategies across multiple items.

CPQ Transactional Model

This layer captures dynamic, quote-specific data generated during the sales process. It includes:

• Cart and Line Items: Represents the customer's selections during configuration and quoting.
• Attribute Values at Line Item Level: Stores user-selected attribute values for each product in the cart.
• Pricing Details: Includes applied price lists, discounts, promotions, and calculated net prices.
• Approval and Workflow Data: Tracks approval steps, statuses, and routing logic for quotes.

Key Relationships

• Product ↔ Price List ↔ Price List Item: Products are linked to multiple price lists through PLIs, enabling flexible pricing strategies.
• Bundle ↔ Options ↔ Attributes: Bundles group products and options, while attributes define variations without creating SKU proliferation.
• Cart ↔ Line Items ↔ Attribute Values: Captures real-time configuration and pricing data during quote creation.

Best Practices

• Keep Models Simple: Avoid unnecessary nesting in bundles and excessive custom objects.
• Use Attributes Over SKUs: Manage variations through attributes instead of creating multiple SKUs.
• Leverage Price Matrices: For tiered or ramp pricing, use matrices linked to PLIs for efficiency.
• Maintain Data Integrity: Regularly review inactive products, options, and rules to keep the catalog clean.