PIM for cosmetics and personal care: INCI, CPNP and retail data

What makes product data hard for cosmetics and personal care brands?

Cosmetics data combines regulated ingredient information with fast-moving marketing content. Under the EU Cosmetics Regulation, each product needs a responsible person, a notification in the Cosmetic Products Notification Portal (CPNP) and a label with the ingredient list in INCI names. The same ingredient list must appear on the pack, the web shop, retailer portals and data pools, in the same version.

Four challenges recur in PIMvendors selections:

• Ingredient governance: INCI lists, allergen statements and warnings must match the formula and the notification.
• Shade and size variants: product lines with many shades and sizes, where ingredients can differ per shade.
• Claims: marketing claims about efficacy and sustainability need evidence and approval.
• Retail and marketplace channels: drugstore chains, supermarkets and marketplaces, each with its own data route and template.

The PIM by industry heatmap rates cosmetics high on variants, regulatory data, syndication and DAM intensity. The profile sits close to PIM for food and beverage on regulated label data and retail data pools, and close to fashion on variants and imagery.

Which standards and regulations apply to cosmetics and personal care?

The Cosmetics Regulation defines the regulated data, and GS1 standards define the retail routes. In PIMvendors selections, cosmetics brands typically face this set:

The allergen row deserves a separate plan. Changes to the regulated allergen list mean that many products need relabelling within a transition period. A PIM that holds allergen data per formula can show which products are affected. A PIM that holds allergens as free text cannot.

Decisive requirements for a cosmetics PIM

Four requirements decide most cosmetics selections. They sit mainly in the data model, process and integration domains of the PIMvendors checklist.

1. Ingredient governance: INCI lists and allergen statements as governed data, linked to formulas, with approval and version history.
2. Variant model: line, shade and size levels, with shade-level ingredient exceptions and shade-level media.
3. Claims evidence: each claim linked to supporting evidence and an approver, with a review date.
4. Retail syndication: data pool publication, retailer templates and marketplace feeds, all fed from the same governed data.

AI fits the content layer. PIMvendors' position is that AI is useful for channel-specific descriptions and translation, and unreliable for regulatory data. Ingredient lists and allergen statements need governed sources. The requirements for regulatory product data page covers evidence modelling. Score these requirements with regulatory affairs present, because they own the consequences of a wrong label.

{{list:requirements:PR}}

Three demo scenarios worth running

Run the demo with your own formulas, shades and retailers. PIMvendors' scenario method gives each vendor the same sample data and script.

1. Allergen update: add a newly regulated allergen to 3 formulas, show which products and shades are affected, route the change through regulatory approval and show the update in a retailer feed.
2. Shade launch: add 6 new shades to an existing line, with one shade carrying a different INCI list, and reach completeness for web shop, marketplace and data pool.
3. Claim review: attach evidence to a sustainability claim, set a review date, then expire the evidence and show what happens to the claim in each channel.

Scenario 1 tests the impact analysis that relabelling projects need. Ask the vendor to show the result as a list that regulatory affairs could hand to packaging design. The Demo Theatre scenario library holds the script format.

Shortlist considerations for cosmetics and personal care

Cosmetics brands shortlist on ingredient governance and retail reach together. PIMvendors describes capability profiles instead of vendor names at this stage:

• Syndication-first platforms with data pool and retailer networks: strong retail and marketplace reach. Limitation: ingredient governance and claims evidence can be shallow.
• Enterprise multi-domain platforms: strong governance, variants and multi-market data. Limitation: cost and implementation time for mid-sized brands.
• Mid-market SaaS PIMs with strong variant models: good usability and fast launches. Limitation: regulatory approval workflows often need configuration.
• Regulatory or formulation systems with product data output: strong ingredient and notification data. Limitation: weak channel content and syndication.

Most brands combine a formulation or regulatory system with a PIM. Test the hand-off of an approved INCI list in the demo. The hand-off is where copy errors start, so it deserves its own acceptance test in the contract. The vendor directory lists vendors alphabetically.

Composite pattern: a skincare brand preparing for allergen relabelling

This composite pattern combines situations PIMvendors sees regularly, and it describes no single client. A skincare and haircare brand sells around 1,200 sellable items in 10 European markets through drugstores, supermarkets, marketplaces and its own web shop. INCI lists live in the formulation system, but marketing copies them by hand into the web shop and retailer portals.

The selection started as a marketplace expansion project. The allergen labelling change turned the priority around. The team first listed which data was regulated, which system owned it, and how many products each formula fed. That work showed that copied ingredient lists were the biggest risk.

The requirements put an integration from the formulation system to the PIM first. The demos ran on the three scenarios above. The decisive scenario was the allergen update: one vendor could not show which shades were affected by a formula change.