Usually, EUDAMED registration is treated as a data task. For a labeling team, it's also a second place the label has to be right.
The deadline is close. Devices that were first placed on the market before May 28 and are still being sold must be registered by November 27, 2026 at the latest. Some sources give November 28, so treat the 27th as your cut-off. For who must register, what's due and how, see our EUDAMED Registration Guide.
This article is about the other half of the job: making sure what you register matches what's printed on the device and its packaging.
Why a Mismatch Can Be Seen
The core data elements submitted to the EUDAMED UDI database are meant to be accessible to the public. Several of them are defined by reference to the label itself. The manufacturer's and authorized representative's details, for example, are entered as they appear on the label.
So a label that disagrees with its record isn't an internal matter. A regulator, a customer or anyone checking can see both.
The Field Map
Here is where the label and the record meet. The fields are paraphrased from the core data elements in Annex VI, Part B. The examples in the last column show how a mismatch can start. They are illustrations and not a measure of how often it happens.
The Basic UDI-DI isn't printed on the label. It's the model-level key in the database, and it appears in the certificate and the EU declaration of conformity. Your UDI-DIs, one per packaging level, are what connect the label to the record. Our UDI Labeling Requirements guide covers how to keep them consistent across levels.
Four Places a Mismatch Can Start
A packaging change. A new pack size or configuration is approved for print, but the record isn't updated. Or the record is updated and the label isn't.
A market variant. A label for one market carries a different trade name or reference from the base record.
A change of economic operator. An address or an authorized representative changes in one place before the other.
A third-party label. A contract manufacturer or supplier produces a label that doesn't go through the same review as your own.
None of these is unusual, and none needs bad intent. They happen because two systems, the artwork and the database, are updated by different people at different times.
A Ten-Minute Check
You can test this on one device today.
- Pick one device that's still on the market.
- Write down the printed data at each packaging level: the unit pack and any outer carton.
- Open the registered record and compare the two, field by field, using the map above.
- For each difference, decide which side is right. If the record is wrong, correct it in EUDAMED. If the label is wrong, the fix goes through your normal artwork approval, and you check the record again afterward.
- Repeat for your highest-volume devices first.
Where the Label Side Fits
The label half of that comparison is the part Content Compare handles. It compares label files against the approved master at every packaging level, language and format, and it verifies the UDI barcodes.
It doesn't check EUDAMED records. That comparison is a data task inside your registration process. What Content Compare does is make sure the label that goes to print is the one that was approved, so the label and the record start from the same source.
Frequently Asked Questions
Is EUDAMED data public?
The core data elements submitted to the UDI database are meant to be accessible to the public. Check the public interface to see what's displayed for your devices.
Does the label have to match the EUDAMED record?
Several fields in the record are defined by reference to the label, such as the manufacturer's and authorized representative's details. Where a field comes from the label, the two should agree, and a mismatch is something regulators and customers can see.
Does Content Compare check EUDAMED?
No. It checks label files against the approved master. Registration data is checked in your registration process.
Where can I find the deadline and who must register?
In our EUDAMED Registration Guide.
Content Compare verifies device labels, IFUs, and UDI carriers against the approved source across every packaging level, language, and format, printed or electronic. See how it works on your own labeling.
