What Is Product Taxonomy?
Product taxonomy is the organized structure used to group products into categories and product families.
For complex catalogs, taxonomy is more than navigation. It provides context for attribute schemas, enrichment rules and internal linking.
See How It WorksSupplier labels should resolve into one canonical category structure.
Directly importing every supplier category often creates duplicate or incompatible structures, so complex catalogs usually need a canonical taxonomy.
Agriculture → Spare Parts → Bearings
Hierarchy creates relationships between broad and specific categories.
The correct depth depends on the product range and customer navigation needs. Increasing specificity should add useful meaning, not arbitrary levels.
01AgricultureBROAD DOMAIN02Spare PartsPRODUCT GROUP03BearingsCATEGORY04Bearing familySHARED DATA MODELProduct families connect similar products to a shared data model.
Products in the same family often need the same core attributes. That link makes enrichment more precise because the system knows which fields are expected.
Bearing schema
DIMENSIONS + TYPEinner_diameterRequired dimensiontyped + unit-awareouter_diameterRequired dimensiontyped + unit-awarewidthRequired dimensiontyped + unit-awarebearing_typeFamily-specific typecontrolled vocabularyTaxonomy and attributes should be designed together.
Once a product is assigned to a family, the catalog can apply the relevant attribute set, validation rules and content structure.
Expected fields
Collect the specifications that actually matter for the family.Rules + formats
Apply the right units, field types and allowed values.Relevant product facts
Build content around the family’s real technical context.Taxonomy is the structure; classification is the act of assigning products to it.
Taxonomy answers “What categories and families exist?” Classification answers “Which of those categories does this product belong to?”
Govern the structure
Define the categories, families and relationships that exist.
Assign the product
Determine where an individual product or batch belongs inside that structure.
Use a real catalog path, not an abstract tree.
The AC820825 reference is classified into the same canonical path used across the ENRIVAQ agriculture pages. Product identity and compatibility stay as fields/relationships rather than creating brand-specific category branches.
Agricultural catalogs often need equipment, component and part relationships.
The right structure depends on how customers search and how the business manages data. Manufacturer references and compatibility should fit into the model without uncontrolled brand branches.
Common questions about product taxonomy.
Four source-backed questions about navigation, supplier categories, AI assistance and enrichment context.
Taxonomy also provides data context.
For complex catalogs, taxonomy helps define families, attribute schemas, enrichment rules and internal relationships in addition to navigation.
See how taxonomy, families and attribute schemas drive enrichment.
The control plane below connects the catalog structure to the downstream enrichment process without collapsing taxonomy and classification into the same task.