What Is ACES and PIES The two standards every parts receiver asks for, in plain English.

A retailer's onboarding email, a marketplace setup guide or a new distributor asks for "ACES and PIES", and nobody stops to say what the words mean. They are the two data standards the North American parts aftermarket uses to trade catalog information. This guide explains each one, shows what a record looks like, and lists what it takes to begin.

What the two names stand for

ACES is the Aftermarket Catalog Exchange Standard. It is the industry standard for managing and communicating product fitment data [1]: the statement that a given part fits a given vehicle. PIES is the Product Information Exchange Standard. It does the same job for product information [2]: what the product is, how it is described, what it costs and how it ships.

The Auto Care Association manages both, under the guidance of a Technology Standards Committee made up of volunteers from its member companies [3]. Each new version passes a 90-day industry review before it is released [1].

It helps to know what the pair is not. It is not software: a standard defines what a file must contain, and any program can write one. It is not a shared pool of everybody's catalogs: Auto Care states that it provides communication standards, not an industry data pool [1]. And it is not only for cars. The same standards serve light, medium and heavy duty vehicles, powersports, off-highway machines and equipment [1] [2].

For how the two files compare and where they connect, see ACES vs PIES.

Key takeaway

ACES carries fitment and PIES carries product information. Both are agreed ways to send data, not programs and not places where data is stored.

Why receivers ask for them

A retailer or a marketplace takes product data from many suppliers. If each one sent its own spreadsheet layout, every file would have to be read and re-keyed by hand. The standards replace that with one machine-readable format, XML, that every trading partner can read [3].

Auto Care lists what that buys: less duplicated effort in communicating and distributing data, lower supply chain costs, faster product introduction, and a contribution to increased sales and reduced returns [1].

Use is close to universal in this market. Auto Care says most companies in the North American aftermarket use the two standards to do business, and that adoption is spreading to Mexico and to Central and South America [1]. The users it names run the length of the supply chain: manufacturers, remanufacturers, program groups, distributors, retailers, ecommerce companies and data solution providers [1].

For a brand, the price of going without is visibility. Walmart Marketplace, for one, takes vehicle compatibility as ACES XML and says a listing needs that data to appear in its auto parts fitment tool [11]. For a part type that shoppers look up by vehicle, a product missing from that search is easy to miss altogether. How each online channel takes the data is covered in the guide to selling parts online.

The reference databases behind the codes

Open either kind of file and you find numbers where you expected names. A vehicle is an id. A part type is an id. A brand is a code. Each one points at a reference database that Auto Care maintains, so that sender and receiver mean exactly the same thing [1].

  • Vehicle Configuration Database (VCdb): the vehicles and equipment sold in the USA, Canada, Mexico and Latin America, with their configurations and attributes [4].
  • Product Classification Database (PCdb): standard names for kinds of product, vehicle specific or not. Brake pads and spark plugs are in it, and so are sponges and T-shirts [5].
  • Qualifier Database (Qdb): coded statements for conditions that no vehicle attribute covers [7].
  • Product Attribute Database (PAdb): the specifications of a product, such as color, finish and material [6].
  • Brand Table: the coded list of brands that both standards draw on [8].

Using either standard takes an annual paid subscription to these databases [1]. They also change. Auto Care publishes new content monthly as downloads and daily through its interface for software [4]. A code that was valid last quarter can be gone this quarter, which is one of the usual reasons a receiver sends a file back.

What an ACES record looks like

The unit of fitment is the application: one statement that one part fits one vehicle. Every application must carry four things: a base vehicle (a year, make and model), a part type, a quantity and a part number [9]. Nothing beyond those four belongs in the record unless it is needed to qualify the fit without ambiguity.

Example - one ACES 4.2 application for an oil filter that fits one of the engines offered on a vehicle (ids shortened to "…")
<App action="A" id="1">
  <BaseVehicle id="…"/>   year + make + model
  <EngineBase id="…"/>    only with this engine
  <Qty>1</Qty>             one per vehicle
  <PartType id="…"/>      engine oil filter
  <Part>EX-5120</Part>     the part number
</App>
The plain-English notes on the right are explanations for this article, not part of the file. In ACES 5.0, PartType is named PartTerminology and Part is named PartNumber.

Read aloud, the record says: part EX-5120 is an engine oil filter, and one is used on this year, make and model when it has this engine. Take the engine line out and the record is still valid. It now claims every engine offered on that vehicle, which is a different statement and, for this filter, a wrong one. The engine line earns its place only because the vehicle came with more than one engine. Had there been a single engine, naming it would add nothing, and listing every engine would claim exactly what naming none does.

Not every product has records like this. Universal parts, fluids, tools and merchandise fit no particular vehicle. They have no applications, and that is correct.

What a PIES record looks like

The unit of product information is the item: one part number and what a seller needs to know about it. In PIES 8.0 every item must state a part number, a Brand ID, a part type and whether the part has ACES applications [10]. Around that core a supplier can send features and benefits, marketing descriptions, pricing, warranty, product attributes, hazardous materials information, kits, interchanges and digital assets such as images [2].

Example - the core of one PIES 8.0 item with two descriptions (ids shortened to "…")
<Item MaintenanceType="A">
  <PartNumber>EX-5120</PartNumber>
  <BrandID>…</BrandID>                       who makes it
  <ACESApplications>Y</ACESApplications>     it has fitment
  <PartTerminologyID>…</PartTerminologyID>   engine oil filter
  <Descriptions>
    <Description MaintenanceType="A" DescriptionCode="SHO"
      LanguageCode="EN">Engine Oil Filter</Description>
    <Description MaintenanceType="A" DescriptionCode="DES"
      LanguageCode="EN">Spin-on engine oil filter with anti-drainback valve</Description>
  </Descriptions>
</Item>
The plain-English notes on the right are explanations for this article, not part of the file. SHO marks a short product description of up to 20 characters and DES a long one of up to 80.

The item never mentions a vehicle. Fitment lives in the other file, and the two meet on the brand and the part number. That is why the same part number, written the same way, has to appear in both.

What it takes to start

Auto Care sets out three steps: subscribe to the reference databases, download the documentation, then create or receive files [1]. A few facts make those steps easier to plan.

  • The documentation is open. The technical documents, schemas and best practices can be read by anyone with a free autocare.org login, and sample data sits in the same place [1]. It is worth reading before any money is spent.
  • Two versions are supported at a time. Auto Care supports only the current and the previous version of each standard: today ACES 5.0 and 4.2, and PIES 8.0 and 7.2 [1] [2]. Ask each receiver which version it takes.
  • Training exists. Auto Care offers e-learning courses, including an introduction to the two standards and an intermediate course [3].

The XML is the smaller part of the work. The larger part is knowing each product well enough to state, vehicle by vehicle and engine by engine, what it fits, and to describe it the way a shopper would look for it.

Key takeaway

The standards give a catalog its shape. They do not supply the knowledge of which part fits which vehicle; that comes from the brand.

What to look for in a first catalog tool

Files can be built in software, by a service provider or, for a small line, close to by hand. Whichever route is on the table, these questions separate a workable one from a painful one:

  1. Can it start from what exists today, such as a spreadsheet or a supplier's file, or does it expect finished XML?
  2. Does it show names beside the ids, so a person can read a record and catch a wrong vehicle before a receiver does?
  3. Does it check every record against the current reference databases, and say why a record is invalid, not only that it is?
  4. When the databases change, how soon is that picked up, and are you told which of your records the change affected?
  5. Can it produce each version your receivers ask for, the previous one included?
  6. Does it accept that some products have no fitment, without marking them incomplete?
  7. If you stop using the tool or the service, do you leave with your whole catalog in a form you can use elsewhere?

Sources

  1. Aftermarket Catalog Exchange Standard (ACES) — Auto Care Association
  2. Product Information Exchange Standard (PIES) — Auto Care Association
  3. Data Standards — Auto Care Association
  4. Vehicle Configuration Database (VCdb) — Auto Care Association
  5. Product Classification Database (PCdb) — Auto Care Association
  6. Product Attribute Database (PAdb) — Auto Care Association
  7. Qualifier Database (Qdb) — Auto Care Association
  8. Brand Table — Auto Care Association
  9. ACES Technical Specification and XSD schema — Auto Care Association (free autocare.org login)
  10. PIES 8.0 XSD schema — Auto Care Association (free autocare.org login)
  11. Automotive fitment: Add vehicle compatibility data — Walmart Marketplace Learn, updated September 2, 2026

About Rivers Edge

Rivers Edge has built catalog software for the automotive aftermarket since 2001, and makes Auto Plus, customer-hosted ACES and PIES catalog management for brands, retailers and distributors. Auto Plus builds both kinds of file from one catalog the customer owns: it takes in XML, flat-file templates and spreadsheet or delimited source files through a column mapper, checks records against the Auto Care reference databases, and exports ACES 3.0 through 5.0 and PIES 7.0 through 8.0.

How Auto Plus handles ACES and PIES · Schedule a demo