Your device data,EUDAMED-ready.

Your device list goes in as it is: ERP export, Excel, or CSV. It comes back mapped to 81 EUDAMED fields, classified against the EMDN tree, and put through up to 135 checks across 44 validation rules.

Every decision scored and recorded.

November 27, 2026 does not move.

EUDAMED roll-out Q&A details the legacy-device timeline · Reg. 2024/1860 changed IVDR transition gates · EUDAMED schema v3.0.30

Every schema revision and guidance update, monitored and applied continuously.

Start your project →See how it works
See a sample before you upload anything →

MDR · IVDR · MDD · IVDD · Money-back guarantee if EUDAMED or your submission partner's tool rejects data entered from our CSV because of our error

EMDN Classification
DeviceEMDN CodeStatus
Surgical scissorsL010403HIGH
Knee implantP090903020104REVIEW
Diagnostic stripW0101060101CONFIRM
Suture, PDO 3-0H010101010103HIGH
4 devices3 HIGH1 REVIEW81 fields mapped
How it works

Four steps. Your device list to data ready to enter in EUDAMED.

01

Upload

Your data, as-is

Export your device list from SAP, Excel, or your ERP. Drop the file. No template, no reformatting required.

Accepts CSV, XLSX, ODS
02

Map

81 EUDAMED fields, auto-mapped

AI reads your column names and maps them to 81 EUDAMED fields. Every match gets a confidence score.

Review mismatches before proceeding
03

Classify

6,773 EMDN leaf codes

Each device is classified against the full EMDN tree. Ambiguous entries are flagged for your review. Nothing is silently guessed.

Ambiguous entries flagged for human review
04

Deliver

Checked against the EUDAMED XSD

Clean CSV, XML files for EUDAMED's bulk upload and a Registration Decision Record (PDF) that you approve. Validated by up to 135 checks across 44 validation rules. Each XML file passes the EUDAMED XSD format check. Your RA team uploads the files or a submission partner does it for you. See what the record contains

Full audit trail, ready for your QMS binder
See where your data stands, free →
Glass-box AI

Every decision is visible.

You approve every classification. EUDAMate shows exactly why each EMDN code was assigned, and flags what needs your review.

DeviceYour ColumnEMDN CodeConfidenceReasoning
Surgical scissorsproduct_typeL010403
HIGH
“Matched: general surgical instrument + scissors morphology”
Knee implantarticle_descP090903020104
REVIEW
“Implantable orthopedic, verify fixation method”
Diagnostic stripproduct_nameW0101060101
CONFIRM
“In vitro diagnostic, subclass ambiguous without IVD indication”
Suture, PDO 3‑0material_typeH010101010103
HIGH
“Wound closure + material field: absorbable polydioxanone”
Drapeitem_categoryT020102
HIGH
“Surgical barrier, draping. Clear category match.”
81 of the 144 EUDAMED device-data fields, mapped per device
Every decision explained as you review, then kept in the RDR you approve
What you actually have

You won't have all 81 fields. Nobody does.

A legacy device needs 23 of them. A typical ERP export covers two or three. The rest sit in technical files, on certificates, in your GS1 account, or nowhere yet.

23
mandatory for a legacy device
17
we work out, for you to check
6
left for you, named before you start

We can't invent data you don't have. We can tell you exactly which 6.

Measured, not asserted

Scored against real submissions.

Run on registered devices, then compared field by field with what their manufacturers had submitted.

The EMDN code
Device name, as uploaded
Plasma Separators For Single Use
Nomenclature code (EMDN) · FLD-UDID-149
B030201Plasmapheresis devices and kits
WhyPlasmapheresis is the separation of plasma. Single use is a property of the device; this branch does not split on it.
Suggested, and the alternatives on screen
One line about what this device is, for example: sterile adhesive wound dressing with absorbent pad

Pick one and the field changes. Nothing is written until you approve it, on every device, including the ones already right.

38%
first suggestion
was their code
68%
on screen, counting
the alternatives
32%
needed one line
from a reviewer

500 devices from 419 companies, names only, with each company's own submissions withheld so nothing could be recognised from its history. Every code you approve feeds the next upload.

The yes/no fields
87
of every 100 filled for you
13
left blank, each with its reason
99%
of those matched
what they submitted
878
devices checked, in
21 countries

It stops where the evidence stops. Matched means matched what the manufacturer submitted, which is the only thing anyone can check.

What you receive

Your Readiness Check,
in minutes.

eudamate.eu/readiness
EUDAMate EUDAMED Readiness Check
Free analysis
No template required
81-field gap report
PDF ready for your RA team
Run a free Readiness Check →

Under the hood

The details you will be asked to defend.

Every technical decision is traceable in your Registration Decision Record.

SCHEMA

Every XML file passes the EUDAMED v3.0.30 XSD format check before export.

CERTIFICATES

When EUDAMate reads a certificate PDF it compares the notified body number and SRN country with a built-in NANDO snapshot and lowers its confidence when the number is not in the snapshot or the country differs.

DEADLINES

Transition deadline warnings for legacy IVDD devices under IVDR Article 110 as amended by Regulation 2024/1860.

NB REFUSAL

A yes/no field for prior notified body refusals, which MDR Article 53(3) has a manufacturer declare when it applies to a notified body. It is not part of the device registration.

LEGACY UDI

Correct EUDAMED DI vs Basic UDI-DI distinction for legacy MDD/AIMDD/IVDD devices.

RULES

Up to 135 checks across 44 validation rules, MDR to legacy, run before the export is delivered.

Supports your ISO 13485 QMS

Controlled vocabulary, append-only audit trail

MDR & IVDR ready

Plus all legacy directives: MDD, AIMDD, IVDD

EUDAMED DTX schema

XML files checked against the official EUDAMED XSD

Database hosted in the EU

Uploaded files deleted right after processing. Project data deleted on a fixed schedule, subscriptions excepted.

PRICING

What it costs.

You see every number before you commit.

SELF-SERVE
PAY PER DEVICEONE-TIME PAYMENT

Self-Serve

Pay per device. Your raw exports in. Clean CSV, XML files and RDR out. Preview your first device free on screen. Preparing 1 or 2 devices costs €39 in total.

Prices for manufacturers

1–2 devices€39 flat
3–24 devices€39 / device
25–99 devices€29 / device
100–499 devices€19 / device
500–1,999 devices€12 / device
2,000+ devices€7 / device

Example: two devices, no subscription: €39 once.

One-time payment per project. No VAT is charged (§19 UStG).

You never pay more than the next tier costs. 24 devices bills the same as 25, and you are credited the 25 tokens.

Processing time grows with the number of devices. Reviewing and approving the classifications is your team's work, at your pace.

INCLUDED

81 EUDAMED fields mapped per device
EMDN classification across 6,773 terminal codes
EUDAMED validation, 50+ checks
Registration Decision Record included

If EUDAMED or your submission partner's upload tool rejects device data entered from our CSV because of a mapping or validation error we made, you get a full refund and a corrected file. This guarantee covers data entered from our CSV. It does not yet cover a rejection of the XML files themselves. Classification choices you approved yourself remain your own regulatory decision.

Delivery guarantee

Registry CareOptional. After delivery.

Keeps your projects and their audit trail for as long as the subscription runs.

Micro≤10 devices
€29/mo
Starter≤50 devices
€79/mo
Standard≤200 devices
€149/mo
Scale≤1,000 devices
€349/mo

Offered after delivery. Two months free with annual billing.

Full breakdown on the EUDAMED data prep pricing page.

EUDAMate works inside your workflow.

Most manufacturers prepare a portfolio once or a few times a year. The subscription plan is built for consultants who prepare data for several clients throughout the year. It includes a multi-client dashboard, an EMDN classification history across all your clients and white-label RDR PDFs that carry your firm's name and logo.

FOR RA CONSULTANTS

Bill for your judgment. We handle the labor.

EUDAMate handles column mapping, EMDN code lookup and 81-field validation. Your clients get a clean, documented output. The time you recover goes back to the regulatory strategy, risk assessment and notified body liaison that warrants your fee.

Every export includes a Registration Decision Record built from a hash-linked audit trail
EMDN classification across 6,773 terminal codes, automated and reviewable
Validation errors caught before your client touches the portal
Output goes out under your client's name, not ours

Token pricing, no monthly commitment. Full breakdown in the pricing section.

FOR REGULATORY PLATFORMS

The data layer your tool is missing.

Your tool handles the portal submission. EUDAMate handles everything before that: mapping raw device exports to 81 EUDAMED fields, running up to 135 checks across 44 rules, classifying EMDN codes, generating a Registration Decision Record. Integrate once as a pre-step. Your users arrive with data ready to enter in EUDAMED rather than the raw exports they started from.

Structured CSV and XML files in EUDAMED's own format
Full audit trail per submission: RDR built from a hash-linked audit trail included
Validated against the EUDAMED schema before it reaches your interface
API-first: documented and testable
Integration options and API access by arrangement.Get in touch →

RESOURCES

Know the deadline.
Know the codes.

MDR · IVDR

May 28, 2026

MDR and IVDR devices entering the EU market on or after May 28 need a valid EUDAMED record in place.
EU 2025/2371

--days
--hrs
--min
--sec
MDD · AIMDD · IVDD

November 27, 2026

Devices placed under MDD, AIMDD, or IVDD need to appear in EUDAMED by November 27. This covers everything already on the EU market.

--days
--hrs
--min
--sec

More in the full library of EUDAMED guides, or look up a code in the EMDN code browser.

FAQ

Questions.

EUDAMED has no CSV import. It takes device data through its user interface, its bulk upload or a machine-to-machine connection. Every export therefore also holds XML files in EUDAMED's bulk upload format, with at most 300 devices in each file. Each file passes the EUDAMED XSD format check before the export is released. That check covers the format. EUDAMED still applies its own business rules when you upload, so it does not show that EUDAMED will accept the data. The export is also validated against up to 135 checks across 44 validation rules for MDR, IVDR and the legacy directives. The Registration Decision Record lists the SHA-256 of the CSV and of each XML file. EUDAMate prepares the data and does not submit it.

We don't use your files to train AI. What we keep is your EMDN decisions: the codes you approve or change, together with the device name, model, trade name and description. They join the matching list we build from the public EUDAMED database. Once a week we also use them to tune the weights of the formula that ranks EMDN suggestions. No customer ever sees another customer's device data. With a subscription your prepared device data stays in your account for as long as the subscription runs. One-off projects are deleted 90 days after your first export (from 1 December 2026; until then 60 days after your last export) or within a day of marking them finished. A project that is never exported is deleted 90 days after it was created (from 1 December 2026; until then 60 days after your last activity on it). Accounts we provide free of charge are exempt from these deletion rules.

No. EUDAMate is a data preparation tool with no connection to EUDAMED. We map your device data to the EUDAMED field schema, classify EMDN codes, and validate against up to 135 checks across 44 validation rules. The result is a clean CSV and XML files in EUDAMED's bulk upload format. Your RA team or submission partner uploads the files or enters the data in EUDAMED. We are the step before submission, not submission itself.

Any tabular format: Excel (.xlsx, .xls), CSV, or TSV, including raw ERP exports. Column names can be in any language: German, French, Turkish, English. The mapping to 81 EUDAMED fields is handled for you.

Enough to start. Most ERPs hold a fraction of what EUDAMED wants, and a part number plus a description is normal. A legacy device needs 23 mandatory fields. We fill 17 of them from what you upload and list the rest field by field. We can't invent data you don't have. What we can do is tell you which fields are missing and where they usually come from, before you start instead of after a rejection.

The RDR is a PDF that names who approved each export. It records each AI suggestion with its confidence, every change anyone made with who and when, the reason for each override and the validation results. Each logged event is linked by SHA-256 to the one before it. Audit events cannot be edited in our database. Anyone holding the record can check its audit trail fingerprint at www.eudamate.eu/verify. File it in your QMS as the record of how your registration data was prepared. Read the full RDR format

Every AI suggestion comes with a confidence score: Green (high confidence, auto-approvable), Yellow (moderate, review suggested), or Red (low or missing, manual entry required). You see the alternatives and you can override any suggestion with a reason. Before export you confirm who approves it.

Yes. Legacy device support is a core focus. By November 27, 2026 every legacy device you are still placing on the EU market needs a EUDAMED record. Two things are out of scope. First, devices for which you place no further units on the EU market from 28 May 2026, the date the UDI/DEV module became mandatory. Second, legacy devices whose Regulation equivalent, MDR or IVDR, is already registered under the same UDI-DI, reference number or trade name, provided no change was made that assigns that Regulation device a new UDI-DI. The two exemptions come back differently. The first falls away if any post-market or vigilance action occurs. The second is narrower: the legacy device needs registering only where the action concerns the legacy device and not its registered Regulation equivalent (EUDAMED roll-out Q&A, Q8 and Q14). The pipeline handles MDR, IVDR, MDD, AIMDD and IVDD, including the EUDAMED DI versus Basic UDI-DI distinction that legacy devices need.

Submission portals handle the upload to EUDAMED. They need clean structured data to work. EUDAMate is the step before. We take your device data as it is and map it to EUDAMED fields in a clean CSV and XML files that pass the EUDAMED XSD format check. It adds to your existing submission workflow and does not replace it.

If EUDAMED or your submission partner's upload tool rejects device data entered from our CSV because of a mapping or validation error we made, you get a full refund and a corrected file. This guarantee covers data entered from our CSV. It does not yet cover a rejection of the XML files themselves. Classification choices you approved yourself remain your own regulatory decision. Your RDR shows each one.

November 27, 2026 does not move.

Your legacy portfolio does not register itself. Preview your first device free, on screen, before you pay for anything.

Start your project →Run a free Readiness Check

€39 for one or two devices. One-time payment per project, no subscription.