Build your vehicle list
Type vehicles in or import a CSV. The columns are yours: Year, Make, Model, Drivetrain, or whatever you sort by, up to six, in any order.
Vehicle search for Shopify
A Year, Make and Model search and a garage for your Shopify store, running on a vehicle list you control. A shopper picks their car once, and every collection they open is filtered to it.
$49 a month. No code, no developer.
How it works
You bring the vehicle list and the fitment on your products. The app turns them into a search your shoppers can use, and it never writes to your products.
Type vehicles in or import a CSV. The columns are yours: Year, Make, Model, Drivetrain, or whatever you sort by, up to six, in any order.
Give each product the vehicles it fits, as tags or as Fitment metafields the app sets up for you. A coverage check shows anything that doesn’t line up.
Add the vehicle search, the garage and the fitment table from your theme editor. No code, no developer.
On your storefront
Add as many as your theme needs. They all read one vehicle list, so the search, the garage and the product page never tell a shopper different things.
One dropdown per column on your list, in your order, offering only what’s on it. Each choice narrows the next, so a shopper can’t pick a car that isn’t on your list.
A shopper saves their car once and it follows them around the store. Every collection they open is filtered to it, with nothing to switch on, and they can change or remove it at any time.
On the product page, one column per field on your list, filled from the product’s Fitment metafields. Years can collapse into ranges, and a Notes column carries anything specific to that part.
If nothing in a collection matches the shopper’s car, the page says so, with a link to see everything and one to change the vehicle. It never shows the whole collection as if it fit.
Keep fitment as tags and it works beside Boost, Globo, Searchanise and other apps that draw the collection page themselves. Keep it in metafields and it feeds Shopify’s own Search & Discovery filters instead.
In the app
Every search is a shopper telling you their car. See which vehicles and makes they pick most, and every search that found nothing, which is either a part you don’t stock yet or fitment that needs fixing.
The cars shoppers pick most, each linked to its results page so you can see what they saw.
Where the demand sits, make by make, so you know which brands and platforms to stock deeper.
Searches that led to an empty page. Each one is a sale you missed, until you add the part or fix the fitment.
Over the last 24 hours or 7, 30 or 90 days. Nothing about the shopper is recorded.
Edit it like a spreadsheet, or import a CSV and export it back out. Every import, save, column change and export is logged with the file name and counts.
Checks your whole catalog against your whole list and shows both sides: vehicles no product carries, which send shoppers to an empty page, and products no vehicle on your list can reach.
Edits and imports wait behind a Save bar, so a half-finished change never reaches your storefront. Discard puts everything back.
With fitment in tags, each make needs a published collection. The app lists any that are missing or unpublished, so a search never lands on a page your storefront can’t show.
The app never asks for access to your prices, descriptions, images, inventory, orders or customers, and never writes to your product titles or tags.
Pricing
Vehicle Search runs on your own vehicle list, so it works for any brand you sell. Plans that include our fitment data are in private beta.
Fitment data Private beta
Adding fitment to every product by hand is the slow part. We’re building it for you: every brand’s fitment normalized into one vehicle database and matched to your products on brand and MPN. It’s in private beta, and the figures below are that database as it stands today.
The file problem
Getting fitment onto product data is the messiest, most time-consuming job in automotive ecommerce. The same vehicle arrives under a different name from every supplier, somebody reconciles it by hand in a spreadsheet, once per brand, forever. The storefront inherits every mistake.
PDF catalogs, tabbed XLSX workbooks, CSVs with merged header rows. No two suppliers ship the same shape, and the shape changes between releases.
One brand writes MK7, another writes Golf VII, a third just writes the years. Drivetrain is frequently left blank, which is not the same as “fits everything.”
Year/Make/Model search only works if every product carries the same vehicle keys. Hand-typed tags drift, so real inventory goes invisible and wrong-fit orders come back.
Illustrative example of the formats the normalization rulebook handles. That reconciliation happens once, on our side, per brand. Not once per store, and not by you.
Brands in the beta
Every catalog below is normalized against the same vehicle rows. These are the brands the fitment data covers so far, and the list keeps growing.
| Brand | Category | Parts | Fitment records |
|---|---|---|---|
| APEXi | Brakes, Engine+5 | 564 | 17,106 |
| BC Racing | Suspension | 3,598 | 78,739 |
| Bilstein | Air suspension, Electronics+1 | 3,867 | 192,497 |
| HKS | Aero, Air suspension+11 | 1,473 | 35,756 |
| Ohlins | Suspension | 252 | 9,397 |
| 61 brands | Live now | 74,442 | 2,856,998 |
New catalogs get added continuously, and brands can publish their own at no cost. Tell us which one you need and we will tell you where it is in the queue.
One vehicle database
Fitment attaches to a canonical vehicle row of year, make, model, chassis, body and drivetrain, or to a whole platform when a part covers the entire chassis. Pick a car and watch a single Year/Make/Model resolve into what it actually is.
Start with the year. The 2015 BMW M4 is the one worth looking at: it comes back as two cars.
Demo set: 12 vehicles pulled from the live Fitmentware database (51,958 total). Counts are real records, not mock-ups.
Why the data holds up
Fitment is only worth anything if it is right. Normalization decisions live in a rulebook that gets versioned and reviewed, so two people importing two brands produce the same answer, and last year’s decision is still legible.
“Golf” is not one car. Golf, GTI and Golf R are separate models, so a Golf R part doesn’t inherit GTI fitment.
A chassis code becomes explicit model years and models, so A90 and 2020–2026 Supra resolve to the same rows.
NULL means unknown, never “fits everything.” Confirmed values are marked as confirmed.
Every brand’s original file is archived against the records it produced, so any row can be audited back to its document.
Vehicle Search for Shopify. The vehicle search, garage and fitment table, running on a vehicle list you manage in the app.
Fitment data. Canonical vehicles, platforms and applications across 61 brand catalogs, matched to your products on brand and MPN.
Brand workspace. Manufacturers get their own login to add MPNs, correct coverage and publish to every store at once. Access is granted by hand today, and it’s free to the brand.
Fitment API. Ask for a part and get the vehicles it fits, or ask for a vehicle and get the parts. Being designed now, and early partners get to set the shape.
Get started
Put vehicle search and a garage on your store for $49 a month. Leave your email and we’ll get you set up.
Goes straight to a person. No sequence, no drip.
Put your fitment in the beta. Hand it to us once, and every store using Fitmentware data carries it the way you engineered it.
Free No cost to the brand. Your data is the point.