How long does it take before Safety Gate publishes a notification?
The regulation does not set a fixed deadline for how many days a notification must appear on the Safety Gate portal. The processing time depends on the competent authority that assesses the notification, on the completeness of the information it receives, and on how serious the reported risk is assessed to be. A notification with a clear product description, type and batch numbers, and a substantiated risk description can be processed faster than a notification about which the authority must first ask questions.
In practice, companies experience delays mainly because the information they provide is incomplete or unclear. Not because the law sets a specific deadline for this, but because the supervisory authority can only assess and publish once the picture is complete. Anyone wishing to understand this process is well advised to first look at the role they have in the chain, because that role determines who must provide which information and to whom.
What Safety Gate is, and what it is not
Safety Gate is the public portal on which the European Commission brings together notifications that Member States forward about products presenting a risk, including the measures taken such as a recall or a sales stop. It is not a system in which a company publishes directly. An undertaking notifies the competent authority in the relevant Member State or States via Safety Business Gateway; that authority assesses the notification and determines whether and how it is forwarded to the European portal. There is an assessment step in between that can differ per country and per case, and we do not make any estimate about it.
Where the processing time gets stuck in practice
The most common bottleneck is a notification that is not substantively complete. Think of a product description without a clear type or batch number, so the authority cannot determine which units are involved. Or a risk description that names the problem but does not substantiate it, causing additional questions to follow first. Companies that have their internal file in order — with a risk analysis, the technical documentation, and a summary of previous complaints — can usually answer those questions faster than companies that have to compile these documents afterwards.
A second bottleneck lies in coordination between multiple parties in the chain. When an importer, a distributor, and an online retailer each have part of the information, it takes time to bring that information together before the notification is complete. Those who know in advance which party manages which data save that step. the free role check that clarifies your position in the chain provides a first direction for that.
A third bottleneck is that companies wait until an incident occurs before thinking about what a notification should look like. An internal compliance system in which complaints are systematically recorded makes it possible, when making a notification, to immediately draw on previously gathered data, rather than having to reconstruct it under time pressure.
What is and is not established
What is established: the regulation requires businesses to report relevant information about a risk to the competent authority, which then assesses and publishes it via Safety Gate. What is not established, and on which we also make no statement: how much time an individual authority needs to assess a specific report, and whether and how strictly it applies its assessment. This varies by Member State, by product category, and by file, and is outside what we as a platform can or wish to assess. For a concrete report, the competent enforcement authority in the Member State in question is the appropriate party to contact with questions about the status.
What a business can control is the preparation. A product file per item, with a structured risk analysis and the underlying technical documentation, is then already ready instead of having to be compiled under time pressure. More on how such a file is structured and which documents belong in it can be found in the knowledge base with explanation per obligation.
Prepare instead of waiting
Most delays in a report do not occur with the enforcement authority, but with the business itself: data that is not centrally recorded, documents that must be requested from a supplier, or a complaints register that is not up to date. This is precisely the moment when the difference lies between a file that is already in place and a file that still has to be assembled. How we structure the information on gpsria.eu and what it is based on is explained on the page about how we source our information.
If you want to know which role you hold in the supply chain and what obligations follow from it, the free role check provides an initial indication for that. For the broader explanation per subject, from risk analysis to complaints register, you can also go through the frequently asked questions or start the free quick scan to see where your situation fits.