UK SCPN Notification Versus EU CPNP: What Exporters And Importers Need To Know

UK Cosmetic SCPN Notification Notification of each cosmetic product made available to consumers in Great Britain through the Submit Cosmetic Product Notifications service. After the UK left the EU, Great Britain established SCPN as its notification route; the EU continues to use the Cosmetic Products Notification Portal (CPNP). Understanding the differences is essential for exporters, importers and logistics partners who handle cross-border cosmetic flows.

The two notification systems share common goals — provide regulators with product identity and responsible person contact details — but they differ in scope, geography and minor data requirements. Exporters shipping to both GB and the EU often need to create separate notifications in SCPN and CPNP and ensure local responsible persons and labelling match the market where the product is offered.

Primary Operational Differences

Key operational differences that affect supply chains include legal territory, responsible person location, and where product technical files are retained.

• Territorial scope: SCPN covers Great Britain (England, Scotland, Wales); CPNP covers the European Union and European Economic Area member states.
• Responsible person location: SCPN entries require a UK-based responsible person for GB; CPNP requires an EU-based responsible person for the EU market.
• Technical documentation: Both regimes assume the responsible person holds the Cosmetic Product Safety Report (CPSR) and product information file, but the location and language of those documents may be market-specific.

How This Affects Exporters And Importers

Exporters must plan for additional administrative steps when a product is sold in multiple jurisdictions. For example, a manufacturer in Asia that used an EU-based authorized representative before Brexit must now appoint a UK-based responsible person for sales into Great Britain or work with a GB importer who accepts that role.

• Dual notifications: Products sold in both markets typically require separate SCPN and CPNP entries unless the responsible person structure covers both territories.
• Label variations: Labels must reflect the responsible person’s contact details and any market-specific language requirements; packaging and batch codes must be aligned with the corresponding notification.
• Customs handling: Shipments to GB that previously relied on EU notifications now need SCPN coverage to avoid customs or enforcement delays.

Practical Compliance Checklist For Cross-Border Supply Chains

Logistics teams should adopt an operational checklist to prevent gaps when moving products between EU and GB markets.

• Confirm responsible persons: Verify the UK responsible person for SCPN and the EU responsible person for CPNP before shipping.
• Maintain separate notification records: Store SCPN and CPNP references in your WMS and link them to SKUs and batches.
• Coordinate label and documentation updates: Ensure label text, responsible person addresses, and CPSR language align with the notified market.

Common Errors When Managing Dual Markets

Frequent mistakes include assuming one notification covers both markets, failing to update SCPN entries after changing the responsible person, and not recording separate batch traceability for each notified market. These errors create practical problems during customs checks and product safety investigations.

• Assumed reciprocity: There is no automatic reciprocity between SCPN and CPNP; each market's notification is independent.
• Incorrect addresses on pack: Using an EU address on products sold in GB can trigger enforcement action if the UK responsible person is not correctly designated.

In short, the UK Cosmetic SCPN Notification is GB’s notification mechanism and is separate from the EU’s CPNP. Exporters and importers must create and maintain the appropriate notification for each market, ensure responsible persons and labelling are aligned with the notified territory, and link SCPN/CPNP references to warehouse records and batch tracking to prevent delays and support rapid incident response.