Vehicle data for parts and accessories fitment

Your shop sells something that has to fit: roof tents, car mats, LED kits, TPMS sensors, turbos, used parts. The question on every product page is the same, does it fit my car?, and every wrong answer is a return, a bad review and a shipping bill.

We want to be straight about what that takes, because it's more than a make and model list. What we offer today is makes, models and years on record: the vehicle step of your selector. We don't offer fitment data, specs or generations. Generations are coming, with a waitlist below.

What a fitment selector actually needs

1. The vehicle: make, model, and the kind of vehicle. This is the step customers see.
2. When it was built: a year, and for most parts a generation (Golf VII, not just Golf), because parts change between generations, not between calendar years.
3. The variant that matters for your part: body type (a roof tent cares about hatchback vs estate), sometimes wheelbase, roof type or engine.
4. The fitment rule: which of your products fit which of those. That's your table, or a standard like TecDoc in Europe or ACES in North America.

What we publish for it today

• Every make and model from the official vehicle registers of these countries, so your selector has the cars your customers drive, including the ones a US list misses.
• Cars, vans, motorcycles, mopeds, trucks and buses with one id scheme. A mats shop that also does vans, or a lighting wholesaler that also sells to bikers, uses one list: Toyota Hilux, Volkswagen Transporter, Yamaha MT-07.
• Body type for every car (hatchback, wagon, SUV, pickup, van and the rest), which already splits many accessory ranges.
• Years on record per model: the first and last year the registers have it. They're registration years, not production dates, and they're a sound default for a year step.
• Stable canonical ids (car/toyota/hilux) to key your own fitment table on and share with suppliers. Renamed models keep their old ids in former_ids, so your table doesn't break on our next release.
• CC-BY 4.0: store the list, use it commercially, ship it inside your shop, with a visible credit.

You can take it as files (free with an account: CSV, JSON, Parquet, SQLite) and import it into WooCommerce, Shopify or your own database, or use the make and model dropdown for the selector's first steps; its requests cost 0 credits.

What's coming: generations

Generations are not published yet. They're the most requested addition we have, from parts shops and marketplaces alike, and they're on the roadmap: generation names and codes with their year ranges, keyed to the same model ids you'd use today, so nothing you build now has to be redone.

To hear the day they ship, join the waitlist: create a free account (the button below) and click "Tell me when generations and specs land" on your getting-started page, or tell us what you sell and where. We don't take orders or payment for generations before they exist. Engines and trims are further out.

When you need TecDoc or ACES instead

If you sell parts that need part-number-level fitment across thousands of SKUs (brake pads, filters, anything with an OE number), the industry standards are TecDoc for Europe and the Auto Care Association's ACES and VCdb for North America. They carry their own vehicle ids and part applications; VCdb subscriptions are listed at $3,150 to $12,075 a year by company revenue (read on November 10, 2026), and TecDoc is licensed through TecAlliance by negotiation. We don't replace them. Shops that sell accessories rather than OE parts (tents, mats, covers, lights) often don't need them, and a clean make, model and body type list plus their own fitment table is enough.

A setup that works today

• Import the list and key your fitment table on our model ids.
• Show make, then model, filtered to your market and ordered by popularity there, so the common cars come first.
• Add body type where your product depends on it.
• Add the generation step the day it ships, on the same ids.