UVDB uses two types of fitment, depending on what you want to do, how accurate you want your fitment, how simple your integration is, and which 3rd parties/marketplaces you want to interact with.
1. Defined Fitments
This is used to link parts to vehicle definitions which are close approximations of real world vehicles.
Who uses this structure?
- eBay USA, eBay Europe, eBay Australia
- Amazon Europe
- Parts of the European aftermarket
Pros:
- Simpler to implement, and you only have to store vehicle definition IDs
- Simpler vehicle selector as only some vehicle base properties are required from the user
- Businesses in Europe are most familiar with vehicle definitions
- Globally scalable to most countries / markets outside USA
Cons:
- Less accurate than config fitments
- Much harder to map to, or pass accuracy responsibility to sellers
2. Config Fitment
This is used to link parts directly to vehicle base properties which is an extremely accurate link to real world vehicle configurations.
Who uses this structure?
- OEMs / Vehicle manufacturers