Deadline

The November 2026 EUDAMED Deadline

Commission Decision (EU) 2025/2371 started the transition period that makes November 27, 2026 the registration deadline for devices already on the EU market that are still being placed on it. This guide explains who it applies to, what data is required and what the legacy transition rules actually say.

12 min readUpdated October 2026
DEADLINE
November 27, 2026 is the final registration deadline for existing devices under the transition period in MDR Article 123(3), as amended by Regulation (EU) 2024/1860 and triggered by Commission Decision (EU) 2025/2371. It covers devices that were on the market before May 28, 2026 and are still being placed on it. A device whose first unit is placed on the market on or after May 28, 2026 must be registered before that first unit is placed.

What Changed

EUDAMED, the European database on medical devices, was always designed to become mandatory. The legal basis is MDR Article 33, which required the European Commission to set up and maintain a European database on medical devices. Both MDR 2017/745 and IVDR 2017/746 called for a phased rollout, module by module, with the deployment schedule governed by Regulation (EU) 2024/1860. The system has been accepting live submissions since 2021. What changed in late 2025 was the formal closure of the last extension window.

Commission Decision (EU) 2025/2371, published November 27, 2025, confirmed that four EUDAMED modules are functional. These are the modules for actor registration, for UDI and devices, for notified bodies and certificates and for market surveillance. That started the transition clocks in MDR Article 123(3). Mandatory use of those modules began May 28, 2026. Devices whose first unit was placed on the market before that date and which are still being placed on it must be registered by November 27, 2026. That covers MDR devices and legacy devices alike. Devices with no unit placed on the market from May 28, 2026 do not need registering unless a post-market surveillance or vigilance action concerns them. A legacy device does not need registering if the same device is already registered as an MDR or IVDR device. The EUDAMED roll-out Q&A (Q8) treats the two as the same device when shared characteristics give them the same identification, such as the UDI-DI, catalogue number or trade name. A changed device that needed a new UDI-DI does not count as the same device.

Is the deadline November 27 or November 28?

November 27, 2026. Both dates trace to the same event. Commission Decision (EU) 2025/2371 was published in the Official Journal on November 27, 2025, and the transition period in MDR Article 123(3), subparagraph (e), runs twelve months from that notice. Counted directly, twelve months from November 27, 2025 is November 27, 2026.

The later reading comes from the Q&A on the gradual roll-out of EUDAMED. Its worked example (Q7) counts the period from the day after the triggering event. A notice published on July 1, 2025 gives a registration date of July 2, 2026. Applied to a November 27, 2025 notice, the same arithmetic gives November 28, 2026.

This site states November 27 throughout, and does so deliberately: it is the earlier of the two readings. If the conservative date is correct, you are compliant. If the later date is correct, you are compliant one day early. The reverse does not hold, and the cost of the two errors is not symmetric. Before relying on the later date in a contract or a submission plan, confirm it with your notified body or national competent authority.

The May date applies to any device whose first unit is placed on the EU market on or after that date. Those devices must be registered in EUDAMED before the first unit is placed. The November date covers devices whose first unit was placed before May 28, 2026 and which are still being placed on the market. Units already sitting with distributors are not placed on the market again.

The same applies to a new identifier on a legacy line. If the first unit of a legacy device with a given identifier is placed on the market on or after May 28, 2026, for example a new pack size, register that device in EUDAMED before the first unit is placed. The EUDAMED roll-out Q&A (Q7) states the before-placement rule for MDR and IVDR devices and does not address legacy devices. MDR Article 123(3)(e) sets the same condition for both groups and MDR Article 120(3d) applies the MDR device registration requirements to legacy devices, so we apply the same rule. Registering before the first unit is compliant under every reading. Waiting until November 27 is compliant only under the most generous one. The new variant must also stay within the legacy conditions of MDR Article 120(3c). There can be no significant change in design or intended purpose and the variant must still comply with the Directive. For a certified device the certificate must also cover it. Confirm both with your notified body first.

IVDR devices and legacy IVDD devices follow IVDR Article 113(3)(fa) instead. It counts six months from May 28, 2026 and also ends in late November 2026. The class-by-class IVDR dates in Regulation (EU) 2024/1860 govern how long legacy IVDs may stay on the market. They do not change when those devices must be registered.

Who Must Register

Registration obligations run along operator type, not product category. The framework applies differently to manufacturers, Authorised Representatives, and importers.

Manufacturers

Any manufacturer placing a device on the EU market must register both an actor record (their own company details) and a device record (the specific product) in EUDAMED. This obligation applies equally to manufacturers established in the EU and those outside the EU who operate through an Authorised Representative. The responsibility sits with the legal manufacturer, not with distributors or resellers.

Authorised Representatives

Non-EU manufacturers must have an EU Authorised Representative with an active EUDAMED actor record before any device registration can proceed. The AR record must be confirmed active and linked to the manufacturer's record. If the AR record is not yet in place, that dependency resolves before device data preparation is useful, and it resolves in a specific order: why your AR must register before you can.

Importers

Importers register separately as economic operators under MDR Article 31. They do not file the device registration. Under MDR Article 13 they must verify that the device is registered and add their details to its registration. An importer must complete its own Article 31 registration before it places a device on the market. That duty does not depend on whether the manufacturer has registered the device. Each Member State sets the penalties for a breach under MDR Article 113.

Clinical investigation and performance study sponsors

Sponsors follow a separate pathway. Clinical investigation applications under MDR Article 62 run through the electronic system in MDR Article 73, which assigns each investigation its own Union-wide identification number under MDR Article 70. That system was not among the four modules declared functional by Commission Decision (EU) 2025/2371, so sponsor obligations are not part of the November 27, 2026 registration deadline this guide covers.

System and procedure pack producers

Economic operators who combine devices into systems or procedure packs under MDR Article 22 have their own EUDAMED duty under MDR Article 29(2): before placing the pack on the market, they must assign it a Basic UDI-DI and provide it to the UDI database. That obligation is separate from the manufacturer records for the component devices included in the system or procedure pack.

Scope exclusions

Custom-made devices and investigational devices follow separate registration pathways and are not subject to the mass-registration EUDAMED workflow. Class I devices self-declared under MDD Annex VII get no exemption from device registration. A device whose declaration of conformity was drawn up before May 26, 2021 and that now needs a notified body under the MDR may stay on the market as a legacy device until December 31, 2028 under MDR Article 120(3b) if it meets the conditions in Article 120(3c). It registers as a legacy device. A device the manufacturer can still self-declare under the MDR has no transition period. It must comply with the MDR and register as an MDR device.

NOTE
EUDAMED uses a role-based access model. Manufacturer, Authorised Representative, and importer records are separate entries, but they are not independent. A non-EU manufacturer's own actor registration names its AR by Actor ID/SRN, and the AR verifies that request before a competent authority ever sees it, so the AR has to be registered first. See the EUDAMED registration order for non-EU manufacturers.

Data Requirements

EUDAMED registration is a data submission problem. The system accepts structured input across the Actor, UDI/Device, and Certificate modules. The full mandatory field set varies with device class, risk classification, and whether the product is an active implantable, SaMD, or contains materials of human or animal origin.

Mandatory fields for every device record

  • UDI-DI: the Device Identifier assigned through a Commission-recognized issuing entity (GS1, HIBCC, ICCBBA or IFA). Legacy devices use a EUDAMED ID instead unless a UDI-DI has already been assigned
  • Basic UDI-DI: the grouping identifier referencing the EU Declaration of Conformity. Legacy devices use a EUDAMED DI instead
  • EMDN code: at least one terminal-level code from the European Medical Device Nomenclature. Legacy devices need one too
  • Risk classification: under the legislation the device is placed on the market under. MDR and IVDR devices use Annex VIII. Legacy devices keep their directive class
  • Trade name and model/version: exactly as it appears on the device label
  • Manufacturer SRN: the Single Registration Number from a completed actor registration
  • Certificate data: the data required depends on the class. MDR Class III devices and Class IIb implantable devices outside the Article 52(4) exceptions such as sutures and staples name the certificate type and the notified body in the device record. So do IVDR Class D devices and Class B or C devices for self-testing or near-patient testing. Other MDR Class IIb and IVDR Class C devices name a type-examination certificate only if one covers the device. The certificate number is optional in all these cases. The notified body enters every certificate it issues in EUDAMED itself under MDR Article 56(5) and IVDR Article 51(5). Legacy devices give the type, notified body, certificate number and expiry date of every Directive certificate that covers the device. This applies to MDD Class I devices without a measuring function and IVDD General devices only where a certificate exists
  • Member State of placing on the EU market: the Member State where the device has been or is to be placed on the market. Required except for a Regulation device with the status not intended for the EU market

Conditional fields

Several flags are required in every MDR device record whatever the class, among them the implantable flag, the flags for human or animal tissues or cells and the system or procedure pack type. Other fields apply only when a condition is met, such as clinical investigation references and certificate details. The EUDAMED data dictionary, published by the European Commission, lists the complete field-by-field requirement matrix.

WARNING
EUDAMED requires every mandatory field before a device record can be submitted. You can save an incomplete record as a draft in the web interface and finish it later. A draft is not a submitted registration. Your data must be complete before you submit.

Legacy Device Rules

Legacy devices from the predecessor frameworks (MDD 93/42/EEC, AIMDD 90/385/EEC and IVDD 98/79/EC) operate under specific transition rules that differ from full MDR/IVDR obligations. The distinction matters for what data you need to prepare now versus later.

What legacy devices must do

Legacy devices still being placed on the market must meet the following requirements. MDR Article 120, as amended by Regulation (EU) 2023/607, sets them for MDD and AIMDD devices. IVDR Article 110, as amended by Regulation (EU) 2024/1860, sets them for IVDD devices.

  • Complete actor registration in EUDAMED (manufacturer and AR if applicable)
  • Report serious incidents and field safety corrective actions under the MDR or IVDR vigilance rules. Until the EUDAMED vigilance module becomes mandatory, reports go through the existing national route
  • Provide an EMDN code and the other mandatory fields of the legacy device record
  • Register the device with a EUDAMED DI and EUDAMED ID in place of the Basic UDI-DI and UDI-DI (MDCG 2019-5). MDR or IVDR UDI assignment obligations do not apply to legacy devices

What changes when a legacy device moves to the MDR or IVDR

A legacy device record is not the same as an MDR or IVDR device record. It uses the EUDAMED DI instead of a Basic UDI-DI and has its own field set. That field set still includes the EMDN code, so legacy devices need EMDN codes now and not only after certification. Once the device is certified under the MDR or IVDR it is registered as a Regulation device with the full Regulation field set.

Legacy status ends at the dates set in MDR Article 120(3a) and (3b) or IVDR Article 110(3a) and (3b). It ends earlier if the manufacturer stops meeting the conditions in MDR Article 120(3c) or IVDR Article 110(3c), or if the notified body withdraws the certificate. After that the device needs an MDR or IVDR certificate to stay on the EU market. There is no indefinite grandfathering.

DEADLINE
The November 27, 2026 deadline is about registration and not certification. Whether a legacy device may still be placed on the market depends on the conditions in MDR Article 120(3c) or IVDR Article 110(3c). Both include a notified body application and a signed written agreement by the dates they set.

Common Mistakes

MistakeWhat Actually HappensPrevention
Wrong UDI-DI level submittedDevice record created but linked to the wrong certificate or DoC level, requiring correction before reviewConfirm Basic UDI-DI and Unit of Use DI with the issuing entity before preparing any data
EMDN code at category level, not terminalNot accepted by EUDAMED, which allows only leaf codes (BR-UDID-636)Always select a terminal (leaf-node) code. Category codes have child entries in the EMDN browser.
Manufacturer SRN not yet confirmed activeDevice registration cannot start. The actor registration has to be validated and the SRN issued before the manufacturer can register devicesVerify actor registration status before building any device dataset
Certificate number taken from internal tracking, not source documentThe record carries a wrong certificate number. The Notified Body confirms a Regulation device's data when it registers the certificate. A legacy device's Directive certificate details come only from the manufacturer, since the Notified Body does not register themPull certificate numbers directly from the NB-issued certificate PDF
Risk class taken from the wrong legislationA legacy device given its MDR class or a Regulation device given its directive class. The record carries the wrong class or fails validationUse the directive class for legacy devices and MDR or IVDR Annex VIII for Regulation devices
Deadline taken from an AI assistantIn our October 2026 tests Claude Opus 5.5, the Claude Code default, gave a date in late May 2027 in all 12 runs. It counted twelve months from May 28, 2026 instead of from publication of Commission Decision (EU) 2025/2371 on November 27, 2025. A manufacturer following it registers six months lateCount the twelve months in MDR Article 123(3)(e) from publication of the Decision and use November 27, 2026 as explained in the section on November 27 or 28 above

Preparation Checklist

Registration in EUDAMED is a data problem before it is a system problem. Most submission failures trace back to incomplete or incorrectly formatted input, not to the database itself. The following checklist covers the inputs that cause the most rejections.

Before you touch EUDAMED

  • Confirm each device's Basic UDI-DI with the issuing entity (GS1, HIBCC, ICCBBA, or IFA)
  • Resolve every device's EMDN code to a terminal node
  • Verify the manufacturer actor record is active and has a confirmed SRN
  • If non-EU, confirm the Authorised Representative actor record is active and linked
  • Pull every certificate number from source documents, not from internal spreadsheets
  • Confirm each device's risk class under the legislation it is placed on the market under, which for legacy devices is the directive class
  • Identify any devices with implantable, active, SaMD, or biological material flags

Data formatting requirements

  • Trade names: match the device label exactly, including capitalization and punctuation
  • Dates: ISO 8601 format (YYYY-MM-DD) throughout the dataset
  • Country codes: two-letter codes from EUDAMED's country list. It follows ISO 3166-1 alpha-2 except that Greece is EL, the United Kingdom is UK and Northern Ireland is XI
  • Languages: each trade name and description is entered with a language. A device can have several trade names in the same language or in different languages
  • EMDN codes: the complete code of a leaf entry as listed in the EMDN, chosen from the list EUDAMED shows
TIP
EUDAMED also runs a Playground environment for training and testing. Access needs a separate registration. Everything entered there is dummy data, including the Actor ID/SRN. None of it moves to production. Use it to rehearse a device registration with test data before you enter real records.

Enforcement after the deadline is national. MDR Article 97 requires the competent authority to set a period to correct the breach before it restricts a device that presents no unacceptable risk. Each Member State sets its own penalties under MDR Article 113. The full procedure is in what happens if you miss the deadline. If your data is not clean and structured today, the window for fixing it is shrinking.

Frequently Asked Questions

What is the November 27, 2026 EUDAMED deadline?

November 27, 2026 is the registration deadline under the transition period in MDR Article 123(3), as amended by Regulation (EU) 2024/1860 and triggered by Commission Decision (EU) 2025/2371. It covers devices that were on the market before May 28, 2026 and are still being placed on it. A manufacturer that misses it is in breach of the registration duty for each device it has not registered. Enforcement is national. Where the device presents no unacceptable risk, MDR Article 97 requires the competent authority to set a period to correct the breach before it restricts the device. Each Member State also sets its own penalties under MDR Article 113.

How is the November 27, 2026 deadline different from May 28, 2026?

Mandatory use of the first four EUDAMED modules began on May 28, 2026. A device whose first unit is placed on the EU market on or after that date must be registered before that first unit is placed. We apply the same rule to a new identifier on a legacy line, such as a new pack size. November 27, 2026 is the deadline for devices whose first unit was placed before May 28, 2026 and which are still being placed on the market.

Is the deadline November 27 or November 28, 2026?

This site states November 27, 2026. Both dates come from the same trigger, Commission Decision (EU) 2025/2371, published in the Official Journal on November 27, 2025, which starts the twelve-month transition period in MDR Article 123(3). Counted directly that gives November 27, 2026. The worked example in the EUDAMED roll-out Q&A (Q7) counts the period from the day after the triggering event, which would give November 28, 2026. We publish the earlier date because the two errors are not symmetric. Missing the deadline puts a manufacturer in breach of its registration duty, while being ready a day early costs nothing. Confirm with your competent authority before relying on the later date contractually.

Who must register in EUDAMED?

Registration obligations run along operator type rather than product category. Manufacturers must register both an actor record and a device record. Non-EU manufacturers need an Authorised Representative with an active actor record. Importers register separately as economic operators under MDR Article 31. Under MDR Article 13 they must verify that each device they import is registered. Producers of systems and procedure packs must assign the pack a Basic UDI-DI and provide it to the UDI database under MDR Article 29(2). Clinical investigation sponsors follow a separate pathway that is not part of this deadline.

Do legacy devices need EMDN codes and a full EUDAMED device record?

Legacy devices need EMDN codes now. They are registered as legacy devices. They carry a EUDAMED DI and EUDAMED ID in place of the Basic UDI-DI and UDI-DI, as MDCG 2019-5 describes. An existing UDI-DI can be used where one has already been assigned. The legacy record is not the full MDR or IVDR record, but it has its own mandatory fields and the EMDN code is one of them. A legacy device does not need its own record if the same device is already registered as an MDR or IVDR device.

What happens if a required field is missing at submission?

EUDAMED requires every mandatory field before a device record can be submitted. You can save an incomplete record as a draft in the web interface and finish it later. A draft is not a submitted registration, so the dataset still has to be complete before the deadline.

Which EMDN code should be used for a device record?

At least one terminal-level code from the European Medical Device Nomenclature. EUDAMED business rule BR-UDID-636 allows only a leaf code, the lowest level of its branch, to be associated with a device. A category-level code is not accepted.

Where does your own data stand?

Upload your device list and see what EUDAMED would reject.

Run a free readiness check →Or start a project in EUDAMate

Related guides

Classification

EMDN Classification Codes

Navigate the EMDN category taxonomy and find the correct terminal code for each device.

UDI

UDI-DI Grouping Rules

The triggers that require a new Device Identifier and how to structure your UDI hierarchy.

Mapping

GMDN to EMDN Mapping

Why there is no official cross-reference and how to bridge the gap systematically.

Deadline

SSCP Upload in EUDAMED: MDCG 2026-4

Why the SSCP of a class III or implantable device already on the market has its own upload date, March 27, 2027.

Deadline

IVDR Legacy Device Deadlines by Class: 2026-2029

The IVDR Article 110 market-placement dates for legacy IVDs by class, and the conditions attached to them.

© 2026 EUDAMateBack to eudamate.eu