TB.One > Product and Article Data > Clusters and Internal Categories > Internal Categories vs. Clusters

Internal Categories vs. Clusters

Clusters and internal categories (along with attribute sets) point to sets of basic data. With both, it is possible to assign components and attributes when creating new products (manually or via import), and to facilitate the connection of new distribution channels. Internal categories and clusters can be used as filters in the article list, allowing you to use the "edit list items" feature, which you can use to assign values to a large number of articles simultaneously. At some channels, you can use clusters or internal categories as the navigation for your own merchant shop within the portal.

The main differences are:

Clusters are not structured hierarchically while internal categories form a tree structure. Only the hierarchically lowest node of an internal category may contain products.

More than one cluster can be assigned to a product, but it can only be part of one internal category.

You can assign a product to an internal category by means of a cluster, but not vice versa.

When assigning channel information. clusters offer more options than internal categories. Via clusters, you can not only assign primary and secondary categories (resp. commodity groups or product types, depending on the channel), but simultaneously enable the products for each channel and define commission groups.

To fully understand the function and scope of clusters, see the article on filtering and bulk editing the article list.

When using internal categories and clusters, it is your responsibility to ensure that the exported information is not contradictory and does not lead to inconsistent data.

 

ATTENTION:
Make sure to avoid information overlap at the following points:

Primary and secondary channel categories (clusters, internal categories, import)

Flags (clusters, internal categories, import)

Components (clusters, internal categories, attribute sets, import)

Attributes (clusters, internal categories, attribute sets, import)

Variant definition (attribute sets, import)

Service logos (clusters, internal categories, import)

Article data (clusters, internal categories, import)

 

Manual product data maintenance:

If you assign a cluster which, in turn, assigns an internal category, your product will take on the internal category, but not the assignments defined by this internal category (via the tab "assignments" or an attribute set). The assignments and attribute sets that are configured via internal categories will only be adopted if you click "Repeat assignment run" at "Basic data > Classifications > Internal categories". You can find this option in the left navigation bar on the tab "Pages". Changing or adding attribute sets to an internal category will instantly add the contained information to all products in that internal category.

Once a property and the corresponding value are stored at a product (e.g. via a cluster), the value will not be overwritten later (e.g. during the category assignment).

Example: "Cluster value = red" and "category value = blue" will result in the component value "red"

Product data maintenance via import:

The data is assigned sequentially. This means the product will first obtain the cluster and - depending on the settings at "Admin > Import > Settings" - the values configured at the cluster. This is followed by - depending on the settings at "Admin > Default values" - the assignments via internal categories and, finally, the attribute sets of the internal category are applied. Since the information is only written to TB.One's database once all information has been processed, the value which was processed last will be implemented.

Example: "Cluster value = red" and "category value = blue" will result in the component value "blue"

 

The following table illustrates the differences between clusters and internal categories:

CLUSTERS

INTERNAL CATEGORIES

Flat array

Hierarchical tree structure or flat

Unlimited clusters assignable

Exactly one internal category per product

Every cluster is assignable.

For tree structures, products can only be assigned to the lowest category level.

--

Links between categories possible. This allows you to automatically create cross-selling and other types of links between the products (i.e. configuration of auto links).

Can be exported as navigation for your own shop (not available for all channels).

Can be exported as navigation for your own shop (not available for all channels).

Can assign an internal category.

The assignment of clusters via an internal category is not possible.

Can activate products by channel.

--

Assignment of a primary, possibly a secondary channel category.

Assignment of a primary, possibly a secondary channel category, also based on brand and/or flags.

Assignment of commission groups (not for all channels).

--

Assignment of product components with/without value.

Assignment of product components with/without value.

Assignment of product attributes with/without value.

Assignment of product attributes with/without value.

Assignment of service logos.

Assignment of service logos.

Assignment of flags.

Assignment of flags.

Assignment of brands.

--

--

Definition of mandatory components/attributes using attribute sets. Attribute sets can be applied to an entire category or based on brands and/or flags within a category. Each category can have any number of attribute sets.

--

Order of the components within the category can be defined.

--

Define standard variants in the category via attribute sets.

Assignment of article data (IntraStat category, country of origin, package template, shipping type, delivery time).

Assignment of article data (IntraStat category, country of origin, package template, shipping type, delivery time).

 

INTERNAL CATEGORY

CLUSTER

8_2_2-IntKat_vergleich_en

8_2_2-Cluster_vergleich_en

Tab "Assignments"

Via "Attribute sets"

Cluster menu

Channel information:

Primary and secondary channel category

 

Product data:

Flags

Components (opt. 1 value)

Attributes (opt. multiple values)

Service logos

 

Article data:

Intrastat category

Country of origin

Package template

Shipping type

Delivery time

 

Basic data:

Components

Attributes

Flags

Service logos, Intrastat number, country of origin, package template, shipping type

Fixed definition or allow additional fields

Optionally: assignment based on brand and/or flag

 

Product data:

Component (opt. with list of values)

Attributes (no values)

Variant fields (opt. with list of values; can be limited to that list)

 

Basic data:

Components

Attributes

Flags

Brands

Internal category

 

Channel information:

Primary and secondary channel category, commission group

Product activation and deactivation

 

Product data:

Brand

Flags

Components (opt. 1 value)

Attributes (opt. multiple values)

Service logos

 

Article data:

Intrastat category

Country of origin

Package template

Shipping type

Delivery time

 

Basic data:

Components

Attributes

Flags

Service logos, Intrastat number, country of origin, package template, shipping type

 

TIP:
You should think about the following questions before data creation:

1.Do you have your own online shop, and do you want to control its navigation via TB.One?

2.Do you want to activate channels such as eBay, and control the navigation of your merchant shop via TB.One? If so, do you want to control the navigation via clusters or internal categories? Structure your navigational hierarchy in a meaningful way. If you use clusters: Assign only one cluster to each product.

3.Would you like TB.One to create links automatically? In this case, you need internal categories.

4.Will your data be entered manually/by several different employees and should you, therefore, define mandatory fields?

5.Will your assortment change/be extended often after your master data has been created?

6.Do you already have a system (ERP, etc.) where you maintain your product master data, and what data can you export from there?


For further information, see also:

Assigning internal categories or clusters manually

Assigning internal categories or clusters via CSV

Assigning internal categories or clusters via XML

Creating internal categories

Importing internal categories via CSV

Importing internal categories via XML

Defining clusters (overview)

The cluster menu and its filters

Creating/configuring clusters

Bulk editing clusters

Using clusters

Import settings: assigning categories via clusters