ACTIVE PRODUCTFan impeller
AC820825PRODUCT SYSTEMP2SOURCE RADAR
Source discovery
Find the Right Sources Before Extracting Product Data
Product enrichment depends on the quality of the information used to build the record.
Finding a webpage that mentions a part number is not enough.
ENRIVAQ uses product identifiers and technical context to discover sources that are relevant to the product before structured data is extracted. That separates source discovery from simple web collection.
MANY CANDIDATESPRODUCT CONTEXTRELEVANT SET
REFERENCE VIEW · PUBLIC SOURCE ROLES FOR AC820825
Why it matters
Wrong source.
Wrong product record.
Technical catalogs often contain products with similar names, related part numbers or several product variants. A source may appear relevant while describing:
If the source is wrong, everything extracted from it can contaminate the product record.
That is why source selection must happen before attribute extraction.Identification signals
Use the product record as context for the search
Source discovery can use several available signals:
AC820825KVERNELANDThe more useful context the initial record contains, the better the research can be constrained.
SignalWhat it contributes
Helps distinguish products with similar names.
Useful when it appears outside the internal catalog.
A strong manufacturer-level product identifier where available.
Especially important for spare parts.
Technical values can help distinguish two otherwise similar candidate products.
Source types
Different sources serve different purposes
The architecture specifically anticipates several kinds of product information sources.
01
IDENTITYManufacturer
Often useful for canonical product identity and technical information.
02
SPECSDistributor
May provide additional specifications or structured product fields.
03
DETAILSELM / LBR
Can contain technical details that are missing from normal ecommerce pages.
No single source type should automatically be treated as correct for every product. The product identity and the actual information need to agree.
Ranking and relevance
Find the sources most likely to describe the actual product
Source discovery should reduce noise rather than simply return a long list of pages. The workflow needs to evaluate whether candidate information matches the known product context.
Relevant factors may include:
identifier matchSTRONG SIGNAL
manufacturer consistencySTRONG SIGNAL
naming similarityWEAK ALONE
compatible technical propertiesSUPPORTING
agreement with existing product informationSUPPORTING
CANDIDATE SETQUALITATIVE GATE
Manufacturer product pageIDENTIFIER + BRAND MATCH
RELEVANTDistributor listingBRAND MATCH · PARTIAL SPECS
RELEVANTTechnical documentationREFERENCED BY PART NUMBER
RELEVANTSimilar part, other generationNAME MATCH ONLY
REJECTEDMarketplace copy of the titleNO TECHNICAL CONTEXT
REJECTEDExact source ranking logicProduct context + source evidence determine whether a candidate contributes data
Conflict handling
Multiple sources may tell you different things
Product information on the web is not perfectly consistent. Two sources may list different dimensions, units or descriptions for what appears to be the same product.
A source discovery workflow should not silently choose whichever value appears first. Instead, conflicting information should move forward as a validation problem.
This is one reason why source discovery and product validation are separate functions.
CONFLICT PRESERVEDValidation / ReviewNO SILENT WINNER
Source UI
Make source context visible
The source view keeps the following evidence visible together:
product being researchedsource listsource typematching contextextracted information associated with the sourceconflicts where relevant
CANDIDATE SOURCES
REVIEW STATEProduct context matches
MANUFACTURERKverneland parts documentation
RELEVANTIdentifier and manufacturer context agree with the active product.
DISTRIBUTORKramp · EAN and brand context
RELEVANTProduct context agrees; specifications remain associated with this source.
DOCUMENTATIONSELM / LBR · conflicting weight evidence
RELEVANTPart reference connects documentation to the active product.
LOOKALIKESimilar title, different generation
REJECTEDNaming is similar, but identity context does not agree.
REFERENCE PRODUCT WORKSPACE · PUBLIC SOURCE CONTEXT REMAINS VISIBLE
Source discovery
Start with a product whose data is difficult to find
Show us the initial record and see how source discovery fits into the enrichment workflow.