In the “Import” tab you can upload .xslx or .csv files. For example, this allows the user to export product data from the iPIM system as a spreadsheet file, edit the product data in a spreadsheet software and then import it again to update the product data in the iPIM system accordingly. For this purpose, the product data from the spreadsheet file are mapped to the corresponding products and attributes in iPIM.
Upload files using an import template
Configuration
The import process consists of three steps. In the first step you select the desired import template and upload your import file. To do so, proceed as follows:
- Select an import template from the “Import template” menu
. 
The input and selection fields “Identifier”, “Format”, “Locale” and “Context” will automatically be filled. If need be, you can make changes to the settings. - Drag the import file over the drop area
and drop it there. Alternatively, click on "
Browse files" 
to call up the import file via the file manager.The file is loaded into the cache and the file name of the file is shown below the drop area.
- To trigger the parsing of the import file, click on the button. A success message is shown and you will be directed to the following step of the import process.
- To reset the configuration, click on the “Action menu” icon (
) to op en the corresponding action menu and click on the option “New”.
Syntax for the attribute import
Attribute values for simple attribute types such as plain string or number attributes can simply be written in the table cells of an import file. More complex attribute types require a particular syntax to be processed correctly during the import. The following table provides an overview of how to represent attribute values in an import file:
| Attribute type | Syntax | Example |
| Date Date and time |
Attribute values for attributes of these types are written according to the syntax dd.mm.yyyy respectively dd.mm.yyyy hh:mm:ss. |  |
| Complex | In order to import complex attributes, the subordinate complex definition attributes and their values are imported. |  |
| Meta attribute | In order to import meta attributes, the subordinate meta definition attributes and their values are imported. |  |
| Logical value (boolean) | Attributes of this type can possess two states which can be represented according to the syntax true/false, yes/no or ja/nein. |  |
| List of values, multiple List of values, single |
For the import of a List of values, multiple attribute, the value IDs of the respective values are written in the import file. Hereby, the values IDs are separated by a | character: Value ID|Value ID|Value ID… The import of a List of values, single attribute follows the same principle. Though, in this case only a single value ID is written in a table cell. Note: Make sure to import the value IDs and not the values. Otherwise the import does not work. |  |
| Number, integer Number, decimal Number, percentage |
For attributes of these types, the attribute values can simply be written in the respective table cells of the import file. Decimal places before and after the decimal point can be separated by commas or points. Note: When importing attributes with units of measurements that aren’t recognized and allocated automatically during the import, there is still the option to allocate units of measurements in the “Mapping” slider. |  |
| Number range, integer Number range, percentage |
Attribute values for attributes of these types are written according to the syntax start value–end value. Decimal places before and after the decimal point can be separated by commas or points. |  |
| Character string, CMYK | Attribute values for attributes of this type are represented by the percentage values of the four colour shares. For example, 0,100,100,0 for the colour red. Note: The colour values are written without empty spaces and commas. |  |
| Character string, HEX | Attribute values for attributes of these types are represented by a three-digit resp. six-digit hexadecimal code. For example, F00 resp. FF0000 for the colour red. |  |
| Character string, localized Character string, not localized |
For attributes of these types, the attribute values can simply be written in the respective table cells of the import file. |  |
| Composition, listed | In case of e.g. ingredients, attribute values for attributes of this type are written according to the following syntax: share#ingredient value ID|share#ingredient value ID|share#ingredient value ID… Note: Units of measurements are not included in the import file. Hence, it makes sense to specify UOMs for the respective attributes. Alternatively, you can also allocate units of measurement in the “Mapping” slider. |  |
| Composition, percentage | In case of e.g. a material composition, attribute values for attribute of this type are written according to the following syntax: percentage share#material value ID|percentage share#material value ID|percentage share#material value ID… |  |
Syntax for taxonomy mappings
Via the import you can map products to categories of a taxonomy.
| Explaination | Example |
| The syntax for the category allocation is written to the following syntax: version ID#category node ID |  |
How can a product be mapped to multiple categories?
In order to map a product to multiple categories, you need to separate them by a pipe (|).
Mapping
Use auto-mapping
Using the auto-mapping function you can map the column names of the import files to the matching iPIM attributes automatically. To do so, proceed as follows:
- Click on the button to trigger the auto-mapping. The attributes which could be matched to the column names of the import file will appear in the “iPIM attributes” column.
- Determine your further course of action:
- To confirm the auto-mapping result, click on the button . A success message is shown and you will be directed to the third step of the import process.
- To reset the mapping so that you can initiate a new mapping, click on the button.
- To get back to the previous step, click on the button .
- To confirm the auto-mapping result, click on the button
Map attributes manually
Instead of using the auto-maping function, you can map the iPIM attributes to the column names of the import file manually. To do so, proceed as follows:
- To map an attribute to a column name of the import file, drag the attribute from the “Attributes” card to the appropriate row in the “Mapping” card. Possibly use the text search to filter the list of attributes by a search term.
- Map all the attributes from the import file to the corresponding iPIM attributes as described above.
- Determine your further course of action:
- To confirm your selection, click on the button . If the process was successful, a corresponding message will appear and you will be directed to the third step of the import process.
- To reset the mapping so that you can initiate a new mapping, click on the button.
- To get back to the previous step, click on the button .
- To confirm your selection, click on the button
- The “Attributes” card lists all the available attributes which are categorized by attribute scopes and types. Among them are system attributes for the mapping of products to primary, secondary and sales categories. Additionally, there are price, text and cross-selling types. And there are category and standard attributes for a wide range of product informationen.
- You can use the manual mapping to map different attributes to each other. That means you can export the attribute values of an attribute and when uploading them again you can map the attribute values from the import file to an other attribute than the original one.
Clear individual mappings
Via the context menu, you can clear the mapping for individual attributes in order to carry out a new mapping afterwards. In order to clear a mapping, proceed as follows:
- In the corresponding table row, right-click on the mapped iPIM attribute in order to access the context menu.
- Click on the “Clear cell contents” option to empty the table cell.
Preview
In the third step you can see a preview of the mapped products, attributes and attribute values. In the upper right corner you can see the number of validation errors that might have occured. At this point you can finish the import process.
- To finish the import process, click on the button . A success message is shown and the attribute values of the mapped attributes will be updated according the data of the import file.
- To get back to the previous step, click on the button .
Create new import templates
If there is no suitable import template for your import file, you can create a new import template during the import process. To do so, proceed as follows:
- If need be, clear all the selection and input fields of the configuration mask. To do so, click on the “Action menu” icon () to call up the action menu and click on the option “New”.All selection and input fields will be cleared.
- Enter a name for the new import template in the “Identifier” field .
- Select a file format from the “Format” menu .
- Optional: If you chose the file format “CSV”, select a character encoding from the “Encoding” menu.
- Optional: If you chose the file format “CSV”, enter the separator that is used in your import file in the “Separator” field.
- Select a data language from the “Locale” menu
. - Select a context level from the “Context” menu
. - Optional: Tick the “Private” checkbox
to mark the import template as private (since version 5.5.3)*. - Drag the import file over the drop area
and drop it there. Alternatively, click on " Browse files" 
to call up the import file via the file manager.The file is loaded into the cache and the file name of the file is shown below the drop area.
- Click on the button to get to the next step of the import process. In the process, the new import template will be saved. Afterwards you can proceed with the import process as described in the section “Uploading a file using an import template”.
Edit import templates
In order to edit an existing import template, proceed as follows:
- Select the import template from the “Import template” menu.
- Make the desired changes.
- To save your changes, click on the “Action menu” icon () to call up the action menu.
- Click on the option “Save” to save your changes. A success message is shown.
Delete import templates
In order to delete an existing import template, proceed as follows:
- Select the desired import template from the “Import template” menu.
- Click on the “Action menu” icon () to call up the action menu.
- Click on the option “Delete” to finalise the deleting. A success message is shown, the selection and input fields in the configuration mask will be cleared and the deleted import template will vanish from the list of import templates.
FAQ
Why should the data in the import file be formatted as text?
In order to guarantee a flawless import, the data in the import file should be formatted as text.
Can attribute values also be deleted via a file import?
Yes, you can also delete attribute values via an upload of a file.
How can I map products to categories of a taxonomy?
The syntax for the category allocation is written according to the syntax version ID#category node ID. In order to map a product to multiple categories, you need to separate them by a pipe (|).
Who can use a private import template?
Private import templates can only be used by the user who created them. If the “Private” checkbox is not ticked, an import template is public and can be used by all users who have been assigned the same user role as the creator.
According to which syntax are attribute values for “List of values, multiple” attributes represented in an import file?
For the import of a List of values, multiple attribute, the value IDs of the respective values are written in the import file, whereby the value IDs are separated by a | character: Value ID|Value ID|Value ID… You need to make sure to import the value IDs and not the values, otherwise the import does not work.
Why does it make sense to specify a default unit of measurement for attributes with a unit of measurement?
Units of measurements are not included in the import file for attributes of the type “Composition, listed”. Hence, it makes sense to specify a default unit of measurement for the respective iPIM attribute, in case the imported units of measurement can’t be allocated automatically during the import. Alternatively, you can also allocate units of measurement in the “Mapping” slider.
How are attribute values for “Character string, CMYK” attributes represented in an import file?
Attribute values for attributes of this type are represented by the percentage values of the four colour shares, for example 0,100,100,0 for the colour red. The colour values are written without empty spaces and commas.