Resources / Customers & Evidence

Before & After Product Enrichment

A serious evidence page should read like an audit of the product record: what was missing, what evidence was accepted, what changed, and what became usable downstream.

Product Record AuditENRICHMENT RUN
SOURCE PROVIDEDOUTPUT READY
Source recordInput state
Evidence decisionValidation state
Enriched recordOutput state
referenceKverneland · AC820825
IDENTITYRESOLVED
canonical productKverneland AC820825 Fan Impeller
record gapsEAN · compatibility · material unresolved
RESEARCHSUPPORTED
accepted fieldsEAN 8716106986118 · Optima / Optima HD · Metal
product typesupplier naming varies by source
CANONICALIZEMAPPED
product typeFan impeller · pneumatic seeding system part
weight1.74 kg vs 2.60 kg across public sources
CONFLICTREVIEW / HOLD
output ruleweight excluded until resolved
IdentityResolved
StructureCompleted
ValidationVisible
ActivationImproved
Attribute-level audit

Show evidence and decisions at field level.

The audit view is deliberately product-like: every row shows the source condition, evidence state, decision and resulting output without decorative callouts.

Attribute Validation MatrixAUDIT MODE
FIELD-LEVEL TRACE
Field
Source value
Evidence
Decision
Output
oem_mpn
AC820825
manufacturer documentation + multiple matching catalogs
ACCEPT
AC820825
ean
not in starting record
Kramp product record
ACCEPT
8716106986118
compatibility
incomplete
Kverneland / distributor product context
ACCEPT
Optima / Optima HD
weight
1.74 kg / 2.60 kg
SELM Agro vs LBR conflict
HOLD
unresolved · excluded from output
Unknown fields stay visible instead of being guessed.ACCEPT / HOLD / MAP / REVIEW
Evidence processing

Track how the record changes through controlled states.

The transformation is shown as an execution ledger: five stages, an event log, and the current state of the resulting product record.

Evidence Pipeline LedgerPROCESS TRACE
CONTROLLED STATES
01Collect
02Interpret
03Structure
04Validate
05Activate
Execution logstate / evidence / action
COLLECTSOURCEcandidate source material captured
INTERPRETIDENTITYproduct context resolved
STRUCTURESCHEMAvalues mapped to canonical fields
VALIDATEEVIDENCEaccepted and held values separated
ACTIVATEOUTPUTapproved record prepared downstream
CURRENT PRODUCT RECORD

Controlled output state

identityresolved contextREADY
attributesstructured valuesREADY
uncertain_fieldsexplicit review queueREVIEW
classificationmapped categoryREADY
publishcustomer release / destination scope is configuredCONTROLLED
Operational examples

Different catalog problems require different interventions.

The examples are presented as an operational case register: input condition, primary issue, enrichment action, downstream effect and state.

Operational Case Register3 CASE TYPES
RESOURCE EVIDENCE
Case
Primary issue
Enrichment action
Downstream effect
State
Incomplete supplier feedDATA INTAKE
missing core specifications
recover supported fields + normalize schema
filters and PDP become more usable
IMPROVED
Legacy technical catalogCATALOG CLEANUP
old naming and inconsistent values
normalize terms + structure attributes
records become consistent and reusable
STRUCTURED
Marketplace preparationCHANNEL READINESS
thin titles and weak attribute coverage
standardize fields + prepare content inputs
higher publishability across channels
READY
Quality delta

Show the operational impact of the improved record.

The dashboard separates measurable record movement from the downstream business effects it enables.

Quality Delta DashboardAFTER ENRICHMENT
BEFORE MARKER = GREY
Reference record movement6-FIELD TARGET SCHEMA · NOT A CATALOG BENCHMARK
Accepted target fields
2 / 6 → 5 / 6
Source provenance
PRESENT ON ACCEPTED / HELD FACTS
Content basis
TITLE + META + DESCRIPTION READY
Conflict visibility
1 FIELD HELD, NOT GUESSED
DOWNSTREAM IMPACT

What the record can support

Filtersstructured attributes become usable facets
PDPbuyers see clearer product meaning
Reuseone improved record supports more channels
Trustuncertainty becomes visible and reviewable
Record stateStructured
Evidence stateTraceable
Review stateExplicit
Activation stateImproved
Resources family canon

Evidence Ribbon / Annotation Field

The family keeps the smoky evidence ribbon in the background, while Resources infographics use enterprise audit views, record tables, validation states and evidence-led product UI.

Continue to Product Enrichment Examples
FAMILY RULES
backgroundsmoky evidence ribbon + smeared fields
graphicsaudit consoles, evidence matrices, record ledgers
motionsubtle audit scans and state progression
lineperfect round runner on site-wide path

Talk to ENRIVAQ

Request a catalog assessment

Tell us enough to make the next step useful for your catalog.