Year, Make, Model — The Hardest "Easy" Problem in Vehicle Data

Ask someone what car they drive and they'll say something like "2020 Honda Civic." That's a year, a make, and a model. Three fields. How hard could it be?

Hard enough that most vehicle databases get it wrong.

The trim explosion

A 2020 Honda Civic isn't one vehicle. It's a family. There's the LX sedan with a 2.0L four-cylinder making 158 hp. There's the Touring with a 1.5L turbo making 174 hp. There's the Si with 205 hp and a six-speed manual. There's the Type R with 306 hp. These are all "2020 Honda Civic" but they share almost nothing beyond the badge.

If your database stores year/make/model without trim, engine, and drivetrain granularity, your users can't distinguish between a $21,000 economy sedan and a $37,000 track car. Your spec comparisons are meaningless. Your recall data may not even apply — some recalls target specific trims or engine variants, not the entire model line.

The submodel problem

It gets worse. Some manufacturers use submodels as an additional layer. A 2018 Toyota Tacoma comes in Access Cab and Double Cab configurations, which are submodels with different wheelbases, payload capacities, and available trims. Some APIs treat these as the same vehicle. They're not.

The naming inconsistency problem

Manufacturers change naming conventions. The same vehicle may be listed as "F-150 XLT SuperCrew" in one source and "F-150 SuperCrew XLT" in another. "4WD" vs "4x4" vs "AWD" varies by manufacturer and sometimes by year. Is it "Silverado 1500" or "Silverado C/K 1500"? The answer depends on which decade you're looking at and which database you're querying.

If you're building a dropdown selector for users to pick their vehicle, these inconsistencies create duplicate entries, missing entries, and confusion. Normalizing manufacturer naming across 100+ makes and 60+ years of model history is a data quality problem that most API providers don't solve — they just pass through whatever their upstream source uses.

What clean YMM data looks like

Year, make, model, trim, submodel, engine, drivetrain, transmission — all normalized and consistent across the catalog. One vehicle per combination, no duplicates, no ambiguous names. When your user selects "2020 Honda Civic Type R," they get 306 hp, not 158 hp.

CarVector's catalog covers 12,000+ vehicle variants broken out by trim and engine, with each variant carrying its own spec sheet. Year/make/model is the search entry point. Trim and engine are the resolution point.