ACES, PIES, PADB and NAPA PartsPro Mapping - For NAPA, Amazon PartsFinder, WHI, Epicor, OptiCat and all ACES/PIES Recipients
More and more data recipients are requiring your application data in ACES format and your product data in PIES format. Additionally, the PIES file they request can be anywhere between version 6.1 to 6.6 with standard or customized fields required. We can help you meet all those expectations.
eCatSolution provides conversion (mapping) and formatting services to all the major automotive formats including:
- NAPA PartsPro
- Amazon PartsFinder
- Advance Auto Parts
- Canadian Tire
- Any Many More...
ACES (Aftermarket Catalog Exchange Standard) is the North American industry standard for the management and exchange of automotive catalog applications data. With ACES, suppliers can publish automotive data with standardized vehicle attributes, parts classifications and qualifier statements. ACES also prescribes a machine-readable format (XML) for trading partners to use in exchanging vast amounts of catalog information electronically.
The Product Information Exchange Standard (PIES) is the best practice for the management and exchange of product attribute information in the vehicle auto care industry. Standardizing product content lowers supply chain costs and contributes to increased sales and operational efficiency. Following an industry standard is the first step towards data synchronization with channel partners which yields increased sales, shorter new product introduction cycles and lower operating costs through reduced order processing, invoicing and shipping errors.
In order to be listed in Amazon's Automotive PartsFinder, your application data needs to be mapped to ACES and uploaded into their system in the ACES XML format. Whether you are just getting started with loading your data into Amazon or just need to update your existing data, we can provide the services you require.
NAPA maintains their own vehicle valid table separate from ACES and has their own specific requirements on how application and product data needs to be maintained. We have been working with the NAPA system for almost two decades and can help you get your data loaded into NAPA right the first time.
The Vehicle Configuration Database (VCdb) is a fully normalized, relational database of vehicle configurations for passenger cars and light trucks sold in the US, Canada and Mexico. Base vehicle information (Year, Make, Model and Submodel) for Vintage vehicles (1896 – 1950) was added to the VCdb in September 2006 for the US. The VCdb represents nearly 50 unique attributes, organized into vehicle systems or attribute groups that are validated against base vehicle and sub-model combinations. The structure of the database allows auto care industry companies to communicate applications with as much or as little detail as necessary. The result is more precise, accurate data. The VCdb is an essential element of any data solution that aims to manage and communicate complex vehicle information in a industry standardized format.
The Product Classification Database (PCdb) is intended to design, populate and implement a data repository for coded hierarchical terminology describing replacement parts, service items and supplies commonly sold in the auto care market. The design of the database supports terminology for many industry segments, including collision repair, and supports classification of application-specific as well as generic commodities found in the auto care market. PCdb codes are central to the exchange of electronic catalog application data and serve to classify and categorize application records. The design of the database allows the hierarchy to be integrated into other automotive industry efforts such as the Product Information Exchange Standard (PIES).
A Qualifier Database (Qdb) is supplied to help standardize terminology within the industry and reduce the number of potentially confusing free-text expressions found in applications. Qualifiers not covered by a vehicle attribute will be contained in the Qdb. In general, only individual qualifiers are stored in the table. You can create compound expressions by joining multiple entries from this table. A placeholder (i.e. parameter) will replace variable data found in a qualifier. This mechanism greatly reduces the number of qualifiers stored in the table.
The Product Attribute database (PAdb) is an auto care industry standard reference database to be used in conjunction with the Product Information Exchange Standard (PIES). The PAdb standardizes the way product-specific performance and physical attributes are exchanged between trading partners. The PAdb defines the way trading partners exchange information about the form, fit and function of thousands of automotive products—making that information consistent and predictable across the industry. Rich, complete and accurate product attribute information is an essential component of marketing any product successfully. All customers—professional shop and retail consumers—rely on robust product attributes to make informed decisions and select the most appropriate product for their needs. Performance and physical attributes address the objective differences between two similar products. This information enables customers to make informed and knowledgeable decisions, fully aware of the differences between similar products.