- Supports evidence updates because Safety Gate notifications include corrective measures, product identity, traceability information, reported accidents, and updates to measures.
"any update, modification or withdrawal"
Use this workflow when a complaint, test result, accident report, marketplace notice, authority contact, or supplier escalation suggests that a consumer product made available in the EU may be dangerous.
It keeps the triage focused on GPSR duties: incident intake, risk assessment, Safety Business Gateway notification, withdrawal or recall decisions, consumer communications, marketplace coordination, and evidence records.
Structured answer sets in this page tree.
Cited legal and guidance references.
Open a GPSR incident file when an accident, complaint, test failure, marketplace report, supplier notice, authority request, or monitoring signal suggests that a consumer product may be a . The GPSR has applied since 13 December 2024. The file should identify the product and affected market, separate the accident-notification test from the dangerous-product test, assign the responsible actor, record each corrective measure, and preserve the evidence behind the decision.
Confirm the legal scope at intake. The GPSR is the baseline for consumer products and products likely to be used by consumers, but Article 2 excludes specified categories and limits the GPSR where product-specific EU safety law regulates the same risk. A harmonised product may also have a separate vigilance or incident regime, so record the applicable instrument and do not assume that one submission satisfies every reporting duty.
Open a case as soon as the signal alleges a safety issue, accident, or . Record the product exactly as it is sold: name, brand, type, model, batch or serial number, barcode, packaging description, images, listing URL, marketplace offer identifier, countries where it was made available, and the economic operators in the supply chain.
Classify the notifier role before anyone submits through the Safety Business Gateway. Submissions are reserved for economic operators and online marketplace providers concerned by the product; the Commission manual says third-party submissions are prohibited. For accidents, importers and distributors inform the manufacturer without undue delay, the manufacturer submits or instructs one of them to submit, and a responsible person that knows of the accident ensures submission when the manufacturer is outside the EU.
The triage owner should separate three questions: what is the defect or safety issue, how the issue can lead to harm, and what evidence supports the risk level. Under Article 3, risk combines the probability that a hazard causes harm with the severity of that harm; serious risk is the category that requires rapid authority intervention, even when effects are not immediate. The Safety Business Gateway form captures a safety description, risk category, risk level, and available laboratory, visual-test, certificate, or risk-assessment material.
Do not delay notification solely because the team has not completed a formal risk assessment. The Safety Business Gateway manual states that determining the risk level is not required for notifying a ; if the notifier cannot assess the level, the form allows an Unknown risk level. Market surveillance authorities can reach a different conclusion from the notifier's grading.
Article 20 applies when an occurrence associated with use of the product resulted in death or serious adverse effects on an individual's health and safety, whether permanent or temporary, including injuries, other bodily damage, illness, or chronic health effects. The manufacturer must ensure notification through the Safety Business Gateway to the authority in the Member State where the accident occurred, without undue delay from when it knows of the accident.
A case that does not meet Article 20 can still involve a . Apply the role-specific notification duties in Articles 9 to 12 and 22 separately. Submit the available core facts without treating an unfinished risk grade as a reason to delay, then keep the Case ID, submission number, submitted copy, translation status, authority correspondence, and later updates in the evidence record.
Keep product identity, risk evidence, Gateway submissions, corrective actions, recall notices, marketplace actions, and follow-up records together.
Once the product is treated as dangerous or potentially dangerous, assign a corrective-action owner and decide which measure removes the risk or, where that is not possible, mitigates it. A withdrawal prevents a product in the supply chain from being made available on the market. A recall aims to return a product that has already been made available to consumers.
A single case may need more than one action. For example, the team may withdraw unsold inventory, recall units already with consumers, warn consumers about safe use while replacement parts are prepared, and ask marketplaces to remove or disable offers. Keep each action separate with scope, duration, responsible company, start date if available, results, and the consumer-facing message.
When recall information is provided in writing, GPSR Article 36 requires a recall notice that consumers can easily understand in the language of each Member State where the product was made available. The notice should help consumers identify the product, understand the hazard, stop using it, obtain the remedy, and contact the business for more information.
Avoid phrasing that lowers perceived risk. The GPSR and the recall-notice template warn against words such as voluntary, precautionary, discretionary, in rare situations, in specific situations, or statements that there have been no reported accidents. The notice should be accessible and, online, essential identification information shown in pictures should also be available as machine-readable text.
"any update, modification or withdrawal"
"WHY IS THIS PRODUCT DANGEROUS?"
"interoperable interface"
"report dangerous products and accidents"
"publishing information on product safety recalls"
"Each action should be clearly described"