Glossary

What is a data dictionary?

A data dictionary documents the meaning and properties of the fields used in a dataset or system. For product data, it can record attribute names, definitions, data types, units, permitted values and requirements. It gives people and integrations a shared explanation of what each field represents, including distinctions that cannot be understood reliably from the field name alone.

Recording meaning as well as format

A useful dictionary explains both the technical properties of a field and its business meaning. It may include the field code, display label, definition, examples, units, allowed values and rules for missing information. Ownership and source guidance can be included where needed. The dictionary should reflect the implemented catalogue, so changes to attributes or validation rules also prompt a review of their documentation.

A weight example

A supplier file might contain a column labelled weight. The receiving team needs to know whether this means the item alone, the retail pack or the shipping carton, and which unit applies. A dictionary could define separate net product weight and packaged weight fields, with examples of the intended scope. That guidance supports the decision about where the incoming value belongs before any conversion or import is attempted.

Dictionary, schema and business glossary

A schema expresses the record structure and constraints that software can enforce. A data dictionary documents the fields within that structure, while a business glossary explains broader concepts such as product, supplier or active range. These resources can be connected without becoming interchangeable. A technically valid number can still be placed in the wrong field when the business meaning is unclear or the dictionary is out of date.

Related terms

Sources and further reading

PIM and PXM services

Explore support for selecting, implementing and improving your PIM.