The Challenge
The company sold premium aftermarket wheels and performance exhaust systems with hundreds of fitment combinations across vehicle makes, models, and years. Their e-commerce store used a vehicle fitment checker that returned a list of compatible SKUs — but customers still bought wrong-fitment items due to confusion about application, finish choices, and specific variant differences. Their return rate on wheels was 19%, primarily from wrong-fitment and appearance mismatch. Their support team handled 85+ pre-sale calls per week from customers asking fitment and appearance questions that should have been answerable from the product page.
The Solution
ConfiguraThor built a vehicle-specific product configurator for their premium wheel lineup. Customers enter their vehicle year, make, and model. The configurator displays only compatible wheel options. For each compatible wheel, a 3D viewer shows the wheel in the selected finish (chrome, gloss black, matte gunmetal, etc.) with accurate rendering of each finish's reflectance. An on-vehicle preview option shows the wheel mounted on a vehicle silhouette for proportion reference. Compatibility rules prevent customers from selecting incompatible lug patterns or offsets.
"We were losing customers to wrong-part returns and support overload. The configurator fixed both at the same time."
Frequently Asked Questions
How does the configurator handle the large number of vehicle fitment combinations?
The configurator integrates with the company's fitment database to determine compatible products for each vehicle selection. When a customer selects their vehicle, the configurator queries the fitment data and returns only compatible wheel options — no complex filtering required from the customer side.
How accurate are the finish renderings in 3D?
Each wheel finish is rendered with physically-based material properties — chrome shows accurate reflectance and environment mapping, matte finishes show the correct diffuse quality, and metallic finishes show appropriate specular behavior. The goal was to eliminate the 'looked different than expected' return category, which required rendering accuracy that matched actual product appearance.
Was the support call reduction measured directly from the configurator launch?
Yes. The team tracked pre-sale support call volume in the 90 days before launch versus the 90 days after, controlling for seasonal variation. The reduction from 85 to 23 calls per week was consistent across the post-launch period and has been maintained.