ACES 5.0 and PIES 8.0: How Parts Data Quality Decides Your Shelf Space

ACES and PIES are the two data-exchange standards of the North American aftermarket: ACES describes what a part fits, PIES describes what the part is. On 26 March 2026 the Auto Care Association released ACES 5.0 and PIES 8.0 together with refreshed reference databases including VCdb 2.0. For traders this is not an IT topic — it decides whether you can be listed at all.

Most people in aftermarket parts assume price and lead time decide the business. But if you have ever had a listing rejected for data non-compliance, or watched an in-stock item fail to appear in a marketplace search, you know there is a third variable: product data quality.

1. What each standard covers

In one line: ACES is fitment data, PIES is product data, and a channel needs both before it can attach your item to a vehicle and present it properly. Missing either one means the product effectively does not exist.

ACES — Aftermarket Catalog Exchange Standard — describes which years, makes, models, sub-models and engine configurations a part fits. It answers "what does this fit".

PIES — Product Information Exchange Standard — describes part number, brand, package dimensions, weight, material, images, attributes and descriptive fields. It answers "what is this part".

Together they form a product file a distributor can import directly. PIES without ACES and the platform cannot attach the item to a vehicle; ACES without PIES and it cannot present the product.

2. Why the 2026 revision matters

The critical point is that two things changed at once: the file format moved up a version, and the underlying vehicle reference database was revised as well. The first slowly rejects your old files; the second can invalidate the vehicle mappings you already built.

Per the Auto Care Association timeline, ACES 5.0 and PIES 8.0 entered industry review in April 2025 and were released on 26 March 2026, alongside VCdb 2.0, Qdb 2.0, PCdb 2.0, PAdb 2.0 and Brand Table 2.0.

The first consequence is that older formats progressively stop being accepted. Most large distributors and marketplaces allow a transition window, but once it closes, files in outdated versions are rejected outright — new items never reach the shelf and existing records cannot be updated.

The second consequence comes from the reference databases. VCdb is the source of every vehicle code; when it revises, mappings built earlier may need redoing. If your data was constructed three years ago and never maintained, a portion of it is probably invalid today.

3. Four ways bad data costs you

The loss never appears on an invoice, but it erodes revenue in four ways: listing failure, invisibility in search, returns, and loss of channel trust. The first two are simply zero sales.

Listing failure is the most direct. The channel requires compliant files; if you cannot produce them, the product never enters the system. That is not a delay, it is no sales opportunity at all.

Invisibility is the most hidden. Marketplace "shop by vehicle" depends entirely on ACES data. With gaps in fitment your product does not appear when a customer filters by vehicle, however competitive your stock and price.

Returns hurt margin most. Wrong fitment produces wrong purchases, and wrong purchases come back. The handling cost of one returned handle — support, reverse logistics, reshipment, rating damage — is often several times the item's gross margin, and lost traffic after a rating drop persists far longer.

Loss of channel trust is hardest to reverse. When your data repeatedly causes problems, buyers remove you from the list of suppliers they can list without worrying.

4. Why files get rejected

Rejections cluster into five causes, and almost all of them can be caught with a pre-submission checklist. In rough order of frequency:

Outdated version numbers, usually because an internal export template has not been updated in years. Incorrect or retired vehicle codes — after a VCdb revision some codes are deprecated and continuing to use them fails validation.

Missing mandatory fields: brand code, packaging data such as GTIN, dimensions and weight, and certain attributes are prerequisites for import; one omission can bounce the entire file.

Unclear side and position marking. This is lethal for handles, window regulators and hinges, where left and right matter, because it leads directly to wrong installs and returns.

Non-compliant images. Most platforms specify resolution, background and file format; images that miss the spec are refused, and products without images convert poorly.

5. A supplier data checklist

Put these five requirements directly into your purchasing documents when sourcing from Asia; they prevent the large majority of downstream data problems. The point is to demand verifiable fields rather than vague specification text.

A complete fitment list covering at least year range, make, model and sub-model, with explicit side and position marking. Do not accept "fits [platform]" descriptions.

OEM cross-reference numbers. This is how workshops and consumers search, and it is your cross-check that fitment is right.

Physical specifications: net weight, gross weight, package dimensions, material and surface finish. These are mandatory PIES content and the basis of freight and shelf-space calculations.

Platform-compliant product images with an explicitly agreed licence scope, to avoid disputes when you use them on marketplaces.

A change-notification duty: the supplier proactively informs you when part numbers change, specifications change, or an item is discontinued. Data maintenance is a process, not a one-off task.

6. Who owns data maintenance

The workable split is: the supplier owns source-data accuracy, and the trader (or its data provider) owns format compliance. Writing that split into the contract saves a great deal of argument later.

The supplier owns the true specification, material, weight and OEM cross-references, because only the manufacturing side knows the actual figures. The trader owns conversion of that source data into current-version compliant files, because only you know your channel's exact requirements.

The logic is practical: suppliers serve many markets and cannot maintain a local format for each. What matters is agreeing update frequency and notification duties in the contract rather than assigning blame after a problem.

7. Comparing three data strategies

Traders generally take one of three approaches, and the cost-benefit differs sharply. Compare them on four dimensions before deciding.

Full outsourcing to a data service provider: highest upfront cost, usually priced per SKU, but highest compliance and fastest go-live. Suits buyers with many SKUs and established revenue.

In-house build: requires upfront investment in learning the standards and tooling, medium maintenance cost, lowest long-run unit cost. Suits companies with a stable range planning to serve the same channels for years.

Relying entirely on supplier-provided data: lowest upfront cost but least controllable compliance, because suppliers may not know your market's current version. Suits early-stage buyers with few SKUs, but is not advisable as a long-term plan.

The decision rule is simple: once your range passes a few hundred SKUs, or you operate on two or more platforms, the first two options usually return more than the third.

8. Turning data quality into an advantage

Most traders treat compliance as a cost, but it can be a moat, because clean data accrues over time and competitors cannot replicate it quickly.

When your data is complete, fitment precise and images present, platform algorithms match your product to the right buyer more often, returns fall, ratings rise, and organic traffic follows — a virtuous cycle.

More practically, a well-maintained dataset sharply lowers the cost of adding a sales channel. The same data, lightly adapted, serves another platform, letting you expand faster than competitors who rebuild each time.

9. Recommended actions

Work in four steps, and put your top twenty revenue SKUs first — they typically account for more than seventy percent of import value.

Take stock of which versions you use today and when mappings were last refreshed. Bring the top twenty SKUs to the current version and validate them. Talk to your main suppliers and fold the checklist above into purchasing documents. Establish quarterly maintenance so updates are routine rather than a reaction to rejection.

10. Three real buyer situations

Data problems present differently by company size, and the right remedy differs too. These are the three cases we meet most often.

A regional wholesaler moving from offline to online. Years of paper or spreadsheet catalogues, data scattered across files, the same part written differently in different tables. Their priority is not rushing to list but establishing a single source of truth — one master table for part number, fitment and specification — otherwise every new platform means redoing the work.

A growing trader already selling on several platforms. Their pain is that each platform demands something different, manual maintenance creates version drift, and platform A is updated while platform B still shows old data. They should invest in centralised management and automated distribution rather than more headcount.

A Tier 1 trader supplying retail chains. They face strict compliance audits and scheduled data refreshes; one rejection can disrupt a whole quarter of listing plans. They need institutionalised maintenance: named owners, update cycles and a validation process.

11. How to verify supplier fitment data

Do not import a supplier's fitment list directly. Three cross-checks will intercept most errors.

Reverse-check via OEM part numbers. A given OEM number normally maps to a specific set of vehicles; if the supplier's list diverges noticeably from that coverage, go back and confirm.

Check left/right logic. Handles and hinges necessarily come in pairs; if a vehicle shows a left part but no right, that usually signals missing data rather than a genuinely one-sided product.

Check year-range plausibility. Model changes have known dates; if a fitment range spans a major facelift, confirm whether it truly carries over or the supplier has merged two generations.

Each check takes under an hour and avoids the return and reputation costs of discovering errors after listing.

12. Closing

A standards revision sounds like a technical event; in practice it is an adjustment of the entry barrier to distribution. The March 2026 revision moved data maintenance from "nice to have" to "fail and you are out".

For traders sourcing from Asia the good news is that the bar is the same for everyone. While most competitors still run on three-year-old data, those willing to clean theirs gain more than compliance: better search exposure, lower returns, and faster expansion into new channels. None of it shows on a quotation, but it decides whether a channel sees you as a supplier worth keeping.

13. Data quality also decides whether AI search can cite you

Data used to matter only for platform search. Now there is another channel: buyers asking ChatGPT or Perplexity where to buy a handle for a given model. These systems cite structured, semantically clear data — not text embedded in images.

The practical implication for aftermarket parts is direct. If your product page carries only an image and a part number, a language model sees almost no readable content. If the page states fitment, year range, position, OEM cross-references and material specification explicitly, it becomes citable when a buyer asks.

This is why we recommend reflecting your ACES/PIES work on your own website, not only in the files you hand to channels. The same clean dataset can feed distributor systems and support your own site's search and AI visibility — a much better return on the same effort.

14. A minimum viable approach for small traders

If your team is two or three people with no budget for a data platform, that does not mean giving up. Here is the minimum we consider genuinely workable.

Build a master sheet with fixed columns: internal part number, OEM cross-reference, make, model, sub-model, year from, year to, side, position, net weight, gross weight, package dimensions, material, finish, image filename. Fixed columns matter more than fancy tooling, because they decide whether the file can be converted automatically later.

Then maintain only your top fifty fast-moving SKUs. Do not attempt the whole range on day one. Those fifty usually carry most of your revenue, so getting them right delivers the clearest benefit.

Finally, build one habit: every time you place an order or request a quotation, ask the supplier to refresh the corresponding fields in that master sheet. Embedding maintenance into an existing process is far more sustainable than scheduling separate time for it.

15. Three common myths

Finally, three myths we are asked about constantly — each of which tends to delay action.

Myth one: "my range is small, I do not need standardisation". In fact a small range is easier to do, and clean data is the ticket the moment you want to add a channel. Cleaning up later, with more SKUs, costs several times as much.

Myth two: "the supplier says they have ACES files, so we are fine". What matters is the version and the validation result, not the existence of a file. Old-version files are worthless after the transition window, and unvalidated files usually reveal their errors only at import.

Myth three: "data is a one-off project". Vehicles are added every year, part numbers change, standards revise. Maintenance is necessarily continuous. Put it in the quarterly routine so you are not scrambling when a rejection arrives.