Use MDR first when the product has a medical purpose, is an accessory to a medical device, or falls into an Annex XVI non-medical product group once common specifications apply.
GPSR is not always displaced by MDR. For products subject to specific EU safety requirements, GPSR applies to aspects and risks that those requirements do not cover; its duties also apply to consumer products outside MDR scope.
Structured answer sets in this page tree.
Cited legal and guidance references.
Start with MDR qualification, but do not treat MDR and as an automatic either-or choice. MDR governs medical devices, accessories, and covered products. GPSR governs and remains relevant to aspects and risks not covered by product-specific EU safety requirements. The result can be MDR only, GPSR only, or MDR plus residual GPSR duties for an uncovered consumer-safety risk.
A cited-source comparison for deciding whether a product belongs under MDR, , or both because GPSR covers an aspect or risk not addressed by the applicable product-specific safety rules.
Use MDR for medical devices, accessories, intended-purpose classification, conformity assessment, technical documentation, clinical evidence, PMS, vigilance, UDI, and EUDAMED.
Use for outside MDR and for aspects or risk categories not covered by applicable product-specific EU safety requirements. Confirm the actor and duty under GPSR rather than treating it as a generic safety label.
| Dimension | MDR | GPSR / general product safety | Operational implication |
|---|---|---|---|
| Scope boundary | Does the product have a medical intended purpose, act as an accessory, or otherwise fall within Regulation (EU) 2017/745? | Is the product a consumer product placed or made available on the market, with risks that are not already covered by MDR, so a review is needed? | Qualify the product under MDR first, then document whether covers the product or any safety aspect or risk left uncovered by MDR. |
| Covered actors | MDR analysis starts with intended purpose, medical claims, software outputs, IFU statements, accessory use, and user population. | covers items intended for consumers and items not intended for consumers that are likely, under reasonably foreseeable conditions, to be used by consumers. Its safety assessment considers the product, presentation, consumer categories, effect on other products, and evolving or learning functions where relevant. | Preserve claim evidence with the scope decision because a marketing or IFU change can change the regulatory route. |
| Trigger | can bring listed non-medical products into MDR-style controls when common specifications apply. | is triggered when a consumer product is outside sector-specific rules or when a covered product has risks that are not addressed by those rules. | Beauty, wellness, body-modification, skin-treatment, and similar products need a documented screen before the side is considered complete. |
| Core obligations | MDR evidence should include qualification rationale, classification rule, technical documentation, clinical evaluation, PMS or PMCF where relevant, vigilance procedures, UDI data, and EUDAMED records. | evidence should include internal risk analysis, technical documentation, traceability, contact details, instructions and safety information, and recall or accident-response records. | Use a shared evidence index only if each record is tagged to the regime and claim it actually supports. |
| Evidence record | MDR devices need PMS and vigilance routing, including serious-incident and field safety corrective action assessment. | Manufacturers must notify accidents caused by a product through the Safety Business Gateway without undue delay after learning of the accident. Dangerous-product corrective-action and recall communications follow separate conditions; not every complaint is an accident or recall. | Incident intake should ask whether the product is an MDR device, an product, a dual-purpose product, or outside the MDR file. |
| Timing and deadlines | If a medical purpose, accessory relationship, classification rule, category, or MDR PMS/vigilance trigger is present, keep the issue in the MDR workstream. | has applied since 13 December 2024. Its manufacturer technical documentation must be retained for 10 years after the product is placed on the market; notification timing depends on whether the event is an accident, a dangerous product, or a recall. | Record the product facts, MDR and conclusions, the scope or residual-risk basis, the responsible actor, the applicable notification route, and the next review trigger. |
| Enforcement | MDR enforcement focuses on conformity assessment, vigilance, post-market surveillance, and market surveillance for devices in MDR scope. | enforcement focuses on dangerous , market surveillance, Safety Gate notifications, and recall handling. | Do not use as a shortcut around MDR. Qualify the product under MDR first, then document what remains outside the medical-device file. |
| Overlap and reuse | MDR and can overlap on a product's non-medical risks, but MDR remains the first check when the intended purpose is medical or the product is an accessory or product. | handles the safety gaps that remain after sector-specific legislation has been checked, including products that are outside MDR scope. | Map shared controls to the MDR requirement and the residual aspect or risk they support; do not treat the two legal conclusions as interchangeable. |
| Practical decision rule | Does the product have a medical intended purpose, act as an accessory, or otherwise fall within Regulation (EU) 2017/745? | Whether or not MDR applies, is this a consumer product with an aspect or risk that applicable product-specific EU safety requirements do not cover? | Record the MDR result and the result separately, including the product, aspect, risk, actor, and evidence behind each conclusion. |
Does the product have a medical intended purpose, act as an accessory, or otherwise fall within Regulation (EU) 2017/745?
Is the product a consumer product placed or made available on the market, with risks that are not already covered by MDR, so a review is needed?
Qualify the product under MDR first, then document whether covers the product or any safety aspect or risk left uncovered by MDR.
MDR analysis starts with intended purpose, medical claims, software outputs, IFU statements, accessory use, and user population.
covers items intended for consumers and items not intended for consumers that are likely, under reasonably foreseeable conditions, to be used by consumers. Its safety assessment considers the product, presentation, consumer categories, effect on other products, and evolving or learning functions where relevant.
Preserve claim evidence with the scope decision because a marketing or IFU change can change the regulatory route.
can bring listed non-medical products into MDR-style controls when common specifications apply.
is triggered when a consumer product is outside sector-specific rules or when a covered product has risks that are not addressed by those rules.
Beauty, wellness, body-modification, skin-treatment, and similar products need a documented screen before the side is considered complete.
MDR evidence should include qualification rationale, classification rule, technical documentation, clinical evaluation, PMS or PMCF where relevant, vigilance procedures, UDI data, and EUDAMED records.
evidence should include internal risk analysis, technical documentation, traceability, contact details, instructions and safety information, and recall or accident-response records.
Use a shared evidence index only if each record is tagged to the regime and claim it actually supports.
MDR devices need PMS and vigilance routing, including serious-incident and field safety corrective action assessment.
Manufacturers must notify accidents caused by a product through the Safety Business Gateway without undue delay after learning of the accident. Dangerous-product corrective-action and recall communications follow separate conditions; not every complaint is an accident or recall.
Incident intake should ask whether the product is an MDR device, an product, a dual-purpose product, or outside the MDR file.
If a medical purpose, accessory relationship, classification rule, category, or MDR PMS/vigilance trigger is present, keep the issue in the MDR workstream.
has applied since 13 December 2024. Its manufacturer technical documentation must be retained for 10 years after the product is placed on the market; notification timing depends on whether the event is an accident, a dangerous product, or a recall.
Record the product facts, MDR and conclusions, the scope or residual-risk basis, the responsible actor, the applicable notification route, and the next review trigger.
MDR enforcement focuses on conformity assessment, vigilance, post-market surveillance, and market surveillance for devices in MDR scope.
enforcement focuses on dangerous , market surveillance, Safety Gate notifications, and recall handling.
Do not use as a shortcut around MDR. Qualify the product under MDR first, then document what remains outside the medical-device file.
MDR and can overlap on a product's non-medical risks, but MDR remains the first check when the intended purpose is medical or the product is an accessory or product.
handles the safety gaps that remain after sector-specific legislation has been checked, including products that are outside MDR scope.
Map shared controls to the MDR requirement and the residual aspect or risk they support; do not treat the two legal conclusions as interchangeable.
Does the product have a medical intended purpose, act as an accessory, or otherwise fall within Regulation (EU) 2017/745?
Whether or not MDR applies, is this a consumer product with an aspect or risk that applicable product-specific EU safety requirements do not cover?
Record the MDR result and the result separately, including the product, aspect, risk, actor, and evidence behind each conclusion.
MDR classification and qualification turn on the product's intended purpose. The MDR text requires classification rules to be applied by intended purpose, and technical documentation must identify the device, intended purpose, risk class, and applicable rule. That makes marketing claims, instructions for use, software outputs, clinical claims, and accessories the first boundary checks.
If the product is sold as a wellness, beauty, sports, comfort, or general consumer product, do not assume that the absence of a medical claim ends the analysis. brings listed groups of products without an intended medical purpose into the MDR framework once common specifications apply.
scope also has exclusions. Medicinal products, food and feed, living plants and animals, certain transport equipment, and products clearly marked for repair or reconditioning before use are among the categories handled outside or specially under Article 2. A professional product is not automatically excluded if consumers are reasonably likely to use it.
Use the MDR sources, Annex XVI checks, claim review, and post-market routing rule to separate medical-device obligations from general product-safety follow-up.
is the main trap in an MDR-versus-general-product-safety comparison. A product can lack a medical purpose and still be pulled into MDR-style controls if it belongs to an Annex XVI group covered by common specifications.
MDCG 2023-6 also warns against casually borrowing clinical data from analogous medical devices for non-medical products. The working sequence is: qualify the product, check Annex XVI, identify any MDR safety requirements that apply, and then assess whether covers the product or a remaining risk.
For devices in MDR scope, post-market surveillance and vigilance are part of the MDR file. The MDR requires procedures for PMS and vigilance, and the Blue Guide describes medical devices as having a specific vigilance system for serious incidents.
For in scope, manufacturers must ensure the general safety requirement is met, perform an internal risk analysis, prepare and update technical documentation, maintain product identification and traceability information, and keep the technical documentation available to market-surveillance authorities for 10 years after placement on the market. GPSR also uses the Safety Business Gateway for accident and dangerous-product notifications. These duties do not replace MDR PMS and vigilance for a device.
"not covered by sector-specific EU harmonisation legislation"
"Manual on borderline and classification"
"this guidance applies only to the non-medical intended purpose"
"This Regulation lays down rules concerning the placing on the market"
"this Regulation applies only to those aspects and risks or categories of risks which are not covered by those requirements"