A detailed description about the horizontal as well as vertical delimited and excel files used to import SKU data using user defined template as well as standard vertical files used to import catalog structure is provided in the following sub-sections.
Horizontal Files and its Format For Import Template
To import a SKU data in a horizontal file, you need to ensure that:
The entire SKU information is sent in one single line of data, that is, each row of data in the input file fully represents a SKU.
There can be any number of fields (or columns) in the data file.
The definition of column is configured in the import template created (which is explained in section Creating a New User Defined Template) and maintained in the PCC portal. This allows the user to fully describe the structure and content of the horizontal format.
There are two types of file format for a horizontal file:
Flat ascii file with fields delimited by a single character, that is, referred as Horizontal Delimited
Microsoft Excel, that is, referred as Horizontal Excel
The following table lists the various fields that can be configured in the import template.
Sr. No. | Field Type | Required | Explanation |
1 | Sku Item Id | Yes | The unique identifier of a SKU. |
2 | SkuTitle | No | The free text title of the SKU. Optional for the SKU. No SKU Title will simply be ignored, that is, existing SKU Title will not be erased. |
3 | TaxonomyPath | No | The entire taxonomy path breadcrumb starting from the root node up to the node where this SKU resides. Presence of valid taxonomy path in the catalog’s primary hierarchy value will relocate the SKU to this node if it already exists in a different taxonomy node. |
4 | TaxonomyNode | No | The node name where this SKU resides. If Taxonomy Path is present for this SKU in this file, this value will be ignored. The node name must resolve to a uniquely identifiable category in the catalog, or else this SKU will not be loaded as whole. Presence of valid taxonomy node value in the catalog’s primary hierarchy will relocate the SKU to this node if it already exists in a different taxonomy node. |
5 | Attribute | No | The name of the attribute and its value and UoM (should be present in the next column). Attributes should be available in the attribute master or else the user will need to create it before uploading the file. |
6 | Unit of Measure | No | When ‘Attribute’ is added in the earlier column, this denotes the unit of measure associated with the attribute value for the SKU in this row of data. The data in this field must uniquely match either a UoM Name or UoM Symbol which is already created for the customer using the PCC portal. |
7 | AttributeWithUoM | No | The name of the attribute should be present in field #3. Its value and UoM (if applicable) should be present in field #4 separated by a space. The UoM will be parsed as all non-white space characters to the right of the last space found in field #4. Field #5 will be ignored. |
8 | DigitalAsset | The digital asset information for the SKU. This needs to be a valid URL or a valid Digital Asset Name. If it is a Digital Asset Name then it should exist in the library. There can be multiple assets for a SKU. Field #4 will carry a valid URL/DA Name if Field#2 is DigitalAsset. | |
9 | SKIP | No | Any value entered for the column having this value will be skipped. |
This choice is applicable when the column is ‘Attribute’ or ‘AttributeWithUoM’. Absence of data in this field means No (i.e. default). No implies that the data found for the attribute of the uploaded file will be appended to any existing value of this attribute for this SKU. This may result in the SKU-Attribute having multiple values. Yes, implies that the data for the attribute will overwrite any existing value(s) of this attribute for this SKU.
A sample horizontal excel file is as shown below.
Result of importing the example data above
A taxonomy node Accessories>Bags existing in the catalog will have 3 SKUs linked to the node Bags with the values as follows:
Item Id 1061475077 with attribute values of Application/Usage having multiple values as Accessories; Key; Tablet, Assembly Required being Yes and a digital asset linked to the SKU
Item Id 1061475076 with attribute values of Application/Usage having multiple values as Accessories; Key; Tablet, Assembly Required being No and a digital asset linked to the SKU
Item Id 1035840960 with attribute values of Application/Usage having value as Multipurpose, Assembly Required being Yes and a digital asset linked to the SKU
Following is a sample horizontal CSV file.
The horizontal CSV and excel files are similar except for the file types. Thus, you need to select the appropriate file type while uploading a file during the import process.
Vertical Files and its Format for Import Template
To import a SKU data in a vertical file, you need to ensure that:
The data pertaining to each SKU is sent in multiple lines (aka, rows or records).
The data in a Vertical file is tabular in nature, with a fixed set of six fields (aka, columns) defined as shown below.
The field position must be in the same order as shown in the following table.
There are two types of file format for a vertical file:
Flat ascii file with fields delimited by a single character, that is, referred as Vertical Delimited
Microsoft Excel, that is, referred as Vertical Excel
The following table lists the various fields required in the vertical file:
Sr. No. | Field Type | Required | Valid Values | Explanation |
1 | Sku Item Id | Yes | The unique identifier of a SKU. | |
2 | Data Entity Type | Yes | Specifies what kind of data exists in Field #4 in this row of data. | |
SkuTitle | The free text title of the SKU. Optional for the SKU. No SKU Title will simply be ignored, i.e. existing SKU Title will not be erased | |||
TaxonomyPath | The entire taxonomy path breadcrumb starting from the root node up to the node where this SKU resides. Presence of valid taxonomy path in the catalog’s primary hierarchy value will relocate the SKU to this node if it already exists in a different taxonomy node. | |||
TaxonomyNode | The node name where this SKU resides. If Taxonomy Path is present for this SKU in this file, this value will be ignored. The node name must resolve to a uniquely identifiable category in the catalog, or else this SKU will not be loaded as whole. Presence of valid taxonomy node value in the catalog’s primary hierarchy will relocate the SKU to this node if it already exists in a different taxonomy node. | |||
Attribute | The name of the attribute and its value and UoM (if applicable) should be present in field #s 3, 4 and 5 respectively. | |||
AttributeWithUoM | The name of the attribute should be present in field #3. Its value and UoM (if applicable) should be present in field #4 separated by a space. The UoM will be parsed as all non-white space characters to the right of the last space found in field #4. Field #5 will be ignored. | |||
DigitalAsset | The digital asset information for the SKU. This needs to be a valid URL or a valid Digital Asset Name. If it is a Digital Asset Name then it should exist in the library. There can be multiple assets for a SKU. Field #4 will carry a valid URL/DA Name if Field#2 is DigitalAsset. | |||
3 | Data Entity Information | No | Attribute Name | This field needs to be populated only when Field #2 is ‘Attribute’ or ‘AttributeWithUoM’. The data in this field contains the attribute name. For a successful load of this row of data, the attribute name must match (case sensitive) an attribute which already exists in the catalog for this import template. Data in this field is ignored for rows where Field #2 is not equal to ‘Attribute’. |
4 | Data Entity Value | Yes | The actual value of the entity defined in Field #2 in this row of data. | |
5 | Unit of Measure | No | When Field #2 = ‘Attribute’, this denotes the unit of measure associated with the attribute value for the SKU in this row of data. The data in this field must match uniquely match with either a UoM Name or UoM Symbol which is already created for the customer using the PCC portal. | |
6 | Overwrite Choice | No | Yes or Y No or N | This choice is applicable when Field #2 is ‘Attribute’ or ‘AttributeWithUoM’. Absence of data in this field means No (i.e. default). Yes implies that the data found in Field #4 (and #5) will overwrite any existing value(s) of this attribute for this Sku. No implies that the data found in Field #4 (and #5) will be appended to any existing value of this attribute for this Sku. This may result in the SKU-Attribute having multiple values. |
Example Data for Vertical File
Following is a sample of how data will be sent in case of a vertical file. Here, as mentioned, information for a single SKU will be sent in multiple rows as compared to a horizontal file where all data for a single SKU is present in one row itself.
NOTE | The first row of data is just for information purposes only to relate back to the definition mentioned in the above table. |
A sample vertical delimited file for importing data using user defined template is as shown below.
Result of importing the example data above
The SKU identified by the Item Id SKU-1234 will be stored in the PCC catalog with a Sku Title of A special product, residing in the taxonomy node traversed as X>Y>Z, with attribute values of Color being Blue, Length being 15 inch, Weight being 10 lbs, and Material having multiple values Wood and Plastic. Both the digital assets will be linked to the SKU.
Horizontal Files and its Format
The horizontal file format is a flat, denormalized list of SKUs, followed by the taxonomy path, SKU type (whether it is a SKU or a PF) and all possible attributes as columns (fields) to the right. The horizontal file can either be in excel or a delimited flat file (user can define the delimiter character). The file contains a header row. Each row after the header row represents the full information about a specific SKU. The presence or absence of column values in each row is used to determine if the corresponding attribute is relevant to the SKU. Any one column is the full taxonomy path where the SKU resides.
All other columns contain attribute values (UoM concatenated if exists) with the attribute name being the column heading..
Following is a sample horizontal excel file.
Following is a sample horizontal CSV file.
The horizontal CSV and excel files are similar except for the file types. Thus, you need to select the appropriate file type while uploading a file during the import process.
Standard Vertical Files
Standard vertical files cannot be imported as a single file. Each catalog entity (taxonomy, attribute, schema, and SKU) has a separate file in CSV (comma separated) format which contains either the master data for certain data entities such as taxonomy and attributes, or relationship between two entities such as schema that needs to be imported.
NOTE | For a successful import using vertical files, it is mandatory to import taxonomy and attribute CSV files. The other files can be imported depending on the entity being added to the catalog. |
While importing vertical files, you need to enter the following details:
Field Delimiter - The vertical files are single entity related files. However, it can have multiple fields which are separated by tab / comma or any other delimiter. Hence, you can enter the Field Delimiter value as tab / comma and so on based on what is used in the file.
Quote Character / Field Enclosure – Type the value as “only if the data in your file is enclosed in quotes else leave it blank.
First Row of Data – This is the row number where the header data begins, that is, the first row of headers. So, the value will be 1.
A detailed description of the various vertical CSV files supported are as follows:
Taxonomy - A vertical list of all the leaf nodes of the taxonomy hierarchy. This will create the taxonomy structure and is the master data for the entity taxonomy.
It is not necessary for the listing to contain all the individual non-leaf nodes. The import process will deduce the hierarchy automatically. However, the listing must contain the full path of all the leaf nodes.
The file also contains taxonomy meta attributes and meta tags information. This is optionally used to send more information about the taxonomy nodes. This meta data essentially provides additional information about the nodes.
Field Name | Required? | Valid Values | PCC | DataBridge | |
|---|---|---|---|---|---|
Description | Comments | ||||
1 | TaxonomyPath | Yes | N/A | ||
The full path from topmost level to the leaf node. | Must match TaxonomyPath from Schema, Sku-Taxonomy and List of values file. | ||||
2 | SourceTaxonomyId | No | N/A | Not supported for vertical file format in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | |
A customer specified unique ID to locate the node listed in the TaxonomyPath field for customers in their internal system. | |||||
3 | Description | No | N/A | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | |
A brief description of the nodes. | |||||
5 | MetaAttributes | No | N/A | ||
A user defined name of a meta attribute with a value that describes additional properties of the node. Name and value delimited by two colons (: :). Each pair delimited by two pipes (||). Ex.: Product Type::Types of analog and digital watches||Product Description::This includes both analog and digital type of watches | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||
6 | Metatags | No | N/A | ||
A single string of characters. Multiple metatags associated to the same node is delimited by two pipes (||). Ex.: MetaTag1||tag 1.1 | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||
7 | Action | No | Add Delete | ||
If left blank, it will be defaulted to Add. If action equals Delete, the taxonomy node and all its children are deleted. If the taxonomy file has Delete for a breadcrumb, but the SKU taxonomy file has SKUs in that node, the import will fail. | This is relevant for PCC and DataBridge. | ||||
NOTE | The column headers are case sensitive and must match the Field Name as shown above. |
The following figure is a sample of a taxonomy file.
NOTE | In case of multiple metatags or meta attributes associated to a node, each metatag or meta attribute is separated by ||. |
Attribute - This will create all the attributes that can be associated to any SKU as well as schema. This is the master data for the entity attribute. The file also contains attribute meta tags information. This is optionally used to send more information about the attributes. This meta data is essentially other characteristics or properties of the attributes that describe the SKU Attribute.
Field Name | Required? | Valid Values | PCC | DataBridge | |||
|---|---|---|---|---|---|---|---|
Description | Comments | ||||||
1 | Attribute Name | Yes | N/A | ||||
The name of the attribute. | |||||||
2 | Source Attribute Id | No | N/A | Not supported for vertical file format in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | |||
A customer specified unique ID which acts as an identifier to locate the attribute for customers in their internal system. | |||||||
3 | Attribute Type | Yes | GLOBAL PRODUCT Sku | GLOBAL: an attribute with type ‘global’ is automatically part of all schemas, that is, it is linked to all taxonomy nodes. PRODUCT or Sku: : an attribute with type ‘Product / Sku is not part of all schemas and is not linked to all taxonomy nodes. | GLOBAL: this attribute is eligible for “global mapping”, and that global map will be propagated/inherited to all node maps where this attribute exists. PRODUCT or Sku: this attribute is not eligible for “global mapping”. Product and Sku mean the same. | ||
4 | Attribute Group Name | No | N/A | ||||
The name of the attribute group. If the attribute group is not present in the catalog, it will be created and the attributes specified in the file for the group will be associated with it. | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
5 | Description | No | N/A | ||||
A brief description of the attributes. | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
6 | Meta Attributes | No | N/A | ||||
A user defined name of a meta attribute with a value that describes additional properties of an attribute. Name and value delimited by two colons (: :). Each pair delimited by two pipes (||). Ex.: Meta_Attribute_1::Color of the Dial||tagAtt1::Grey | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
7 | Metatags | No | N/A | ||||
Following is a list of predefined meta tags: Product Description Product Long Description Product Short Description Brand Name Manufacturer Name Manufacture Part Number UPC Marketing Copy Marketing Bullet Price In addition to the above mentioned tags, customized tags can also be added. Multiple metatags associated to the same attribute is delimited by two pipes (||). Ex.: MetaTag1||tag 1.1 | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
8 | Action | No | Add Delete | ||||
If left blank, it is defaulted as Add. The action Delete in the Attribute file will delete the attribute from the whole catalog affecting all SKU and schema. If you want to delete a specific attribute value for a SKU, do not send the value(as SKU attribute import works like a replace) and for the schema file, send the Action flag as ‘Delete’, if the attribute does not have to be deleted for the whole catalog. | This is relevant for PCC and DataBridge. | ||||||
NOTE | The column headers are case sensitive and must match the Field Name as shown above. |
The following figure is a sample of an attribute file.
Attribute Metadata - The Attribute Meta Data file is optionally used to send more information about the attributes which are part of the Attribute file above. This file is essential for Type A and Type C MIL Matching. This meta data is essentially other characteristics or properties of the attributes that describe the SKU Attribute.
Although any type of metadata can be consumed by DataBridge, the only meta-attribute that is recognized and used by DataBridge is “Denotation”.
NOTE | This is applicable for DataBridge only. |
Field Name | Required? | Valid Values | Description | |
|---|---|---|---|---|
1 | Attribute Name | Yes | Must match Attribute Name from Attribute file | The name of the attribute. |
2 | Meta Attribute Name | Yes | Denotation | Any value will be accepted in the import, but Denotation only will be used for MIL Matching in downstream processes. |
3 | Meta Attribute Value | Yes | See description | The valid values are: UPC MANUFACTURER_INFO MANUFACTURER_NAME MANUFACTURER_PART_NUMBER DISTRIBUTOR_INFO DISTRIBUTOR_PART_NUMBER DISTRIBUTOR_NAME TARGET_COMPANY_SKU_ID |
NOTE | The column headers are case sensitive and must match the Field Name as shown above. |
The following figure is a sample of an attribute metadata file.
Schema - The schema files define what attributes are relevant to each taxonomy node. This will create the relationship between taxonomy hierarchy and attributes.
NOTE | To upload a schema file, it is mandatory to upload taxonomy and attribute files successfully. The schema file is required for uploading schema related information in both PCC and DataBridge. |
Field Name | Required? | Valid Values | PCC | DataBridge | |||
|---|---|---|---|---|---|---|---|
Description | Comments | ||||||
1 | TaxonomyPath | Yes | Must match TaxonomyPath from Taxonomy file | ||||
The full path from topmost level to the leaf node. | |||||||
2 | Attribute | Yes | Must match Attribute Name from Attribute file | ||||
The name of the attribute. | |||||||
3 | Attribute Type | No | GLOBAL PRODUCT Sku | ||||
This is the same field from the “Attribute” file. This field can be left blank. The import will inherit the type from the Attribute file. | |||||||
4 | In Schema | No | 0 1 | ||||
Default is 1. Either 0 or 1 can be specified. Either of these values will have no impact on system behavior. | |||||||
5 | Data Type | Yes | String Datetime Numeric Integer Text Number Boolean Date | ||||
This defines the datatype of the attribute. If not found, default is String. The top 4 values are native data types. The bottom 4 values are alias data types which map to the native types: Text → String Number → Numeric Boolean → String Date→ Datetime The import will accept any value for the Data type; that is, the import will not fail if the value is not one of the 8 listed values. However, schema constraints cannot be enforced/checked unless the data type is valid. | |||||||
6 | Navigation Order | No | |||||
Default is 1. The value can be any integer value. | |||||||
7 | Display Order | No | |||||
Default is 1. The value can be any integer value. | |||||||
8 | Description | No | N/A | ||||
A brief description for the attribute listed in the Attribute Name column. | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
9 | Meta Attributes | No | N/A | ||||
A user defined name of a meta attribute with a value that describes additional properties of a schema attribute. Name and value delimited by two colons (: :). Each pair delimited by two pipes (||). Ex.: Meta_Attribute_1::Color of the Dial||tagAtt1::Grey. | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
10 | Metatags | No | N/A | ||||
The meta tag defined for the schema attribute. Multiple metatags associated to the same schema attribute is delimited by two pipes (||). Ex.: MetaTag1||tag 1.1 | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
11 | Source Attribute Id | No | |||||
The unique ID assigned to the attribute listed in the Attribute Name field. | Not supported for vertical file format in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
12 | Source Taxonomy Id | No | N/A | ||||
The unique ID assigned to the node listed in the TaxonomyPath field. | Not supported for vertical file format in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
13 | Action | No | Add Delete | ||||
If left blank, it will be defaulted to Add. If the Action flag equals Delete, the schema attribute of a node will be deleted. Note: If an attribute is a global attribute in PCC, then marking it as delete in schema will not delete the attribute. The attribute type needs to be changed to Product first and in the next import, it should be marked delete in the schema. | This is relevant for PCC and DataBridge. | ||||||
These fields will have values only if schema constraints are set | |||||||
14 | Multivalue | No | 0, 1 | ||||
Default is 0 (i.e. single value). | |||||||
15 | Required | No | 0, 1 | ||||
Default is 0 (i.e. not required). | |||||||
16 | Min Value | No | Any numeric value | ||||
If Data Type is not Numeric or Integer, Min Value is ignored. | |||||||
17 | Max Value | No | Any numeric value | ||||
If Data Type is not Numeric or Integer, Max Value is ignored. | |||||||
18 | Min Length | No | Any numeric value | ||||
If Data Type is not String, Min Length is ignored. | |||||||
19 | Max Length | No | Any numeric value | ||||
If Data Type is not String, Max Length is ignored. | |||||||
20 | Stringent LOV | No | 0, 1 | ||||
Default is 0 (i.e. not validated against LOV). | |||||||
21 | Enforce UOM | No | 0, 1 | ||||
Default is 0 (do not enforce). | |||||||
22 | Pattern | No | Any regular expression pattern | ||||
If Data Type is not String, Pattern is ignored. | |||||||
23 | Enforce Numeric | No | 0,1 | ||||
Default is 0 (do not enforce). | |||||||
NOTE | The column headers are case sensitive and must match the Field Name as mentioned in the table above. |
The following figure is a sample of a schema file.
1 file split into 2 parts
Schema LoV - This file imposes the constraint on what valid values an attribute can have within a schema. This will create the list of values (aka valid values) against the schema attributes.
NOTE | To upload a schema LoV file, it is mandatory to upload taxonomy, attribute and schema files successfully. The schema LoV file is required for uploading schema LoV related information in both PCC and DataBridge. |
Field Name | Required? | Valid Values | PCC | DataBridge | |||
|---|---|---|---|---|---|---|---|
Description | Comments | ||||||
1 | TaxonomyPath | Yes | Must match TaxonomyPath from Taxonomy file | ||||
The full path from topmost level to the leaf node. | |||||||
2 | SourceTaxonomyId | No | N/A | ||||
The unique ID assigned to the node listed in the TaxonomyPath field. | Not supported for vertical file format in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
3 | AttributeName | Yes | Must match Attribute Name from Attribute file | ||||
The name of the attribute. | |||||||
4 | SourceAttributeId | No | N/A | ||||
The unique ID assigned to the attribute listed in the AttributeName field. | Not supported for vertical file format in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
5 | LovEntry | Yes | N/A | ||||
The valid value. Each valid value per taxonomy-attribute should be in a new row in the file. | |||||||
6 | UoM | No | |||||
The valid UoM. Each valid UoM per taxonomy-attribute should be in a new row in the file. | Not supported for vertical file format in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
NOTE | The column headers are case sensitive and must match the Field Name as mentioned in the table above. |
The following figure is a sample of a schema LoV file.
SKU-Taxonomy - This file defines where the SKUs reside in the product hierarchy. This will create the SKUs under the respective taxonomy.
NOTE | To upload a SKU-Taxonomy file, it is mandatory to upload the taxonomy file successfully. |
The SKU master data is derived from this file.
Field Name | Required? | Valid Values | PCC | DataBridge | |||
|---|---|---|---|---|---|---|---|
Description | Comments | ||||||
1 | TaxonomyPath | Yes | N/A | ||||
The full path from topmost level to the leaf node. The path can be of a cross listed SKU or actual SKU. | Must match Taxonomy Path from Taxonomy file | ||||||
2 | ItemID | Yes | N/A | ||||
The unique identifier for the SKU. | |||||||
3 | ParentItemID | No | N/A | ||||
The unique identifier for the parent PF which has SKUs / child PFs associated with it. | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
4 | SkuTitle | No | N/A | ||||
The title for the SKU. | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
5 | SkuType | No | SKU ProductFamily | ||||
SKU – the value will be SKU for a SKU ItemID ProductFamily – the value will be ProductFamily for a PF ItemID | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
6 | SourceTaxonomyId | No | N/A | ||||
The unique ID assigned to the node listed in the TaxonomyPath field. | Not supported for vertical file format in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
7 | TaxonomyType | No | R C | ||||
The value will be R (for Resident Taxonomy) or C (for Crosslist taxonomy) based on the path mentioned in the TaxonomyPath field. If the path mentioned is for a cross listed SKU, the value will be C else it will be R. | Not used in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. | ||||||
8 | Action | No | Add Delete | ||||
If left blank, it is defaulted as Add. If Action equals Delete in a SKU taxonomy file, the SKU will be deleted from the taxonomy. Ensure that the SKU is not sent in the SKU attribute file as well. | This is relevant for PCC and DataBridge. | ||||||
NOTE | The column headers are case sensitive and must match the Field Name as mentioned in the table above. |
The following figure is a sample of a SKU-Taxonomy file.
SKU-Attribute - This file defines all the attributes and their values for all the SKUs. This will populate the values of the attributes for each SKU.
NOTE | To upload a SKU-Attribute file, it is mandatory to upload the SKU-Taxonomy and Attribute file successfully. This file is required for uploading SKU attribute related information in both PCC and DataBridge. |
Field Name | Required? | Valid Values | Description | |
|---|---|---|---|---|
1 | ItemID | Yes | Must match ItemID from SKU-Taxonomy file | The unique identifier for the SKU |
2 | AttributeName | Yes | Must match Attribute Name from Attribute file | The name of the attribute. |
3 | AttributeValue | Yes | N/A | The actual value of the attribute. |
4 | UoM | No | The unit of measure applicable for the attribute value. | |
5 | SourceAttributeId | No | N/A | The unique ID assigned to the attribute listed in the AttributeName field. Not supported for vertical file format in DataBridge. In case of synchronization with DataBridge, these will be ignored while importing in DataBridge. |
NOTE | The column headers are case sensitive and must match the Field Name as mentioned in the table above. |
The following figure is a sample of a SKU-Attribute file.
SKU File Resources - This file contains information about all the digital assets associated with the SKU only.
NOTE | To upload a SKU FileResources file, it is mandatory to upload the SKU-Taxonomy file successfully. This file is required for uploading SKU asset related information in both PCC and DataBridge. |
Field Name | Required? | Valid Values | Description | |
|---|---|---|---|---|
1 | ItemID | Yes | Must match ItemID from SKU-Taxonomy file | The unique identifier for the SKU. |
2 | AssetName | Yes | N/A | The name/explanation of the asset, such as Product Manual, Front Picture, etc. |
3 | AssetType | Yes | N/A | The type of file. For example, jpeg pictures, PDF documents, etc. This is a free form text field, with no validation during import. |
4 | AssetLink | Yes | N/A | The proper publicly accessible internet hyperlink to the location of the digital asset. |
5 | Properties | No | N/A | Array of name-value pairs of other properties for the digital asset. Name and value delimited by two colons (: :). Each pair delimited by two pipes (||). Ex.: Resolution::900x600||Author::James Bond||Quality::Good|| |
NOTE | The column headers are case sensitive and must match the Field Name as mentioned in the table above. |
The following figure is a sample of a SKU-Fileresource file.
File Resources - This file contains information about all the digital assets associated with entities such as attribute, SKU and taxonomy. This should be used when assets are associated with other entities such as attributes, taxonomy and so on. If assets linked to only SKUs need to be added, the SKU File Resources file should be uploaded as explained in the above step.
NOTE | Depending on the assets associated with entities, the relevant files should be uploaded. For example, if assets are linked to attributes and SKUs, it is mandatory to upload the Attribute and SKU-Taxonomy files to upload a FileResources file successfully. |
Field Name | Required? | Valid Values | Description | |
|---|---|---|---|---|
1 | EntityKey | Yes | Must match:
| SKU - The unique identifier for the SKU. Attribute – The name of the attribute. Taxonomy - The full path from topmost level to the leaf node. |
2 | EntityType | Yes | Attribute Taxonomy Sku | Attribute – The type will be attribute if the EntityKey is an attribute name. Taxonomy – The type will be taxonomy if the EntityKey is the taxonomy path. Sku – The type will be Sku if the EntityKey is the ItemID of the SKU. |
3 | SourceId | No | N/A | If the Entitytype is Attribute, the source ID will be the Id assigned to the attribute. If the Entitytype is Taxonomy, the source ID will be the Id assigned to the node. If the Entitytype is SKU, this will be blank. |
4 | AssetName | Yes | N/A | The name/explanation of the asset, such as Product Manual, Front Picture, etc. |
5 | AssetType | Yes | N/A | The type of file. For example, jpeg pictures, PDF documents, etc. This is a free form text field, with no validation during import. |
6 | AssetLink | Yes | N/A | The proper publicly accessible internet hyperlink to the location of the digital asset. |
7 | Metatags | No | N/A | This column will show all the Meta Tags associated with the asset. In case there are multiple metatags, they will be separated by “||” as shown here: Watch || Black Watch || Watch for Kids |
8 | Properties | No | N/A | Array of name-value pairs of other properties for the digital asset. Name and value delimited by two colons (: :). Each pair delimited by two pipes (||). Ex.: Resolution::900x600||Author::James Bond||Quality::Good|| |
NOTE | The column headers are case sensitive and must match the Field Name as mentioned in the table above. |
The following figure is a sample of a File resource file in PCC.
In case of DataBridge, you can get the export in a File Resource file which will give the details of digital assets attached to SKU(s). Here is a sample of the SKU File Resource for DataBridge:
BIF (DataBridge Interchange Format)
BIF which is “DataBridge Interchange Format” can be used to export asset information for all or specific entities.
The following figure is a sample of a BIF file:
