Category-level dashboards tell you the market moved. Attribute-level data tells you how, where, and what to do about it. Inside the discipline of turning messy public catalogs into product understanding.
ARArjun Mehta
Two retailers both "carry 400 espresso machines." One carries 400 variations of the same three chassis at overlapping price points; the other carries 400 genuinely distinct products spanning five feature tiers. Category-level data says they're identical. Product intelligence exists because the difference is where the strategy is.
Why attributes are hard, and worth it
Public catalogs are written for merchants and shoppers, not analysts. The same product appears under different names; specifications use incompatible vocabularies ("capacity: 1L" vs "1.0 liter" vs "35 oz"); bundles hide their contents; variants multiply. Normalizing this into comparable attributes is unglamorous work with an outsized payoff: once attributes are comparable, everything downstream — gap analysis, benchmarking, launch detection — becomes arithmetic instead of archaeology.
Normalization — one canonical vocabulary per attribute, versioned, with documented mapping decisions.
Entity resolution — the same physical product recognized across retailers, with match provenance.
Variant flattening — color/size/kit variants grouped under sellable parents so breadth isn't inflated.
Bundle deconstruction — promotional bundles mapped to their component SKUs for honest price comparison.
The lifecycle layer
Observing catalogs over time converts a static snapshot into a lifecycle record: introductions, refreshes, delistings, and the quiet A/B assortment experiments most retailers run constantly. For a product manager, a competitor's introduction pattern is the closest thing to a public roadmap. For a category manager, delisting velocity in a subcategory is a leading indicator of margin pressure.
New product introductions by quarter, tracked category
Introductions
Source: Heroku assortment tracker — new product introductions in one monitored category, quarterly counts.
Gap analysis that holds up in a meeting
The standard output of product intelligence is the coverage matrix: your assortment against the competitive set, per attribute and price tier. Done well, it ends arguments. "We have nothing above $400 in the cordless line" is a much better meeting opener than "I feel we're underrepresented in premium" — and much harder to dismiss.
Price tier
Your SKUs
Market SKUs
Coverage gap
Entry (< $150)
38
210
Low — adequate presence
Mid ($150–$400)
62
340
Moderate — depth in 2 of 5 feature tiers
Premium ($400+)
9
180
High — no smart-connected offering
Coverage gaps are opportunities only if demand exists. Pair the matrix with search intelligence before commissioning a roadmap.
Integration, not another silo
The graveyard of product intelligence is the standalone BI portal nobody opens. The data earns its keep inside existing workflows — as tables in the merchandising warehouse, as inputs to pricing tools, as columns in the PIM. Design the delivery for the systems your teams already use, and adoption follows.
If you're assessing your own readiness, start with one category, one competitor set, and one decision that needs evidence. Prove the loop there; expand on results rather than enthusiasm.
Arjun works with enterprise clients to design data programs that survive contact with reality — legacy systems, procurement cycles, and all. He writes about integrating external data without creating new silos.
Organizations drown in signals and starve for decisions. A practical taxonomy for classifying market signals by decision relevance — and for building the escalation paths that make monitoring pay for itself.
Market intelligence has quietly changed shape: from quarterly reports assembled by hand to continuous programs built on structured public-web data. Here's what that change actually looks like in practice.
Maya Chen·
2 comments
LO
Louise Fontaine
The coverage matrix framing ended a six-month argument in our assortment meetings. “Evidence beats vibes” is now a slide in our onboarding.
MA
Marcus Lee
(Team note) Attribute schema definitions are versioned and published to clients on every change — worth asking any provider, including us, exactly how their schemas evolve.
2 comments
The coverage matrix framing ended a six-month argument in our assortment meetings. “Evidence beats vibes” is now a slide in our onboarding.