Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
Automotive ecommerce lives or dies on fitment: the shopper has to be confident that the part fits their vehicle before they buy. On Adobe Commerce that means three things working together: clean fitment data (in North America, usually supplied in the ACES and PIES standards), a year/make/model (YMM) search that narrows the catalog fast, and a data model that can handle millions of part-to-vehicle rows without slowing the store. Get the data right first; the search UX is only as good as what sits behind it.
Why auto parts are a hard catalog
A typical retail product has a few attributes. An auto part has an application list: every vehicle it fits, often qualified by engine, drive type, body style or production date. One brake pad set can fit dozens of vehicle configurations. Multiply that by a catalog of tens of thousands of SKUs and the fitment data quickly becomes larger than the product catalog itself.
That is why generic ecommerce advice ("add good filters") falls short. Fitment is a relationship between two datasets, parts and vehicles, and the platform has to store, index and query that relationship efficiently.
ACES and PIES explained
In the North American aftermarket, the Auto Care Association maintains the two standards most suppliers use to exchange catalog data. They answer different questions.
| Standard | Answers | Reference data it relies on | What you do with it in Adobe Commerce |
|---|---|---|---|
| ACES (Aftermarket Catalog Exchange Standard) | Which vehicles does this part fit? | VCdb (vehicle configurations), Qdb (fitment qualifiers), PCdb (part types) | Import into a fitment table, index for YMM search, show "fits your vehicle" on product pages |
| PIES (Product Information Exchange Standard) | What is this product? Dimensions, attributes, packaging, pricing, images, descriptions | PAdb (product attributes), PCdb | Map to product attributes, media and prices, often through a PIM |
A few points that matter when you plan a build:
- ACES files are XML that reference vehicle IDs from the VCdb rather than spelling out the vehicle. You need the VCdb to turn those IDs into "2019 Ford F-150 XLT 3.5L."
- The VCdb is a paid annual subscription from the Auto Care Association, which also gives access to the Qdb and PCdb. The PAdb is needed to create or receive PIES files. Packaging can change, so check Auto Care's current subscription terms (as of November 2026). Budget for the licence and decide who owns it: you or your data provider.
- Coverage is regional. The VCdb covers vehicles for the USA, Canada, Mexico and Latin America. If you sell in Europe, suppliers commonly use other catalog data (TecAlliance describes its TecDoc catalogue as the leading aftermarket data standard in Europe), so expect a separate mapping.
- Updates are frequent. The VCdb can be downloaded monthly, or daily through an API. New model years and corrections arrive constantly, so treat fitment as a pipeline, not a one-off import.
Many merchants do not handle raw ACES and PIES themselves. They receive files from brands or buy them through a catalog data provider, then load them through a PIM. Our Magento PIM integration guide covers where a PIM fits.
Modeling fitment data in Adobe Commerce
Adobe Commerce has no native fitment feature. You choose one of three approaches, and the choice depends mostly on data size.
| Approach | How it works | Works up to | Watch out for |
|---|---|---|---|
| Fitment as product attributes | Year, make and model as multi-select attributes on each product, used as layered navigation filters | Small catalogs with simple, unqualified fitment | Cannot express "fits 2015 Civic but only with the 1.8L engine"; attribute option lists and index size grow fast |
| Custom fitment module | A dedicated fitment table (part ID, vehicle ID, qualifiers) imported from ACES, plus a custom index feeding OpenSearch | Most serious parts stores, into millions of fitment rows | Needs careful indexing and import design; the most build effort up front |
| External fitment service | A third-party fitment API returns compatible SKUs for a vehicle; Commerce filters or reorders results | Very large or multi-region catalogs | Adds a live dependency on search pages; check latency, caching and licensing terms |
A quick sizing exercise
Before choosing, do the arithmetic with your own numbers. As an illustration only: 40,000 SKUs that each fit an average of 50 vehicle configurations produce 2 million fitment rows. Add qualifiers and you have a dataset that should never live as product attributes. Ask your data supplier for the real row count of a full ACES file for your lines; it is the single most useful number for sizing the build.
The custom module approach usually stores fitment in its own tables and pushes a compact representation into the search index, so a YMM selection becomes a fast filter rather than a database join on every page view. The Magento OpenSearch guide explains how Magento's search indexing works and where custom indexes fit.
YMM search UX that converts
Fitment data is invisible until the search experience exposes it. A good YMM journey follows a predictable pattern, and the design work belongs in your storefront UX plan from the start:
- Vehicle selector first. Year, then make, then model, then submodel or engine, with each dropdown narrowed by the previous choice. Show only combinations that exist in your fitment data.
- Remember the vehicle. Save it in a "my garage" for logged-in customers and in local storage for guests, so the choice follows them across pages.
- Filter everything. Once a vehicle is selected, category pages and search results show only fitting parts, with a clear banner ("Showing parts for 2019 F-150 XLT") and a way to clear it.
- Confirm on the product page. Show "Fits your vehicle," "Does not fit" or "Check qualifiers" with the specific note (for example, "rear disc brakes only"). This is where returns are prevented.
- Handle universal parts. Tools, fluids and accessories fit everything. Flag them so they are not hidden when a vehicle is selected.
- Offer alternatives. Part-number search, OE cross-reference search and, where you license it, VIN or license plate lookup for shoppers who do not know their trim.
- Keep it fast. Each dropdown change should respond almost instantly. Cache the vehicle lists; they change monthly, not per request.
Natural-language search is also changing parts shopping, with queries like "front brake pads for my 2018 Camry." Our guide to AI site search covers how vector and AI search can sit alongside a structured fitment filter, which should remain the source of truth.
SEO for fitment pages
Vehicle-specific landing pages ("2019 F-150 brake pads") can capture valuable search demand, but generating a page for every vehicle and category combination creates millions of thin URLs. Pick the combinations with real demand and real inventory, give them unique content, and keep filter-only combinations out of the index with canonical tags and robots rules. Treat YMM filter URLs the way you treat faceted navigation.
Configurable kits and bundles
Parts stores often sell kits: a brake job with pads, rotors and hardware, or a lift kit with options. These are configurator problems as much as fitment problems, because each component must also fit the vehicle. Our guide to product configurators in Adobe Commerce compares bundle products, custom options and rules-based configurators, which is the next decision after fitment.
Build checklist
- Confirm your data source: brand-supplied ACES/PIES, a data provider, or your own catalog team, and who holds the VCdb and PAdb subscriptions.
- Measure the fitment row count and update frequency.
- Choose attributes, custom module or external service based on that size.
- Design the import as a repeatable pipeline with validation and error reports.
- Design the YMM journey, the garage and the product page fitment message.
- Load-test search and category pages with a vehicle selected, using production-sized data.
- Plan which vehicle landing pages deserve indexing.
Fitment projects reward getting the data model right before the storefront work begins. If you are scoping one, Mistri's Adobe Commerce development team can help you size the data and choose the approach.
Sources
Vehicle Configuration Database (VCdb) (Auto Care Association); Auto Care data subscriptions (Auto Care Association); Managing crawling of faceted navigation URLs (Google); TecDoc catalogue (TecAlliance).
