Year Make Model search for Shopify auto parts stores

Your customer knows one thing: what they drive. Every second they spend translating that into your catalog is a second they can spend on somebody else’s. Year → Make → Model → Submodel, four taps, only the parts that fit. Stored in your Shopify metaobjects, not a vendor’s database.

Free to 50 products. $49/mo with Smart Parse. Template 01: Year / Make / Model / Submodel — 2021 › Ford › F-150 › XLT 4WD.

ViewForge fitment panel with Year, Make, Model and Submodel dropdowns narrowing an auto parts catalog to a 2021 Ford F-150 XLT 4WD
Auto parts

Three levels is not enough for a car.

The trim level is where the money is

Year, Make and Model narrow a 2021 F-150 to a few hundred parts. Submodel is what takes it to the right one. XLT 4WD and Raptor share a nameplate and not much else. An app that stops at three levels hands the shopper a list and makes them do the last step themselves — which is the exact step they were unsure about when they arrived. ViewForge’s automotive template ships four cascading levels, and you can relabel the fourth to Engine or Trim if that is how your catalog thinks.

Your fitment data already exists

Almost every auto parts merchant already wrote fitment down — in the product title. "Front Brake Pads for 2017–2021 Honda Civic LX/EX/Touring" is a fitment record that no database can read. Smart Parse reads it. Point the Professional tier at your existing titles and descriptions and it extracts the year ranges, makes, models and trims into structured records, each with a confidence score, so you spend your review time on the uncertain ones instead of typing all of them.

ACES/PIES if you have it, CSV if you do not

The industry-standard route is ACES for fitment and PIES for product data. If your suppliers send those files, Premium imports them and decodes VINs against NHTSA. But most independents do not have ACES. They have a spreadsheet. Starter takes the spreadsheet — column mapping, fuzzy matching against what is already loaded so you do not double-enter, and a coverage dashboard that names the SKUs still carrying no fitment.

Uninstall is the real test

Ask any fitment vendor what happens to your data when you cancel. If the answer involves an export request or a support ticket, you are renting your own catalog. ViewForge writes fitment as Shopify metaobjects — native records in your store. Cancel and the records stay. Query them from the Storefront API, export them through Admin GraphQL, hand them to a different metaobject-aware tool. Nobody has to give them back, because nobody else ever had them.

What auto parts merchants actually run into

Feature
Typical YMM app
ViewForge
Submodel / trim as a 4th level
Often 3 levels only
Year / Make / Model / Submodel
ACES / PIES import
Enterprise tier or none
$240 Premium
NHTSA VIN decode
$300+/mo or missing
$240 Premium
Fitment already in your titles
Retype it
Smart Parse extracts it
Where the fitment lives
Vendor database
Your Shopify metaobjects
Cost to test on a small catalog
14-day trial
Free to 50 products, no clock
The math

What a 5,000-SKU auto catalog costs to run.

Smart Parse is the tier most auto parts stores land on, because it is the one that turns product copy you already wrote into fitment you can filter on. $588 a year, all in.

Install free
Prove it works first 50 products, no time limit
$0
CSV import + coverage dashboard Starter, to 1,000 products
$19/mo
Smart Parse from your titles Professional, to 5,000 products
$49/mo
ACES/PIES + NHTSA VIN decode Premium, unlimited
$240/mo
Your fitment data on cancellation
Stays

Auto parts fitment on Shopify — frequently asked questions

What is the best Year Make Model Shopify app for auto parts?

Answer three questions and the choice makes itself. How many SKUs carry fitment? Where does the data live when you cancel? Do you need a fourth level for trim? ViewForge is the only metaobject-native option — fitment is stored in your Shopify store rather than a vendor database — it ships four cascading levels by default, and it is free up to 50 products so you can test it against your own catalog before paying anyone. $19/month covers 1,000 products with CSV import; $49/month adds Smart Parse.

How does YMM fitment search work on a Shopify storefront?

The shopper picks Year, then Make, then Model, then Submodel, from dropdowns that narrow each other — choosing Ford means the Model list only shows Fords. Your collection filters to parts matching that exact configuration. ViewForge renders the widget through Shopify theme app extensions and stores the compatibility records as metaobjects, so the storefront queries your own store rather than round-tripping to a third-party API on every click.

Can Smart Parse really pull fitment out of my product titles?

That is what it is for. Smart Parse reads your existing titles and descriptions, finds fitment statements like "Fits 2019–2022 Ford F-150 XLT", and converts them into structured fitment entities with a confidence score attached. You review and apply them rather than accepting them blind. It is on the $49/month Professional tier, and it is the difference between a weekend of setup and a quarter of data entry for a catalog that already describes fitment in prose.

Does ViewForge support ACES and PIES for auto parts?

ACES/PIES import is on the $240/month Premium tier, along with NHTSA VIN decoding and unlimited fitment records. If your suppliers ship ACES files, that is the fastest path in. If they do not — the common case for independents — the $19/month Starter tier imports plain CSV with column mapping and fuzzy matching, and the coverage dashboard shows which products still have no fitment.

What happens to my auto fitment data if I uninstall ViewForge?

It stays in your Shopify store. Fitment records are written as Shopify metaobjects, which are native Shopify data — uninstalling an app does not delete them. You can export them through Admin GraphQL, read them from the Storefront API, or point another metaobject-aware tool at them. That is the practical difference from a vendor-database app, where uninstalling means paying someone to migrate data you thought was yours.

Fitment records extracted from existing product titles and matched to the vehicles they fit
Bottom line

You already own the fitment data. It is sitting in your product titles, written as "Fits 2017–2021 Honda Civic LX/EX." Smart Parse lifts it out and turns it into structured records you can filter on. Nobody has to retype 12,000 SKUs to get a working dropdown — that is the entire reason the Professional tier exists. see ViewForge →