| Scope boundary | MSR Article 4 applies to products subject to listed Union harmonisation legislation, including RoHS, EMC, LVD, and RED, 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: EMC for electromagnetic compatibility, LVD for electrical equipment within voltage limits, RED for radio equipment, and RoHS 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. |
|---|
| Covered actors | MSR Article 4 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 Article 4 operator. | Keep two owner fields in the release checklist: the sector conformity owner and the Article 4 authority-contact owner. |
|---|
| Trigger | MSR governs how products covered by Union harmonisation legislation are checked after or around market access: surveillance, cooperation, customs controls, Article 4 operators, authority evidence requests, and corrective action. | EMC, LVD, RED, and RoHS 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. |
|---|
| Core obligations | 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. | EMC, LVD, RED, and RoHS 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. |
|---|
| Evidence record | 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 EMC, LVD, RED, RoHS, or other applicable Union harmonisation acts. |
|---|
| Timing and deadlines | MSR and the surrounding market-surveillance framework address controls on products entering the Union market, including cooperation between customs and market-surveillance authorities. | EMC, LVD, RED, and RoHS evidence may be what resolves a border hold, but those sector laws are not the customs workflow itself. | For imported products, pair the customs file with the Article 4 operator record and the sector technical-file index before the first shipment. |
|---|
| Enforcement | 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 EMC, LVD, RED, and RoHS 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. |
|---|
| Overlap and reuse | 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? | EMC, LVD, RED, and RoHS still answer the first question: does the product itself meet the applicable essential, safety, radio, or substance requirements? | 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. |
|---|
| Practical decision rule | If a file already proves the product complies with EMC, LVD, RED, or RoHS, MSR may still require a separate response package, reachable operator details, and a faster authority-facing workflow. | If the product is still missing the sector-law proof itself, fix EMC, LVD, RED, or RoHS first; MSR cannot rescue an unfinished conformity case. | 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. |
|---|