Glossary

What is a product hierarchy?

A product hierarchy organises product records or groups into parent and child levels. The levels can represent different relationships, such as a product model and its variants or categories within a catalogue. The purpose of each hierarchy must be explicit, because classification, shared values and component relationships follow different rules even when they are all displayed as a tree.

Defining what each level represents

A hierarchy gives structure to related records, but its appearance does not explain the relationship by itself. A parent might represent a product model, a category or an assembly. The data model should define what can appear at each level, how children are identified and which information belongs to the parent. It should also state whether values are inherited or simply linked.

A product-model example

A lighting manufacturer could organise a range under a model record that holds a shared description and installation guide. Child records distinguish particular finishes and sizes, with their own identifiers and specifications. A website can use that structure to present the available versions together. The catalogue team still needs to decide which attributes are genuinely shared and which must be maintained for each sellable version.

Hierarchy, taxonomy and associations

A taxonomy organises classification concepts or categories. A product-model hierarchy organises related product records. A bill of materials describes components and quantities, while an association can link complementary products without making either a child of the other. These structures can coexist. Using one tree for every purpose can create ambiguity, so document the meaning of each parent-child relationship before using it to drive navigation, inheritance or product exports.

Related terms

Sources and further reading

PIM and PXM services

Explore support for selecting, implementing and improving your PIM.