ACES and PIES Explained: The Data Standards Behind Every Auto Parts Listing
What are ACES and PIES?
ACES and PIES are the two data standards that make an auto part findable and sellable, especially online. ACES (Aftermarket Catalog Exchange Standard) describes fitment — which part fits which vehicle. PIES (Product Information Exchange Standard) describes the product itself — its description, dimensions, images, packaging, and attributes. Together they are the reason a shopper can type in a year/make/model and get exactly the right part instead of a wall of maybes.
Both standards are owned and maintained by the Auto Care Association (specifically its technology arm). This trips people up constantly, so it is worth stating plainly: ACES and PIES are Auto Care Association standards. SEMA maintains its own related data programs, but ACES and PIES themselves belong to the Auto Care Association. If you sell parts and someone tells you SEMA owns ACES, they are mistaken.
Why the standards exist at all
Before ACES and PIES, every supplier described parts their own way and every retailer had to re-map that data by hand. A "front brake pad" from one brand and a "brake pad, front" from another were the same thing wearing different clothes, and matching them to vehicles was a manual nightmare. The standards created a shared language so a manufacturer can publish data once and any retailer, marketplace, or distributor can ingest it the same way. That is the whole point: publish once, consume everywhere.
The reference databases behind ACES and PIES
ACES and PIES are not just file formats — they lean on shared reference databases so everyone uses the same vocabulary. There are four you should know:
VCdb — Vehicle Configuration Database
The master list of vehicles. Every year/make/model, plus sub-configurations like engine, drive type, body style, and bed length. When ACES says a part fits a vehicle, it points at VCdb identifiers rather than free text. That is what makes fitment machine-readable.
PCdb — Product Classification Database
The master list of part types. "Disc Brake Pad," "Oxygen Sensor," "Cabin Air Filter" — each has a standardized part terminology ID. This is how a marketplace knows two listings are the same category even if the marketing names differ.
PAdb — Product Attribute Database
The master list of attributes and their valid values. Thread size, amperage, material, position — PAdb defines which attributes are allowed for a given part type and what values are legal. It keeps product specs consistent instead of free-form.
Qdb — Qualifier Database
The master list of qualifiers — the "except," "with," and "when" conditions that fitment so often needs. More on qualifiers next, because they are where fitment gets subtle.
Qualifiers: the small print that prevents returns
A qualifier is a condition attached to a fitment record. A brake rotor might fit a 2019 Silverado 1500 — but only with the 6-lug wheel and except heavy-duty brake package. Those conditions come from the Qdb, and they are the difference between a correct listing and an expensive mistake.
This is where fitment lives or dies. Coarse fitment ("fits 2015-2020 F-150") feels convenient but is wrong often enough to generate returns. Precise fitment with the right qualifiers ("fits 2015-2020 F-150 with 3.5L EcoBoost, except Raptor") is what actually protects the customer and the seller. Qualifiers are not optional detail; they are the mechanism that encodes real-world engineering nuance into data.
Why bad fitment data is so expensive
In the auto parts aftermarket, a return is not just a refund. It is a return shipping cost, a restocking cost, a lost sale, a marketplace metric ding, and often a customer who never comes back. Marketplaces like eBay and Amazon track fitment-related returns closely, and sellers with high defect rates get throttled or suspended.
The root cause of most fitment returns is almost always upstream data: a missing qualifier, a part mapped to the wrong VCdb configuration, a coarse year-range that swept in a vehicle that never fit. Clean ACES data is the cheapest returns-prevention program a parts seller can run, because it stops the wrong sale before it happens.
How ACES and PIES actually flow in practice
- A manufacturer builds ACES (fitment) and PIES (product) files for their catalog, referencing VCdb, PCdb, PAdb, and Qdb.
- Those files are published to receivers — distributors, retailers, marketplaces, data pool providers.
- Each receiver validates the files (are the vehicle references valid? are attributes legal? are images present?) and loads them.
- The listing goes live with accurate fitment, so a year/make/model search returns the right part with the right qualifiers.
Every weak link — an outdated VCdb version, an unvalidated file, a dropped qualifier — degrades the listing downstream. This is why validation and version management matter as much as the data itself.
Frequently asked questions
Who owns ACES and PIES? The Auto Care Association. It maintains the standards and the underlying reference databases (VCdb, PCdb, PAdb, Qdb). Companies license that reference data from the Association; they do not get it from SEMA.
What is the difference between ACES and PIES again? ACES = fitment (part-to-vehicle). PIES = product information (descriptions, specs, images, packaging). You almost always need both.
Do I need ACES and PIES to sell online? To sell effectively on fitment-driven channels, yes. Marketplaces and retailers expect standardized fitment and product data, and shoppers expect year/make/model search to just work.
Can software build and validate this for me? Yes. Good tooling operates on the reference data you license, builds and validates ACES and PIES files, catches invalid vehicle references and missing qualifiers, and keeps you on current database versions — all without reselling the licensed data itself.
The bottom line
ACES and PIES are the invisible infrastructure of the auto parts aftermarket. ACES tells the world which part fits which vehicle; PIES tells the world what the part is; VCdb, PCdb, PAdb, and Qdb keep everyone speaking the same language; and qualifiers encode the small print that keeps returns down. Get this data right and everything downstream — search, marketplaces, distribution — just works.
We build and run software that produces, validates, and manages ACES and PIES at scale, operating on the data our clients own and license. If your fitment is driving returns or your product data is a mess, see how we approach catalog data, or reach out — tell us the problem, we'll figure out the technology.