28 May 2026: The EUDAMED Deadline MedTech Leaders Can't Ignore
The EUDAMED deadline is 28 May 2026. What UDI, consignment and field inventory compliance actually requires of MedTech leaders, and how to close the gap in just 6-8 weeks.
The deadline no medical device leader can afford to miss
On 28 May 2026, the European Database on Medical Devices (EUDAMED) becomes mandatory. From that date, the Unique Device Identification (UDI) and registration modules are no longer voluntary - every manufacturer, importer and authorised representative placing medical devices on the EU market must register and submit UDI data.
For most MedTech supply chain leaders we talk to, the regulation isn't the problem. The operational reality is.
"We can register the device in EUDAMED. The hard part is knowing where every unit actually is - in our warehouse, at a hospital on consignment, or in a surgeon's loaner kit - and keeping that UDI record accurate in real time." - VP Supply Chain, global orthopaedics OEM
What EUDAMED actually demands of your operation
It's not just a database entry. Full EUDAMED readiness requires:
- UDI-DI and UDI-PI captured and synchronised with your ERP for every single device
- Traceability down to batch/lot and expiry - including consigned stock at customer sites
- Vigilance and post-market surveillance data linked back to the specific device instance
- Actor registration (manufacturer, importer, authorised representative) with correct Single Registration Numbers
Your ERP was never designed for the last part of that chain - the field. That's where EUDAMED compliance quietly breaks.
The field inventory gap
In MedTech, roughly 30-40% of finished goods inventory sits outside the warehouse - at hospitals on consignment, in loaner kits, with sales reps in trunk stock, at surgical centres. Spreadsheets, paper logs and manual phone calls still dominate this layer in 2026.
That creates three EUDAMED failure modes:
- Stale UDI data. A consigned implant gets swapped at the hospital, but the UDI record in your ERP still shows the original lot.
- Missing traceability. A recall hits a batch - and you can't tell regulators within 24 hours exactly which hospitals have affected units.
- Expiry blind spots. A lot expires on the shelf at a surgical centre. Nobody logs it. It gets used.
Each one is a direct EUDAMED breach. Each one is a patient safety issue.
What "ready" looks like operationally
The manufacturers we see getting ahead of 28 May are doing four things:
- Closing the field inventory layer. Deploying mobile-first, barcode-based tools that let hospital staff, reps and field engineers log every movement - with UDI, lot and expiry - in under 10 seconds.
- Integrating with the ERP of record. No parallel system. Every field transaction syncs back to SAP, Oracle, Sage, BC or whatever runs the business.
- Automating EUDAMED submissions. UDI data flows from master data → ERP → EUDAMED without manual re-keying.
- Running recall drills. Can you pull every affected unit, at every location, within 4 hours? Most can't. The ones who've closed the field gap can.
The Ventory proof point
A global medtech manufacturer uses Ventory to track consigned medical devices at hospital sites across Europe. Every movement is logged against UDI, lot and expiry - in real time, with 95%+ adoption from field staff - and synchronised into their core ERP. That same architecture is what makes EUDAMED compliance a data question rather than a fire drill.
At a national ambulance service, a similar deployment delivered 99.76% stock accuracy across 100 ambulances - proof that the model works beyond the warehouse wall.
What to do in the next 30 days
If 28 May 2026 is on your radar (and it should be), the order of operations we recommend:
- Run a UDI gap assessment - what percentage of your field inventory has clean, current UDI/lot/expiry data today?
- Pick the highest-risk category (usually implants on consignment) and close the loop there first
- Pilot a field inventory layer at 3-5 customer sites before rolling broadly
- Wire it into your EUDAMED submission process - so compliance becomes a byproduct of good operations, not a monthly project
The regulation isn't going away. The companies that treat 28 May as an operating-model deadline - not a data-entry deadline - will be the ones still competing on the other side.
Need a UDI/EUDAMED field inventory assessment? Book a 30-minute call with our MedTech team - we'll walk through your current gaps and what closing them looks like in 6-8 weeks.
Frequently asked questions
What is EUDAMED and when does it become mandatory?
EUDAMED is the European Database on Medical Devices. From 28 May 2026, its UDI and device registration modules become mandatory - every manufacturer, importer and authorised representative placing medical devices on the EU market must register and submit UDI data.
Who needs to comply with EUDAMED?
All MedTech manufacturers, importers and EU authorised representatives selling medical devices in the EU. It applies to devices in your warehouse, devices on consignment at hospitals, loaner kits and any stock at customer sites.
What does EUDAMED require at the point of use?
Real-time capture of UDI-DI, UDI-PI (lot, serial, expiry) every time a device is used, transferred or returned - with a clean audit trail from field back to ERP and into EUDAMED.
Why do most MedTech ERPs fail EUDAMED compliance?
Because 30-40% of MedTech inventory sits outside the warehouse - on consignment, in loaner kits, in trunk stock. Traditional ERPs assume stock lives in the warehouse. A field inventory layer closes that gap.
How fast can we deploy a field inventory layer before 28 May 2026?
Typical Ventory deployments go live in 4-8 weeks for a first vertical (usually implants on consignment). Production-ready, ERP-integrated, with 95%+ field adoption.
About Ventory
Ventory is a real-time field inventory management platform trusted by leading medtech manufacturers, healthcare providers and logistics operators. ERP-agnostic (SAP, Oracle, Sage, Dynamics 365 BC), mobile-first, and built for EU MDR, FDA UDI and EUDAMED compliance. Learn more at ventory.io.
