Custom attributes

Your definitions, running on every product in the category.

Core is what the product is. Contextual is what the market says about it. Custom is the part only you can write: your segments, your thresholds, your naming. We apply it identically to every UPC, re-apply it every run, and keep it on the same record as everything else.

One can of caffeinated sparkling water

0values on this can that exist only because a customer defined them. Each one is a rule, applied to every UPC in the category the same way.

How the category ships

standard hierarchy
Beverages
Carbonated soft drinks
Sparkling water
Flavored sparkling water

How your team actually argues about it

your hierarchy
Better-for-you
Functional refreshment
Caffeinated sparkling
Three levels, because that is how the review runs.

The rule that puts it in the second column

Better-for-you sugar 0g · 25 cal or under · no artificial color
This can 0g · 5 cal · nonein the set
The rest of the category about 18,000 UPCs, same rule, every run

Illustrative definition, invented customer. The mechanism is real: the rule is yours, it runs on the whole category rather than a sample, and a product leaves the set the run its facts stop clearing the bar.

A definition, not a spreadsheet

Most custom segmentation lives in one analyst's file and drifts the moment somebody else maintains it. Here it is a rule on the record, applied the same way to every UPC and re-applied every run.

Hierarchies
your category tree, not ours

Your department, category and segment naming, mapped onto every product we hold. Reports stop needing a translation layer between our taxonomy and the one your business actually runs on.

Thresholds
the line your team draws

Better-for-you, premium, value, single serve. You set where the cut falls, we apply it across the whole category, and a product moves in or out of the set the run its facts change.

Flags and groupings
the sets you argue about

Own brand against national brand, a demand space that spans three aisles, a watchlist. Anything a team currently keeps by hand becomes a field on the record that everyone reads the same way.

Where the arguing stops

Most category debates are not about the numbers. They are about whose definition of the set is the right one. This turns that into a setting rather than a standoff.

01

Category management

Run the review on your own segment structure and your own thresholds, against the same product record everyone else in the room is reading. The set stops being the thing under debate.

02

Insights and strategy

Cut the category the way the strategy actually frames it, including groupings that span aisles and appear in no standard hierarchy anywhere.

03

Data and engineering

Stop maintaining a mapping table that drifts between refreshes. The definition lives with the record, versions with it, and arrives already applied to every UPC in the feed.

Outcomes from teams already running it

A Fortune 100 CPG was coding its product file by hand, and coverage stalled near 68 percent. A custom catalog now codes the whole file to their own taxonomy every cycle, including the 26,185 products no one had ever reached.

98%

accuracy coding to their taxonomy, independently validated

Fortune 100 CPG →
32%

of the file had never been coded by hand, now covered

Fortune 100 CPG →
4x

the contracted delivery cadence, refreshed weekly

Fortune 100 CPG →
>80K

products coded every cycle, all to their definitions

Fortune 100 CPG →

Three layers, and nothing counted twice

Custom is the third layer. Core holds what the product is, Contextual holds what the market says about it, and Custom holds the structure you define. Every attribute is coded into exactly one of the three, so the layers add up to the whole record and nothing is counted twice.

One product, one key

0 12345 67890 5

Every attribute hangs off the same UPC and is coded into exactly one layer. Add the layers up and you have the whole record, with nothing counted twice.

Corelisting, pack and label

What the product is. Identifiers, brand hierarchy, taxonomy, size and multipack, packaging, origin and titles. True whether or not anyone ever buys it.

AnswersWhat is this product, and which of my SKUs match it?

Contextualreviews, search and social

What the market says about it. Claims and ingredients as they are discussed, benefits, occasions, audiences and the words shoppers actually use. It moves as the conversation moves.

AnswersWhy are people buying this, and what is rising?

Customyour definitionsyou are here

The structure you set. Your segments, your thresholds, your naming and your own hierarchy, applied to every UPC in the category the same way.

AnswersWhich products count, by our definition rather than anyone else's?

Three ways to take delivery

The same record, delivered three ways. Most teams start with one and add another once the record is in their stack.

01

Licensed feed

The record delivered to your warehouse, normalized at the UPC and refreshed on a schedule you set. It joins to your sales data on the key you already use.

Best when you have a data team and the record needs to live inside your own stack.

02

Harmonya Insights

The record inside our platform, where category and insights teams ask the questions themselves without waiting on a ticket.

Best when the people with the questions are not the people with SQL.

03

Work we run

We scope the question, run it against the record and hand back the answer, with the working shown so your team can defend it internally.

Best when the deadline is close and the answer matters more than the pipeline.

What our Customers are saying

“The relationship between Coca-Cola and Harmonya has truly felt like a partnership. We treat them as an extension of our team.

Rylee Rogers

Category Sales Advisor

View Full Story
View Full Story

“Before Harmonya, we couldn’t track competitor innovations online effectively. Now we can see how fast they’re scaling, just like we do in brick and mortar.”

Michael Mackezyk

Senior Manager, Data Capabilities

View Full Story
View Full Story

"Harmonya is becoming a powerful unlock across our organization—it's  being explored as a cross-functional innovation, brand strategy, and product development tool."

TJ Hanel

Director Omni-Commerce Retail Media Strategy

View Case Studies
View Case Studies

"Harmonya enables us to efficiently uncover deeper insights into consumer sentiment and product ingredient preferences, allowing us to identify actionable opportunities to meet shopper needs and enhance category shopability"

Kristina Foreman

Category Analyst

View Case Studies
View Case Studies

"Harmonya is elevating and enhancing the way we analyze and tell stories with data. The platform enables us to uncover deeper insights that have measurable impact. The team is collaborative, innovative, and truly invested in our success!"

Savita Kharbas

Senior Director of Category and Consumer Insights

View Case Studies
View Case Studies

“With Harmonya’s review data, we can quantify what customers are saying and compare which products meet their needs best—not based on what we say, but on what they say.”

Rylee Rogers

Category Sales Advisor

View Full Story
View Full Story

"Working with Harmonya has been a game-changer – keeping us deeply engaged through new product releases while empowering us to turn complex data into clear, actionable insights."

Wendy Fan

Commercial Strategy Manager

View Case Studies
View Case Studies

“What Harmonya came up with was an AI-powered solution that helped us match 2,000 missing items. That gave us visibility into $1.7 billion in annual sales we were previously blind to.”

Michael Mackezyk

Senior Manager, Data Capabilities

View Full Story
View Full Story

"The Harmonya team has played a vital role in finding insights on texture, flavor, and nutritional content across our competitive set, identifying innovation whitespace, and sparking additional conversations as we develop concepts for our brands."

Bailey Harrison

Senior Associate Brand Manager

View Case Studies
View Case Studies

Harmonya Helps You Make Faster, More Confident Decisions

Custom attributes are the part of the record only your team can write. Once your definitions live on it, every report, every system and every argument starts from the same set.

Product Dictionary

One consistent reference for product attributes and language, across every system and category.

See the use case

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.