Selling vehicle-compatible parts on a spare parts site
Compatibility uncertainty is the biggest obstacle to sales in spare parts. This guide explains how to clarify the vehicle, why searches must be exact matches, and where compatibility data should reside.
The most critical moment in spare parts sales is when the visitor thinks, 'Will this part fit my vehicle?'. Regardless of how competitive the price is, a visitor unsure of compatibility either calls or leaves the site. Selling the wrong part means returns, shipping costs, and customer dissatisfaction. This guide explains how to structure vehicle-compatible sales on a spare parts site.
Information required to clarify the vehicle
The same model name may be produced with different engine and chassis options in different years. To find the compatible part, the following information is usually required:
- Brand and model (e.g., Fiat Egea, Renault Clio 5)
- Model year
- Engine (e.g., 1.3 Multijet, 1.0 TCe)
- Body type (sedan, hatchback) if necessary
- Chassis number in uncertain situations
Once this information is clarified, it should not be asked again for the rest of the conversation. When the visitor asks for discs, then brake pads, then oil filters, the same vehicle information should be used.
Part code and OEM number
Experts and experienced customers search for parts by code. When an OEM number or stock code is entered on a site, an exact match should be searched; when the code matches, the list should not be filled with other similarly named products. Otherwise, a customer who entered the correct code would be offered the wrong part.
Where should compatibility data reside?
Compatibility information on most spare parts sites resides in one of two places: as text in product descriptions or in a matching table between vehicle and part in the database. The matching table is more reliable because information like 'Fiat Egea 2015-2023 1.3 Multijet' can be written differently in text, whereas in a table it is in a single format. For an AI agent to read this table directly is the most important factor determining the accuracy of the answer.
| Approach | Advantage | Point to note |
|---|---|---|
| Compatibility in product descriptions | No extra table needed | Consistency must be ensured |
| Tool-part matching table | Uniform, queryable | Table must be kept up to date |
| Equivalent code table | Suggestion for parts not in stock | Equivalence information must be verified |
Reminding of complementary parts
Customers replacing brake discs are advised to also replace pads, and customers buying timing belt kits are advised to consider the water pump. These suggestions increase the sales value, but their primary benefit is preventing issues for the customer during installation. Having these suggestions written in the knowledge base ensures that every representative makes the same recommendation.
Currency and price freshness
After finding a compatible part, the customer's first question is about stock and price. In systems working with catalogue feeds, this information is as up-to-date as the last transmission; in systems connected directly to the store database, answers are provided with real-time information. Whichever is chosen, the price displayed to the customer must come directly from your data.
Conversation example
It is easiest to see how compatible sales work with an example. The visitor writes 'front brake disc'. Instead of showing the list immediately, the representative asks for the vehicle; the visitor says '2019 Egea, diesel'. The representative clarifies the engine (1.3 Multijet), searches the catalogue with this vehicle, and shows two products: front brake disc kit and compatible pads. The visitor wants to add the disc to the cart; the representative adds it using the site's add-to-cart action and reminds them of the free shipping threshold. Throughout the conversation, vehicle information was asked only once, and the visitor did not browse any pages.
Customer asking and knowing codes
Spare parts sites have two types of customers. End users know the vehicle but not the part code; mechanics or garages know the code and want quick results. The same conversation serves both customer types well: for the mechanic writing the code, the matching product is shown immediately; for the end user describing their vehicle, a few questions are asked first. Writing short answers in the knowledge base for frequent stock and delivery time queries significantly reduces phone traffic.
Preventing returns and wrong parts
The cost of selling the wrong part is not just the shipping fee; the customer's vehicle waits at the garage, installation appointments are missed, and trust is damaged. Therefore, in situations where compatibility cannot be guaranteed, it is correct to hand over the conversation to the team rather than forcing the sale. Since the panel shows which product search the representative based their answer on, suspicious suggestions can be quickly checked by the team.
How SmartOperator solves this
In SmartOperator, the spare parts template clarifies the brand, model, year, and engine; when a part code is entered, a direct match is searched in the catalogue.
- Spare parts template: brand, model, year, and engine are asked; chassis number may be requested.
- Direct code search: when the code matches, the list is not populated with loose results.
- Store database: the matching table and stock are read only via a read-only connection.
- Product card and cart: priced card, adding to cart via the site's action.