WKS 11b - Quote Model and Structure Part 2
Workshop on to continue covering the quote model and structure.
Participants
Name | Company | Role |
|---|---|---|
Teemu Salonen | Valio | Pricing Analyst |
Tomi Toivonen | Valio | Pricing Manager |
Omar Bendada | Ben Consulting Services | Business Analyst |
Sofia Simaria | Ben Consulting Services | Proxy Product Owner |
Kaoutar Bennadi | Ben Consulting Services | Developer |
Alain Becker | Pearson Ham Group | Operation Manager |
Christiaan Van Eden | Pearson Ham Group | Consultant |
Goal
This workshop is to define the quote model and structure.
Workshop materials
Topic | Document | Comment |
|---|---|---|
CPQ tool | CPQ tool demo | Tool walkthrough to illustrate functionalities and assess alternatives |
Valio specs |
| Understanding Valio-specific requirements |
Main results
Quote System Structure and Product Information
Team discussing quote model and information to include for product groups and online items
Proposed view for quote system: basic product information, ID, name, pricing, and guidance in one view
Guidance values from Zilliant determined by customer ID and product ID combination
Product categories correspond to specific columns in quote line
Omar proposes creating specific tables for each product category
Separate tables recommended to reduce back-office risk
Product details potentially needed for customer-facing quote document
Goal is to add product attributes that can be visible in the system and referenced for calculations
Need to create a column referencing basic milk products for overall volume calculations
Goal: Create comprehensive quote model template documenting all discussed quote and quote line item fields
Volume and Pricing Calculations
Line item volume not directly considered in Zilliant guidance results, but transaction volume impacts optimization
Annual volume will be manually entered by sales representatives in quote line
Basic milk products have unique volume calculation: volumes aggregated across similar products to determine pricing class
Complex scenario identified: Products A and B might have same volume but different invoice prices
Sales reps will input total volume across products to determine product classification
Team agrees to revisit volume and classification logic in next session
Performance concern: Querying 2000 products repeatedly can create system slowdown
Product Availability and Discontinuation
Products with future sales max date can still be selected, with sales reps informed about potential deletion
Consider flagging products with future sales max date to alert sales reps about potential discontinuation
Currently no supersession information to track product replacements
Sales max date should be compared against agreement start date for product selection
Potential new rule: max date should be greater than Start date plus 31 days
Explore strategies for handling product discontinuation, including visual flagging in quote system
Distribution Channels and Delivery Charges
Implement system alerts preventing sales reps from adding products unavailable in specific distribution channels
Add source origin column in quote system to help sales reps select most appropriate product source
Investigate delivery charges calculation based on parent vs child customer geography
Customer typically prefers single delivery charge across multiple locations
Team processes 100,000-200,000 deliveries annually and aims to generate delivery charge revenue
Delivery charge recommendations to be manually defined by pricing team, not auto-generated in Price IQ
Action list
- BCS to document quote model and structure for Valio to review
- BCS to assess requirements for customer master data processing, so as to capture the relevant parent customer data from the original children in customer master and transactions (eg geography, category…)
- Valio to redesign lookup table for Basic Milk guidance
- Valio to check if there is a field in Product master that could be used to flag products as ‘Basic Milk’ or the other relevant categories within the Valio guidance and regulatory limits
- Team to consider consolidating the multiple Valio guidance tables into a single table
- BCS team to ask Zilliant if possible to visually highlight item lines based on the product discontinuation logic
Decisions
- Since we cannot have multiple ‘Items' tabs according to where the products are sourced from, this can be managed by adding a column 'Product Source’ to the quote line item.
- Data processing of customer data from Zilliant is still something worth exploring, as it could bring a lot of value. Let’s define the use-cases/complexity and define a plan/estimate with Zilliant.
List of requirements
‘Product Source’ column in the quote line with options ‘Valio WH’, ‘Valio Factory’, FSD, CC
Product attribute ‘Distribution Channel’ to be used for warning sales reps is they are adding products unavailable in the distribution channel relevant to the quote.
Session recording
https://tldv.io/app/meetings/682ef5d9fc81be001310389e/