industry-department-solutions
latest
false
- Overview
- Platform setup and administration
- Platform setup and administration
- Platform architecture
- Data Bridge onboarding overview
- Connecting a Peak-managed data lake
- Connecting a customer-managed data lake
- Creating an AWS IAM role for Data Bridge
- Connecting a Snowflake data warehouse
- Connecting a Redshift data warehouse (public connectivity)
- Connecting a Redshift data warehouse (private connectivity)
- Reauthorizing a Snowflake OAuth connection
- Using Snowflake with Peak
- SQL Explorer overview
- Roles and permissions
- User management
- Inventory management solution
- Commercial pricing solution
- Merchandising solution
Supply Chain & Retail Solutions user guide
Last updated Apr 16, 2026
Customers dataset
The customers dataset contains key information about customers used in manufacturing pricing scenarios. It defines who products are being quoted and sold to, and enables pricing analysis at customer and segment levels.
This dataset is required for both application deployment and pricing insights analysis.
Purpose
The commercial pricing solution uses the customers dataset to:
- Identify customers associated with quotes and sales transactions
- Enable customer-level pricing analysis
- Support segmentation and categorization for pricing strategies
- Differentiate pricing behavior across customer categories and subcategories
This dataset is essential for Quote Pricing use cases.
Required fields
| Field | Description | Type | Priority | Use | Notes |
|---|---|---|---|---|---|
customer_id | Unique identifier for each customer. | string | Required | Application / Insights | N/A |
customer_name | Customer name. | string | Required | Application / Insights | N/A |
customer_category | Customer category. | string | Required | Application / Insights | N/A |
customer_subcategory | Customer sub-category. | string | Required | Application / Insights | N/A |
source | Source of creation of the customer entry in the table. | enum | Required | Application / Insights | Enum values: peak, customerQuote Pricing - Data Onboarding... |
updated_at | Timestamp when the record was updated. | timestamp_tz | Required | Application / Insights | N/A |
Usage notes
- All customers referenced in the Quote Line and Sales datasets must exist in the Customers dataset.
- The
customer_idmust be consistent across all related datasets. - The
sourcefield distinguishes between records created by the Peak application and customer-provided records - Accurate customer categorization improves segmentation-based pricing strategies.
Why this dataset matters
Without the Customers dataset, the solution cannot evaluate quote pricing behavior, analyze customer-level demand response, or generate customer-specific pricing recommendations.