EU Market Surveillance Regulation (MSR) vs Digital Services Act (DSA) marketplace boundary
MSR governs product compliance and market surveillance for covered Union harmonisation products, including Article 4 operators, targeted online offers, authority powers, corrective action, and customs controls.
The DSA governs intermediary services. For covered consumer marketplaces, Articles 30 to 32 add trader traceability, interfaces that support product-law disclosures, checks, and information to buyers of illegal products or services.
Use to decide whether a covered product can be made available in the EU and how authorities, customs, and economic operators handle non-compliance. Use the to decide what an intermediary service or must do about trader onboarding, listing design, notices, and buyer information. A marketplace can fall under both: the DSA does not replace the product-law duties that MSR enforces, and MSR does not supply the DSA's platform-process rules.
Side-by-side comparison
EU Market Surveillance Regulation (MSR) vs Digital Services Act (DSA): marketplace boundary
A source-backed comparison for deciding whether a marketplace issue belongs in product compliance, intermediary-service duties, or both.
Use for product compliance and market-surveillance questions involving covered products, economic operators, , distance sales, fulfilment, customs controls, authority requests, and corrective action.
Second framework
Digital Services Act (DSA)
Use the for intermediary-service and platform-process duties, including trader traceability, marketplace interface fields, notices, suspensions, and information to buyers of illegal products or services.
EU Market Surveillance Regulation (MSR) vs Digital Services Act (DSA): marketplace boundary
Is a covered product being made available, placed on the market, put into service, imported, offered online, or otherwise handled by an economic operator under Union harmonisation law?
Does the service qualify as an intermediary service and, for Articles 30 to 32, as an online platform that allows consumers to conclude distance contracts with traders?
Name the intermediary-service provider and determine whether it is a hosting service, online platform, consumer marketplace, or designated very large online platform. These service roles are separate from economic-operator roles.
For a covered consumer marketplace, Article 30 requires specified trader information before the trader uses the service and requires best efforts to assess whether that information is reliable and complete.
treats products offered online or through other distance-sales means as made available on the market when the offer is targeted at end users in the Union.
Article 31 requires a covered consumer marketplace to provide interface fields that enable traders to supply required pre-contractual, product-compliance, and product-safety information, including the economic operator and applicable identification, labelling, and marking.
covers controls on products entering the Union market, including risk-based checks, suspension of release for free circulation, authority decisions, and follow-up on non-compliant or serious-risk products.
evidence is service-facing: trader identity and verification records, self-certifications, interface fields, product or service identifiers, notice decisions, suspension records, and buyer-information records. It does not replace customs release evidence.
Keep customs documents, authority notices, release or refusal decisions, and corrective-action evidence in the file even if marketplace teams also support customer messaging.
records may include market-surveillance authority requests, online-interface removal or warning measures, ICSMS entries, Safety Gate alerts, EUPCN coordination context, and corrective-action evidence.
The has applied generally since 17 February 2024. Article 30 gave marketplaces already used by traders on that date 12 months to make best efforts to obtain the listed trader information; current onboarding should apply the pre-use rule.
Use as the active workstream when the blocker is product conformity, , EU contact details, online product offer, fulfilment, customs release, authority request, corrective action, ICSMS, or Safety Gate.
Use the workstream for intermediary-service orders and notices, trader traceability, marketplace interface design, service suspension, and information to buyers of illegal products or services.
Check whether the matter already has a product-compliance anchor, such as , a customs hold, or a corrective-action request, before assigning the legal owner.
The governs the provider's service process. Article 31 helps traders present product-law information, but it does not transfer the manufacturer's or other economic operator's substantive product-conformity duties to the platform.
When a product offer, importer, fulfilment provider, or customs event is present, route the issue into first and keep the product file complete before looking at platform governance.
When the issue concerns trader onboarding, listing fields, notice processing, suspension, or informing buyers about an illegal product, apply the relevant rule and provider-size exception.
Open both workstreams when the same listing involves a non-compliant covered product and a marketplace-process duty; close each against its own evidence.
Is a covered product being made available, placed on the market, put into service, imported, offered online, or otherwise handled by an economic operator under Union harmonisation law?
Does the service qualify as an intermediary service and, for Articles 30 to 32, as an online platform that allows consumers to conclude distance contracts with traders?
Name the intermediary-service provider and determine whether it is a hosting service, online platform, consumer marketplace, or designated very large online platform. These service roles are separate from economic-operator roles.
For a covered consumer marketplace, Article 30 requires specified trader information before the trader uses the service and requires best efforts to assess whether that information is reliable and complete.
treats products offered online or through other distance-sales means as made available on the market when the offer is targeted at end users in the Union.
Article 31 requires a covered consumer marketplace to provide interface fields that enable traders to supply required pre-contractual, product-compliance, and product-safety information, including the economic operator and applicable identification, labelling, and marking.
covers controls on products entering the Union market, including risk-based checks, suspension of release for free circulation, authority decisions, and follow-up on non-compliant or serious-risk products.
evidence is service-facing: trader identity and verification records, self-certifications, interface fields, product or service identifiers, notice decisions, suspension records, and buyer-information records. It does not replace customs release evidence.
Keep customs documents, authority notices, release or refusal decisions, and corrective-action evidence in the file even if marketplace teams also support customer messaging.
records may include market-surveillance authority requests, online-interface removal or warning measures, ICSMS entries, Safety Gate alerts, EUPCN coordination context, and corrective-action evidence.
The has applied generally since 17 February 2024. Article 30 gave marketplaces already used by traders on that date 12 months to make best efforts to obtain the listed trader information; current onboarding should apply the pre-use rule.
Use as the active workstream when the blocker is product conformity, , EU contact details, online product offer, fulfilment, customs release, authority request, corrective action, ICSMS, or Safety Gate.
Use the workstream for intermediary-service orders and notices, trader traceability, marketplace interface design, service suspension, and information to buyers of illegal products or services.
Check whether the matter already has a product-compliance anchor, such as , a customs hold, or a corrective-action request, before assigning the legal owner.
The governs the provider's service process. Article 31 helps traders present product-law information, but it does not transfer the manufacturer's or other economic operator's substantive product-conformity duties to the platform.
When a product offer, importer, fulfilment provider, or customs event is present, route the issue into first and keep the product file complete before looking at platform governance.
When the issue concerns trader onboarding, listing fields, notice processing, suspension, or informing buyers about an illegal product, apply the relevant rule and provider-size exception.
Open both workstreams when the same listing involves a non-compliant covered product and a marketplace-process duty; close each against its own evidence.
How should teams decide between MSR and DSA for marketplace compliance?
If the issue involves a covered product, EU-targeted online offer, operator, , customs event, market-surveillance authority request, or corrective action, open or update the record.
If consumers conclude distance contracts with traders on the platform, check Article 29's provider-size exception, Article 30 trader traceability, Article 31 interface requirements, and Article 32 buyer information.
If both fact patterns are present, keep separate owners, source citations, evidence tags, and closure criteria so product compliance and online-service governance are not merged.
For , identify the product, the applicable Union harmonisation legislation, the economic operators, and whether an online offer targets end users in the Union. applies only to the product laws listed in Article 4(5), as amended, or to later legislation that makes Article 4 applicable.
For the , identify the intermediary service and its provider. Articles 30 to 32 apply specifically to providers of online platforms that allow consumers to conclude distance contracts with traders. Article 29 excludes qualifying micro and small enterprise providers from that section, subject to the 12-month rule after losing that status and the exception for designated very large online platforms.
Confirm the product law and the product's manufacturer, importer, distributor, authorised representative, or roles.
Identify the EU-established economic operator only where Article 4 covers the product.
Classify the service separately: an online platform under the is a hosting service that stores and disseminates information to the public at a recipient's request, subject to the DSA's definition and ancillary-feature exclusion.
If consumers can conclude distance contracts with traders on the platform, assess Articles 29 to 32 as well as the product-law lane.
expressly covers products offered online or through other distance-sales means when the offer is targeted at end users in the Union. For a marketplace workflow, the first practical question is therefore whether a concrete product offer is targeted at EU end users and who is the economic operator for that product.
The does not displace product law. Article 31 requires covered marketplaces to design their interfaces so traders can provide pre-contractual, product-compliance, and product-safety information required by applicable Union law. It specifically calls for fields for the economic operator under and for product identification, trader signs, and applicable labelling or marking.
Route product conformity, technical documentation, EU contact details, , corrective action, and authority cooperation into the workstream.
Route trader verification, notice handling, interface fields, and buyer information about illegal products into the workstream.
Do not use a intake label to skip checks for products sold, shipped, fulfilled, imported, or otherwise made available in the EU.
Tag shared evidence by duty. A product identifier or economic-operator address may support both workstreams, but Article 31 interface design and documentation access remain different obligations.
Separate product compliance from platform governance
Route marketplace issues into MSR product compliance and DSA trader, listing, notice, and buyer-information duties without merging the evidence or responsible owners.
The evidence file should be product-specific. A reviewer should be able to see the product category, applicable harmonised product legislation, economic-operator role, EU contact details, technical documentation location, authority contact route, and corrective-action owner.
For imported products, keep customs and border-control records separate from ordinary marketplace intake notes. Articles 25 to 28 cover controls on products entering the Union market, suspension of release for free circulation, market-surveillance authority decisions, and follow-up when a product is non-compliant or presents a serious risk.
Store the responsible economic-operator decision and the evidence showing the operator is established in the Union.
Index EU declarations, technical documentation, test reports, labels, instructions, warnings, and product-contact details that support conformity.
For online offers, keep screenshots or listing exports showing the product, seller, EU targeting facts, and date reviewed.
For border events, keep customs notices, market-surveillance authority correspondence, suspension or release decisions, ICSMS references where available, and corrective-action records.
For dangerous non-food product cases, keep Safety Gate references separate from routine product-compliance notes.
The handoff should identify both the product event and the platform event. The owner records the applicable product law, economic operator, EU-targeted offer, authority request, corrective action, or customs event. The owner records the provider classification, trader-onboarding evidence, listing fields, notice decision, and any buyer-information action.
Under Article 30, a covered marketplace must obtain specified trader identity, payment-account, register, and self-certification information before the trader uses the service, make best efforts to assess reliability and completeness, and suspend the service in the circumstances set out in that article. Under Article 32, if it becomes aware that a trader offered an illegal product or service, it must inform identifiable buyers from the preceding six months of the illegality, trader identity, and relevant redress, or publish that information when it lacks all contact details.
Use as controlling when a product-compliance or market-surveillance authority decision is the blocker.
Use the workstream for provider status, trader traceability, notice handling, marketplace interface design, and buyer information.
Run both workstreams when a marketplace both makes products available in the EU and operates an online-service workflow that requires separate legal analysis.
Mark the matter out of scope for this comparison when no product, economic operator, EU-targeted offer, border event, or MSR authority workflow is present.