Parts that fit, found in three clicks.

How to add year, make, model search to Shopify

Shopify search and filters know products, tags and metafields, not vehicles. For a parts store, that leaves shoppers guessing whether a part fits. Hand-built collections per vehicle do not scale, because a part can fit dozens of cars.

Vehicle Fitment & YMM Search adds a year, make and model search, with optional submodel and engine, and a clear answer on every product page. Results open on your own collection pages, so your theme’s design, filters and sorting keep working.

How it works

1. You import fitment from a CSV. The app checks it and shows each error before anything changes.
2. The app tags each product with the vehicles it fits, and stores the rest in metafields.
3. The shopper picks year, make and model in the search block.
4. The search opens your collection page, filtered by that tag.
5. Product pages show Fits your vehicle or Does not fit, check submodel and engine, and list every vehicle in a fitment table.
6. My Garage keeps their vehicles on their device, with no account.

Universal parts stay visible for every vehicle. The storefront part is one small script and stylesheet from Shopify’s CDN, and it makes no calls to our server.

What your fitment CSV needs

One row per product and vehicle: product handle, SKU or product ID, then year or a year range such as 2015-2020, make and model. Submodel, engine, notes and a universal column are optional. A year range counts as one row, which keeps your row count down.

There is no vehicle database included. You import the fitment you already have from your suppliers or your own catalog, so shoppers only see vehicles you sell for. A sample file is in the docs, and our fitment CSV guide covers how to prepare data, with common mistakes. Export gives you a CSV back at any time.

The free plan works on live stores, and it suits a small specialist store with a few vehicles. See the app page for current prices.

Tags by hand, generic filters or a fitment app?

If you sell for one vehicle platform, one collection per model is enough. Choose an app when parts fit many vehicles, or a shopper needs a yes or no. A similar product exists for WooCommerce.

See Vehicle Fitment on the apps site.

SEO and data quality

Results use your own collection pages, so they fit your existing structure. Still, a vehicle search is a shopping tool. To be found for searches such as "2018 F-150 brake pads", write useful collection text and guides, and keep main vehicle ranges in product titles where they are true.

Quality beats size. Use consistent make and model names, add submodel and engine only where they change the fit, and put position in the notes. Start with your best sellers, then extend.

Compatibility

Every Shopify plan, no Plus features, and only product permissions, with no customer or order access. It needs the Online Store channel and a theme with app blocks. On uninstall, the kvf- product tags stay, so links to your collection pages keep working. Shopify removes the app blocks and the fitment metafields, and our server deletes your store’s data. Export your CSV first if you want a copy.

Check collections and filters

Results open on a collection filtered by a product tag, so test a vehicle with many parts, one with a few, and one with none, and check what your theme shows when a filter returns nothing. A short message on that collection pointing shoppers to support stops an empty result from being a dead end.

Put the search block where drivers start: the home page, and at the top of the collection. Keep the fitment table on the product page, as it lets a shopper with a similar vehicle check for themselves.