- Articles 1 and 2 support marketplace registration, interface linking, and configuring the frequency and content of Safety Gate Portal information downloads.
"frequency and content"
This workflow is relevant when an online marketplace receives a product-safety notice, a market surveillance authority order, a Safety Gate signal, or accident information about an offer listed through its interface.
The workflow separates authority orders, user notices, voluntary Safety Gate matching, seller notification, consumer recall duties, Safety Business Gateway reporting, and evidence needed before a listing is removed, warned, or reinstated.
Structured answer sets in this page tree.
Cited legal and guidance references.
Article 22 of Regulation (EU) 2023/988 has applied since 13 December 2024 and gives a product-safety response model: maintain contact points and internal processes, act on authority orders within the statutory clock, process product-safety notices, use Safety Gate Portal information, notify sellers and affected consumers where required, immediately report dangerous products through the Safety Business Gateway when the marketplace has actual knowledge, and report qualifying accidents without undue delay when it has been informed of them.
The first response decision is the intake channel. A market surveillance authority order under Article 22(4), a product-safety notice received through the notice mechanism referred to in Article 16 of the Digital Services Act, a Safety Gate Portal match, and accident information do not have the same required action or timing.
Run a scope check at the same time. Article 22 concerns offers of consumer products through an intermediary interface; the product still needs the Article 2 analysis where another EU safety law governs the same risk or a GPSR exclusion applies. Keep the marketplace provider's duties separate from the manufacturer's, importer's, distributor's, responsible person's, and trader's duties.
For an authority order, the marketplace response should mirror the order: remove the content, disable access, or display an explicit warning. For a notice or Safety Gate match, the decision should record why the offer is the dangerous product, an identical offer, a related but unconfirmed match, or outside the cited evidence.
The GPSR sources support fast action and cooperation, but they do not provide a general marketplace reinstatement clock. Treat reinstatement as an evidence decision: the listing should stay removed, disabled, or warned until the order is satisfied, the Safety Gate match is disproved, or the seller and responsible economic operator provide evidence that resolves the product-safety basis for the action. A marketplace's voluntary Safety Gate monitoring does not convert every similar-looking listing into an identical product; the product identifiers and risk evidence still have to support the match.
The two-working-day order limit and three-working-day notice limit come from binding Article 22. Commission Implementing Regulation (EU) 2024/1459 is binding for the interoperable interface. Safety Gate pages and system instructions provide operational guidance, while the intake categories, mismatch examples, closure pack, and reinstatement evidence on this page are Sorena workflow recommendations.
This workflow helps align intake timestamps, authority-order response, product-safety notice handling, Safety Gate checks, seller and consumer notifications, Gateway reporting, and reinstatement evidence.
"frequency and content"
"internal processes for product safety"
"report dangerous products and accidents"
"description of the risk"