What is VIN-based auto parts search?
VIN-based parts search uses a vehicle's 17-character VIN (Vehicle Identification Number) to identify the exact make, model, year, engine, trim, and assembly location of that specific car. Once the VIN is decoded, the parts catalog is filtered to show only parts confirmed compatible with that vehicle. This replaces the traditional Year/Make/Model/Engine 4-dropdown selector with a single field that is faster and more accurate, since the VIN captures sub-variants that dropdowns often miss — different engine options within the same year and model, for example.
What VIN decode API should I use?
The best VIN decode API depends on your market. For US-registered VINs, the NHTSA VIN decode API is free and covers most passenger vehicles. For global coverage, AutoISO, Vincario, or CarVertical provide paid APIs that cover India, UAE, and Europe. For Indian vehicles specifically, Vahan data provides registration-level accuracy but requires regulatory authorization. XPndAI builds a fallback chain — primary decode API → secondary → manual override — to maximize coverage and minimize zero-decode results on your vehicle population.
What is TecDoc and is it the right fitment database for me?
TecDoc is the automotive industry's largest fitment database, maintained by TecAlliance, covering 940M+ fitment records across Europe, India, Middle East, and other markets. It maps part numbers to vehicle configurations for OEM and aftermarket parts. TecDoc is suitable if you sell primarily in India, UAE, or Europe and your parts suppliers use standard part numbers that appear in the TecDoc catalog. ACES/PIES is the equivalent for North American market parts. If you have a proprietary catalog or regional parts not in TecDoc, XPndAI builds custom fitment tables from your catalog and supplier data.
How does AI natural language parts search work?
The AI layer processes the buyer's text input — "front brake pads for my 2019 Swift petrol" — and extracts structured attributes: vehicle (Maruti Swift), year (2019), fuel type (petrol), and part category (brake pads). These extracted values are fed into the same fitment engine that handles structured searches. The AI also handles alternate part names, regional terminology, partial descriptions, and typos that standard search would miss. On zero-result queries, the AI can suggest related part categories or ask a clarifying question.
Can the fitment engine handle multiple markets — India, UAE, and UK?
Yes. Multi-market fitment requires separate data for each market because the same model sold in India, the UAE, and the UK can have different engines, trim levels, right/left-hand drive, and emission standards. TecDoc covers all three markets but the regional catalog entries differ. XPndAI builds market-aware fitment — the catalog filters by market, showing only parts confirmed for the buyer's region's vehicle specification. VIN decode also returns assembly plant data, which confirms the market variant from the VIN itself without buyer input.