Product data enrichment

Fill the attributes your sources never carried

Fourteen sources can describe one product, and not one of them carries every field. Enrichment reads all of them, plus the pack and the listing, so the attribute you need is present rather than missing.

No source describes a product completely

One product, fourteen sourcesProduct data enrichment
Sources carrying a complete record
0

Thirteen of the fourteen give a description. Eight give nutrition. Two give a price. One gives structured features. Not one gives all of it.

Live records from the catalog · one UPC in tortilla chips
What each field costs to findI · III
Field · sources out of fourteen that carried it
ICoverage by field13 to 1
Description13
Nutrition8
Reviews6
Imagery3
Price2
Features1

The further down this list an attribute sits, the more of the market you have to read to find it at all.

IIThe long tail is the point1 of 14

Structured features came from a single source. Take that source away and the attribute does not exist for this product anywhere in the feed.

Single point of failure
IIIAbsence reads as zero6 of 14

Six of the fourteen carry nothing but a description. A system that trusts them treats a missing attribute as an absent one, and the product quietly drops out of every cut built on it.

Missing is not the same as no

The attribute you need is usually present somewhere. It is almost never present in the place you were already looking.

Field coverage for a single UPC in tortilla chips, counted across the fourteen sources the catalog holds for it. Source names are generalized to their type.

How a gap gets filled

Three things separate filling a gap from guessing at one.

Read, not inferred
from the pack and the listing

A missing attribute is found by reading the places it is actually written down: the pack copy, the ingredient statement, the nutrition panel, the product page. It is not predicted from what similar products tend to be, which is the difference between a filled field and a plausible one.

Scored, not asserted
a confidence on every field

Every value carries a score, so you set the threshold you are willing to act on rather than accepting the whole file at one quality. A team using the data for a planogram and a team using it for a claim audit do not need the same bar.

Traced, not orphaned
every value keeps its source

Each filled field keeps a line back to what it was read from. When somebody challenges a number in a meeting, the answer is the page it came from rather than an assurance that the model is usually right.

Where each attribute actually came from

Fourteen sources for one UPC, and the field each one carried. The last row is the record enrichment returns.

UPC 851769007003 Tortilla chips 14 sources read
SourceDescNutrRevwImagePriceFeatAbout
Distributor feed
Marketplace
Retailer site
Pharmacy retail
Retailer API
Retailer API
Label database
Retailer site
Retailer site
Retailer site
Retailer API
Retailer site
Grocery platform
Retailer API
Sources carrying it13863211
Enriched record
Fourteen live source records for one UPC, with a mark where the source carried that field. Every row has a gap and the widest row still misses two fields. The enriched record is the union, read from the pack, the listing and the label rather than taken from whichever source happened to be first.

Harmonya Helps You Make Faster, More Confident Decisions

A filled attribute is only useful if the product it sits on is the product you think it is. Resolution comes first, then depth.

Product Catalog licensing

Twelve sources, eleven names, one row. See how records get resolved before they get filled.

See the licensed layer

Request a Demo

Thirty minutes on your categories. How the record gets built, what it holds, and the questions your team could put to it.

Get a Demo
Arrow