Modes of Data Import

We can import SKU data or the entire Catalog structure into the catalog based on the requirement. The two formats through which the product data or the catalog structure that can be imported into the catalog are explained in the following sections:

• Importing the Catalog Structure using PCC Supported File Formats

• Importing SKU Data to the Catalog using User Defined Import Template

• Importing SKU Data to the Catalog using Hybrid Import Template

• Connector

Importing the Catalog Structure using PCC Supported File Formats

A catalog structure which consists of entities such as Taxonomy, Attribute, Schema and SKU can be imported into the catalog using the PCC supported file formats. The process to upload and execute the import remains the same for any PCC standard file format except for the mandatory fields to be entered depending on the file format chosen. Here, let us understand the import process using standard vertical files.

Import using Standard Vertical Files

For example, we have standard vertical files shared by the customer to import the catalog structure as shown below.

Figure 287: Sample file

Each of these individual files contain respective information related to the entity. Following is the screenshot of the Taxonomy file containing the taxonomy path and other details related to the nodes.

Similarly, attribute related files will contain attribute details and so on. Let us understand how to import these catalog entities into the catalog in PCC.

To import catalog structure into a catalog:

1. Go to Import > Catalog Import.

2. Click +New Import and the following screen appears.

Figure 288: New import screen

3. Enter the Import Name- This name will be used to save the file and will appear on the Imports page. For example, John Test Import.

4. Select the Catalog where the imported data will be saved. As you start typing the name of the catalog, the drop-down list is displayed. For example, we need to import the catalog entities to a catalog named Test Catalog.

5. Select PCC Standard File Type as the format as we will be uploading standard vertical files. Refer section A.4 Standard Vertical Files for more details on vertical files.

As soon as you select PCC Standard File Type, the option to upload files and File Upload Location is displayed as shown below.

6. If you want to upload the file from your local machine, select Local Machine.

   In case of vertical files, you can upload a folder having all the vertical files or you can upload files one by one selecting the Upload File option. You can also drag and drop files here.

7. To upload a folder having all the vertical files, click Upload Folder and select the folder containing the vertical files. The following message is displayed.

8. Click Upload and the files are uploaded as shown below.

9. If you want to upload file from external source, select External Location. This will prompt you to choose the location from the Select External File Location dropdown.

10. Once you choose the location, click on Configure File Name Pattern for Import File hyperlink where you can add the name of a file appended to Batch Id.

11. There is also a provision to make changes to the existing file. Select the SKU Addition Preference value from the dropdown.

The values are explained below:

Note: If you are Importing the file for the first time, select Add new & update existing SKU(s) as the value.

12. Select Match SKUs in input file with catalog SKU using value either as SKU Item Id or Custom list of attributes.

    On selecting Custom list of attributes, click Add Attribute. Now enter the attribute in Attribute column. In Matching Logic, select the value from three available values – Exact as is value, Remove special character, and Use alias as shown in the screenshot below:

13. Click on the icon to delete the added attribute.

14. Click on the Default Taxonomy Node link if you want to select the default taxonomy path from the catalog, incase if the import file has new SKUs with no taxonomy. On the Select Taxonomy Node, select the node and click Select.

15. Scheduled Imports: You can set up scheduled imports to run automatically based on a configured schedule. Click +Add Schedule to configure and then select the Frequency, Date, and Time from the dropdown menu.

16. Select the Import File Type next to each file uploaded and a list of all supported file types are displayed as shown below.

For example, in the case of Attribute file, you need to select file type as Standard Vertical – Attribute. Thus, you need to select the respective file types for all the vertical files uploaded.

The following fields are displayed based on the import file type selected:

• Field Delimiter – Here, you need to enter the delimiter (such as tab or ,) used to separate one field from another in a delimited file. This is applicable for only standard vertical files.

• Field Enclosure – Here, you need to enter the value as quotes (“) if the data in the file itself is enclosed in quotes. This is applicable for only standard vertical files. If the data is not enclosed in quotes, keep the field as blank.

• First Row Of Data  - Here, you need to enter the row number where the headers start in the file. In case of vertical and horizontal files, this value will always consider the header as shown below. This is applicable for both standard vertical and horizontal excel and CSV files.

• Taxonomy Path Delimiter – Here, you need to enter the single character delimiter used between nodes to define the taxonomy path. This is applicable for only horizontal excel and CSV files.

• Item Id Column - Here, you need to enter the column number where the SKU Item ID is present in the file. This is applicable for only horizontal excel and CSV files.

• Taxonomy Column - Here, you need to enter the column number where the Taxonomy for the SKUs is present in the file. This is applicable for only horizontal excel and CSV files.

• Multivalue Field Delimiter - Here, you need to enter the delimiter that will be used to separate multiple values for the same attributes or Digital Assets. For example: ; (a semicolon). This is applicable for only horizontal excel and CSV files.

Based on the file type selected, upload the relevant file. The following table lists the file type and its description along with the mandatory fields to be entered for each file type.

Table 31: Import File Type and Fields

As per the example mentioned in Figure 287: Sample file, four files are uploaded. You need to select the respective file types as shown in the following figure.

Figure 289: File type selected for standard files

In this case, type the Field Delimiter as tab, Field Enclosure as “and First Row of Data as 1 as shown below.

Since there are multiple files, instead of typing the values for each and every file uploaded, you can copy-paste the values.

17. Click the Copy Values icon and the Paste Values icon is enabled next to the remaining files.

18. Click the Paste Values icon next to the remaining files where the field values have not been entered as shown below.

The values are copied successfully.

19. Click the Remove icon to remove any uploaded file, if required. You can also add additional files, by dragging and dropping the files as needed.

20. Click Add Import and the import file is uploaded. You can track the status of the uploaded file on the Imports page. However, the process is not complete yet as you need to process the import file. Refer Processing the Uploaded Files and Viewing its Status section to complete the import process.

Once the import process is completed successfully, the catalog entities are added to the selected catalog as shown below.

As shown in the figure above, all the catalog entities present in the file are now added to the selected catalog, after successful completion of the import process.

DA Linkage to SKUs during Import using Standard Vertical Files

In case of standard vertical files, each entity has a separate file. A SkuFileResource is a vertical file containing details of digital assets to be linked. Here, the name of the asset as well as a valid link to the location of the digital asset is also provided. Sometimes, the file will also contain properties of the asset.

Following is a sample of a SkuFileResource file.

Once the import is completed, the users will receive an automated notification on their registered email address. The notification will give a breakup of digital assets uploaded, processed, and errored out as shown below.

There are 3 scenarios that will be checked for while uploading assets which are detailed in section DA Linkage to SKUs during Import.

Importing SKU Data to the Catalog using User Defined Import Template

Let us import SKU data into a catalog which already has the taxonomy structure, and the attributes added. Here, we will also understand how to create, update and delete a user defined template while importing data using the template as explained in following sections:

• Creating a New User Defined Template

• Reusing Template

• Updating Templates

• Deleting a Template

For example, we have a horizontal csv file shared by the customer to import SKU data as shown below.

Figure 290: Horizontal file

This file contains all SKU details to be imported, that is, the SKU ID, taxonomy path for the SKUs and the SKU Attribute Values. We need to import the SKU IDs along with the attribute values for the respective SKUs in an existing catalog with the taxonomy and attribute mentioned above.

The following figure displays the tree structure and attribute already present in the catalog to which the SKU data will be imported.

To import SKU data to the catalog:

1. Follow steps 1 to 4 as mentioned here.

   By default, the User Defined Import Template is selected. To select a user defined template, you first need to create the template. Refer section Creating a New Template for more details.

2. Select the Template from the drop-down list. All templates created for the catalog will be displayed as shown in the following figure.

Figure 291: Select template

The Import File Type will be auto populated based on the selections made while creating the template as shown below:

Figure 292: Upload file based on template selected

3. Select the file source: Local Machine or External Location.

   1. Local Machine: If you choose this option, you can upload the SKU data file. Click Upload File to select and upload the file.

Once the file is uploaded, if you want to replace the uploaded file, click the Delete icon to upload a new one.

b. External Location: If you choose this option, select a file from the FTP or SFTP setup, as shown in the screenshot below.

4. Click on Configure File Name Pattern for Import File, a hyperlink appears when selecting FTP/SFTP as shown in the image:

A pop-up shows up where you need to enter a common pattern for identifying import files by using the variable. Click the arrow next to the variable to select it while creating the pattern. Refer to the screenshot below for a pattern example.

5. Click Done to apply the pattern.

This setup ensures that only correctly formatted files are recognized and imported automatically from the FTP/SFTP source.

6. Select one of the following options from SKU Addition Preference dropdown based on your import requirement:

   • Add New & Update existing SKUs

   • Add new SKUs, no updating existing SKUs

   • Update existing SKUs only, do not add new SKUs.

7. Under Match SKUs in input file with catalog SKU using -> select the option from either SKU Item Id or Custom list of attributes.

8. Click on the Default Taxonomy Node link if you want to select the default taxonomy path from the catalog, incase if the import file has new SKUs with no taxonomy.

9. On the Select Taxonomy Node, select the node and click Select.

10. Scheduled Imports -> You can set up scheduled imports to run automatically based on a configured schedule. Click Add Schedule to configure.

Note: This option is not visible if you choose External Location as the option under Select Files From field.

11. Select the Frequency from the dropdown, Date and Time.

12. Click Add Import and the import file is uploaded.

You can track the status of the uploaded file on the Imports page. However, the process is not complete yet as you need to process the import file. Refer Processing the Uploaded Files and Viewing its Status section to complete the import process.

Once the import process is completed successfully, the SKU ID and the attribute values are added to the selected catalog as shown below.

As shown in the figure above, the SKU IDs with their respective attribute values are added after successful completion of the import process.

Creating a New User Defined Template

To import a SKU data to a catalog (with nodes and attributes already created), it is important to create a template. Since we will only be importing SKU data, it is important to configure the other parameters in the template, that is, taxonomy nodes, attributes and so on depending on the file shared. As stated earlier, you can create a template for horizontal/vertical delimited or excel files only.

Let us consider the same file mentioned in Figure 290: Horizontal file. This is a horizontal delimited file and lists the SKU ID, taxonomy path and attribute with SKU attribute values.

There are three steps in creating an import template namely; creating a template name, configuring the template and previewing and saving the same.

To create a new template:

1. Click Import > Catalog Import Templates and the following screen appears.

Figure 293: Import template screen

2. Click Create New Catalog Import Template and the following screen appears.

Figure 294: Create new template

3. Enter the relevant details as shown below:

Table 32: Template name fields description

3. Click Next and the following screen appears. Since the File Type selected is Horizontal Delimited, the following fields are displayed as shown below.

Figure 295: Template options

4. Enter the relevant details as shown below. Let us assume the same horizontal file for which we need to create the template and enter the values accordingly.

Once a field is added, the Add Field button is enabled. Click to add more fields.

5. Click the Remove Field icon next to the field in case you need to remove any of the fields added.

   You can also preview the template being configured with a sample file. However, since this is a sample file, data will not be imported.

   The following figure displays the values configured for the template based on the sample horizontal file to be imported.

6. Click Preview with a Sample File and the following screen appears.

Figure 296: Template preview screen

This screen allows you to view a sample file with the configured template settings.

7. Click Browse and select the sample file to be uploaded.

8. Click Upload and the sample file is displayed based on the template configured. A preview window is displayed as shown below.

Figure 297: Preview result

9. Click Remove File to remove the uploaded sample file in case you need to try other sample files.

10. Click Save Template and the import template is added successfully. You can edit, delete, and save the template by clicking on various icons under Actions column. You can view the details of the template added in the Import Templates page as shown below.

Figure 298: Import template details

Deleting Attributes with Empty Values

As mentioned, while creating a template, this toggle field determines how the import behaves for an empty attribute value in the file being imported. There are two scenarios:

• If the toggle is off - In this case, the empty value for the attribute in the file is ignored and the current value in the catalog is not modified.

• If the toggle is turned on – In this case, the empty value for the attribute in the file replaces the current value in the catalog, that is, the current value is deleted and replaced with empty value.

Let us look at an example for more clarity. For example, the following figure displays a node with SKU attribute values before we perform the import function.

Following is the file that is to be imported in which the SKU attribute value for SKU ID 04853960 for attribute Material is empty.

Case 1 – if the toggle is turned off, the current value in the catalog is not modified, that is, the value Rubber is not deleted as shown below.

Case 2 – if the toggle is turned on, the current value in the catalog is deleted, that is, the value Rubber is deleted and since the file has no value, it is replaced with empty value as shown below.

Thus, depending on the requirement, you can set the toggle accordingly while creating a template.

DA Linkage to SKUs during Import using User Defined Template

While importing SKU data using a user defined template, you can also link the DAs to the SKUs. In order to link the DA to the SKU, the import file should include either the name of the asset (here, the DA with the exact name should also exist in the asset library) or a valid link to the asset.

Before importing the file with DAs using a user defined template, it is important to set the template with the DA information.

Let us consider a horizontal delimited file that lists the SKUs and the DAs to be linked as shown below.

While creating a new / editing an existing template, you need to add the relevant details based on the information present in the import file. In the above example, the file has the following fields:

• Item ID

• Taxonomy

• Material

• DA

Thus, in the template, you need to configure the fields in the same sequence as mentioned in Creating a New Template section.

Once the template is updated, you can import using this template.

The file includes 3 SKUs and there are 3 DAs to be linked. Following are the scenarios:

• DA name – The DA name is listed in the file and the asset with the same name exists in the asset library.  

Once the file is successfully uploaded using the user defined template, the asset gets linked to the SKU as shown below.

• A valid link to the asset – A link to the asset is provided and the asset has been uploaded to the asset library using the same URL. Thus, this asset also exists in the library but it was uploaded using the URL.

Once the file is successfully uploaded using the user defined template, the asset gets linked to the SKU as shown below.

• Asset that does not exist in the library – A valid link to the asset is provided in the file. However, this asset does not exist in the asset library and when the file is imported, the asset should be created in the library and linked to the SKU.

Once the file is successfully uploaded using the user defined template, assets are added to the library as well as linked to the SKU as shown below.

Reusing User Defined Template

Instead of recreating a template each time, you also have the option to reuse an already-created template.

To reuse a template:

1. Click the Save As Template   icon on the right-hand side of the template in the Import Templates page.

2. A pop-in window opens as shown below. Fill-in the 3 mandatory fields.

3. Template Name: Enter a Name for the new template.

4. Select the Catalog where you want to add the new template.

5. Select the File Type for the template from the drop-down list.

6. Click on the Submit button.

7. Now, you can find the new template in the Import Templates page as shown below.

Updating User Defined Template

Once the template is created, you can make any changes in the template configuration parameters. This is useful when multiple users are working on the same template and based on the SKU data being imported, the changes need to be updated in the template as well.

To update a template:

1. Click the Update Template   icon `next to the template in the Import Templates page. The Edit Import Template page is displayed as shown below.

Figure 299: Edit template

2. Edit the Template Name if needed. However, you cannot change the catalog and file type once the template is created.

3. Click Next and edit the template configuration parameters as needed.

   Follow the same steps to make further changes as mentioned in Creating a New Template section and save the changes.

   The template is updated with changes made.

Delete a User Defined Template

You can also delete a template created in case it is no longer relevant to be used for importing SKU data.

To delete a template:

1. Click the Delete Template   icon next to the template in the Import Templates page. The Delete Template page is displayed with details of the catalog from which it will be deleted.

2. Click Yes, I Confirm to delete the template successfully from the catalog.

Importing SKU Data to the Catalog using Hybrid Import Template

Before we proceed with the Hybrid Import, the Taxonomy structure and category should already be available in the catalog and when the user imports the file using Hybrid Template, the respective SKUs will get created under those categories. If there is no category found for any of the SKU(s), then those SKU(s) will not be imported.

You should also keep in mind that the Taxonomy, Assets, SKU Title, and Relationships should all be present either in the beginning or at the end of the horizontal/vertical attributes. Make sure that the file is modified accordingly before you proceed.

Let’s first explore how to create, edit, replicate or reuse, or delete a Hybrid Import Template while setting up a new import using Hybrid Import Template option.

Creating a Hybrid Import Template

Steps to create hybrid import template:

1. Once you launch the catalog, select Import, and then click on Import Templates from the drop-down menu on the left-hand corner.

The following window opens.

2. Now, you must select the Hybrid Import Templates tab.

3. Click on Create New Hybrid Import Template button found on the top right-hand side of the page as highlighted in the screenshot below:

4. The Create Hybrid Import Template window opens where you must give the following details:

5. Template Name-> Enter the Template name which is mandatory.

   NOTE | The Template Name should be unique for each of the Hybrid Templates of a catalog. If you enter a duplicate Template Name, PCC will prevent you from creating the template with the below message popping up.

6. File Type-> Select the File Type from the drop-down list. The file will be in either Delimited or Excel format.

7. Is Usable by Creator Only (Optional) -> If you want the template to be used only by the creator, toggle the corresponding button ON.

8. Once you have filled out the details, click Next on the bottom of the page.

9. Now, you’ll land on the Template Configuration tab as shown below:

On the left, the file type which you chose previously will be seen as shown below:

10. If you choose the Delimiter file type, you will be asked to enter the Field Delimiter.

11. Then, you must mandatorily enter the Header Row Number.

As per the sample file (as shown below), the Header Row Number is 1.

12. Now, we must enter the Multivalue Delimiter.

As per the sample file (as shown below), the Multivalue Delimiter is “,”.

13. You can use this option to delete attributes which have empty values. By default, it will be set as “No”. But, when you set as “Yes”, all the attributes which have no value during this import will be deleted.

NOTE | In case an attribute had a value previously but does not have a value during this import, the attribute will be deleted when you set it as “Yes”. So, use this option cautiously.

14. Now you must select whether the Excel file is denoted by alphabets or numbers.

In our sample file, they are referenced by alphabets.

1. Now, you must enter the Column Position for SKU Item ID.

In our sample file (as shown below), it is in Column A.

15. You must toggle YES if the file contains SKU Title. Since our sample file does not contain SKU Title, we will choose “No”.

NOTE |If you toggle YES, it is mandatory for you to enter the column containing the SKU Title.

16. Toggle ON if the file contains Taxonomy. Now, you can choose “For Taxonomy Node” or “For Taxonomy Path” depending on what is available on your template file.

In our sample template file, the Taxonomy Node is found between column C and column H (a total depth of 6) as shown below:

So, we will fill out the Taxonomy details as shown below:

In case the template file contains Taxonomy Path, we will have to fill in the Taxonomy Path Delimiter used and the Column Position for Taxonomy Path from the file. Below is a sample of how we ought to fill the same.

17. If your file contains Relationships, you must toggle YES and mention the Number of Relationships, the Column Position for Relationships and Relationship Sequence. You can choose either of these options from the drop-down list for Relationship Sequence:

18. If your file contains Digital Assets, you must toggle YES and mention the Number of Digital Assets, the Column Position for Digital Assets, the Digital Asset Field Sequence and the Field Position for Primary Digital Asset. Below is a screenshot of the drop-down list containing the various options available for Digital Asset Field Sequence.

In our sample file, the Number of Digital Assets is “32”, the Column Position for Digital Assets is from “I to AN”, the Digital Asset has only “Name” and the Field Position for Primary Digital Asset is “I”. So, we must fill out the details as shown below.

NOTE | Make sure that when the assets are pre-loaded as files, the asset name in the file should match up with the user uploaded file name that exists in PCC.

19. If your file contains Horizontal Attribute, you must toggle you must toggle YES and mention the Number of Attributes and the Column Position for Horizontal Attribute. In our sample file, the Number of Attributes is “78” and the Column Position is from “AO to DN”. So, we must fill out the details as shown below.

20. Now, if your file contains Vertical Attribute, you must toggle YES and mention the Number of Attributes, Column Position for Horizontal Attribute and choose the Attribute Set Sequence from the drop-down list. Below is a screenshot of the drop-down list containing the various options available for Attribute Set Sequence:

The ‘Attribute Set Sequence’ in our file is “Name, Value, UoM” as shown in the below sample:

In our sample file, the Number of Attributes is “50”, the Column Position is from “DO to JH” and the Attribute Set Sequence is “Name, Value, UoM”. So, we must fill out the details as shown below.

NOTE | UoM data must match uniquely either with a UoM Name or UoM Symbol which is already created for the customer in the Catalog.

21. Once you have filled in all the necessary fields, click on the Save Template button found at the bottom of the page.

22. The following message will pop-up confirming that the template has been created successfully.

23. You can find the newly created template among the list of templates under the Hybrid Import Templates tab on the Import Templates page.

Edit Hybrid Import Template

Steps to edit the hybrid import template:

1. If you want to edit the template, click on the   icon found on the right-hand side of the template.

2. On the next window, you will get the option to update the Template Name and the toggle ON/OFF the permission of the template to be used only by the creator. You will not be able to change the File Type.

   For example, let us rename the Template as “John Hybrid Test Template”. Once you have made any changes to this page, click Next.

3. Now, make the necessary changes to the template on the Template Configuration tab and click on Save Template.

4. The following message will pop-up confirming that the template has been successfully updated.

Since we have updated the Template name, the same is now reflected on the list of Templates (as shown below)

Delete Hybrid Import Template

Steps to delete Hybrid Import Template:

1. If you want to delete the template, click on the   icon found on the right-hand side of the template.

2. You will get the following message if you are sure of deleting the template. If you click on “Yes, I Confirm”, the template will get deleted.

Reusing Hybrid Import Template

Steps to reuse or replicate the existing hybrid import template:

1. If you want to make a copy of the template, click on the   icon found on the right-hand side of the template.

2. You must enter a new name for the template and select the File Type from the drop-down list.

3. Once you fill in the details, the Submit button will get activated. When you click on it, the new template will be created.

The newly created template will now be available in the list of Hybrid templates.

Import Files using Hybrid Import Template

Importing file using Hybrid Import Template option:

1. On the PCC homepage menu bar, click on Catalog Imports under Import.

2. On the Catalog Imports, click on the New Import button.

3. Now on the next page that opens, we must fill in the following details and upload the import file:

4. Enter the Import Name (It is mandatory to enter the import name)

5. Once you start typing the catalog name, PCC will start suggesting the available catalogs for you to select the catalog to which you want to do the import.

6. Select Hybrid Import Template option.

7. Select the template from the drop-down list and the Import File Type field will automatically get filled by the system.

8. Click on the Upload File    button and browse to the location to select the Import File and click on Open.

9. After you upload the file, if you want to remove the file, you can do so by clicking on the   icon found on the right-hand side of the uploaded file.

10. Once you have filled in all the details, click on the Add Import button found in the bottom of the page.

You will get the following message as the import gets added to PCC.

11. Now, you can follow the steps in 15.2 to process the imported file.

Connector

The Connector import option is designed for bringing product data from external systems such as Eclipse ERP or AD eCommerce directly into PCC catalogs. Connectors ensure data consistency by aligning imported attributes, SKUs, taxonomies, and digital assets with catalog standards already defined in PCC.

By automating imports and enabling scheduled synchronization, connectors reduce manual effort, maintain Data Integrity, and streamline catalog onboarding across different platforms.

How It Works:

Connectors enable PCC to integrate with external systems such as ERP platforms (e.g., Eclipse) or digital ecosystems (e.g., AD eCommerce). Once configured, a connector establishes a secure link between the systems and automates catalog synchronization. Depending on the connector, PCC can:

• Import product taxonomies, attributes, SKUs, and digital assets.

• Align imported data with PCC standards through Attribute Mapping.

• Run manual or scheduled jobs to ensure ongoing synchronization.

This reduces manual effort, accelerates onboarding, and ensures data consistency across platforms.

Let’s look into how to import data using Connector:

1. Follow steps from 1 to 4 as mentioned in PCC Supported File Formats.

2. Select Connector as the import option.

3. Select the connector from the dropdown. (Currently we only support Eclipse ERP or AD eCommerce).

   

4. Select the store from the dropdown.

   Here all the stores configured under the selected connector (Eclipse ERP or AD eCommerce) gets displayed.

5. Click on the Default Taxonomy Node link to select the default taxonomy path from the catalog. On the Select Taxonomy Node, select the node and click Select.

6. Scheduled Imports: You can set up scheduled imports to run automatically based on a configured schedule. Click +Add Schedule to configure and then select the Frequency, Date, and Time from the dropdown menu.

7. Data Filters-> Showcases the available data filters for the selected connectors:

• Update After: Choose when to update the data:

  • All SKUs- Updates all SKUs

  • SKUs modified since last store import- Updates only SKUs changed since the last import.

  • SKUs modified since date- Select a date to update only SKUs modified after that date.

• Branch Code: This represents the branch associated with a product. Specifically, in an ERP system, a product can be assigned to multiple branches, each storing additional product-related information. So by specifying the branch code, you could access more detailed Product Information.

Note: The Data Filters and Branch Code fields are exclusive to the Eclipse ERP connector.