A retailer's guide to shade, ingredient, and claim data in beauty
Beauty shoppers ask five questions before buying: shade, finish, ingredients, claims, wear. Here's what happens when your product page can't answer them.
A shopper looking at a lipstick online can't swatch it, can't smell it, and can't ask a store associate whether it'll survive lunch. Your product page has to answer every question a counter associate would answer, or the shopper returns the product, files a complaint, or just buys from someone whose page did the job. Here's what a beauty PDP actually needs, using a lipstick as the working example.
The five questions every beauty shopper is silently asking
Before checkout, a beauty shopper is looking for answers to roughly the same five questions, whether they're buying lipstick, foundation, or a serum:
- Will this match me? Shade name, shade number, undertone (warm/cool/neutral), and how it compares to a shade they already own.
- What will it feel/look like on? Finish (matte, satin, gloss, metallic), texture, and whether it transfers or settles into lines.
- What's actually in it? Full ingredient list in standard INCI naming, not a marketing summary.
- Can I trust the claims on the label? "Cruelty-free," "clean," "vegan," "paraben-free," "non-comedogenic" — these need to mean something specific, not just sound good.
- How long will it last, and what if it doesn't work for me? Wear time, and a clear return/exchange path for a shade that looked right on screen and wrong in person.
A raw supplier feed answers maybe two of these. The rest gets left as a marketing paragraph, or left out entirely.
Before and after: one lipstick listing
Here's a realistic before/after for a single matte lipstick SKU, going from a typical vendor feed to an enriched listing.
| Attribute | Raw feed | Enriched listing |
|---|---|---|
| Title | "Lipstick Red" | "Matte Lipstick — Brick Red 04, Warm Undertone" |
| Shade data | None | Shade name, shade number, undertone family, closest-match note ("similar depth to MAC Ruby Woo, cooler undertone") |
| Finish/texture | None | Matte, non-drying formula, low transfer, buildable coverage |
| Ingredients | "See packaging" | Full INCI list, ordered by concentration, with top irritant-risk ingredients flagged (fragrance, specific dyes) |
| Claims | "Cruelty-free" (unlinked) | Cruelty-free (Leaping Bunny cert. number), vegan (no beeswax/carmine), paraben-free — each claim tied to a verifiable standard |
| Size/net weight | Missing | 3.5 g / 0.12 oz |
| Wear/use | Missing | 6-8 hour wear claim, application tips, patch-test note |
That middle column — "See packaging" — is the actual state of a huge share of beauty catalogs today. The ingredient list exists; it's just sitting on a physical box, not on the page where the purchase decision happens.
Why these specific gaps cost you money
Beauty already runs a wider return-rate band than most categories. Return-rate benchmarks for beauty and personal care generally sit in the mid-single digits to low double digits, with color cosmetics — foundation and lip color especially — pulling toward the high end because of shade mismatches and skin-sensitivity reactions. Shade guesswork is consistently named as one of the top drivers: industry accounts describe Giorgio Armani's Luminous Silk Foundation as one of the most-returned items in prestige beauty specifically because shade selection online was hard to get right.
The mechanism is straightforward. In a store, a shopper swatches on their wrist, asks an associate, and walks out with the right shade. Online, the page has to do all three jobs at once. When shade, undertone, and finish aren't specified precisely, shoppers guess wrong at a meaningfully higher rate, and return.
Missing ingredient data creates a second, quieter cost: pre-purchase support tickets ("does this have fragrance," "is this nut-free"), abandoned carts from shoppers who won't buy without knowing, and post-purchase reactions that turn into refunds instead of repeat purchases.
The claims minefield
Beauty claims carry regulatory weight that a lot of catalogs don't treat seriously enough. A few things worth building into your data model now:
- Ingredient naming is standardized, not optional. Under FDA cosmetic labeling rules, ingredients must be listed by their INCI name in descending order of concentration, with ingredients at 1% or below allowed in any order after that, and color additives listed last. Product pages that paraphrase ("Made with vitamin C") without the INCI backbone create a mismatch between page and package that erodes trust and invites returns.
- Fragrance allergen disclosure is coming. Under the Modernization of Cosmetics Regulation Act (MoCRA), the FDA is working toward a rule requiring individual fragrance allergens to be named rather than folded into the catch-all term "fragrance." The proposed rule is now expected in 2026, with final requirements likely a year or more after that — but brands that start structuring allergen data now won't be scrambling later.
- "Clean," "cruelty-free," and "vegan" all need a receipt. These claims aren't legally defined the same way "organic" is for food. Regulators and platforms increasingly expect a claim to point to something verifiable — a certification body, a specific excluded-ingredient list, a testing policy — not just a badge.
None of this is exotic. It's the difference between a claim and a fact a shopper can check.
The AI shopping agent test
Ask ChatGPT, Gemini, or Perplexity to "recommend a long-wear matte lipstick in a warm red that's fragrance-free." A listing with clean shade, finish, and ingredient data is retrievable and comparable; a listing with "See packaging" in the ingredients field is invisible to that query, no matter how good the product actually is. AI shopping agents parse structured attributes the same way a screen reader does — they can't infer what isn't written down.
A checklist for fixing beauty PDPs
- Every color/shade SKU has a shade name, shade number, and undertone family, not just a swatch image
- Finish and texture are specified in consistent, comparable terms across the catalog
- Full INCI ingredient list is on the page, ordered correctly, not just referenced
- Known allergens and irritant-prone ingredients are flagged, not buried
- Every marketing claim (clean, cruelty-free, vegan, non-comedogenic) is tied to a specific, checkable standard
- Net weight, wear time, and application guidance are present and consistent with the physical label
- Attributes stay in sync as formulas, certifications, or regulations change
Where Anglera fits
Anglera continuously scores your beauty catalog against gaps like these — missing shade or undertone data, ingredient lists that don't match INCI order, claims with no backing standard — and gap-fills and enriches the attributes automatically, whether your data lives in a PIM, a spreadsheet, or nowhere formal at all. Your PIM stores the shade name; Anglera makes sure the undertone, finish, ingredients, and claims are there too, kept current as regulations like MoCRA's fragrance rule move from proposed to final.