For high-quality product data, it's essential to properly configure the main entities within the system before beginning its use. The term “entity” is used for modules or tables of structured data that are stored in the system with a specific purpose. So, the categories, channels, associations, catalogs, etc. count as entities. The entities can be linked to one another, for example, a product can belong to several categories at the same time.
The user does not necessarily have to use all available entities. If he does not need some entities, these can simply be deactivated, and vice versa, if further entities are required, these can also be created and linked to existing entities.
In this article, we assume the requirements of an average user who needs all entities. We will outline the necessary configurations for optimal system functionality. Below, we'll explain which entities should be configured to ensure comprehensive and effective system operation.
A product attribute determines a certain property of a product. Thanks to the typing of the attributes, their values are also typed. The product attributes are not only used to describe the product in full, but also for the filters to help the end customer find the required product more quickly. This is precisely why the product description with the attributes is very important. Typical attributes for clothing are, for example, size and color.
AtroPIM has 14 attribute types. The use of attribute types is necessary for better typing and corresponding validation of the data in the system. For more information on attributes and their types, please read the documentation.
For more information on configuring the product attributes, read the article: “How to create the product attributes?”.
Associations are used to store various relationships between the products. Such relationships may appear interesting to potential customers for a variety of reasons - one may want to buy a replacement for an existing product, another may be interested in certain associated products, etc. Associations can be both one-sided (product A is associated with product B, but not the other way around ) as well as bilateral (if product A is associated with product B, then product B is also associated with product A).
With AtroPIM each user can configure the relationship types he intends to use himself. The following types of relationships are pre-configured:
The definition of a Classification is the first step in segmenting the user's product range. You need Classifications in order to unify the descriptions of the products of the same nature. Classifications determine which attributes a product from this Classification should have.
For more information on the configuration of the Classifications, read the article: “How to create the Classifications?” .
With the help of the categories, the end customer can find the required product faster. A good example of the product categories are the categories in any online shop. Since the category is for marketing purposes only, the product can be assigned to more than one category so that it will be displayed more frequently.
Only one parent category can be entered for each category. With the help of such links, a category tree is created; the category without a parent category is the root category, the category without child categories is called a leaf category. The child categories of a certain category are called sub-categories.
If several root categories are created for the categories, the user will work with several category trees.
In the view of a category tree (view Tree View
) you can clearly see all available category trees.
Using the drag-and-drop function, you can quickly make changes to the structure of any tree.
For better usability and acceleration of the customer journey, we recommend not creating more than 3 category levels. Of course, every user has their own specific needs, but one has to consider the following: the simpler the category tree, the more likely it is that the customer will find exactly what they are looking for.
The creation of the categories can often be based on product properties, which are usually to be described by product attributes.
Example 1:
So you can create the category "TV" and add the following sub-categories to this category:
It is advisable to relieve the category tree of superfluous sub-categories and instead add the “Diagonal” attribute to the Classification and specify the appropriate value for each TV set. An important advantage of using attributes is the ability to filter the entries. If the user uses the filtering by attributes, he will find the required product faster than if he only uses the categories and sub-categories.
So everyone has to find the golden mean for themselves, where the categories end and the attributes begin.
The following rules apply when creating the categories:
Catalogs can be used in the system to manage different product ranges, catalogs from different suppliers or different versions of your own catalogs. A master catalog can be created by merging the data from other catalogs.
Channels are the destinations for product information; these can be, for example: the creation of a print catalog, online stores, marketplaces, etc. The use of the channels enables an effective implementation of your multichannel or omnichannel strategy.
For more information on the configuration of the Classifications, read the article: “How to use the catalogs and channels correctly?”.