MSR vs EMC, LVD, RED, and RoHS where surveillance meets sector law
MSR is the horizontal market-surveillance, customs-control, cooperation, and Article 4 responsible-operator framework for covered Union harmonisation legislation.
EMC, LVD, RED, and RoHS remain sector product laws: they define the product-specific conformity route, technical documentation, EU declaration of conformity, CE marking basis, and substance or safety requirements.
First decide which sector laws apply to the product; then add the MSR surveillance and layer. , , , and are not a package that automatically applies to every electrical product. Product type, voltage, radio function, exclusions, and whether another Union act regulates the same requirement determine the sector scope.
Side-by-side comparison
MSR vs EMC, LVD, RED, and RoHS
Use MSR for surveillance, customs, , and authority-response mechanics; use , , , and for the product-specific conformity case behind the CE marking.
A horizontal framework for market surveillance authorities, customs controls, Union cooperation, responsible economic operators, information requests, risk handling, and corrective action.
Second framework
EMC, LVD, RED, and RoHS
Sector Union harmonisation laws that define whether a particular product needs electromagnetic compatibility, electrical safety, radio-equipment, or restricted-substance conformity evidence.
MSR applies to products subject to listed Union harmonisation legislation, including , , , and , when the product is placed on the EU market and the Article 4 conditions are met.
The sector laws apply only when the product falls within their own scope: for electromagnetic compatibility, for electrical equipment within voltage limits, for radio equipment, and for restricted hazardous substances in electrical and electronic equipment.
MSR requires a responsible economic operator established in the Union: an EU manufacturer, importer, authorised representative with the required mandate, or fulfilment service provider where no other listed Union actor exists.
The sector conformity duties remain attached to the manufacturer and, depending on the supply chain and act, importers, distributors, authorised representatives, notified bodies, or other actors. Their duties are not erased by naming an operator.
MSR governs how products covered by Union harmonisation legislation are checked after or around market access: surveillance, cooperation, customs controls, operators, authority evidence requests, and corrective action.
, , , and govern the product-specific conformity case: which essential, safety, radio, compatibility, or hazardous-substance requirements apply before the product is placed or made available on the EU market.
Do not ask whether MSR or a sector directive applies as an either-or question. A covered product may need sector conformity first and MSR-ready evidence access at the same time.
MSR does not create the technical file, DoC, or CE marking basis. It makes those sector records operationally available to market-surveillance authorities and ties them to a reachable Union operator.
, , , and drive the content of the technical documentation, the applicable conformity assessment, the EU declaration of conformity, and the CE marking claim for the product.
A CE-marked product still needs an MSR-ready evidence route: the signed DoC and technical-file index must be retrievable, version-matched, and explainable to authorities.
Under MSR, the responsible operator must provide information and documentation necessary to demonstrate conformity after a reasoned authority request and cooperate on corrective action when required.
The sector laws supply the substance of the answer: test reports, risk assessment, standards analysis, restricted-substance evidence, design records, DoC, and technical documentation for the applicable product rules.
MSR and the surrounding market-surveillance framework address controls on products entering the Union market, including cooperation between customs and market-surveillance authorities.
Use MSR to prove that the product can be found, contacted, documented, checked, stopped, corrected, withdrawn, or recalled through a Union-facing surveillance workflow.
Use , , , and to prove that the product design, testing, materials, documentation, and declaration actually satisfy the applicable product requirements.
MSR adds a second question after the sector-law check: can the competent Union actor produce the sector file, answer the authority, and support corrective action without delay?
Reuse the same technical evidence, but split the ownership: sector teams own the compliance content, while the MSR owner owns access, response, and authority coordination.
If a file already proves the product complies with , , , or , MSR may still require a separate response package, reachable operator details, and a faster authority-facing workflow.
Use the sector law to close the product gap and MSR to close the access and coordination gap; the two workstreams often run in parallel, but they do not ask the same question.
Comparison row 1
Scope boundary
EU Market Surveillance Regulation
MSR applies to products subject to listed Union harmonisation legislation, including , , , and , when the product is placed on the EU market and the Article 4 conditions are met.
The sector laws apply only when the product falls within their own scope: for electromagnetic compatibility, for electrical equipment within voltage limits, for radio equipment, and for restricted hazardous substances in electrical and electronic equipment.
Start with the product design and intended market, then mark each applicable sector law and the separate MSR operator and evidence-access checks.
Comparison row 2
Covered actors
EU Market Surveillance Regulation
MSR requires a responsible economic operator established in the Union: an EU manufacturer, importer, authorised representative with the required mandate, or fulfilment service provider where no other listed Union actor exists.
The sector conformity duties remain attached to the manufacturer and, depending on the supply chain and act, importers, distributors, authorised representatives, notified bodies, or other actors. Their duties are not erased by naming an operator.
Keep two owner fields in the release checklist: the sector conformity owner and the authority-contact owner.
Comparison row 3
Trigger
EU Market Surveillance Regulation
MSR governs how products covered by Union harmonisation legislation are checked after or around market access: surveillance, cooperation, customs controls, operators, authority evidence requests, and corrective action.
, , , and govern the product-specific conformity case: which essential, safety, radio, compatibility, or hazardous-substance requirements apply before the product is placed or made available on the EU market.
Do not ask whether MSR or a sector directive applies as an either-or question. A covered product may need sector conformity first and MSR-ready evidence access at the same time.
Comparison row 4
Core obligations
EU Market Surveillance Regulation
MSR does not create the technical file, DoC, or CE marking basis. It makes those sector records operationally available to market-surveillance authorities and ties them to a reachable Union operator.
, , , and drive the content of the technical documentation, the applicable conformity assessment, the EU declaration of conformity, and the CE marking claim for the product.
A CE-marked product still needs an MSR-ready evidence route: the signed DoC and technical-file index must be retrievable, version-matched, and explainable to authorities.
Comparison row 5
Evidence record
EU Market Surveillance Regulation
Under MSR, the responsible operator must provide information and documentation necessary to demonstrate conformity after a reasoned authority request and cooperate on corrective action when required.
The sector laws supply the substance of the answer: test reports, risk assessment, standards analysis, restricted-substance evidence, design records, DoC, and technical documentation for the applicable product rules.
Prepare request packs by law: one cover response for MSR, with annexes tagged to , , , , or other applicable Union harmonisation acts.
Comparison row 6
Timing and deadlines
EU Market Surveillance Regulation
MSR and the surrounding market-surveillance framework address controls on products entering the Union market, including cooperation between customs and market-surveillance authorities.
For imported products, pair the customs file with the operator record and the sector technical-file index before the first shipment.
Comparison row 7
Enforcement
EU Market Surveillance Regulation
Use MSR to prove that the product can be found, contacted, documented, checked, stopped, corrected, withdrawn, or recalled through a Union-facing surveillance workflow.
Use , , , and to prove that the product design, testing, materials, documentation, and declaration actually satisfy the applicable product requirements.
A complete compliance pack needs both: sector proof for the CE claim and MSR proof that authorities can obtain and act on that proof.
Comparison row 8
Overlap and reuse
EU Market Surveillance Regulation
MSR adds a second question after the sector-law check: can the competent Union actor produce the sector file, answer the authority, and support corrective action without delay?
Reuse the same technical evidence, but split the ownership: sector teams own the compliance content, while the MSR owner owns access, response, and authority coordination.
Comparison row 9
Practical decision rule
EU Market Surveillance Regulation
If a file already proves the product complies with , , , or , MSR may still require a separate response package, reachable operator details, and a faster authority-facing workflow.
Use the sector law to close the product gap and MSR to close the access and coordination gap; the two workstreams often run in parallel, but they do not ask the same question.
Practical decision rule
How to decide what workstream owns a gap
If the gap is missing tests, missing standards rationale, missing restricted-substance evidence, missing risk assessment, or an incorrect DoC, assign it to the relevant sector-law owner.
If the gap is no Union operator, unreachable documentation, inconsistent operator contact details, a customs hold, or an unanswered authority request, assign it to the MSR owner.
If an authority request challenges the CE claim, run both workstreams: sector experts validate the technical case while the MSR owner manages the authority response and corrective-action record.
Treat , , , and as separate product-law columns. EMC covers electromagnetic compatibility of equipment; LVD covers electrical equipment designed for use within its stated voltage limits, subject to exclusions; RED covers radio equipment and includes safety and electromagnetic-compatibility essential requirements; RoHS restricts listed hazardous substances in electrical and electronic equipment within its scope, subject to exclusions and exemptions.
Treat MSR as the surveillance and access-to-evidence column. It asks who in the Union can be contacted under , whether technical documentation and the EU declaration can be made available to authorities, how customs or market-surveillance checks are handled, and how corrective action is coordinated if a product presents a risk or is non-compliant.
Run the sector tests against the product as designed and marketed. A mains-powered appliance can fall under and ; a Wi-Fi or Bluetooth product is an example of equipment that can fall under ; and either product can also fall under if it meets the EEE scope. These are examples only. Intended function, voltage rating, radio capability, installation form, exclusions, exemptions, and other applicable Union acts control the final result.
: determine whether the product is apparatus or a fixed installation liable to generate electromagnetic disturbance or have its performance affected by disturbance. Check the Directive's exclusions and the special fixed-installation rules instead of assuming every electronic component needs the ordinary apparatus route.
: check whether the equipment is designed for 50 to 1,000 V AC or 75 to 1,500 V DC, then apply the Annex II exclusions. Equipment outside those voltage bands does not enter LVD merely because it is electrical.
: check whether the product intentionally emits or receives radio waves for radio communication or radiodetermination, including a product completed with an antenna for that purpose. RED applies its own electrical-safety objectives without the voltage limit and its own electromagnetic-compatibility objective, so ordinary LVD and do not apply separately to radio equipment for those same requirements.
: check whether the equipment depends on electric current or electromagnetic fields for at least one intended function and stays within 1,000 V AC or 1,500 V DC, then check Article 2 exclusions and Annex III or IV exemptions. The Annex II limits apply by weight in each homogeneous material: 0.01% for cadmium and 0.1% for the other listed substances.
Do not use an responsible economic operator as a substitute for , , , or conformity assessment.
Do not treat a signed EU declaration of conformity as the whole MSR answer; authorities can still ask for information, documentation, cooperation, and corrective action.
Keep the same product identifier across the sector technical file, DoC, CE marking records, contact details, customs files, and authority correspondence.
Reassess scope when intended use, voltage, radio hardware or software, materials, supplier declarations, product configuration, installation model, sector exemptions, harmonised standards, or the placing-on-market route changes. For legacy stock, record the original placement date and check the transition rule in each applicable sector act.
For each applicable sector law, the evidence pack should show why the product meets that law. Do not automatically run and as separate directives for a product: RED itself incorporates electrical-safety objectives without the LVD voltage limit and electromagnetic-compatibility objectives. Other equipment may instead fall directly under EMC, LVD, , or a combination, depending on scope and exclusions.
For MSR, the evidence pack should show that the sector evidence is reachable and usable by authorities. focuses on an economic operator established in the Union, verification that the EU declaration and technical documentation have been drawn up where the sector law requires them, availability of the declaration, authority-facing documentation, risk information, and cooperation on corrective action.
Maintain a scope memo and technical-file index that maps each document to , , , , or MSR instead of placing all evidence under one generic CE folder.
Store the current EU declaration of conformity with the product model, version, applicable Union harmonisation acts, standards or specifications used, manufacturer details, and signature record.
Record the operator name, trade name or trademark, and contact details exactly as they appear on the product, packaging, parcel, or accompanying document.
Keep authority requests, answers, translations, test-report extracts, sampling decisions, customs holds, and corrective actions in an MSR response log.
A market-surveillance or customs issue usually starts as an evidence-access problem before it becomes a design problem. The product team may already have , , , or evidence, but the MSR question is whether the right Union actor can produce it quickly, in an authority-understandable language, and with a clear explanation of the product version and applicable acts.
If the authority challenges the product, separate three decisions: whether the sector technical case is valid, whether the operator and contact details are correct, and whether the requested corrective action, withdrawal, recall, or risk mitigation is needed under the authority process.
Route requests by product model, placing-on-market facts, EU economic operator, and applicable sector laws.
Answer with the minimum complete evidence set: DoC, technical-file index, relevant test or assessment extracts, operator contact record, and corrective-action status.
Escalate internally when the request exposes a missing sector assessment, a missing operator, inconsistent CE or DoC records, or a customs hold affecting release for free circulation.
Current consolidated source for the RoHS EEE and homogeneous-material definitions, scope exclusions, exemption annexes, and Annex II limits of 0.01% cadmium and 0.1% for the other listed substances by weight in homogeneous materials.