Supplier Portal - Import

In addition to managing supplier data directly in the supplier portal, it is possible to import data to the portal manually or via actions.

This document describes how the supplier import works when used in the portal.

Data file

As a general principle, the supplier import uses the same file format as the normal Perfion importer:

  • Unique feature names in row 1

  • Items and data in row 2 and downwards

  • Localized features must be postfixed with language code (_XX)

  • Multiple values must be separated by semi colon (e.g. “value1;value2”)

There are however some important differences between the original file format and the supplier data file format. These are discussed below.

Key columns

The first significant change is the content of key columns A and B.

Column A

Column A must always contain the Supplier Identifier Feature. When a supplier imports a file, this column must always contain the supplier's own identifier value in all rows. Otherwise, the import will fail. When an administrator imports a file, it can contains items (rows) from multiple suppliers.

Column B

Column B must always contain the Supplier Key Feature and the values identifying each supplier item. Values in column A+B always define a unique item across all suppliers.

Hierarchy is not allowed in supplier items. This means that the column _parent is never used in supplier imports.

Categorizer feature

The categorizer feature defined in the Company setup will often support hierarchy internally in Perfion. When exposed to suppliers, the hierarchy is removed so that suppliers always see a flat list of categories. This means that the “piped” hierarchy notation (e.g. “Coffee & Tea|Coffee Machines”) is not needed in supplier imports. When specifying a category in the excel file, simply write the name of the category itself (e.g.. “Coffee Machines”)

Image and file references

Images and files are imported from a zip-file uploaded together with the data file. Folders are not supported in the zip-file (all files must be at root level). This simple principle makes it easy to reference an image or a file in the data file. Simply write the name of the asset (e.g. “myredmachine.jpg”) in the data file without any path or folders. The supplier importer will then look for the asset file in the zip-file.

Deleting existing value

Existing supplier values in the portal can be deleted by the importer by writing [DeleteValues] in the matching excel cells.

Assets

Assets to be imported must be saved in a zip-file. Folders are not supported in the zip-file (all files must be at root level).

Multivalue assets

Import of multivalue assets follow this “substitution principle”:

  1. Values in excel file represent the “desired set of assets on product after import”

    1. Example: “asset1;asset5;asset9”

  2. Existing assets not mentioned in excel file are removed from product

  3. New assets mentioned in excel file AND provided in zip-file are added to product

  4. Existing assets mentioned in zip-file and provided in zip-file are replaced on product IF asset is different from existing (identical assets are ignored)

Status for new items

If supplier is allowed to create new items in the portal, it is possible to specify a status for new items created by the importer. Status for new items can be set to Draft (default) or Submitted.

The supplier importer never updates status for existing items

If Submitted is selected in the dialogue, the importer checks if all mandatory values are present for new items in the excel file. If not, the importer fails with information about missing mandatory values.

Tech notes

Selectable feature validation

The importer validates selectable values against existing items in Perfion. If excel file contains a selectable value not present in Perfion, the import fails with information about selectable feature validation.

Example: Supplier tries to import a product with color “Ultra Black”. This color does not exist as a selectable value in Perfion → Import fails .

Feature validation

Validation rules at feature level (numeric ranges, regular expressions) are enforced by the supplier importer.

Example: You have a rule on item name that it must not exceed 50 characters. Supplier tries to import 60 characters → Import fails.