Guide

How to add Year / Make / Model search to a Shopify store

Shopify has no built-in way to say which part fits which vehicle. This guide covers what you need, the free approach and where it stops working, and the part that causes the most trouble later: keeping fitment intact when supplier files change.

Written by the developer of Fitment Sync, a fitment app for Shopify. The free approach is covered too, because for some stores it is enough.

You need two things, and themes usually provide only one

A working vehicle search on a parts store has two halves:

1. Fitment data — the record of which part fits which year, make, model and trim, and in which position.
2. A way for shoppers to use it — a vehicle selector that narrows the catalog, and an answer on each product page saying whether the part fits their vehicle.

Auto parts themes often ship with a search box styled for year, make and model. That is the second half only. The data has to come from somewhere else, and that is usually where a store gets stuck.

What fitment data looks like

The common shape is one row for each part on each vehicle. The part is identified by its SKU, not by a Shopify product ID, which is what lets the file your supplier sends be matched to your own catalog.

A few things follow from this shape:

• A single part can have dozens or hundreds of rows, one per vehicle it fits.
• A year range such as 2010-2023 means one fitment per model year, so the first row above is fourteen fitments, not one.
• The same part can fit the front of one vehicle and the rear of another, so position belongs with the vehicle, not with the part.

The free approach: metafields and Search & Discovery

Shopify's Search & Discovery app can turn product metafields into storefront filters. You add metafields such as make, model and year to each product, fill them in, and create a filter for each one.

It costs nothing and needs no app. It also has limits that matter for vehicles:

• Filters are checked independently. Shopify combines different filters with AND, but each one is matched on its own. A rotor listed for a Toyota 4Runner and a Honda Civic carries the makes Toyota and Honda and the models 4Runner and Civic, so a shopper who picks Honda and 4Runner still sees it, even though no such vehicle exists.
• Each filter shows at most 100 values to shoppers. Years and makes usually fit. Models across several makes, or submodels, often do not.
• Filters appear on collection and search result pages. There is no step-by-step vehicle picker, and nothing on the product page tells a shopper whether the part fits.
• The data lives on each product. Your supplier's file is one row per part per vehicle, while a product import is organized by product, so every supplier update means rebuilding the file before you can load it.

If you sell a narrow range for a handful of vehicles and update it rarely, this can be enough. Once the catalog grows or suppliers update it regularly, the maintenance tends to be what breaks first.

What to look for in a fitment app

• It reads the file your supplier already sends. A CSV keyed by SKU, with year ranges expanded for you, rather than a format you have to convert to.
• The vehicle selector only offers vehicles you stock parts for. A selector that lists every car ever made leads shoppers to empty results.
• The product page gives an answer, including "no". Many shoppers never use the selector. They arrive on a product page from a search engine, an ad or a shared link, and that page has to tell them whether the part fits.

• Updates do not wipe your data. This is covered below, because it is the part that is easy to miss when choosing.
• You can export what you have. Fitment data takes work to build. You should be able to take it with you as a file.

The update problem

Suppliers send updated fitment files regularly, and a file usually covers one brand or one part of your catalog, not everything. How an app applies that file decides whether your data survives it. There are two common ways to get it wrong:

• Replace everything. The new file becomes the whole database. Every brand the file does not mention disappears, along with any fitment you added by hand.
• Only ever add. Nothing is lost, but nothing is corrected either. When a supplier fixes a mistake, such as a part listed for the front that actually fits the rear, the wrong row stays next to the right one.

How Fitment Sync handles it

Fitment Sync is built around that update step. When you import a file you choose how it applies:

• Add only — nothing already stored changes.
• Add and update — rows that match on part, vehicle and position take the file's values. Nothing is removed.
• Replace one brand — everything stored for that brand, including rows added by hand, is replaced by the file. Every other brand is left exactly as it was.
• Replace the parts in this file — only the SKUs the file lists are replaced.

A preview shows what the file would add, update and remove before anything is saved. Rows that cannot be read are listed with their line number and the reason, including part numbers that do not match anything in your catalog, so they are never dropped silently. Column names are detected automatically, and year ranges are expanded for you.

On the storefront, a vehicle selector offers only the vehicles you have parts for, and each product page says whether the part fits the shopper's vehicle, followed by the full list of vehicles it covers. Both are added from the theme editor, with no changes to your theme's code.

To see the shopper's side before installing anything, the interactive demo runs the same vehicle search on sample data. On the data side, the next guide covers importing a supplier fitment file without losing what you already have, and where auto parts stores get vehicle fitment data.