Product Data for Skincare: Explaining Ingredients and Efficacy

In most retail categories, a customer buys a brand, a price and a look. In skincare, they buy an effect. A serum sells because it contains 10% niacinamide, because it suits oily and blemish-prone skin, because it targets fine lines. The product data that closes the sale is not the SKU or the price — it's the ingredients and what they do. And that's exactly the data that arrives in the worst possible shape.

Product data for skincare is data about ingredients and efficacy: INCI lists, active concentrations, skin type and effect — the attributes that actually drive the purchase. This is a focused corner of the broader beauty & cosmetics data challenge, and it has its own specific pain: the most valuable information hides inside a legally-formatted ingredient string that no shop filter can read as delivered.

What makes ingredient and efficacy data so hard to handle?

The core skincare attributes are unusually rich — and unusually unstructured on delivery:

• INCI lists: the legally-ordered string of Latin ingredient names on every product. Perfect for regulatory compliance, useless as a filter — a customer searches „hyaluronic acid“, not „Sodium Hyaluronate“.
• Active concentrations: „10% niacinamide“, „0.3% retinol“ — the number that sells the product, often buried in a datasheet or missing entirely from the feed.
• Skin type & concern: dry, oily, combination, sensitive; anti-aging, blemish, hydration — the filters customers actually shop by, rarely delivered as clean attributes.
• Application & routine: AM/PM, before/after other steps — context that turns a spec into a reason to buy.

None of this is a simple column in most supplier files. The job is to parse and derive it — to turn one INCI string into a set of structured, filterable attributes plus content that explains them. That's a consolidate, normalize and enrich problem with a heavy enrichment tail.

What does the delivery actually look like — GDSN plus indie Excel?

Skincare data arrives on two very different tracks, and most retailers carry both at once:

• Big brands via GDSN: large, listed cosmetics brands feed the GDSN (Global Data Synchronisation Network) with clean master data, GTINs and often INCI and regulatory fields. The branded core is relatively well-served.
• Indie and naturals labels via Excel/PDF: the fast-growing indie segment ships spreadsheets with inconsistent columns, unparsed INCI strings and zero sales content. Here you are effectively the data producer.

So even where GDSN does its job, it hands you a clean record — not a shoppable one. The efficacy story, the skin-type filters and the readable content all still have to be built. And for the indie longtail, even the clean record is missing.

How does Productbay turn ingredients into structured attributes and content?

The throughline is a three-step job, and skincare leans hardest on the middle step — and that's exactly what Productbay is built for:

• Consolidate: import every source once — GDSN feed, supplier Excel, PDF datasheet, feed URL, FTP, API — and match by GTIN or SKU so existing products update and new ones are created. GDSN brands and indie spreadsheets land in one catalog.
• Enrich: AI parses INCI lists into structured ingredients, maps them to plain-language benefits, derives skin-type and effect attributes, extracts active concentrations, reads specs out of PDF datasheets, translates via DeepL, and drafts efficacy descriptions — always into a review queue, so your team controls regulatory and efficacy claims before anything goes live.
• Publish: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp), and feed exports for Amazon, OTTO and Kaufland — each with per-channel transformations.

The result: an INCI string becomes a set of searchable ingredient filters, a raw indie spreadsheet becomes a structured product with skin-type and effect attributes, and every SKU carries content that actually explains what it does. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs. For the full category picture, see product data in beauty & cosmetics retail.

Frequently Asked Questions