Navigation directory
134 pages
No pages match your search.
Product enrichment works best when the system knows what a complete record should look like.
A taxonomy provides that structure. It defines where products belong, which attributes are relevant to each product family and how the catalog remains consistent across suppliers and systems.
ENRIVAQ uses the target taxonomy as the structure into which enriched product data can be mapped.
REFERENCE TAXONOMY · CATEGORY STRUCTURE SHOWN FOR AC820825
Different suppliers may use different categories, naming patterns, hierarchy levels, product families, attribute sets and terminology. If those structures are imported directly, the catalog can become a collection of incompatible supplier taxonomies.
A canonical taxonomy gives navigation, filters, product comparison, enrichment rules, SEO structure and data maintenance one consistent model.
A taxonomy can organize products through several hierarchy levels. The exact hierarchy depends on the business and product range. The important principle is that the category structure should be deliberate and consistent rather than created independently by each supplier feed.
The visual shows relationships between levels. The hierarchy shown here is an illustrative taxonomy path; production mappings use the customer’s actual business taxonomy.
Agricultural Machinery → Seeding Equipment → Pneumatic Seeding System Parts → Fan ImpellersA bearing and a hydraulic hose should not share the same required specification set. Taxonomy can connect a product category to the attributes relevant to that family.
The category node acts as a schema anchor: it determines which fields are expected for this family and which are not.
These examples should be replaced with the actual schemas used by the product or customer.
The approved architecture defines the mapping concept as Source → Canonical Taxonomy. ENRIVAQ should map product records into the business-defined target structure, not invent a new catalog model during enrichment.
Agricultural catalogs can contain several structural levels. This example shows the hierarchy concept; the implemented catalog uses the customer’s real agricultural taxonomy.
Fan impeller used only as the visual endpoint of the hierarchy.
REFERENCE HIERARCHY · FINAL NODES FOLLOW THE CUSTOMER TAXONOMY
A clean taxonomy can support clearer category context, filters, breadcrumbs, internal relationships and product-page organization. SEO is a downstream benefit of a real product structure, not a reason to distort that structure.
The strongest SEO architecture comes from a real product structure combined with useful, distinct page content.
Show us your current categories, supplier structures and target attribute model.