The Complete Compliance Checklist for Cosmetics Brands Selling in European Retail
A joint guide by LabelCheck × Syncra — covering label compliance and product data compliance
Getting a cosmetic product onto a European retailer's shelf requires two types of compliance: your physical label must meet EU regulations, and your product data must meet retailer onboarding standards. This guide covers both.
Part 1
EU cosmetic label compliance
The 14 label checkpoints, 2023/1545 allergen updates, language rules, and country-specific packaging requirements.
Part 2
GDSN product data compliance
Country-by-country data pool expectations, common rejection reasons, and a pre-submission validation checklist.
Part 1
EU Cosmetic Label Compliance (by LabelCheck)
Article 19 of EC 1223/2009 is often quoted as a short list, but in practice brands need a deeper operational checklist. At LabelCheck, we break label review into 14 checkpoints so that pack artwork, regulatory copy, and market-specific exceptions are validated before the retailer flags them.
Responsible Person name and EU address
Articles 4 and 19(1)(a)
Show the legal entity responsible for the cosmetic product and a valid EU or EEA postal address on pack.
Country of origin for imported products
Article 19(1)(a)
If the finished product is manufactured outside the EU, the label must state the country of origin clearly.
Batch or lot number
Article 19(1)(b)
Every unit needs a traceable batch code so authorities and the Responsible Person can isolate the exact manufacturing run.
Date of minimum durability where shelf life is under 30 months
Article 19(1)(c)
Short-shelf-life products need a best-before style date using the required format and symbol.
PAO symbol where shelf life is over 30 months
Article 19(1)(c)
Longer-life products must show the open-jar symbol with the number of months the product remains safe after opening.
Precautions and warnings
Article 19(1)(d)
Carry forward every mandatory warning tied to the product category or formula, especially for dyes, aerosols, acids, and sun products.
Instructions for use where needed
Article 19(1)(d)
If incorrect use could create a safety issue, the pack or insert must explain how to use the product safely.
Nominal content
Article 19(1)(f)
State the net quantity in metric units that matches the consumer unit actually sold in retail.
Product function
Article 19(1)(f)
If the product function is not obvious from presentation, call it out directly on pack.
Ingredient list with correct INCI nomenclature
Article 19(1)(g)
List ingredients under the 'Ingredients' heading using official INCI names in the correct order.
Fragrance allergen declarations
Article 19(1)(g) and Annex III
List the reportable fragrance allergens separately when they exceed the applicable leave-on or rinse-off thresholds.
Nanomaterial disclosure
Article 19(1)(g)
Ingredients present in nanoform must be followed by '(nano)' in the ingredient list.
Refer-to-insert symbol where information moves off pack
Article 19(2)
If information has to sit on a leaflet, tag, or card because of pack size, the pack must direct the shopper there with the correct symbol.
Target-market language coverage
Article 19(5)
Warnings, function, and usage copy must appear in the official language or languages required in the country where the product is sold.
The updated allergen requirement is the big 2026 deadline
Regulation (EU) 2023/1545 expanded the fragrance allergen list from the legacy 26 substances to more than 80 reportable allergens. For brands selling leave-on products, the disclosure threshold remains 0.001%. For rinse-off products, it remains 0.01%.
The enforcement dates matter. New products placed on the EU market must comply by July 31, 2026, and products already on the market have until July 31, 2028. In practical terms, every fragrance blend, essential oil, and botanical-rich formula needs a fresh cross-check against the final label artwork.
If you are still relying on a fragrance house document created under the older 26-allergen framework, your retail label review is already lagging behind formulation reality.
Country-specific rules still block otherwise compliant packs
EU-wide cosmetic law is only part of the job. Packaging, language, and local retailer expectations still vary by destination market, which is why our reviews always pair EC 1223/2009 with the target market you actually plan to sell into.
| Market | Watch item | Why it matters |
|---|---|---|
| France | Triman + Info-tri | If you sell cosmetics in France, packaging rules sit on top of cosmetic law. The Triman logo and sorting instructions are a common miss for brands shipping cross-border into Amazon.fr or French retail. |
| Belgium | French + Dutch at minimum in practice | Belgium is one of the easiest places to get caught by language assumptions. If the mandatory text is incomplete in the relevant local language set, retailers and inspectors can stop the product. |
| Finland | Finnish + Swedish | Multi-language labels are often unavoidable. Tiny packs usually need inserts or booklet labels if the content cannot be made legible on the primary container. |
| Germany, Italy, Spain | Local-language mandatory text | Do not treat English as a universal fallback. Retail buyers expect the customer-facing copy to match the local market version of the pack. |
Common mistakes we keep finding in market audits
Our Amazon.fr face cream audit is a useful reality check: all 3 products had issues, and the average score was 10 out of 14. Even established brands miss the updated allergen logic, French packaging overlays, or basic INCI quality control.
Allergen declarations are the fastest-moving failure point
In our public audit of 3 best-selling face creams on Amazon.fr, all 3 products had allergen-related findings. The July 31, 2026 deadline for new products under Regulation (EU) 2023/1545 is pushing brands to revisit fragrance houses, botanical extracts, and legacy pack copy now.
Cross-border French packaging still misses Triman
Two of the three audited products sold cross-border into France lacked a visible Triman symbol on the listing imagery. That is exactly the kind of issue that slows retailer approval or triggers a marketplace clean-up later.
Small INCI errors signal bigger QA gaps
Our Amazon audit found incorrect INCI spellings and duplicate ingredient entries. Those are not cosmetic typos; they are evidence that the label file, formula source, and approval process are out of sync.
If you want the broader failure pattern, our 10 common EU cosmetic label mistakes and full EU label guide go deeper on each rule.
Check your label before the buyer does.
LabelCheck reviews your pack against EU cosmetic label requirements, updated allergen rules, and country-specific issues like French retail packaging markings.
Check your label →Part 2
GDSN Product Data Compliance (by Syncra)
We are publishing Syncra's GDSN section below with the same structure and CTA they shared for this joint guide.
GDSN Compliance for Cosmetics Brands Selling in European Retail
Label compliance is only half the job of getting a cosmetics product onto a European retailer's shelf. Once the pack artwork, INCI list, claims, and responsible person details are correct, retailers still need the product data in the format their systems can accept. That is where GDSN comes in.
GDSN, the Global Data Synchronisation Network, is the GS1 standard for exchanging product master data between brands, distributors, and retailers. In practice, if you want to sell through Carrefour, Tesco, Albert Heijn, Colruyt, Eroski, or Esselunga, your buyer will usually expect GDSN-compliant product data through the relevant country data pool. A compliant label helps you pass regulatory review. GDSN-compliant data helps you pass retailer onboarding and stay live once the product is listed.
For cosmetics brands, that means one thing: if your label says one thing and your GDSN record says another, the listing gets delayed, rejected, or flagged for manual review.
What cosmetics brands need in GDSN
Cosmetics are not as nutrition-heavy as food, but they still require a complete, retailer-ready product data set. At minimum, brands should expect to maintain:
- Core trade item identification: GTIN, brand, sub-brand, product description, functional name, target market, and information provider GLN
- Correct cosmetics classification: the right GPC category for the specific product type, not a generic beauty catch-all
- Ingredients and INCI data: the same ingredient declaration used on pack, in the same order, carried into product data so retailer content teams do not have to re-key it manually
- Regulatory reference fields: for EU products, the relevant cosmetic notification reference such as the CPNP record, plus the responsible person details that support market access workflows
- Net content and unit of measure: for example 30 ml, 50 ml, or 200 ml, exactly aligned with the consumer unit on pack
- Packaging dimensions and logistics data: height, width, depth, gross weight, case configuration, and packaging type for ecommerce and shelf planning
- Hazard or handling attributes where applicable: especially for flammable aerosols, acetone-based removers, or other cosmetic products that trigger additional transport, storage, or hazard handling checks
The practical rule is simple: your GDSN record should mirror the approved label in structured fields.
Country-by-country GDSN requirements for cosmetics
The GS1 data model is global, but each market applies it through its own data pool and local retailer expectations.
| Market | Data pool | What cosmetics brands should validate |
|---|---|---|
| France | PARANGON | French-language consumer-facing attributes, especially product name, usage text, and ingredient declaration. French retailers also tend to check that the ingredient and allergen-related text is formatted consistently with the pack copy they review. |
| Germany | 1WorldSync | Cosmetics do not use food nutrition fields such as dual kJ/kcal, but German recipients still scrutinize description quality, ingredient listing format, and the correct use of non-food classification and measurement fields. |
| Spain | AECOC | Spanish translations are expected for customer-facing attributes. If the physical pack for Spain differs from another EU market, the Spanish GDSN record should reflect that version rather than a generic EU master. |
| Italy | GS1 Italy | Italian-language product attributes matter, especially name, usage instructions, and marketing text shown downstream in retailer content systems. Cosmetics brands should also keep pack copy and image assets aligned with the Italian data set. |
| United Kingdom | productDNA | Post-Brexit workflows require extra care. If you sell into Great Britain and Northern Ireland, keep market-specific records straight, including the correct responsible person setup and any UK-specific notification references where applicable. |
| Netherlands | GS1 Data Source | Dutch-language consumer fields are commonly expected for product descriptions and usage text. Clean dimensions, net content, and packaging data are particularly important because Dutch retailers often reuse GDSN data across ecommerce and logistics flows. |
| Belgium | My Product Manager | Belgium is the market most likely to force duplication of content work, because key consumer-facing fields usually need both Dutch and French. If one language set is missing or shorter than the other, the record often gets held for review. |
For cosmetics brands, the operational takeaway is that one EU master record is rarely enough. The underlying product may be the same, but language, responsible person details, notification references, and retailer content expectations still vary by destination market.
Common GDSN rejection reasons for cosmetics
Most cosmetics rejections are not caused by a single catastrophic error. They happen because product data is incomplete, inconsistent, or too generic for the target market. The most common issues include:
- Wrong GPC classification: a face serum, deodorant aerosol, and shampoo should not all sit under the same broad category
- Incomplete ingredient declarations: the label may have a full INCI list, but the GDSN record contains a shortened marketing version or an outdated formula
- Missing regulatory references: CPNP details, responsible person data, or market-specific compliance notes are absent or mismatched
- Missing hazard or handling information: especially for aerosols, alcohol-heavy products, or removers that require extra storage or transport handling fields
- Dimensions and net content do not match pack: the unit on shelf is 50 ml, but the product data says 1 ea or uses the wrong measurement code
- Language gaps: the record is technically complete, but the target market requires French, Spanish, Italian, Dutch, or Dutch plus French text
These are the errors that slow down retailer onboarding. Retailers usually send the record back and expect the supplier to correct it upstream.
How to get compliant before submission
The best way to avoid rejections is to treat cosmetics GDSN publication as a validation process, not a one-time upload. Before sending data to any pool, run through this checklist:
- 1. Validate the identifiers: confirm GTIN, GLN, target market, and brand ownership are correct.
- 2. Lock the approved ingredient source: use one source of truth for the final INCI list and push that exact version into product data.
- 3. Populate regulatory fields early: include CPNP or other market-specific notification references, plus responsible person details, before retailer review starts.
- 4. Check the product classification: make sure the GPC matches the actual cosmetic type and selling unit.
- 5. Measure the sellable unit and case accurately: height, width, depth, gross weight, and net content should match the physical product.
- 6. Create market-specific language variants: do not rely on one English master record for France, Spain, Italy, the Netherlands, or Belgium.
- 7. Validate exception products separately: aerosols, flammable products, gift sets, and multi-packs often fail for reasons standard skincare units do not.
- 8. Run a pre-submission audit: catch missing fields, bad mappings, and local-market gaps before the retailer or data pool does.
This is where automation makes the difference. Syncra validates product records against country-specific GDSN expectations and flags missing fields before submission.
Check your cosmetics product data for free →Conclusion
Label compliance + data compliance = shelf-ready. Use LabelCheck for your labels, Syncra for your product data.