UVDB simply provides a good structure for linking to parts. When creating software, marketplaces, or even internal systems, this is a good scalable foundation. There are a few key aspects to UVDB.

Vehicle Definitions (UDEFs)

Vehicle definitions are a detailed grouping of vehicles by their relevant base properties.‍

For example:

Screen Shot 2021-11-17 at 4.36.21 PM.png

When displaying Vehicle Definitions on a storefront, vehicle definition details are broken down to:

Make, Model, Year, Series, Engine Details, Vehicle Details

Screen Shot 2021-11-17 at 4.52.22 PM.png

Vehicle definitions are close approximations to valid configs. There are far fewer, and are usually accurate to around 98%, and higher for common parts such as brakes, filters, etc. Vehicle definitions link to specific base properties. They can link to multiple of the following: Models, Submodels, BodyCodes, EngineDesignations. This is because the same vehicle definition may be sold under a different "Model", "Submodel", etc in different regions.

Vehicle Base Properties

These are simple properties used to help identify any vehicle. Base properties are things like Makes, Models, Years, Body Codes, Body Types, etc. These are simple resources that are linked to by config fitments, vehicle definitions, and valid configs. See the GraphQL playground for more specific descriptions of each base property.

Vehicle Base Properties

Custom Restrictions

Custom restrictions are specific vehicle properties. Custom restrictions are useful in situations where you need more granular fitment than the Vehicle Definition. Custom restrictions allow extremely unique restrictions to be added (Seat cover type, has parking sensor, etc).

https://www.youtube.com/watch?v=nY4e50dIjVc