By importing product data via a CSV (Comma-Separated Values) file to ProductIP’s FTP/SFTP server, ProductIP automatically creates technical files and stores the data directly into those technical files. This automation saves time, reduces manual errors, and streamlines compliance by integrating your internal systems with ProductIP. The imports will appear in your account as pre-draft files.
Feature access
This feature is available for Professional and Enterprise customers. Contact sales@productip.com to discuss the options or to consider an upgrade.
Before you begin
Prepare a CSV file matching ProductIP’s field requirements. Configure FTP/SFTP access with authentication.
Video instructions
A short step-by-step guide will follow soon!
Steps
-
Define which fields you want to import from the provided list (please refer to the ProductIP import articles interface (CSV import)).
-
Specify the CSV settings:
-
Field enclosure ASCII value (e.g., “)
-
Field separator ASCII value (e.g., ,or 😉
- File encoding (e.g., UTF-8)
- Date format (e.g., YYYY-MM-DD)
-
Number of header lines (e.g., 3)
-
-
Indicate field position order by filling 1, 2, 3 … and select which set of fields are unique for a file in the primary field (mark a small square box with a “✓” or “x”). Fields marked with “-” are not applicable.
-
Add text to the tags to provide the context information of the tag.
- Submit a sample CSV file to helpdesk@productip.com for configuration and testing.
- Choose import frequency (daily or weekly) and decide if IP restrictions apply.
-
Specify the preferred FTP connection type (FTPS, or SFTP) and authentication method (key or basic).
- ProductIP tests the import in a test environment and provides feedback within two weeks.
-
Receive production server credentials if the import is approved.
- Upload your CSV files regularly to the production (S)FTP server.
- Verify imported data within ProductIP for accuracy and completeness.
-
Receive automatic notifications if imports fail. ProductIP IT will follow up to resolve any issues.
Tips and best practices
- Use a consistent date format (e.g.,
YYYY-MM-DD) throughout your dataset to prevent import errors. - Ensure a one-to-one field mapping between your CSV and the system:
Each column in the CSV must correspond to a single, unique field in our system. It is not possible to import multiple CSV fields into one system field.
If necessary, merge related fields into a single column in the CSV before submitting. - If your field data contains an enclosure character (“), it must be doubled in the CSV file.Example: 14” wheel should become 14”” wheel in the CSV file, if your enclosure character is ”.
Troubleshooting
- Import failed?
Check the email notifications for error details, such as encoding issues, missing fields, or invalid data. - Unexpected field mappings?
Ensure field positions (1, 2, 3, …) are correctly filled in and correspond to the actual column order in the CSV. - Duplicate records?
Review the “primary field” settings to confirm the correct fields are marked as unique.
Still having issues? Contact ProductIP via helpdesk@productip.com.
FAQ
- Can I import multiple files at once?
Yes, you can upload multiple CSV files at a time to the (S)FTP server.
- What if my CSV format changes?
Notify ProductIP IT before changes. A new configuration may be needed to accommodate updated fields or formats.
- Are all product fields mandatory?
Only product article number and product name are mandatory; other fields are optional but recommended for completeness.
- Why are my supplier contact details not appearing correctly?
If a supplier code is included in an import template and the Use supplier information from Address Book checkbox is selected under Account Settings in Company Account, the default contact person in the Address book will overwrite the supplier contact details entered in the template. As a result, the default Address book contact will appear in the technical file.
- Will importing data via CSV update the Address book?
No. Importing data via CSV only adds new data to the Address book and does not update existing Address book entries. This is intended to protect the Address book from unwanted changes.
