ACES and PIES are the two data standards the automotive aftermarket uses to share parts data. ACES, the Aftermarket Catalog Exchange Standard, says which vehicles a part fits. PIES, the Product Information Exchange Standard, describes the part itself: its part number, attributes, descriptions and images. The Auto Care Association maintains both.
Manufacturers, distributors, retailers and marketplaces use these files to exchange catalog data without building a custom format for every partner. This guide explains what each standard holds and how fitment data powers year, make and model search. It also covers the software involved and what to check before the data reaches your storefront.
What are ACES and PIES?
ACES and PIES are XML formats for sending parts data between trading partners, such as a manufacturer sending its catalog to a distributor. The Auto Care Association says most automotive aftermarket companies in North America use them, and adoption is spreading to Mexico, Central and South America. Both cover light, medium and heavy duty vehicles, powersports, off-highway and equipment.
The two standards split the work. ACES answers "does this part fit my vehicle?" and PIES answers "what is this part?"
| ACES | PIES | |
|---|---|---|
| Full name | Aftermarket Catalog Exchange Standard | Product Information Exchange Standard |
| Question it answers | Which vehicles does this part fit? | What is this part? |
| What it holds | Vehicle applications: year, make, model, engine and other vehicle details, plus fitment conditions | Product details: part number, brand, attributes, descriptions, pricing, packaging, warranty, interchanges and digital assets |
| Reference databases | Vehicle Configuration Database (VCdb) and Qualifier Database (Qdb) | Product Attribute Database (PAdb) |
| Shared reference data | Product Classification Database (PCdb) and brand codes | Product Classification Database (PCdb) and brand codes |
| Current version | 5.0 | 8.0 |
No law requires ACES or PIES, but trading partners often ask for them. Walmart Marketplace, for example, needs fitment information on file for automotive products to show in its auto parts fitment widget, and it accepts ACES files or its own vehicle compatibility template.
The documentation is public, but the reference databases need an annual paid subscription from the Auto Care Association.
What is ACES data?
ACES data is a list of applications. Each application ties one of your part numbers to a vehicle it fits. Auto Care's own example is a part that shoppers find through a year, make and model lookup. ACES is how the supplier tells every trading partner which vehicles that part belongs to.
What an ACES application holds
An application names the part number and part type, then the vehicle: year, make and model, plus details such as submodel or engine when they change the fit. It can add the part's position on the vehicle, such as front or rear, and the quantity used.
Qualifiers cover the conditions those fields can't, such as "with towing package" or a change partway through a model year. Without them, two versions of the same model look identical, and one part shows as fitting both.
The reference databases behind ACES
ACES records use codes from shared databases instead of free text. The Vehicle Configuration Database (VCdb) gives every vehicle configuration a standard record, so one model year and trim has a single record that every partner uses. The Qualifier Database (Qdb) holds standard wording for fitment conditions. Both standards use the Product Classification Database (PCdb) for part types.
Because everyone uses the same codes, a receiving system can match applications automatically instead of reading a supplier's own vehicle names.
What is PIES data?
PIES data describes the part itself. According to the Auto Care Association's PIES overview, a PIES file can carry features and benefits, marketing descriptions, pricing, warranty, product attributes and specifications, hazardous materials, kits, interchanges and digital assets.
The reference databases behind PIES
PIES uses the PCdb for part types, the same list ACES uses. The Product Attribute Database (PAdb) lists standard attributes for each part type, so a brake pad's friction material is recorded the same way by every supplier. Brand codes identify the brand and its owner.
Why PIES data shapes your product pages
A retailer's product page for a part is built largely from PIES data: the title, the bullets, the specifications table and the images. When a PIES file arrives with only part numbers and a one-line description, the retailer has to fill the rest before the page can answer a shopper's questions.
The descriptions also need to match the attributes. A description that says "ceramic pads" on a part whose PIES attributes say semi-metallic gives the shopper two different answers.
How does year, make and model search use fitment data?
A year, make and model (YMM) lookup asks the shopper to pick their vehicle, then shows only the parts with a matching ACES application. The lookup is only as accurate as the applications behind it. Qualifiers settle the cases YMM alone can't, such as two engines offered in the same model year.
Where fitment data goes wrong
Most fitment errors fall into a few patterns:
- Applications that are too broad. A part mapped to every engine in a model, when it fits only one, shows up for shoppers it doesn't fit.
- Missing qualifiers. The vehicle matches, but the condition that decides the fit isn't recorded.
- Different values across channels. Part numbers, brand codes or attributes that differ between your storefront, distributors and marketplaces.
- Version mismatches. A file built for an older version of ACES or PIES sent to a partner that has moved to the current one, or the reverse.
How do AI shopping assistants use fitment data?
AI shopping assistants answer "will this fit my car?" from the same kind of structured product compatibility data. A part that's wrongly mapped to a vehicle can show up as compatible in a search filter and in an assistant's answer.
What software do you need for ACES and PIES?
Suppliers need software that creates ACES and PIES files and checks them against the standards. Their trading partners need a system that loads the data into their own catalogs.
To create and send files
Catalog software or a data service provider maps your applications to VCdb records, builds the XML files and checks them against the standards before they go to partners. Walmart's fitment guide lists several third-party providers for sellers who need help creating ACES and PIES files.
To use the data in your catalog
A PIM holds the product data your files and product pages draw from, including attributes, descriptions, images and fitment mappings, so each channel gets the same values. Your ecommerce platform or marketplace then reads the fitment data to run YMM search and fitment filters.
How does Hypotenuse AI help with automotive product data?
Hypotenuse AI is an AI PIM for auto parts and accessories. It keeps product and fitment data in one place, including year-make-model-trim mappings. When fitment changes, the update syncs across linked SKUs.
When supplier data arrives in different formats, AI attribute mapping maps it into one structure. Ecommerce product data enrichment fills missing attributes from spec sheets and manufacturer documents. Hypotenuse AI makes sure missing and conflicting details are filled and reconciled before SKUs reach your product pages or distributor portals. It then writes titles and bullets from the record, including technical specs and compatibility notes.
To see this on your own parts catalog, book a demo.
Frequently asked questions
What is an ACES file?
An ACES file is an XML file that lists a supplier's applications, each one linking a part number to a vehicle it fits. It follows the Auto Care Association's schema, so any partner using the same version can load it. The current version is ACES 5.0.
What are the VCdb and PCdb?
The VCdb, or Vehicle Configuration Database, is the standard list of vehicle configurations that ACES applications point to. The PCdb, or Product Classification Database, is the standard list of part types used by both ACES and PIES. The Auto Care Association maintains both, and they need a paid subscription.




.avif)