Vehicle and product relationships
Organize the relationship between makes, models, years and parts, including field dependencies and matching rules. Configure product-fitment information so filtering and product checks use a consistent data basis.
A motorcycle parts brand
Client identity withheld
Cascading make, model and year selectors filter collections and display product-level compatibility checks.
Learn about our work
This motorcycle accessories brand serves the North American aftermarket. Products in the same category can fit different models and model years, so shoppers need to establish compatibility as well as browse by appearance or part type.
The client wanted customers to start with their own vehicle, selecting make, model and year to find the relevant parts. The implementation required clear product-fitment relationships and consistent vehicle conditions across collection filtering and individual product checks.
We defined fitment rules and product markers, developed linked vehicle selectors, and integrated the relevant collection and product-page features. The delivery supports both finding candidate parts and reviewing an explicit fit or no-fit result before purchasing.
Product categories alone do not establish motorcycle-part compatibility; vehicle details are required.
Make, model and year choices depend on one another, and results must use the same vehicle criteria.
Collections narrow the candidates; product pages provide a final compatibility check for the selected item.
Organize the relationship between makes, models, years and parts, including field dependencies and matching rules. Configure product-fitment information so filtering and product checks use a consistent data basis.
Develop successive vehicle-condition inputs and connect them with the filtering action. Check option dependencies and page state when customers change their vehicle details.
Apply vehicle conditions to the product list to show candidate parts. Integrate fitment checks and matching or non-matching feedback within the product page.
Check results against the actual fitment relationships for different vehicle conditions. Test selectors, collections and product interactions alongside the agreed page configuration before launch acceptance.

The collection connects vehicle controls with the product list. Shoppers enter a make, model and year, then continue through the corresponding candidates as part of the parts-discovery task.

A dedicated fitment area helps shoppers check their vehicle against the current item. Collection filtering and product-level results use the same matching relationships, connecting discovery with final confirmation.

After the shopper changes the vehicle criteria, the product page presents the corresponding fitment result. This view shows the vehicle selector together with an incompatibility message, connecting the selection to a clear, product-specific check before purchase.
An example parts-search journey shows how collection and product checks work together.
Enter vehicle details and complete the dependent selections.
Review the matching parts in the filtered collection.
Read the selected part's specifications and purchase information.
Check whether the current product fits the selected vehicle on the product page.
Use the same vehicle information for selectors, collection results and product checks.
The collection narrows the options; the product page verifies the selected part.
Use the same vehicle criteria and fitment data for both collection filtering and product checks.
Select the available make, model and year in sequence.
Earlier choices determine later options, preserving the search context.
Identify matching parts using the confirmed vehicle-to-product mappings.
Filter using fitment data rather than product-title keyword matching alone.
Collections show matching products; product pages show the selected item's compatibility result.
Support broad product selection and individual fitment checks at the appropriate stages.
Brand, model and year
Products matching the selected vehicle
Show results and product compatibility
A simplified workflow diagram showing responsibilities and information flow.
Confirm vehicle fields, selector dependencies, fitment data and query rules.
Build the collection vehicle selector and filtering logic, then integrate product-page fitment checks.
Validate collection and product results against fitment data, then configure the agreed promotion.
Test vehicle combinations, query states and interactions, resolve issues and launch.
When vehicle details change, verify dependent options and the current selection state.
Check collection results against the agreed fitment data.
Check the fitment lookup and status messages on the product page.
Verify collection filters, product interactions and the agreed promotional settings.
Customers narrow the catalog by make, model and year, bringing fitment data into product discovery.
Candidate filtering and individual compatibility checks use the same vehicle conditions and product relationships.
The product page presents fit or no-fit results to support compatibility decisions for the current item.
Start with your business needs and identify the right next step together.