Items let you easily manage product data and bundle products together. This article shows you how to use items in Fabric PIM.

An item is any good or service sold or sourced by a merchant. An item can be digital or physical and is defined, organized, enriched, managed, and published in PIM. Every item has a record in PIM differentiated by a unique identifier (usually a SKU) that serves as the primary attribute for any operations performed on the item.

Before creating an item, you must map four basic attributes in PIM Settings. These basic attributes are used by PIM to deliver a consistent and reliable experience across channels. They are frequently used by other systems as well, so proper mapping is essential to ensure other systems can read and use data from PIM. 

For example, PIM uses the term "SKU" to refer to a unique product identifier while some merchants use the terms "UPC" or "Part Number". Each of the basic attributes must be mapped to exactly one attribute from the list of attributes. There are certain limitations on what can be mapped to these basic attributes - 

Basic attributes include:


Mapping Name

Attribute Specifications

Mapping Specification

Why is this needed to be mapped?


  • Must be a Mandatory Attribute

  • Each SKU value must be unique

  • Required before creating an item in PIM

  • Mapping cannot be changed after item has been created

  • This attribute serves as the primary identifier for items to be created in PIM

Product Title

  • A Text/Number type attribute is recommended

  • Mapping cannot be changed after item has been created

  • This attribute helps PIM identify the display name of the product

Primary Product Image 

  • A text type attribute is recommended here 

  • Mapping cannot be changed after item has been created

  • This attribute helps PIM identify the main image of the product for thumbnail purposes


  • Must be a mandatory attribute

  • Must be a Boolean type attribute

  • Name the attribute to be "Active" which can be set to TRUE/FALSE

  • Mapping cannot be changed after item has been created

  • Required to maintain the status of item to Active/Disabled

  • Only items where status is set to Active=TRUE will be available for the commerce API to consume

Variant Attribute

  • A text type attribute is recommended here

  • Required if using Fabric Storefront and other Fabric products

  • Mapping cannot be changed after item has been created

  • This attribute helps Fabric applications identify the attributes that drive variants for items (for example - Color, Size)

  • If there are more than one such attributes, put their exact titles separated by comma in the attribute value field on Item Details Page


Notes about attribute mapped with Status:

  1. This attribute defines the status of item to be active and disabled
  2. It must be a mandatory attribute to be added to all items with type strictly as boolean.
  3. Only items where Active is set to be TRUE will be available for the storefront/commerce API to consume.
  4. Items where the attribute doesn't exist or has status as False/blank will not be available on storefront.

  1. Select Catalog from the left panel of PIM.
  2. Go to Items.
  3. Click +New item. A list of available Items will be displayed. At the top of the page, click Add SKUs.
  4. Select a subcategory from Primary Hierarchy. Selecting a subcategory of the primary hierarchy is required and only the last subcategory in the hierarchy can be selected. The primary hierarchy node must have at least one item attribute assigned for item creation to occur.
  5. Complete the form that appears, ensuring all Mandatory attributes are populated.
  6. Click Save.
Selecting a category from Primary Hierarchy


Create item


You can add variants for any item in PIM. When a variant is added to an Item, the item becomes the parent. New items that are added become children.

  1. Navigate to Items from the left panel.
  2. A list of items will appear with the following fields: Display image, SKU, Display name, Created on, and Status.
  3. Click the Parent item that you want to add children to.
  4. Click Add Children in the top right corner of the page.
  5. Define the parent-child relationship using the instructions below.
  1. Select Attributes to be inhereted from parent to child.
  2. Click Save.

Note: The SKU can not be inherited.

Inherit Parent Attributes
  1. Click Existing children SKUs in the side panel.
  2. Select child SKUs (only SKUs from the same category/subcategory are shown).
  3. Click Save.
Select existing child SKUs
  1. Click Create Children SKUs in the side panel.
  2. Define the number of variants. New columns will appear with attributes that were not inherited from the parent item. 
  3. Complete required attributes.
  4. Click Save.
Create child SKUs

  1. Navigate to Items from the left panel.
  2. Click the item you want to edit.
  3. Select the variant you want to edit from the list of children items on the right side of the page.
  4. Edit variant attributes.
    • You can only edit the non-inherited attributes for the variant items.
    • Fetch attribute values from parent items by clicking the copy icon.
  5. Click Save.

Edit attributes

  1. Navigate to Items from the left panel.
  2. Select the Item you want to delete.
  3. Indicate whether you want to delete Parent only or Parent and Children.
  4. Click Delete and Confirm.

Delete item

  1. Create attributes: All item attributes must exist in PIM prior to data import. This lets PIM read the data and store the attribute values for every item. These attributes can be created manually or using the bulk attribute import feature.
  2. Set up your primary hierarchy: Configure your primary hierarchy before importing items. Currently, you can only bulk import one primary hierarchy category at a time. You must define the category in the CSV import file.

Once attributes and hierarchies are set up, you can import CSV files to create items. A CSV template file is available here. You can also download a template specific to the category.

  1. Hierarchy Node: This represents the category of Primary Hierarchy where the item belongs and has to be provided to create an item. Any item without a node will not be created.
  2. SKU: It is recommended to provide a SKU for all items. If a SKU is not provided, PIM will generate a random eight-character SKU for the items.
  3. Parent SKU: This is only required for item variant SKUs. Leave this field blank if the item doesn't have a parent.
  1. Fabric PIM only accepts CSV files; no other data or file formats are accepted at this time.
  2. Hierarchy Node is mandatory. If the hierarchy node is missing, the item will not be created.
  3. Delimiter for the hierarchy nodes is “->”. If the primary hierarchy node is not mapped correctly or not found in the system, the item will not be created.
  4. Headers of the CSV file (first row) represent the attributes of the item. Attribute titles are not case sensitive, but we recommend you maintain case-consistency with the original attribute titles.
  5. Formulas in formula-driven attributes will be executed automatically after items have been imported.
  6. Empty rows and columns are ignored.
  7. Attribute data format must conform to attribute type requirements:
    • Text: text string
    • Number: only numbers are imported; other data is ignored
    • Boolean: TRUE or FALSE only; other values are ignored
    • Date: use the same format used during attribute creation
    • List of values: the value must be an exact match to one of the list values
  8. Rows with only the Hierarchy Node populated will be considered as an item and, for each row, an item will be created.
  9. The Status attribute will always be imported as FALSE.
  10. In case the CSV doesn't have an attribute that is added to the Primary Hierarchy, you can simply add a new column in the CSV and put the attribute name in header, upload will populate the value for this attribute.
  1. Go to the Item List page.
  2. Click Import Items.
  3. Select the appropriate hierarchy node.
  4. Select the file to upload (must adhere to the guidelines above).
  5. Click Upload.

Note: You can monitor the status of your upload in Import History.

List view with import button

The status of bulk imports is available on the Import History page.

  1. Go to the Item List page.
  2. Click Import History.
  3. All imports are listed with their status.
  4. Click a specific import to view additional details, including errors.

Note: You can export errored items, correct the errors, and re-upload the file using the process detailed above.

Import history


Bulk Import Error Messaging

Error Message

What it means?

What happens to the item?

How to resolve?


Hierarchy Node not found

Hierarchy Node name is incorrect or missing

Item can’t be created without a proper hierarhy node is given

Verify the name of the node and the delimiter. #2 and #3 here


Internal Server Error

Server issues

Item is not created/updated

Try again

This is an intermittent issue, might come randomly.

“Attribute Name” not found

The attribute mentioned in the CSV header is not added to the Hierarchy. Attribute Name must be an exact match.

Item is created but this specific attribute will be ignored

Check the name of the attribute, ensure that this attribute is added to the primary hierarchy you are trying to import items for.


“Attribute Name” value is invalid

The value provided has some flaws/valiation issues

The attribute value will not be saved to the item.

Provide correct attribute value.

Example - if you add a text for a number type attribute, you will receive this error.

Active Mandatory attributes required

In order to set Active = TRUE for an item, all mandatory attributes are required

Item will be created and attributes will be updated. Item can’t be set to Active=TRUE so this attribute will be ignored. Item Status will remain Active = FALSE

Ensure that all mandatory attributes have a value in the CSV you are trying to import

When doing a delta import, it is required to have all mandatory attribute and values added for the existing items for the “Active” attribute

Some mandatory attribute values are missing

There are some mandatory attributes for the hierarchy/items that need values. These could be global mandatory (set at the attribute level) or hierarchy mandatory (Set at the individual hierarchy level)

Item is created with errors. Only given attribute values will be added

Include values for all the mandatory attributes

Items can always be created with errors, but they can’t be published unless all mandatory attributes have a value.



Last update: Oct 18, 2021

Have any questions?
Let's Talk.