ACES and PIES, explained: the fitment standards that decide whether your SKU ships.

The first time a national retailer asks you for your ACES and PIES files, you find out very quickly whether you have a data operation or a hope.

This post is a plain-English tour of the two standards that run the automotive aftermarket — what they do, why buyers care, and what to have built before you walk into a line review.

What they are, in one line each

ACES — the Aftermarket Catalog Exchange Standard — tells a retailer's system which vehicles your part fits. Year, make, model, engine, drive type, sub-model, and qualifier conditions (tow package, heavy-duty cooling, to-VIN cutoffs).

PIES — the Product Information Exchange Standard — is everything else about the product itself. Descriptions, attributes, weights and dimensions, pack data, images, UPC, country of origin, pricing tiers, hazmat codes, warranty language.

ACES is the "what it fits." PIES is the "what it is." They travel together.

Both are governed by the Auto Care Association and delivered as XML files against shared vehicle and part reference databases.

The reference databases behind ACES

ACES doesn't describe vehicles in free text — it points to entries in shared databases maintained by the Auto Care Association:

• VCdb — Vehicle Configuration Database. Every year/make/model/engine combination in the U.S. vehicle park, each keyed by a BaseVehicleID.
• PCdb — Parts Classification Database. The part-type taxonomy (e.g., "Wiper Blade" vs. "Wiper Refill").
• Qdb — Qualifier Database. The "with tow package," "to VIN 234567," "sold in pairs" language.

Your fitment entries join your SKU to one or more VCdb rows plus optional qualifiers. Do it wrong and your part shows up on the wrong vehicles in retailer search. That is how chargebacks start.

Why retailers actually care

A buyer's real question isn't "do you have an ACES file?" — it's "what's your coverage?" Meaning: of the top 100 VIO (vehicles in operation) combinations in my market, what percent does your line fit?

If you're pitching a new wiper program to AutoZone and your ACES file covers 62% of top-100 VIO, the buyer has a problem. The consumer walks in, types in their 2019 Honda Civic, and the site tells them "no match." That is a lost sale and a category gap. Your competitor at 91% coverage just won the conversation before you sat down.

The same math runs in the DIFM (installer-focused) channel. WORLDPAC, NAPA, O'Reilly FIRST Call — they all search on ACES fitment. No ACES = not in the catalog = no sales.

The five things a buyer actually checks

1. Coverage percentage against the retailer's top VIO list.
2. ACES version. Current is 4.2. If you're still sending 3.x, that's a red flag on its own.
3. PIES completeness — attribute coverage, hi-res images, marketing copy, pack data.
4. Digital assets — at least three product images, 300 DPI, lifestyle shot, packaging shot.
5. Update cadence — how often you refresh as you add SKUs or new model-year coverage drops.

Number 5 is where most small vendors fall down. ACES/PIES isn't "write it once and ship it." Fall model-year releases trigger an update cycle. Missed updates mean missed vehicles mean lost sales at retail.

The tooling you need

Nobody builds ACES by hand past maybe 20 SKUs. The industry runs on a handful of platforms:

• DCi (Data Continuum) — the category leader, used by most mid-to-large aftermarket brands.
• MyFitment — strong for e-commerce, Amazon Auto, and direct-to-retailer feeds.
• SEMA Data Co-op — originally performance-focused, now broad.
• Illumaware — strong on the brand-portfolio side.
• Autoware — solid mid-market option.

Budget expectation: $15K–$60K/year depending on SKU count and update frequency. Factor it into your category program pricing. It is non-negotiable infrastructure, not overhead.

The sequence for a new automotive brand

If you're just starting to sell into national retail, here's the order of operations that actually works:

1. Join the Auto Care Association. You need VCdb/PCdb/Qdb access, and membership is the cleanest path.
2. Pick your tooling before you build your catalog. Migrating catalogs between platforms is painful.
3. Build PIES first. You can sell product data without fitment in some categories (car care, accessories). You cannot sell application-specific parts without ACES.
4. Define coverage targets by retailer. AutoZone and O'Reilly will tell you their top VIOs. Walmart will benchmark you against the current set.
5. Set a quarterly refresh cadence, with an extra update after the fall VCdb model-year drop.

What this means for your next line review

If your category is application-specific — wipers, filters, brakes, lighting, lamps, bulbs, fluids engineered per-vehicle — then ACES coverage is a go/no-go filter before the buyer hears your pitch.

If your category is universal — car care, cargo accessories, emergency, general cleaning — then PIES is what the buyer grades you on. Incomplete attributes, low-res images, or missing marketing copy are what push your line to the "revisit next cycle" pile.

Either way: the vendors who walk in with clean ACES and PIES files, current coverage math, and a quarterly refresh plan look like operators. The ones who don't look like hobbyists.

Coverage is the conversation. Own it before you walk in.