Product taxonomy that makes a changing catalog easier to navigate.
Product taxonomy is the controlled classification system used to organize products into categories and subcategories. It gives buyers a predictable path through the catalog and gives product teams a shared structure for attributes, rules, and channel output.
Hierarchy
Organize products from broad families to specific types.
Attributes
Attach the right specifications to each product class.
Governance
Apply one approved structure across incoming sources.
Definition
What is product taxonomy?
Product taxonomy is a hierarchical system for classifying an assortment. It normally moves from broad categories to narrower subcategories and product types, creating a stable vocabulary for navigation, filtering, merchandising, analytics, and product-data governance.
A taxonomy answers where a product belongs. A distributor might place a rotary hammer under Power Tools, then Drills, then Rotary Hammers. That position can determine which attributes are required, which filters appear, and where the product is published. The structure should reflect how buyers evaluate the assortment rather than simply mirroring an internal department chart.
- Category and subcategory hierarchy
- Product types with shared attribute requirements
- Consistent names and identifiers
- Mappings between supplier and channel classifications
Catalog model
How are taxonomy, categories, and product attributes different?
Taxonomy is the overall classification framework. Categories are the individual nodes within it. Attributes describe the products assigned to those nodes. A category such as Industrial Pumps may require flow rate, maximum pressure, connection type, and material, while a different branch needs a different specification set.
Facets and filters often use those attributes to help buyers narrow results. A filter is therefore not the taxonomy itself, even though the two work together. Clear boundaries make the model easier to maintain and prevent teams from creating duplicate categories whenever they need a new filter.
| Element | Purpose | Example |
|---|---|---|
| Taxonomy | Defines the full classification system | Tools → Drills → Rotary Hammers |
| Category | Groups products at one point in the hierarchy | Rotary Hammers |
| Attribute | Describes a product characteristic | Impact energy: 2.7 J |
| Facet | Lets buyers filter a product set | Voltage: 18 V |
| Channel mapping | Translates the internal structure to a destination | Shopify product category |
Source mapping
Keep supplier classifications without multiplying catalog structures.
Suppliers rarely use the same hierarchy. One file may describe a family as Fasteners, another as Fixings, and a third may provide only a manufacturer group code. Copying every source category into the storefront creates an inconsistent catalog and makes reporting unreliable.
Nexodo maps recurring supplier fields into a common product model while retaining the source observation. Catalog owners can see what the supplier provided, assign the approved category, and reuse that decision. The supplier vocabulary remains evidence; the canonical taxonomy remains controlled.
Governance
How should a product taxonomy be maintained?
Begin with buyer tasks and a representative assortment. Define broad families, identify the product types buyers compare, and attach only the attributes needed to distinguish them. Test the hierarchy with search, navigation, filters, and real product assignments before expanding it.
Every change needs an owner and a reason. Adding, moving, or merging a category can affect URLs, filters, analytics, required attributes, and channel mappings. Review those dependencies, redirect retired public paths, and measure whether buyers find products more efficiently after the change.
- Name an owner for each major branch
- Document category-entry criteria
- Test products that sit near category boundaries
- Review zero-result searches and filter usage
- Map destination taxonomies explicitly
PIM workflow
Use PIM to connect classification with product-data quality.
A PIM makes taxonomy operational by linking product types to required attributes, validation rules, assets, and channel readiness. The catalog team can see whether a product belongs in the category and whether it contains the information that category requires.
Nexodo currently focuses on governed products, source observations, quality rules, assets, and Shopify publishing. It is not an automated taxonomy-generation service. Teams should validate classifications and changes against their own assortment before making them canonical.
Frequently asked questions
Clear answers before you evaluate a PIM.
What is taxonomy in products?+
It is the controlled hierarchy and vocabulary used to classify products so teams and buyers can browse, filter, compare, govern, and publish an assortment consistently.
What is an example of product taxonomy?+
A hardware catalog could use Tools, Power Tools, Drills, and Rotary Hammers as successive levels, then require attributes such as voltage, chuck type, and impact energy.
Does Shopify have a product taxonomy?+
Yes. Shopify maintains a standard product taxonomy for product categories and associated attributes. A PIM can map an internal taxonomy and supplier classifications to the appropriate Shopify category.
How often should taxonomy be reviewed?+
Review it when the assortment, buyer behavior, channel requirements, or reporting needs change, and perform a structured health review at least annually.
Continue your product data research
Product catalog management software for changing supplier data.
Read more →Product data qualityFind the catalog problems that block a confident purchase.
Read more →Product data enrichmentProduct data enrichment without losing the source behind the record.
Read more →Shopify PIMPut governed product data upstream of Shopify.
Read more →Test Nexodo with a supplier file your team already uses.
Import a CSV or Google Sheet, review changed values, and see whether the workflow fits your catalog before you commit.
- Use a representative product sample
- See source evidence and import history
- No invented feature claims