One set of words every system describes a product in.
The identifiers a product is keyed to. The attribute names, and the values each one can take. Core, Contextual and Custom, applied to the items in scope.
The same answer, whoever in the business runs it.
Product dictionary
One item, four systems
Illustrative. Invented brand, invented identifiers.
Sales
NB SPRK WTR BLD ORG 12Z
Ecommerce
Northbank Sparkling Water, Blood Orange, 12 fl oz
Category
SW-FLAV-SINGLE
Supply chain
899412-BO-12
Resolved to one product: UPC 0 99999 04412 8
What internal naming does not carry.
Each team named products for the system it works in, and those conventions are consistent inside their own systems.
The same item then sits in sales, ecommerce, category and supply chain under four descriptions, and no field in any of them says the four are one product.
Where it comes from
The definitions come first, then the coding.
Each attribute and each of its values is agreed with you before any product is coded against it.
Products come in from millions of listings across retailers, normalized to a single record per UPC before any coding runs. The products in scope are then coded against that same set of definitions.
Refreshed on a schedule agreed with you, and applied the same way to every product in the category.
What the dictionary carries.
Identifiers
What a product is keyed to, so two systems can be joined on it. UPC, retailer item number.
Attribute names
One agreed name for each thing a product can be described by. Pack format, flavor.
Values
The set a name is allowed to take, and the rule that sorts an item into one of them. Single serve against multipack.
Core, Contextual and Custom attributes are all written in this dictionary.
The questions this answers.
Which description of an item your systems should join on.
Data harmonization
What is missing, duplicated or wrong on a product before anyone joins it.
Data cleansing
What happens to an item that gets listed after the dictionary is built.
Automated product coding
Whether the description your systems hold is the one an agent reads.
AI and agent readiness
A leading US retailer ran its catalog against one maintained set of attribute definitions, replacing non-informative labels and recoding products on behavioral and contextual cues. Non-informative labels fell 71% and category precision rose 22%, and newly listed items were coded within 72 hours.
Where this sits.
Product attributes. The three types a definition can be written in.
Managed catalog. Attributes maintained under those definitions.
Data harmonization. Four system names for one item, resolved to a single UPC.
Missing attribute values. The fields a product does not carry, filled against the same definitions.
How you get it.
A feed into your own systems
The dictionary and the coded attributes under it, written to your identifiers and your field names.
Insights Platform
The same attributes, open on screen to whoever needs to check a definition.
Work our team runs
We do the mapping between the systems that have to agree.
What our Customers are saying
See What Shopper-Led
Product Data Can Do
Go from messy, generic product data to precise, shopper-led decisions. Learn how Harmonya structures, enriches, and analyzes data to drive action.







