TecDoc vs ACES/PIES
TecDoc runs parts catalogues across Europe. ACES and PIES are how the North American aftermarket exchanges fitment and product data. Here is how they differ, where each one fits, and how Mecaparts works with both.
Two standards, built for two markets.
| TecDoc |   | |
|---|---|---|
| Maintained by | TecAlliance | Auto Care Association |
| Main market | Europe, and used in many other regions | United States, Canada and Mexico; a Latin America package covers the rest of the region |
| What it is | One central catalogue: articles, criteria, OE and IAM references, images, documents and vehicle links | Two exchange standards: ACES says which vehicles a part fits, PIES describes the product itself |
| How a vehicle is identified | TecDoc vehicle type, with a unique number (often called KType) | Vehicle Configuration database (VCdb): year, make and model, refined by engine, submodel and other attributes |
| How data travels | Suppliers deliver to TecDoc (TAF data packages or API); sellers query the catalogue through TecAlliance services | XML files sent by each brand or data provider to distributors, sellers and marketplaces |
| Reference data | Included in the TecDoc catalogue | VCdb, PCdb (part types), Qdb (qualifiers), PAdb (attributes) and Brand Table, by annual subscription |
| Current version | Catalogue updated continuously | ACES 5.0 and PIES 8.0, released April 2, 2026 |
| What you need as a seller | A TecDoc data licence from TecAlliance or an authorised provider | Auto Care subscriptions to read the files, and ACES/PIES files from the brands you sell |
| With Mecaparts | Live in the Shopify app and in our WooCommerce and PrestaShop projects | Integration project on Shopify, WooCommerce or PrestaShop |
One catalogue, or files that travel.
TecDoc is a central catalogue. Suppliers publish their articles and vehicle links into it, and every licensed seller reads the same data from one place.
ACES and PIES are file formats. Each brand produces its own ACES file for fitment and PIES file for product data, against shared reference databases, and sends them to its partners. There is no single catalogue to query: a seller collects and loads the files of every brand it carries.
In practice, TecDoc work is about licence scope and API usage. ACES/PIES work is about collecting files, checking them and keeping versions in sync.
Same concepts, different names.
Both standards describe the same things: a vehicle, a part, and the link between them. This is how we map them to one product model in your store.
| Concept | TecDoc | ACES / PIES | Where it lands in your store |
|---|---|---|---|
| Vehicle | Vehicle type (KType) | VCdb base vehicle + configuration IDs | Vehicle IDs on each variant |
| Fitment | Article ↔ vehicle linkage | ACES application record (part number, vehicle, position, quantity, notes) | Compatible vehicles list and the fit badge |
| Part type | Generic article | PCdb part terminology | Collections and category tree |
| Attributes | Article criteria | PIES attributes, using PAdb definitions | Product specifications |
| References | OE and IAM numbers, trade numbers | PIES part numbers and interchange | Searchable references |
| Media | Images and documents | PIES digital assets; ACES 5.0 adds vehicle- and part-specific assets | Product media and documents |
| Packaging | Packaging and logistics data | PIES packages (PIES 8.0 adds several configurations per level and EPR data) | Weight and shipping data |
Field names in the last column are the metafields the Mecaparts Shopify app writes today. ACES/PIES data is mapped to the same fields in a project.
It depends on where your buyers are.
Choose TecDoc. Most European brands publish their catalogue there, and buyers expect KBA or plate search on top.
TecDocChoose ACES/PIES. Brands, distributors and the large marketplaces exchange fitment and product data in these files.
ACES/PIESUse both, with one product model in your store. Fitment from either source ends up in the same vehicle search.
BothTecDoc in the app. ACES/PIES as a project.
- TecDoc is built into the Mecaparts Shopify app, and into our WooCommerce and PrestaShop integrations.
- ACES/PIES integrations are delivered as fixed-price projects on Shopify, WooCommerce or PrestaShop.
- One vehicle search and one fit badge for buyers, whatever the data source.
- You keep your own TecDoc licence and Auto Care subscriptions. We don't resell data.
We review your ACES and PIES files, or your TecDoc licence, and report coverage, errors and missing vehicles.
We map VCdb vehicles, PCdb part types and PIES attributes to your store's product model, next to any TecDoc data.
Products, fitment and attributes are imported into Shopify, WooCommerce or PrestaShop, with a report for every file.
New file versions from your brands are processed on a schedule, and vehicle search stays up to date.
Does Mecaparts replace TecDoc with ACES/PIES?
Can one store use TecDoc and ACES/PIES at the same time?
Do I need an Auto Care subscription?
Which versions do you work with?
Can you check the quality of my files?
How is an ACES/PIES project priced?
Where these facts come from
- Auto Care Association: ACES 5.0 and PIES 8.0 release (April 2, 2026)
- Auto Care Association: data standards subscriptions
- TecAlliance: TecDoc data format
- TecAlliance: TecDoc data suppliers
TecDoc and TecAlliance are trademarks of TecAlliance GmbH. ACES and PIES are registered trademarks of the Auto Care Association. Mecaparts is independent of both organisations.