ACES & PIES Data Management for Automotive Aftermarket Catalogs
ACES and PIES are the Auto Care Association’s data standards for the automotive aftermarket. ACES describes which vehicles a part fits, and PIES describes the part itself: attributes, packaging, pricing, digital assets and more. ACES/PIES data management means producing, validating and maintaining both from one governed source of product truth. That source is usually a PIM, so files stay accurate for every trading partner and every version change, including ACES 5.0 and PIES 8.0.
| ACES 5.0 | PIES 8.0 | |
|---|---|---|
| Answers | What does it fit? | What is it? |
| Contains | Vehicle applications, qualifiers, notes | Attributes, descriptions, packaging, pricing, assets |
| References | VCdb, PCdb, Qdb, Brand Table | PCdb, PAdb, Brand Table |
| Format | XML | XML |
ACES vs PIES: What Each Standard Covers
| ACES (Aftermarket Catalog Exchange Standard) | PIES (Product Information Exchange Standard) | |
|---|---|---|
| Purpose | Communicates which vehicles a part fits | Communicates what the part is and how it’s sold |
| Core content | Applications: vehicle, part type, position, qualifiers, notes | Item data: descriptions, attributes, dimensions, packaging, pricing, digital assets, interchange |
| Key reference databases | VCdb (vehicles), PCdb (part types), Qdb (qualifiers) | PCdb (part types), PAdb (part attributes) |
| Typical owner | Catalog / fitment team | Product data / marketing team |
| Where it goes | Distributors, retailers, catalog providers, marketplaces | Distributors, retailers, data pools, marketplaces |
Fitment is the heart of ACES. See how we manage automotive fitment data →
ACES 5.0 and PIES 8.0
The Auto Care Association released ACES 5.0 and PIES 8.0 in April 2026, together with VCdb 2.0, Qdb 2.0, PCdb 2.0, PAdb 5.0 and Brand Table 2.0.1–3
What’s new
- Vehicle- and part-specific non-diagram digital assets in the App segment
- Multiple descriptions per digital asset
- Expanded multilingual support for the MfrLabel field
What’s new
- Extended Producer Responsibility (EPR) packaging data for regulatory compliance
- Multiple package configurations at a single pack level
- Digital-asset file hashing and record sequencing for better validation
Still on ACES 4.2 or PIES 7.2?
Many trading partners will receive older versions for some time, so the practical question is when each of your receivers will expect 5.0 and 8.0. Plan the data-model changes (new asset, packaging and EPR fields), confirm each receiver’s timeline, and run versions in parallel during the transition rather than switching everything at once.
The Reference Databases Behind ACES & PIES
ACES and PIES files point to shared Auto Care reference databases. Keeping your data aligned to them is what makes files acceptable to receivers.
Mapping Project vs Managed ACES/PIES Workflow
Many teams treat ACES/PIES as a file-mapping project. It works once, then drifts. We build it as an ongoing, PIM-governed workflow.
| One-off mapping project | Managed workflow in a PIM | |
|---|---|---|
| Source of truth | Spreadsheets prepared for each send | One governed product and fitment record |
| Validation | Errors found when a receiver rejects the file | Schema, reference-data and fitment checks before every export |
| Updates | Re-mapped by hand for each change | Changes flow automatically into the next export |
| Version changes | A new project for every ACES/PIES release | Versioned export templates; old and new run in parallel |
| Multiple receivers | A separate file effort per partner | Receiver-specific output from the same data |
Source Data → PIM → Validated Exports
Validation and Data Quality
- Schema validation against the ACES or PIES version each receiver expects
- Reference-data alignment with the current VCdb, PCdb, PAdb, Qdb and Brand Table
- Fitment checks for holes, overlaps and invalid applications
- Completeness by receiver, so required PIES attributes and assets are present before sending
Attribute and asset gaps are usually an enrichment problem. Automotive product data enrichment →
Working With Trading Partners
Every distributor, retailer and catalog provider has its own requirements: version, required fields, file cadence and delivery method. We document each receiver’s rules, generate their output from the same governed data, and route their feedback back into the PIM so the next file is better than the last.
During version transitions, receivers on ACES 4.2/PIES 7.2 and those on 5.0/8.0 can be served in parallel from one source.
What We See in Implementations
- Outdated reference data is the most common silent failure. Files pass internally, then fail at the receiver because the VCdb or PCdb version moved on.
- PIES gaps are attribute gaps. Missing PAdb attributes, dimensions and assets cause more rejections than formatting errors.
- Receiver rules belong in the system, not in someone’s inbox. Capturing them as export configuration removes the single point of failure.
Engagement Options
Assess
Review your current ACES/PIES versions, receivers, rejection history and data gaps, with a prioritized plan.
Catalog Assessment →Implement
Build the data model, reference-data alignment, validation and receiver-specific exports in your PIM: Akeneo, Syndigo, Inriver, TruPIM or others.
PIM implementation →Operate
Managed data operations for ongoing updates, receiver onboarding and version changes.
Managed services →StrikeTru implements multiple PIM platforms and also offers TruPIM, its own PIM for growing businesses. We recommend the platform that fits your catalog and receivers.
What is the difference between ACES and PIES?
ACES communicates which vehicles a part fits (its applications). PIES communicates what the part is: descriptions, attributes, packaging, pricing and digital assets. Most aftermarket suppliers need both, generated from the same product data.
What are the latest ACES and PIES versions?
ACES 5.0 and PIES 8.0, released by the Auto Care Association in April 2026 alongside VCdb 2.0, Qdb 2.0, PCdb 2.0, PAdb 5.0 and Brand Table 2.0.
Do I need to move from ACES 4.2 to 5.0 right away?
It depends on when your trading partners expect the new versions. Confirm each receiver’s timeline, plan the data-model changes, and serve old and new versions in parallel during the transition.
Can a PIM generate ACES and PIES files?
Yes, when it has a fitment data model, alignment to the Auto Care reference databases, validation rules and receiver-specific export templates. That setup is the core of our implementation work.
What are VCdb, PCdb, PAdb and Qdb?
They are Auto Care reference databases: VCdb defines vehicles, PCdb defines part types, PAdb defines the attributes for each part type, and Qdb standardizes fitment qualifiers.
Is StrikeTru ACES/PIES certified?
StrikeTru provides ACES/PIES implementation and data-management support: modeling, validation, exports and ongoing operations inside your PIM. We don’t present this as a certification.
How do you keep files current when standards change?
Data lives in one governed PIM record, exports use versioned templates, and we review affected data and receiver rules whenever Auto Care publishes a new version or database update.
Review Your ACES/PIES Workflow
Tell us your current versions, receivers and the rejections you’re seeing. We’ll show where your workflow breaks and what it takes to get ready for ACES 5.0 and PIES 8.0.
Automotive PIM Resources
Sources:
1. Auto Care Association, “Auto Care Association Releases ACES 5.0 and PIES 8.0,” April 2, 2026 (autocare.org).
2. Auto Care Association, “ACES 5.0 and PIES 8.0 Are Here,” April 1, 2026 (autocare.org).
3. Aftermarket News, “Auto Care Association Releases ACES 5.0, PIES 8.0 Standards” (aftermarketnews.com).
ACES and PIES are trademarks of the Auto Care Association.