EU Market Surveillance Regulation EUPCN, ICSMS, and Safety Gate
The EU Product Compliance Network coordinates market surveillance practice, ICSMS records and exchanges market surveillance information, and Safety Gate circulates rapid alerts for dangerous non-food products.
This page helps prepare product files, contact points, traceability data, and response evidence before an authority request, ICSMS case, border hold, or serious-risk alert.
coordinates authorities and the Commission; it is not an operator case-submission channel. is the authority information and communication system for market-surveillance checks, cooperation, measures, and relevant customs records. circulates alerts about dangerous non-food products. For dangerous consumer products, operators use the separate Safety Business Gateway where Regulation (EU) 2023/988 requires notification.
1
Section 1
What each system is for
Treat as the coordination layer, not as a case inbox for operators. Regulation (EU) 2019/1020 established the Network to structure cooperation between Member State enforcement authorities and the Commission, coordinate market-surveillance practice and ADCO activity, and advise on further development of and the Article 34 information system. Its own decisions are legally non-binding recommendations.
Treat as the authority information layer. Its restricted area supports exchange of investigated-product data, test results, economic-operator information, accident information, measures, and documented checks. Its public area exposes selected product and non-compliance information, not the authorities' internal documents or exchanges.
Treat as the rapid-alert layer for dangerous non-food products. National authorities circulate alerts describing the product, the risk, and measures taken by an economic operator or ordered by an authority, and other countries follow up if the same product is found on their markets.
What is the difference between , , and ?
coordinates market surveillance authorities and the European Commission. is the authority system for recording and exchanging product investigations, checks, tests, operator details, and measures. rapidly circulates alerts about dangerous non-food products and the measures taken. A single product issue can involve all three, but each has a different purpose.
Can an economic operator file a product case directly in ?
No. Market surveillance authorities, single liaison offices, the European Commission, and designated border-control authorities use the restricted area. An economic operator supplies evidence to the requesting authority; the authority decides what to record or exchange in ICSMS. Selected product and non-compliance information may later appear in the public area.
Is the same as the Safety Business Gateway?
No. Authorities use to exchange rapid alerts. Businesses use the Safety Business Gateway for notifications required under the General Product Safety Regulation, including notifications about dangerous consumer products. Keep the authority alert and the operator submission separate in the case record.
Use context when a case points to coordinated EU surveillance priorities, joint activities, ADCO work, or Network guidance.
Use readiness when an authority may request technical documentation, compliance data, test results, product identifiers, supply-chain details, or corrective-action evidence.
Use readiness when a dangerous product, recall, withdrawal, online removal, consumer warning, or serious-risk measure may need rapid cross-border circulation.
is used when market surveillance information helps authorities assess, coordinate, or document enforcement activity. Regulation (EU) 2019/1020 requires product-case information to be entered for in-depth compliance checks, including product identity, test or check results, economic-operator details, and corrective action. Authorities also use the system's standard forms for cross-border information and enforcement requests. The 30-day Article 22 period applies to the requested authority's information response, not to an economic operator's separate response deadline.
is used for rapid circulation of dangerous-product measures. Regulation (EU) 2019/1020 calls the rapid system RAPEX and provides an interface with the Article 34 information system to avoid double data entry. Regulation (EU) 2023/988 renamed it the Safety Gate Rapid Alert System and requires Member States to submit Article 20 notifications through it. Where a serious-risk measure or its effects go beyond one Member State, the authority notifies the Commission immediately; follow-up measures for the same product are also shared through the system.
The practical difference for a company is the evidence package. An -related request is often about proving compliance, tracing the product, and showing corrective action. A situation is also about speed: identifying affected product, risk, markets, measures, consumer communications, recall status, and whether online offers or listings must be removed or warned against.
Prepare product identifiers that match packaging, labels, online listings, declarations, test reports, batches, serial numbers, software or firmware versions, and supplier records.
Keep a response log that separates authority requests, documents supplied, samples or tests, risk assessment, operator decisions, ordered measures, voluntary measures, and public communications.
If a serious risk is suspected, preserve the risk analysis, incident evidence, distribution map, affected units, corrective-action rationale, recall notice drafts, and proof of marketplace or channel actions.
is an authority-and-Commission coordination network. Market surveillance authorities enter product information in , and Member States submit MSR Article 20 notifications through . Economic operators must cooperate with market surveillance authorities on actions that eliminate or mitigate product risks and may have to supply documents, technical specifications, compliance data, supply-chain details, and technical product information needed for assessment. A company should not describe its internal case record as an ICSMS filing or an MSR Safety Gate notification; a separate operator submission through the Safety Business Gateway can be required under the GPSR for dangerous consumer products.
Build the file around the product as sold in the EU, not around a generic model name. The record should show the responsible economic operator, applicable Union harmonisation legislation, declarations, technical documentation index, standards or test evidence, online offer data, importer or fulfilment-service-provider details where relevant, distribution footprint, and current corrective-action owner.
For serious-risk readiness, link product identification to customer and channel reach. and GPSR recall practice depend on being able to identify the affected product, explain the hazard and risk, identify measures already taken, and show how consumers, distributors, marketplaces, and authorities were reached.
Maintain one authority-response pack per product family with EU role mapping, contact points, declarations, test evidence, instructions, labels, online listings, batch data, and supplier traceability.
Define who can approve a risk assessment, voluntary corrective action, recall notice, marketplace removal, Safety Business Gateway submission, and authority response.
Keep evidence of actions taken: stop-sale instructions, withdrawal or recall records, consumer warnings, repair or remedy scripts, marketplace takedown confirmations, distributor notices, and post-action verification.
The same issue can move across layers. A national authority may investigate and document a product in , a serious-risk case may trigger circulation, and or ADCO activity may shape coordinated surveillance themes. Operators should therefore avoid fragmented files where product compliance, incident response, customer communications, and marketplace actions live in separate systems with no shared identifier.
Keep one case record that can support both compliance assessment and rapid-response work. It should tie the product, risk, evidence, affected markets, operator role, authority correspondence, and corrective measures to the same product identifiers. That makes it easier to answer a document request, explain a risk decision, prove follow-through, and reconcile public information with evidence records.
Do not assume that a alert is only a public-relations event or that is only an internal authority database. Both can expose gaps in traceability, role assignment, test evidence, online offer control, and recall execution. The practical control is to be able to produce a complete, dated, cited evidence trail quickly.
Use exact product identity in every response: model, batch or serial range, version, image, listing URL, brand, importer, manufacturer, responsible person where applicable, and affected EU markets.
Separate facts from decisions: test findings, incident reports, risk assessment, legal basis, authority order, voluntary measure, and management approval should be distinguishable.
After action is taken, keep verification evidence showing that products were withdrawn, recalled, relabelled, repaired, blocked at the border, removed from online offers, or otherwise risk-mitigated.
Prepare one evidence pack for ICSMS and Safety Gate response
Connect product identity, risk assessment, technical evidence, distribution data, online offers, authority correspondence, and corrective-action proof before a market surveillance request becomes a rapid-response case.
Consolidated text current from 23 May 2024 for the EU Product Compliance Network, Article 34 information system, Article 20 serious-risk exchange, customs cooperation, authority powers, and operator cooperation.