Three vendors, three demos, and each one ends with a clean ACES file and a clean PIES file on the screen. On that evidence the tools look interchangeable. The differences appear months later: when a receiver sends a file back, when a database update quietly breaks a few hundred records, or when you try to take your catalog somewhere else.
Why the demos all look alike
The Aftermarket Catalog Exchange Standard (ACES) and the Product Information Exchange Standard (PIES) define what a finished file must contain. They say nothing about how the data got there. Any tool, and any service provider, can show a valid file built from tidy sample parts.
A buyer is not choosing the file. A buyer is choosing the work behind it: how fitment is entered and checked, how the catalog keeps up as vehicles and codes change, and what a person sees when something is wrong. That work decides how often files come back and how many hours each correction takes. For what a returned file costs, see why receivers send fitment files back.
The same questions apply whether the catalog will live in installed software, in a hosted service or with a provider that builds files from your spreadsheets. None of the three is right or wrong in itself.
Every tool can show a valid file. Compare what happens before the export, and what happens when a record is wrong.
Write down what the catalog must do
An evaluation goes faster with a one-page list of needs written before the first call. Five facts about your own business shape nearly everything else:
- Who receives your data, and in which versions. 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]. Receivers move at their own pace, so ask each one.
- Which vehicles and regions you sell into. The vehicle database is subscribed to in packages: light duty and powersports, medium and heavy duty trucks, off-highway and equipment, and Latin America [3]. A tool has to handle the packages you need.
- Which channels sit beyond your trading partners. A marketplace may take the standards its own way. Walmart Marketplace accepts ACES XML for vehicle compatibility and cautions that not all PIES data maps into its catalog [7]. The guide to selling parts online covers the channels one by one.
- What you are starting from. Spreadsheets, a supplier's XML, an older system, or nothing yet.
- How much of the line has no vehicle fitment. Universal parts, fluids and merchandise need product data and no applications.
Reference data comes first
Every record in either standard points at codes in Auto Care's reference databases, and those databases move. New content is published monthly as downloads and daily through Auto Care's programming interface [4]. A catalog that was fully valid in spring can hold invalid records by summer without anyone touching it.
So the first technical question is not about screens. It is how the tool gets each update, how soon, and what it does next. A good answer includes a list of your records that the update affected, with the reason, ready to be worked.
Licensing belongs in the same conversation. Subscriptions to the databases run for 12 months and are renewed each year [3]. Under Auto Care's license agreement, a third party hired to build files from the databases must be a subscriber in its own right [5]. Ask whose subscription covers the work, yours, the vendor's or both, and get the answer in writing.
Validation that says why
"It validates" can mean three different things, and a demo rarely says which:
- The file is well formed. It matches the published schema for its version. The schemas are open to anyone with a free autocare.org login [1], so this is the least a tool can do.
- The codes exist and belong together. The vehicle, the engine and the other attributes on a record form a configuration that the current vehicle database really holds.
- The catalog makes sense. No duplicate applications, no two parts claiming the same spot on the same vehicle by accident, no note that contradicts the mapped fitment, no attributes mapped beyond what the fit needs.
The second and third levels are where files get returned. For each, ask to see a failing record. The useful answer names the record, shows the vehicle and part in words as well as ids, and says what is wrong. "Invalid" with no reason sends a person digging.
There is also a referee. Auto Care's Catalog Assessment tool, free to its data standards subscribers, reports on both kinds of file [6]. Running a tool's export through it is an independent check that owes nothing to the vendor.
Ask every vendor to show a record failing, not only a file passing. The explanation on that screen is what your staff will live with.
Data in, data out, and the way home
Getting a catalog in is usually the largest single cost of changing tools. Ask what the import accepts, what it does with a row it cannot place, and whether a person can fix that row where it stands or has to go back to the source file. An import that guesses is worse than one that stops and asks.
On the way out, one export seldom suits every receiver. Look for a separate, saved setup for each receiver: its version, its brands, the part of the line it carries and any limits of its system. Then ask how a change to one part reaches all of them.
The last export is the one that matters most: the day you leave. A full copy of the catalog should come out in a documented form, including the work the standards do not carry. That question has its own article, hosted or customer-hosted catalog software, and the answer belongs in the contract.
Test with your own parts
A prepared demo shows the vendor's best parts. A fair test uses yours. Pick 25 to 50 part numbers that represent the line, and make sure the awkward ones are in the set:
- A part that fits only one engine or one drive type of a vehicle.
- A part with a condition no vehicle attribute covers, such as a gear ratio.
- A part with no vehicle fitment at all.
- A part number written two ways in your own records.
- A few records you already know are wrong.
Hand over the data as it really is, and watch the whole path: the load, the errors, the corrections and the export. Time it. Then run the exported files through the Catalog Assessment tool, or send them to a receiver that offers a test submission, and compare results across vendors.
Two further checks cost little. Ask to speak with a customer of about your size and product type, and ask that customer what happened the last time a database update broke records. And ask who answers a support call: someone who knows fitment, or someone who knows only the screens.
The shortlist checklist
Put the same questions to every vendor and service provider on the list, and write the answers side by side:
- Which ACES and PIES versions can it export today, and can each receiver have its own?
- How do reference database updates arrive, how soon, and how are you told which records each one affected?
- Whose Auto Care subscription covers the reference data, and is that in the agreement?
- Does validation check configurations against the current databases, and does it say why a record fails?
- Does it catch what a schema cannot: duplicates, overlaps, conflicting notes and needless attributes?
- What does the import accept, and what happens to a row it cannot place?
- Can a person read a record in words, with names beside the ids?
- Does it treat a part with no fitment as normal?
- Beyond the two standards, what does it send to the marketplaces and stores you sell through?
- Where does the catalog live, who can reach it, and what do you receive, in what form, if you leave?
- Will the vendor run the test above with your parts before you sign?
A vendor that answers all eleven plainly has earned a place on the shortlist. A vague answer to any one of them marks where the trouble would start.
Sources
- Aftermarket Catalog Exchange Standard (ACES) — Auto Care Association
- Product Information Exchange Standard (PIES) — Auto Care Association
- Data Standards Subscriptions — Auto Care Association
- Vehicle Configuration Database (VCdb) — Auto Care Association
- Technology License Agreement, February 28, 2025 — Auto Care Association
- Top Mistakes You May Be Making in Your ACES and PIES Files — Auto Care Association, August 11, 2023
- 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 validates incoming data against the Auto Care reference databases, keeps a separate export profile for each receiver across ACES 3.0 through 5.0 and PIES 7.0 through 8.0, and holds the catalog in the customer's own database.