Brand A lens
RECORD AKverneland AC820825 original / AGD replacement reference
- Category label
- Fan components
- Attribute name
- Outer Ø
- Unit / format
- millimetres
- MPN / OEM
- AC820825
PRESERVEbrand · MPN · OEM · supplier refs
Agriculture verticalMulti-brand catalogs
Brand lenses / shared catalog core
Create One Consistent Catalog Across Multiple Spare Parts Brands
Multi-brand agricultural catalogs have a structural problem: every manufacturer and supplier describes products in its own way, but the customer expects one coherent store.
For ENRIVAQ, enrichment means completing the usable card: validated technical attributes are combined with SEO keyword targets, unique factual product content, SEO metadata and target-language output rather than being delivered as attributes alone.
ENRIVAQ is designed to map those different inputs into a common taxonomy with standardized attributes, identifiers and cross-reference structures while preserving brand-specific information.
Brand Lenses / Shared Product Family CoreCONSISTENT CATALOG ≠ ERASED BRAND IDENTITY
Brand B lens
RECORD BKverneland AC820825 original / AGD replacement reference
- Category label
- Blower parts
- Attribute name
- Outside diameter
- Unit / format
- centimetres
- MPN / OEM
- AC820825
PRESERVEbrand · MPN · OEM · supplier refs
Brand C lens
RECORD CKverneland AC820825 original / AGD replacement reference
- Category label
- Air-system parts
- Attribute name
- OD
- Unit / format
- value + source unit
- MPN / OEM
- AC820825
PRESERVEbrand · MPN · OEM · supplier refs
Shared canonical layer
NORMALIZE COMMON STRUCTUREtaxonomy · attributes · units · filters
PRESERVE DIFFERENTIATIONbrand · MPN · OEM · supplier references
Different data languages
Different brands bring different data languages
Category names, attribute labels, units, abbreviations and identifier formats can vary from one source to another.
If each feed defines the catalog structure, the result becomes fragmented: duplicate categories, duplicate filters and inconsistent product pages.
The target catalog therefore needs its own canonical data model.
Brand ABrand BBrand CCanonical concept
Outer Ø
Outside diameter
OD
outer_diameterProduct group
Family
Category
target_category42 mm
4.2 cm
42
42 mmOEM ref
OE number
Cross ref.
reference_type + valueThe catalog model becomes the language bridge. Source-specific wording is mapped into shared concepts rather than copied into filters and categories.
Preserve distinctions
Preserve the information that distinguishes each product
Standardization should not erase manufacturer identity.
Brand, MPN, OEM and supplier-specific references can remain explicit while common attributes and category structure are normalized.
This balance lets the catalog stay consistent without turning different products into generic records.
Shared core
Canonical product family
Common taxonomy, attributes, units and filter logic.
Two-layer record model
Normalize the common layer. Preserve the identity layer.
- Target taxonomy
- Mapped target category SHARED
- Technical attribute
- outer_diameter SHARED
- Unit / format
- canonical unit defined by schema SHARED
- Brand
- AC820825 PRESERVE
- MPN / OEM / supplier reference
- AC820825 PRESERVE
- Brand-specific technical nuance
- Original vs aftermarket relationship kept explicit DO NOT FLATTEN
The target model standardizes what customers should compare while keeping the fields that distinguish one brand/product record from another.
Normalize values and units
Normalize values and units across the entire catalog
Common technical values should follow the same representation regardless of source.
For example, a dimension should not appear as three separate filter values simply because suppliers use different units or formatting.
Standardization should follow the approved catalog schema.
Unit Calibration BenchSAME TECHNICAL VALUE → ONE REPRESENTATION
42 mm
millimeter source representation
4.2 cm
centimeter source representation
“42”
unit omitted / contextual source value
NORMALIZEschema-owned unit rule
Canonical catalog value
42 mm
One value in the approved representation becomes the filter/comparison value.
UNIT RULE: Canonical identity · OEM reference · brand/manufacturer · aftermarket relation · compatibility · technical attributesIllustrative example only. Real values and conversion rules must come from the catalog’s approved schema and source context.
Catalog proof
Show several brand records inside one catalog structure
This visual should make the value of standardization and mapping immediately obvious.
Brand identity stays visible; the surrounding catalog structure becomes consistent.
BRAND A RECORD
AC820825 reference family
- Brand
- AC820825
- MPN
- AC820825
- Dimension source
- AC820825
BRAND B RECORD
AC820825 reference family
- Brand
- AC820825
- MPN
- AC820825
- Dimension source
- AC820825
BRAND C RECORD
AC820825 reference family
- Brand
- AC820825
- MPN
- AC820825
- Dimension source
- AC820825
SHARED CATALOG STRUCTURE
Fan impellers / replacement references around AC820825
Pneumatic Seeding System Parts → Fan Impellersmanufacturer_ref / compatibility / materialCanonical unit per technical fieldBRAND PRESERVEDMPN/OEM PRESERVED
This is not three feeds collapsed into one product. It is several brand-specific products represented inside one consistent catalog model.
Starting point
Use a product family that exists across several brands
Bring the same or similar part type from multiple suppliers and compare how the records can be standardized.
Cross-Brand Product Family ComparatorSELECT A FAMILY WITH REAL OVERLAP
Brand / product identity
Category label
Attribute label
Unit / format
MPN / OEM
Comparable core
Brand A
AC820825 reference family
Brand B
AC820825 reference family
Brand C
AC820825 reference family
Choose the family where the same buying criteria appear under different brand-specific data languages.
COMPARE → MAP → PRESERVE → STANDARDIZEControlled next step
Start with one product family across several brands
Use real overlapping products to prove the canonical model while preserving brand-specific identity and references.