makeup color matching

What a 45,000-product makeup catalog asks of color indexing

TruHue’s public catalog claims show the scale; the harder work for beautytech is keeping each shade’s color meaning useful and consistent.

By Beatrix Fallowfield·October 7, 2026·4 min read
What matters here
  1. TruHue’s homepage uses both 40,000+ and 45,000+ as its product count, while listing 735 brands.
  2. A large makeup product database needs to distinguish product identity from shade-level color judgment.
  3. TruHue describes its model as 12-season scoring with YAY, OKAY, and NAY results; its backend is not public.

A makeup product database gets harder to trust as it gets larger. The public TruHue homepage puts that problem in plain view: one section says the app covers 40,000+ products, while another says 45,000+, with 735 brands in both claims. The difference may reflect a page update, but the copy does not explain it. For builders, that small inconsistency is a useful reminder: catalog scale is a claim that needs a clear definition and a dependable count.

TruHue is a freemium 12-season color analysis and makeup matching app. Its site says users can identify a season and get products scored YAY, OKAY, or NAY against that palette. It describes the analysis as using answers about hair, eyes, and skin, plus a selfie. The homepage also promotes product scanning and browser access. Those are public product claims; the site does not disclose how its catalog is structured, how often it is refreshed, or how a shade score is calculated.

Catalog size is not the same as coverage

For a practitioner, “45,000 products” raises immediate questions. Does a count refer to product pages, individual shades, or both? Are multiple sizes or renamed shades counted separately? How are discontinued items treated? Without those definitions, raw totals can sound more precise than they are. A catalog can grow while remaining thin in particular categories, price bands, or color families.

That distinction matters because makeup is sold at more than one level. A product line may have a shared name and many shade options; the matching task belongs to the shade, not just the line. A usable index has to make the individual option findable and preserve its relationship to the broader product. That is an operational requirement for the category, not a claim about TruHue’s internal architecture.

Color labels add another layer. Brand shade names are written for shoppers, not as a common technical vocabulary. “Rose,” “nude,” or “warm” can point to different colors across products. A category index therefore needs to avoid treating marketing language as a reliable substitute for a color description. The practical work is deciding what information is consistent enough to compare, and what remains ambiguous.

Swatches are evidence, not ground truth

Images create their own indexing problem. Lighting, camera settings, packaging, and the surface used for a swatch can all affect how a color appears on screen. Multi-tone formulas complicate the picture further: a marbled blush or reflective highlighter may not have one simple color value. Our earlier examination of printed swatches and digital shade analysis for complex makeup covers why a single flat swatch can be a poor summary.

For beautytech teams, the takeaway is not to chase a perfect label for every pan. It is to keep the limits of the evidence visible. A shade name, image, and color judgment are different kinds of information. If they are collapsed into one field, later corrections become harder and recommendations can look more certain than their inputs justify.

Keep the judgment legible

TruHue’s public-facing output is deliberately simple: YAY, OKAY, or NAY for a 12-season palette. That vocabulary gives shoppers a quick decision signal. Behind any such signal, though, there are boundary cases. Two shades may sit close together; a product may suit a season in one context but not another; and a user may prefer a color that is not a conventional palette match. The public materials do not specify how TruHue handles these cases.

Builders should treat the result label as a conclusion, not as a substitute for the underlying catalog record. The more practical questions are whether a shade can be identified precisely, whether the evidence is current, and whether a user can understand the recommendation’s limits. For a closer look at how seasonal scoring thresholds affect edge cases, see our earlier analysis of shade-scoring thresholds.

What changed, and what remains unknown

The visible development in TruHue’s public materials is the scale being claimed: 735 brands and counts ranging from 40,000+ to 45,000+ products. That is a substantial catalog proposition, but the inconsistent totals make count definitions worth tightening. The materials supplied for this digest establish freemium access and describe a free color analysis quiz and app; they do not establish a pricing change or a new release.

They also do not reveal the mechanics behind what readers might call TruHue architecture: ingestion, shade-level identifiers, image review, refresh cadence, or scoring rules. It would be a mistake to invent those details from a product page. The useful lesson for anyone building beautytech color indexing is narrower and more durable: define what you count, distinguish product from shade, and make uncertainty part of the system rather than hiding it behind a tidy label.

More from TruHue News