Multiple application records may appear in the search result for defined search criteria in the Application Manager Screen. While some application records contain clear information, others may need more clarifying data. The application record must contain enough information to say whether the part is designed to fit a vehicle at all generic conditions or specific options / conditions.
The counterman must ensure that the part fits the vehicle and meets the customer’s requirements. As the fitment data is stored as an application record (linkages), the confusing application records must be addressed correctly. Thus, a solution to address confusing application records is called the ‘Confusing Counterman Solution.’
This solution is designed to improve the process of selling the correct part to the customer in the retail store. When a customer wants to buy a part for a vehicle, the counterman may have to ask questions about the vehicle to ensure that the right part is being sold. The questions are guided by the data populated in the application records. If multiple identical application records exist that would confuse the counterman, such application records are considered unclear / confusing application records.
For example, if an application record mentions that the part would fit the vehicle belonging to a specific SubModel, then the counterman must know the SubModel of the customer’s car.
The implementation of this solution will:
-
Limit the questions that a counterman would ask. For example, if a customer’s car model only exists with one engine, the counterman is clear about this and need not have to ask what engine is in the customer’s car.
-
Clarify the counterman about the type of questions to ask the customer.
-
Ensure that the counterman should have one precise result to suggest to the customer. The clear difference between the multiple results is displayed if there are multiple results.
The Confusing Counterman solution can generate a report of ambiguous application records when configured within the Application Manager screen. The report is called as confusing counterman report. The objective of generating the report is to identify the confusing application records and rectify the ambiguity in the application records.
This document includes the following related to the Confusing Counterman solution: