The Complete Compliance Checklist for Cosmetics Brands Selling in European Retail

Label compliance gets a cosmetics product through regulatory review. GDSN gets that approved product data into retailer systems. If you want to sell through Carrefour, Tesco, Albert Heijn, Colruyt, Eroski, or Esselunga, you need both.

GDSN, the Global Data Synchronisation Network, is the GS1 standard for exchanging structured product data between suppliers and retailers. For cosmetics brands, that means buyer teams do not just review your artwork files and claims. They also expect a retailer-ready product record with the right identifiers, dimensions, classification, ingredient data, and market-specific language fields.

That matters because retailer onboarding is increasingly data-driven. A compliant label on its own is not enough if the data pool record is incomplete, translated incorrectly, or missing the operational fields retailers use for ecommerce, warehouse setup, and in-store listing. In practice, GDSN is how your approved cosmetic product gets from a spreadsheet or PIM into the retailer's actual commercial workflow.

What GDSN means for cosmetics brands

Cosmetics brands often discover GDSN only after a retailer says, "Please send the item through our data pool." At that point, the issue is no longer label design. It is data readiness. Your record needs to describe the sellable unit in a structured format retailers can trust.

For cosmetics, the most important GDSN fields usually include:

• Core identification — GTIN, brand, product description, functional name, target market, and information provider GLN
• Correct product classification — the right GPC for the specific cosmetic type, not a generic beauty placeholder
• Ingredients and INCI data — the pack-approved ingredient declaration in the same order used on pack
• Regulatory fields — details that support compliance review, such as the CPNP reference for EU products and the responsible person setup used for the target market
• Net content and measurements — for example 30 ml, 50 ml, or 200 ml, with the correct unit of measure
• Packaging and logistics data — height, width, depth, gross weight, pack hierarchy, and packaging type
• Hazard or handling attributes where applicable — especially for aerosols, solvent-based removers, and other products that trigger extra transport or storage checks

The key principle is consistency. The GDSN record should mirror the approved label, but in structured fields. If the artwork says one thing and the retailer data says another, the buyer will usually stop the listing until the mismatch is resolved.

Country-by-country GDSN checks for cosmetics

The GS1 model is global, but each market applies it through its own data pool and local retailer expectations. For cosmetics brands selling across Europe, one master record is rarely enough.

For cosmetics brands, the operational takeaway is simple: standardize the product first, then localize the record by market. The base formula may be identical, but language, responsible person details, notification references, and retailer content rules still vary.

Common GDSN rejection reasons for cosmetics

Most cosmetics submissions do not fail because of one dramatic error. They fail because the data is incomplete, inconsistent, or too generic for the target market. The most common rejection patterns are:

• Wrong GPC classification — a face serum, aerosol deodorant, and shampoo should not all sit under the same broad category
• Incomplete ingredient declarations — the label has the full INCI list, but the product data contains an older formula or a shortened marketing version
• Missing regulatory references — CPNP details, responsible person data, or market-specific compliance notes are absent or mismatched
• Missing hazard or handling attributes — especially for aerosols, flammable products, or solvent-based removers
• Net content or dimensions do not match pack — for example the shelf unit is 50 ml, but the data is published with the wrong measurement code
• Language gaps — the record is technically complete, but the target market needs French, Spanish, Italian, Dutch, or Dutch plus French text

These are the errors that slow retailer onboarding. Even if a retailer could fix them manually, they usually will not. They send the record back and expect the supplier to correct it upstream.

How to get compliant before submission

The best way to avoid delays is to treat cosmetics GDSN publication as a validation process, not a one-time upload. Before sending a record to any pool, use this checklist:

1. Validate the identifiers — confirm GTIN, GLN, brand ownership, and target market.
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 market-specific notification references plus the correct responsible person details before retailer review starts.
4. Check the product classification — make sure the GPC reflects 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 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.

That is where automation helps. Syncra validates cosmetics records against country-specific GDSN expectations, flags missing fields before submission, and helps brands keep one catalog aligned across multiple European markets without maintaining separate spreadsheet workflows for every retailer.