If you’ve looked into selling replacement parts online, you’ve probably hit the term “fitment data” and wondered whether it applies to you. The answer depends on who you ask — and most of the people who talk about fitment data are talking about a specific industry context that may or may not match your catalog.
This is an honest explainer. What fitment data actually is, where the term comes from, why it matters for some ecommerce catalogs and not others, and what to use instead if your catalog doesn’t fit the auto-industry definition.
The short answer
Fitment data is structured information that tells a shopper whether a part will fit their equipment. That’s it. Everything else — the standards, the data formats, the industry-specific terminology — is how that information gets encoded and shared between manufacturers, distributors, and retailers.
The simplest useful definition: fitment data is a mapping. On one side, parts. On the other side, equipment. In the middle, the relationships that say “this part fits this equipment.”
Where the term comes from
“Fitment” as a term is auto-industry heritage. It’s been standardized in the automotive aftermarket for decades, with established data formats and industry bodies dedicated to maintaining those formats.
The two main standards you’ll see referenced are:
- ACES (Aftermarket Catalog Exchange Standard) — defines how vehicle fitment data is structured and communicated
- PIES (Product Information Exchange Standard) — defines how product attributes are structured and communicated
Both are maintained by the Auto Care Association, which is a trade organization for the US auto parts aftermarket industry. If you’re selling auto parts seriously, you’ve probably run into ACES/PIES — and if you haven’t, you will.
The key thing to understand: ACES and PIES are not universal. They’re auto-industry standards. They don’t apply to HVAC filter compatibility, appliance parts, power equipment, or most other replacement-parts categories. This is where a lot of merchants get confused — they hear “fitment data” and assume they need ACES/PIES, when actually they don’t need that framework at all.
Fitment vs compatibility
Here’s the terminology shorthand I use:
Fitment — the auto-industry word, specifically referring to vehicle compatibility using year/make/model conventions. Often implies ACES/PIES data formats.
Compatibility — the broader, vertical-agnostic term. Works for any industry where parts need to match equipment by brand and model.
Both describe the same core concept. The words matter less than the structure of the data underneath.
What auto fitment data looks like
In the auto world, fitment data follows a specific shape because vehicles follow a specific shape. The identifying attributes are:
- Year (2018, 2019, 2020)
- Make (Ford, Honda, Toyota)
- Model (F-150, Civic, Camry)
- Submodel / Trim (XLT, Sport, LE)
- Engine (2.7L EcoBoost, 1.5L Turbo, 2.5L Hybrid)
This is often called “YMM” (Year-Make-Model) or “YMMT” (Year-Make-Model-Trim) data. At full depth, a single brake pad might be compatible with 50+ specific year/make/model/trim/engine combinations — each one a separate row of fitment data.
The complexity is what makes auto parts hard. A shopper needs to identify their exact vehicle configuration to find a part that fits. The industry solved this with VIN lookups (the 17-character Vehicle Identification Number decodes to a specific YMMT combination) and standardized databases that every auto parts seller can plug into.
What non-auto fitment data looks like
Now apply the same concept to HVAC filters. What are the identifying attributes?
- Brand (Honeywell, Coway, Levoit)
- Model (HPA300, AP-1512HH, Core 300)
That’s it. No year. No engine. No trim level. HVAC equipment doesn’t have the same year-over-year variation that cars do — a Honeywell HPA300 from 2020 and a Honeywell HPA300 from 2024 use the same filter.
Apply it to appliance parts:
- Brand (Whirlpool, GE, Samsung)
- Model (WRS325SDHZ, GTE18GTNRWW, DW80R9950US)
Apply it to industrial bearings:
- Manufacturer (SKF, Timken, NSK)
- Part number (6203-2RS, 6203-ZZ, 6203-LLB)
- Compatible equipment series (varies by buyer)
The pattern is the same across every non-auto vertical: brand + model is the identifying pair. Sometimes you need a third dimension (year, sub-series, variant), but the two-dimension mapping covers the majority of use cases.
“Fitment data” is just “compatibility data” wearing an auto-industry uniform. The underlying concept works for any parts catalog.
When you need ACES/PIES and when you don’t
You need ACES/PIES if:
- You sell auto parts and want to integrate with auto-industry distributors, catalogs, or retailers
- Your suppliers provide data in ACES/PIES format and you want to use it directly
- You’re selling into channels (like Amazon Auto) that expect structured fitment data in those formats
You don’t need ACES/PIES if:
- You sell HVAC, appliance, industrial, power equipment, electronics, agricultural, or any non-auto parts
- You sell auto parts but only within your own store and don’t integrate with auto-industry distributor feeds
- You want to manage your own compatibility data and don’t have external data sources to plug into
A lot of merchants over-index on ACES/PIES because the first compatibility tools they look at (which were mostly auto-focused) talk about it. If your catalog isn’t auto, skip it. Use a simpler data model that fits your actual needs.
The practical data model for most ecommerce merchants
Here’s what fitment/compatibility data looks like for most ecommerce catalogs, stripped of auto-industry baggage:
Core fields (required):
- SKU or product ID — the part in your catalog
- Brand — the equipment manufacturer
- Model — the equipment model
Recommended fields (improve quality):
- Category — what type of part it is (“Filter,” “Belt,” “Pump”)
- Model alias — alternate names/codes for the same equipment
- Confidence — Verified, Likely, or Unverified
- Notes — any caveat (“fits, but requires adapter X”)
Advanced fields (improve experience):
- Product variant ID — direct link to a Shopify variant for add-to-cart
- Image URL — product image to show in search results
- Product URL — direct link to the product page
A parts catalog of 500 SKUs, each fitting 20 equipment models on average, becomes 10,000 compatibility records. That’s manageable with the right tools and unmanageable with a spreadsheet.
The hidden third dimension
Some verticals have a third dimension beyond brand and model. For example:
- Power equipment often needs engine/serial range (a Stihl MS 271 has multiple engine variants)
- Appliance parts sometimes need manufacture year range (models get updated silently)
- Electronics sometimes need firmware or revision (laptop battery fits model X, but only revision B or later)
If your vertical has this third dimension, you need a data model that can represent it. Most compatibility tools support optional sub-model fields. Plan for it.
How fitment data gets used on a storefront
Regardless of vertical, fitment data earns its keep in three places on a storefront. I’ve covered this in more depth in another post, so the short version:
Product page — a fit-check widget so shoppers can confirm before adding to cart.
Finder page — a dedicated search experience where shoppers enter their equipment and see all compatible parts.
Collection page — a filter that narrows the collection to what fits a shopper’s specific model.
A compatibility dataset that isn’t surfaced on the storefront is just an expensive database. The surfaces are where the ROI lives.
How to start if you’re building this from scratch
If you don’t have fitment/compatibility data yet and are building from zero, here’s the pragmatic sequence:
Step 1 — Identify your data source. Manufacturer spec sheets, existing spreadsheets, product title/description inference. Where does compatibility information currently live?
Step 2 — Decide your schema. At minimum: SKU, brand, model. Add fields as your complexity requires.
Step 3 — Load your top 20% of products first. The Pareto rule applies — a subset of your catalog drives most of your revenue. Get those mapped cleanly before worrying about the long tail.
Step 4 — Surface it on the storefront. Data without a surface is waste. Install a tool that puts the compatibility data in front of shoppers.
Step 5 — Track what’s missing. Every compatibility check that returns no matches is a signal. Either your data has a gap, or there’s an adjacent product you should carry.
FAQ
Is “fitment” the same as “compatibility”?
Close enough for most conversations. “Fitment” carries auto-industry connotations and often implies ACES/PIES data formats. “Compatibility” is the broader, vertical-agnostic term. I use “compatibility” because it covers every parts vertical without baggage.
Do I need special software to manage fitment data?
For anything beyond a small catalog, yes. Spreadsheets don’t scale to tens of thousands of cross-reference rows, and they don’t surface well on storefronts. Purpose-built tools exist for this and are much cheaper than maintaining the alternative.
Where do I get the fitment data in the first place?
Three common sources. First, manufacturer spec sheets (free but time-consuming to parse). Second, industry data providers (pricier, mostly auto-focused). Third, your own Shopify product catalog (AI-assisted tools can infer initial compatibility data from product titles and descriptions).
How much fitment data is enough?
The best benchmark: whatever covers the top 80% of shopper searches. You’ll know it’s enough when “no match” searches become rare and your support inbox stops filling up with “does this fit my…” questions.
Does ACES/PIES work for non-auto parts?
Technically you could force it to, but it’s not designed for anything outside the automotive aftermarket. For non-auto verticals, use a simpler brand+model data model — you’ll save yourself significant complexity.
Closing
“Fitment data” sounds technical because the term grew up in the auto industry, where compatibility genuinely is technical. For the rest of ecommerce, the concept is simpler than the vocabulary makes it seem: structured data that says “this part fits this equipment.”
If you’re selling replacement parts on Shopify, you already have the concept in your head — it’s what makes every “does this fit?” support email make sense. The question is whether you’ve structured it in a way that your storefront can use.
Do that, and wrong-fit returns quietly drop. Don’t do it, and you’ll keep paying the tax.