Product Master · Feed Prioritization

Don't master
464 feeds.
Fifty matter.

Every manufacturer you bring into the Product Master costs one Mint Namespace — a compiler, normalization rules, a canonical source. Skip one and every product they make stays hand-keyed forever. This ranks all 464 feeds by what building one actually saves: products off the manual-entry pile first, then spend and reach.

← feeds built, by spend rank cumulative spend covered ↑
464
feeds in priced work (Harman + Legrand AV rolled up)
$45.3M
attributed spend (cost basis)
1,200
distinct projects
7,384
products to master (manual-entry pile)
34%
of spend is last 24 months

The build zone

Ranked by manual-entry burden — the distinct products you'd otherwise hand-key. Flip the axis to spend or reach; the meter follows whichever you pick.

Below the build zone: more manufacturers — between them 161 appear in a single project · 94 total under $1,000 — the long tail, not worth a feed

One feed, many brands

Two owner families collapse to a single feed — one compiler covers the whole shelf, so they rank as one build, not a scatter of siblings. AMX stays separate. Numbers are deduped at the feed level (products and projects), so these aren't sums.

AMX is kept as its own feed ( products, ) — it reaches the Master through a separate Harman channel, so it earns its own compiler. Legrand AV folds in every owned brand in your data; WattBox is deliberately left out — it's Snap One, not Legrand.

Four lenses, four answers

Products is the rank that matters most — it's the manual entry you erase. But spend, reach, and raw volume each pull differently, and where they disagree is the call.

Manual-entry burden
Most distinct products. Master these and the most hand-keying disappears.
Easy passes
Big spend, few products — the dollars tempt you, but there's almost nothing to hand-enter. Keep keying them.
Widest reach
In the most projects. The name shows up everywhere, even when spend is modest.
Volume traps
Most pieces, least money — cable by the thousand-foot. High count, low value.

How this was counted

Universe
Catalog line items only (line.product_id → product), kind = physical, owner-furnished excluded, hidden kept. Project phases exclude TEMPLATE and TRASH.
Spend basis
Per line, first non-zero of line.cost → line.price → product.cost → product.price → mapp → msrp, times quantity. Avoids multiplying by a missing price.
Custom lines
The ~$29M of custom line items carry no manufacturer and are excluded — naming them is the normalization layer's job, not this report's.
Recent
Spend on projects created in the last 24 months. A momentum read, not a forecast.
Source: JetBuilt integration DB · 464 feeds · re-run from reports/manufacturer_usage.sql Proxy for Mint Namespace prioritization · spl-master-catalog