To have a successful import, your .xml file must meet the format and structural requirements defined by the PIES standard and supported by PDM. This includes using the correct file extension, encoding, and schema version, as well as including the required segments and fields.
This article outlines the minimum requirements your PIES file must meet to be considered valid for import, including:
File format and encoding expectations
Required XML segments and their structure
Mandatory fields within each segment.
Examples of expected values.
By following these guidelines, you can ensure your data is properly structured and ready for import into PDM.
Prepare your PIES file
Make sure your XML file meets these requirements before uploading:
Extension: Must be .xml
Encoding: Use UTF‑8
Schema Version: Should match the versions supported by PDM, such as 7.2
Required Sections:
Header: General info about your file
Items: Your product records, one for each item
Trailer: Summary details
Tip: If you’re unsure, add a test product in PDM and export a sample PIES XML to use as a template.
Fill in All Required Fields
Minimum Required Segments
Here are the fields PDM expects to see in your file:
Segment Name | XML Element | Description |
Header |
| File metadata and trading partner info |
Items |
| Contains one or more |
Trailer |
| File summary and validation info |
Minimum Required Fields to create a new product
Header Segment (<Header>)
Field Name | XML Element | Requirement | Expected Value Example | Notes |
PIES Version |
| Mandatory | 7.2 | Current PIES version |
Submission Type |
| Mandatory | FULL, UPDATE, TEST | Indicates file type |
PCdb Version Date |
| Mandatory | 2025-07-31 | Latest Autocare table version |
PAdb Version Date |
| Mandatory | 2025-07-31 | Latest Autocare table version |
FULL, UPDATE, or TEST Submission Type: All work the same in PDM
Here are the expected values for the Header segment and the version of PIES, you can see them by going to ACES/PIES XML Headers in the Brand settings segment.
Keep in mind this is the order our system follows; even if the format is correct, if they are in different positions, the import will get errors.
Item Segment (<Item> inside <Items>)
Field Name | XML Element | Requirement | Expected Value Example | Notes |
Maintenance Type |
|
Mandatory | A (Add), C (Change) | Indicates action for item |
Part Number |
|
Mandatory |
TEST01 | Unique product identifier |
Brand AAIAID |
|
Mandatory |
XXXX | Brand code (Autocare or internal) |
Trailer Segment (<Trailer>)
Field Name | XML Element | Requirement | Expected Value Example | Notes |
Item Count |
|
| 1 | Number of items in file |
Transaction Date |
| Mandatory | 2025-07-10 | Date file was created |
Step-by-Step Instructions
Validate your XML file against the PIES guidelines before importing.
Confirm that all mandatory fields are present.
Choose the correct Brand
Click on the Import/Export tab on the left bar.
In the Import/Export tab, select Import.
Choose PIES as the format.
Click Upload and select your PIES file.
After uploading, review the import report for errors.
If there are errors, download the error report and follow the instructions.
To understand the structure and expected format, we recommend filling everything manually for a part number and exporting PIES to have a template.
Tips for Successful Import
Always validate your XML file with the official PIES guidelines before importing.
Ensure all required elements and attributes are present and correctly formatted.
Only include one brand per XML file.
Do not alter the XML header structure unless instructed.
Review error messages carefully and correct issues before re-importing.
If you remove segments from the file, PDM will ignore that; they won't be removed.
You cannot leave a segment without any data. You'll get the warning "Missing child elements"
Handling Errors
Here are a few examples of common human errors and how to fix them.
Header incorrect order
Error: Element '{http://www.aftermarket.org}BlanketEffectiveDate': This element is not expected. Expected is ( {http://www.aftermarket.org}SubmissionType}).
This is because it follows the order established in the Header Segment
Fix: The order of the header needs to be changed from this
To this
Field named incorrectly
Error: Element '{http://www.aftermarket.org}OrderablePackage': This element is not expected. Expected is one of ( {http://www.aftermarket.org}InnerQuantity, {http://www.aftermarket.org}Orderable, {http://www.aftermarket.org}Dimensions, {http://www.aftermarket.org}Weights, {http://www.aftermarket.org}WeightVariance, {http://www.aftermarket.org}StackingFactor, {http://www.aftermarket.org}HazardousMaterial ).
Fix: It needs to be changed from OrderablePackage to Orderable
Field is incomplete or empty
Error: Element '{http://www.aftermarket.org}SubBrandAAIAID': '' is not a valid value of the local atomic type.
In this case, it's because on line 23 there's this value: <SubBrandAAIAID />. That's not the expected formant and it doesn't have data
Fix: This is the expected format
Incorrect UOM
Error: Reference not found: Dimensions_uom (EA).
Fix: Each is not a valid UOM, the expected is inches, cm, etc.
Character limit
Error: Element '{http://www.aftermarket.org}DimensionalWeight': '0.0000694444444444444' is not a valid value of the local atomic type
Fix: The report is not very clear but only 4 decimals are allowed, so it's a null value 0.0000
Error:
Element '{http://www.aftermarket.org}DimensionalWeight': '0.179166666666667' is not a valid value of the local atomic type.
Element '{http://www.aftermarket.org}DimensionalWeight': [facet 'fractionDigits'] The value '0.179166666666667' has more fractional digits than are allowed ('4').
Element '{http://www.aftermarket.org}DimensionalWeight': [facet 'totalDigits'] The value '0.179166666666667' has more digits than are allowed ('9').
Fix: The character limit is 9 and the decimal limit is 4
We always recommend downloading the import errors to know what needs to be fixed and start from there. If you have any questions or if an error report is not very clear, please reach out via Chat support, and we'll gladly assist you.