Import tips

Conversion Mode for Bol and Amazon Content Files

For importing content files from Bol and Amazon, a conversion mode is available. By selecting this conversion mode, the file is immediately converted into the correct format, making the import process easier.
You can select this conversion mode when uploading the file.

Note! This conversion mode only works if the file you upload is an export directly from Bol or Amazon and is only applicable to content files.

Direct Import

For some of our integrations, a direct import button is available in the integration settings. If the integration is linked with ProductFlow, you have the option to export an offer file from the respective integration using this button.
The export will appear on the import page after a few minutes, from where you can import the file.

Note! Through direct import, it is only possible to export offer information.

The direct import option is available in the integration settings for the following channels:

Mapping Suggestions

In the first step of the import, you have the option to select a sales channel for which you want to receive mapping suggestions ('Suggestion for mapping sales channels'). Select the sales channel for which you want to import the information. This will allow our system to recognize certain fields and provide a mapping suggestion, making mapping easier and faster.

Importing Sales Channel Specific Content

To make sales channel specific fields available in the import mappings, it is necessary to classify this sales channel first.

Create a category in ProductFlow and classify it for the respective sales channel. You do this by clicking on 'Categories' in the menu and selecting 'Classification' for the correct sales channel on this page. Here you can classify the category for the sales channel.

To make the fields available in the import, classifying one category is sufficient.

​Importing Propositions

Through the import, it is possible to link propositions to products. Creating new propositions via the import is currently not supported. Therefore, when importing propositions, it is important that the proposition name is already known in ProductFlow.
1. First, create the propositions in ProductFlow and give them exactly the name as they appear in your import file.

2. Import the propositions by choosing the import mapping 'Proposition Name'.

The created propositions are now linked to the correct products.

Importing Families

It is possible to import families/variants and content at the family level.

Use this template to set up the import file.

Importing Two-Level Families

Fill in the Family SKUs and Variant SKUs in the template file.
The Extra Family SKU does not need to be filled in for a two-level family.

Further complete the file with the content you want to import at the family level.

Import Run 1 = Importing Families and Variants

Upload the file in ProductFlow.

Step 1 Options;
Import mode = Create & Update

Base product = No base product

Unique columns = No

Suggestion for mapping sales channels = n/a

Only fields for sales channels = Disabled

Default language = Select the desired language, usually Dutch

Default currency = Select the desired currency, usually Euro

Default delimiter = Select the delimiter applicable in the file. If no delimiters are used, you can leave this on the default setting.

Keep the setting Ignore duplicate SKUs OFF.

Ensure that the correct header row and tab are selected in the sheet configuration.
Any other tabs can be ignored.
​

Step 2 Selectors;

Select the Variant SKU as SKU.

Step 3 Mappings;

Map the Family SKU as Family SKU.

Step 4 Review and Step 5 Report;

The file is analyzed after which it can be imported.

Are error messages appearing? Check out this article for an explanation of the most common error messages.

The variants and families are imported into ProductFlow.

Import run 2 = Importing family content

Once run 1 is imported, you can run the same file a second time to import the content.

Step 1 Options;
All settings can remain the same as in run 1.

An important change is the setting Ignore duplicate SKUs. Set this setting to ON for run 2. This is necessary because Family SKUs appear more frequently in the file.

Step 2 Selectors;

Select the Family SKU as SKU.

Step 3 Mappings;

Remove the mapping Family SKU as Family SKU from the previous run.

Map all the content you want to import at the family level.

Important! We automatically import the content of the first Family SKU we encounter in the file.

Step 4 Review and Step 5 Report;

The file is analyzed and then can be imported.

Messages about Duplicated SKUs will appear. These can be ignored. The content for the first unique Family SKU from the file is imported, the others are skipped and shown in these messages.

The families/variants with family content are now imported.

Importing three-level family.

Fill in the Extra Family SKUs, Family SKUs, and Variant SKUs in the template file. Here, the Extra Family SKU is the highest family product and the Family SKU is the middle family product.

Further fill in the file with the content you want to import at the family level.

Import run 1 = Importing families and variants

Upload the file in ProductFlow.

Step 1 Options;
Import mode = Create & Update

Base product = No base product

Unique columns = No

Suggestion for mapping sales channels = n/a

Only fields for sales channels = Disabled

Default language = Select the desired language, usually Dutch

Default currency = Select the desired currency, usually Euro

Default delimiter = Select the delimiter applicable in the file. If no delimiters are used, you can leave this on the default.

Leave the setting Ignore duplicate SKUs OFF.

Ensure that the correct header row and tab are selected in the sheet configuration.
Any other tabs can be ignored.
​

Step 2 Selectors;

Select the Variant SKU as SKU.

Step 3 Mappings;

Map the Extra Family SKU as Family Levels Level 2.

Map the Family SKU as Family Levels Level 1.

Step 4 Review and Step 5 Report;

The file is analyzed and then can be imported.

Are error messages appearing? Check out this article for an explanation of the most common error messages.

The variants and families are imported into ProductFlow.

Import run 2 = Importing family content

Once run 1 is imported, you can run the same file a second time to import the content.

Step 1 Options;
All settings can remain the same as in run 1.

An important change is the setting Ignore duplicate SKUs. Set this setting to ON for run 2. This is necessary because Family SKUs appear more frequently in the file.
​

Step 2 Selectors;

Importing content at the highest family level?

Select the Extra Family SKU as SKU.
​
Importing content at the middle family level?

Select the Family SKU as SKU.

Step 3 Mappings;

Remove the mapping Extra Family SKU as Family SKU from the previous run.

Map all the content you want to import at the family level.

Important! We automatically import the content of the first Family SKU we encounter in the file.

Step 4 Review and Step 5 Report;

The file is analyzed and then can be imported.

Messages about Duplicated SKUs will appear. These can be ignored. The content for the first unique Family SKU from the file is imported, the others are skipped and shown in these messages.

The families/variants with family content are now imported.

Importing sets

Ensure that before you import the sets, all parts are already 'individually' in ProductFlow. Then you can 'link' them together in a set.

To place the parts into a set via import, a set SKU must be in the import file with the SKUs of the parts following it (on the same line).
​

NOTE! For each part, we need to know how often it appears in the set. You indicate this in the import file by placing the quantity after the part SKU. This must always be done this way. In the example below, each part appears 1x in the set.

Example:

Set SKU Part 1 Part 2 Part 3
FragranceSet Lavender-1 Rose-1 Mint-1
FragranceSet2 Lavender-1 Rose-1 Mint-1
​

Selector

Set SKU = SKU

Mapping
Part 1 = Part
Part 2 = Part
Part 3 = Part

Use this template file to import Sets.