GPSR Article 22 adds product-safety duties for online marketplaces and ties several of them to DSA mechanisms, including orders, notices, trader information, repeated non-compliance, and product-safety information in listings.
This comparison helps separate the GPSR product-safety file from the DSA marketplace workflow, especially for dangerous products, online-interface takedown, listing data, recalls, accident reports, and evidence.
Start with Article 22 when an online marketplace case concerns a dangerous consumer product. It adds product-safety duties and imports selected procedures; it does not replace the DSA or reduce the platform's other DSA duties. For this comparison, separate the product-safety decision from the platform process for listings, orders, notices, trader information, repeated non-compliant traders, recalls, consumer warnings, accident notifications, and evidence.
Side-by-side comparison
GPSR vs DSA marketplaces: dangerous-product comparison
A scope-bounded comparison of marketplace duties and the mechanisms that GPSR Article 22 references for dangerous products offered online.
controls the consumer-product safety question: whether a product is safe, dangerous, recalled, withdrawn, subject to a safety warning, or reportable through Safety Business Gateway or Safety Gate workflows.
Second framework
DSA marketplace touchpoints
The side is limited here to the mechanisms Article 22 references for marketplaces: contact points, orders, notices, listing information, trader self-certification, and suspension of frequent non-compliant traders.
GPSR vs DSA marketplaces: dangerous-product comparison
asks whether a consumer product made available on the EU market is safe, dangerous, non-compliant, recalled, withdrawn, or subject to a safety warning or accident report.
The -referenced marketplace question is narrower: whether the online platform process for product-safety orders, notices, listing information, trader commitments, or repeated non-compliance has been triggered.
Open the case under when the fact pattern is a product-safety risk; add the -referenced marketplace track only for the platform process that handles the offer.
gives market-surveillance authorities a product-safety route to require removal of content for an offer of a dangerous product, disabling access to it, or displaying an explicit warning.
requires marketplace interfaces to let traders provide specified product-safety information for each offered product and to display it or make it easily accessible to consumers on the listing.
The supplies two related controls. Article 31 requires marketplaces to design their interfaces so traders can provide Article 30 information, and Article 22(9) adds the product-safety fields. GPSR Article 22(10) separately requires the trader's DSA Article 30(1) self-certification before the offer is published.
Listing QA should test product-safety fields, trader information, product identifiers, warnings, and displayed accessibility before the listing goes live.
says marketplace providers must process notices related to product-safety issues for products offered online without undue delay and in any event within three working days of receipt.
The touchpoint is the notice channel: identifies notices received in accordance with DSA Article 16, but the deadline stated here comes from GPSR Article 22(8).
evidence can include accident information, dangerous-product notifications, Safety Business Gateway submissions, Safety Gate follow-up, and corrective measures such as withdrawal, recall, or online-content removal.
The -referenced marketplace evidence is the platform trail around the offer: listing identifiers, provider name, notices, orders, removals, warnings, trader suspension, and consumer communications.
Do not rely on a takedown ticket alone. Pair it with product-risk evidence, accident or incident facts, notification status, and recall or corrective-action records.
requires affected consumers who can be identified to be notified directly and without undue delay in product safety recalls or safety warnings, including marketplace-provider duties under Article 22(12).
The touchpoint does not supersede the recall file. The marketplace record should show how the platform used buyer data, listing records, and consumer-contact paths to support the GPSR recall or safety warning.
Keep recall notice content, direct-consumer notification evidence, remedy information, listing history, and marketplace customer-data decisions in the same case record.
For compliance with Article 23, Article 22(11) requires marketplaces to suspend, for a reasonable period and after a prior warning, traders that frequently offer products non-compliant with the GPSR. The assessment must be case-specific, proportionate, and objective.
Article 23 supplies the suspension framework and requires case-by-case assessment of relevant facts and circumstances. identifies frequent GPSR product non-compliance as the conduct to which that framework applies here.
Build a trader history file with warnings, non-compliant listings, evidence of repeat conduct, suspension decision, duration, and reinstatement criteria.
and the -referenced marketplace rules often use the same listing, notice, trader, and order record, so the record should avoid splitting one incident into two disconnected evidence sets.
The references in Article 22 are only there to run the marketplace process around a product-safety problem, not to turn the matter into a full DSA compliance review.
If the immediate question is whether the product is safe, dangerous, recalled, or reportable, anchor the case in and treat the marketplace steps as support work.
If the immediate question is how the platform should process the listing, notice, order, or trader account, apply the Article 22 marketplace track but keep the scope on product safety.
asks whether a consumer product made available on the EU market is safe, dangerous, non-compliant, recalled, withdrawn, or subject to a safety warning or accident report.
The -referenced marketplace question is narrower: whether the online platform process for product-safety orders, notices, listing information, trader commitments, or repeated non-compliance has been triggered.
Open the case under when the fact pattern is a product-safety risk; add the -referenced marketplace track only for the platform process that handles the offer.
gives market-surveillance authorities a product-safety route to require removal of content for an offer of a dangerous product, disabling access to it, or displaying an explicit warning.
requires marketplace interfaces to let traders provide specified product-safety information for each offered product and to display it or make it easily accessible to consumers on the listing.
The supplies two related controls. Article 31 requires marketplaces to design their interfaces so traders can provide Article 30 information, and Article 22(9) adds the product-safety fields. GPSR Article 22(10) separately requires the trader's DSA Article 30(1) self-certification before the offer is published.
Listing QA should test product-safety fields, trader information, product identifiers, warnings, and displayed accessibility before the listing goes live.
says marketplace providers must process notices related to product-safety issues for products offered online without undue delay and in any event within three working days of receipt.
The touchpoint is the notice channel: identifies notices received in accordance with DSA Article 16, but the deadline stated here comes from GPSR Article 22(8).
evidence can include accident information, dangerous-product notifications, Safety Business Gateway submissions, Safety Gate follow-up, and corrective measures such as withdrawal, recall, or online-content removal.
The -referenced marketplace evidence is the platform trail around the offer: listing identifiers, provider name, notices, orders, removals, warnings, trader suspension, and consumer communications.
Do not rely on a takedown ticket alone. Pair it with product-risk evidence, accident or incident facts, notification status, and recall or corrective-action records.
requires affected consumers who can be identified to be notified directly and without undue delay in product safety recalls or safety warnings, including marketplace-provider duties under Article 22(12).
The touchpoint does not supersede the recall file. The marketplace record should show how the platform used buyer data, listing records, and consumer-contact paths to support the GPSR recall or safety warning.
Keep recall notice content, direct-consumer notification evidence, remedy information, listing history, and marketplace customer-data decisions in the same case record.
For compliance with Article 23, Article 22(11) requires marketplaces to suspend, for a reasonable period and after a prior warning, traders that frequently offer products non-compliant with the GPSR. The assessment must be case-specific, proportionate, and objective.
Article 23 supplies the suspension framework and requires case-by-case assessment of relevant facts and circumstances. identifies frequent GPSR product non-compliance as the conduct to which that framework applies here.
Build a trader history file with warnings, non-compliant listings, evidence of repeat conduct, suspension decision, duration, and reinstatement criteria.
and the -referenced marketplace rules often use the same listing, notice, trader, and order record, so the record should avoid splitting one incident into two disconnected evidence sets.
The references in Article 22 are only there to run the marketplace process around a product-safety problem, not to turn the matter into a full DSA compliance review.
If the immediate question is whether the product is safe, dangerous, recalled, or reportable, anchor the case in and treat the marketplace steps as support work.
If the immediate question is how the platform should process the listing, notice, order, or trader account, apply the Article 22 marketplace track but keep the scope on product safety.
How should teams decide which duty owns the next action?
If the question is whether the product is dangerous, recalled, reportable, or safe to keep available, treat as the controlling track.
If the next step is a product-safety order, notice, listing-field fix, trader self-certification, or repeated non-compliant trader action, run the Article 22 marketplace track and keep the reference narrow.
If the issue goes beyond product safety into general governance, recommender systems, ads, systemic risk, or transparency reporting, do not expand this comparison without DSA-specific source support.
Where GPSR and DSA marketplace duties actually meet
The starts from consumer product safety: only safe products may be made available on the EU market, and providers of online marketplaces have specific product-safety duties when products are offered through their services.
Article 22 expressly connects to Articles 9, 11, 12, 16, 23, 30 and 31. Those cross-references cover authority orders, contact points, notices, trader traceability and self-certification, interface design, and suspension. The DSA still applies on its own terms, including duties outside product safety; this page does not assess those wider duties.
Use for the product-safety judgment: dangerous product, risk information, corrective action, recall, safety warning, Safety Business Gateway, and Safety Gate Portal evidence.
Use the references only where Article 22 invokes them for online marketplace operation: orders, notices, listing information, trader traceability, and repeated non-compliance.
Keep one evidence index, but tag every record as -only, -referenced-by-GPSR, or shared because the same listing, notice, or trader record supports both.
Evidence to keep when a marketplace listing becomes a product-safety issue
For a dangerous-product matter, the case file should show the product identifier, offer URL, unique listing identifier where available, trader and marketplace information, risk basis, notice or order received, content action taken, consumer communication, recall notice, accident information, and any Safety Business Gateway or Safety Gate follow-up.
records should also show why the product was treated as dangerous or non-compliant. The delegated Safety Gate rules reference product identification, traceability information, offer URL and unique identifier, marketplace provider name, risk description, accidents or incidents, corrective measures, and links to recall notices where available.
Capture screenshots or exports of the online interface before and after removal, disabling, warning display, or listing correction.
Keep the notice, order, trader communication, internal triage note, product-risk evidence, and timestamped action log together.
When recall or safety-warning duties are triggered, retain the direct-consumer notification plan, recall notice text, remedies offered, and any customer-data use decision.
Operating rule for takedown, listing, recall, and incident workflows
Treat each case as two linked tracks. The track decides whether the consumer product is dangerous or non-compliant, what corrective action is needed, whether consumers must be warned or recalled, and whether Safety Business Gateway or Safety Gate records are needed. The marketplace track implements the online-interface action and preserves the listing, notice, order, trader, and consumer-notification evidence.
Do not generalize beyond the provisions cited here. For recommender-system transparency, advertising, systemic risk, or wider DSA governance, use DSA-specific sources.
For listings: require product-safety and traceability fields that Article 22 says marketplaces must enable and display or make easily accessible to consumers.
For takedown: record whether the action came from a market-surveillance order, a Article 16 notice concerning product safety, the marketplace's own Article 22 monitoring, voluntary removal, or a recall or withdrawal decision.
For recalls and accidents: keep product identification, hazard, consumer action, remedy, marketplace notification, Safety Business Gateway submission, and any follow-up authority communication in one case record.
Explains the interoperable interface that marketplace providers may use after Safety Gate Portal registration to obtain information about measures against dangerous products.
"providers of online marketplaces may link their interfaces"
DSA Article 23 establishes suspension after prior warning and a case-by-case, proportionate and objective assessment; GPSR Article 22(11) applies it to traders that frequently offer GPSR-non-compliant products.