Auto Parts Catalog Standards:
What Are ACES, PIES and Why They Matter
Every quote error, every wrong part shipped, every "I'm not sure if this fits" conversation traces back to catalog data quality. ACES and PIES are the two standards the North American auto parts industry built to solve this — and understanding them is the prerequisite to any meaningful catalog automation.
The catalog problem that ACES and PIES were built to solve
Before industry standards existed, every parts manufacturer published their catalog in a proprietary format. Distributors and dealers had to maintain separate lookup processes for each brand — and when a buyer asked "does this fit my vehicle?", the answer depended on which brand's PDF you happened to have open.
Errors were common. Returns were expensive. And scaling a parts operation meant hiring more people to manually manage incompatible data sets from dozens of suppliers.
ACES and PIES were developed by the Auto Care Association (formerly AAIA) to solve this at the industry level — creating shared formats that any manufacturer, distributor, or retailer could use to exchange parts data without custom translation for every trading partner.
Who maintains these standards: The Auto Care Association and the Automotive Aftermarket Suppliers Association (AASA) jointly govern ACES and PIES. Both standards are updated annually and are the mandatory data format for major US retailers like AutoZone, O'Reilly, Advance Auto Parts, and Amazon Automotive.
ACES: Aftermarket Catalog Exchange Standard
ACES (Aftermarket Catalog Exchange Standard) answers one question: which vehicles does this part fit?
It does this through fitment data — a structured mapping between parts and vehicles. Each ACES record defines an application: a combination of year, make, model, submodel, engine, transmission, and other vehicle attributes for which a specific part is confirmed to fit.
What an ACES record contains
- Part number — the manufacturer's part identifier
- Base vehicle ID — year/make/model reference from the ACES vehicle database (VCdb)
- Submodel — trim level or body style (e.g., XLT, Sport, Crew Cab)
- Engine — displacement, cylinders, fuel type (critical for parts like filters, sensors)
- Transmission — automatic/manual, number of speeds
- Notes — installation instructions, fitment qualifiers, warnings
ACES data is delivered as XML files and references the Vehicle Configuration Database (VCdb) — a master list of vehicle definitions maintained by the Auto Care Association. When a manufacturer says their part fits a "2021 Toyota Tacoma TRD Off-Road 3.5L V6 6-speed automatic," they're referencing a specific VCdb ID, not a free-text string.
This is what makes ACES powerful: fitment data is structured and verifiable, not a text description that two systems might interpret differently.
PIES: Product Information Exchange Standard
Where ACES answers "what does it fit?", PIES (Product Information Exchange Standard) answers "what is it?" — all the descriptive and commercial data about the part itself.
What PIES data covers
- Descriptions — short description, long description, marketing copy
- Dimensions and weight — for shipping and fitment space verification
- Package information — inner pack, master pack, pallet quantities
- Images — primary, alternate, installation, detail shots (with standardized naming)
- Brand and part number — including alternate numbers, superseded parts, cross-references
- HAZMAT data — for regulated materials like batteries, refrigerants, fluids
- Digital assets — installation instructions PDFs, 3D models, video links
PIES is delivered as XML and references the Parts Classification Database (PCdb) — a master taxonomy of part types. When a part is classified as a "Brake Caliper — Front Left," it's not a text description; it's a PCdb category ID that every system in the supply chain reads the same way.
How ACES and PIES work together
Neither standard is complete on its own. A typical catalog exchange includes both:
- PIES file — describes every part in your catalog with all its attributes, images, and packaging data
- ACES file — maps each part to every vehicle it fits, with all the application qualifiers
When a buyer asks "Do you have rotors for a 2020 Chevy Silverado 1500 LT 5.3L?", a system with both ACES and PIES data can:
- Look up the VCdb ID for that specific vehicle configuration
- Query the ACES file for all parts that fit that vehicle ID in the "Rotor" PCdb category
- Pull the PIES data for those parts — description, brand, dimensions, available images
- Return a complete, accurate answer in under a second
This is how automated quoting works at scale. The catalog does the heavy lifting; the AI layer handles the conversation.
Without structured catalog data: A parts lookup requires a human to open the supplier catalog, search by vehicle, scan the results, verify the part number, check stock, and respond. With ACES/PIES integrated into your system, the same lookup is automated and takes milliseconds.
Other catalog standards used in the market
ACES and PIES dominate the North American aftermarket. But dealers working with other data sources will encounter additional formats:
ISHOP (Mexico / Latin America)
Widely used among Mexican auto parts distributors and manufacturers. Covers fitment and product data in a format similar to ACES/PIES but optimized for the Mexican vehicle market and VIN structures. Many distributors in Mexico supply both ACES and ISHOP files depending on their trading partner's requirements.
IPO (International Parts Operations)
Used by some OEM-adjacent manufacturers and exporters for international markets. Less common than ACES/PIES/ISHOP but appears in cross-border supply chains, particularly for European-manufactured parts sold in the Americas.
What "catalog quality" actually means in practice
A parts dealer can have ACES and PIES files from every supplier and still have a catalog quality problem. The common issues:
- Incomplete fitment coverage — the ACES file has 40% of the vehicle applications the part actually fits; the rest weren't populated by the manufacturer
- Missing images — PIES records without images cause 30–40% lower conversion in digital channels
- Stale data — manufacturers update ACES/PIES files quarterly; distributors who don't refresh their catalog feed quote parts that have been superseded
- No cross-reference data — a buyer asks for the competitor's part number; without cross-reference data in PIES, the system can't match it to your stock
Catalog quality isn't a one-time project — it's an ongoing operation. Leading distributors review their catalog feeds monthly and audit fitment accuracy against return data.
How AI uses ACES/PIES to automate quotes
When a digital quoter like Victoria receives a buyer's request, it's not searching PDFs or text databases. It queries structured ACES data to identify fitment, pulls PIES data for the product details, checks live inventory, and applies your pricing rules — all in a single operation.
The quality of the answer is directly proportional to the quality of the underlying catalog data. An AI layer on top of a clean ACES/PIES catalog is a significant competitive advantage. The same AI on top of a spreadsheet catalog is a liability.
This is why catalog standardization is the first technical milestone for any dealer looking to automate their quoting operation — before integrating WhatsApp, before connecting an ERP, the catalog has to be structured and current.
Is your catalog ready for automation?
See how Victoria reads your catalog and quotes in real time
30 minutes. No commitment. We show you how Victoria works with your real catalogs and ERP.