Registering 300+ Devices in swissdamed Without Losing a Month

RegTrac graphic titled swissdamed Bulk Upload, showing XML file upload and the M2M API feeding device registrations into swissdamed, with up to 300 UDI-DIs per XML file

If you have five devices, swissdamed’s online editor will do the job in an afternoon. For anything larger, a swissdamed XML upload is the practical route.

If you have 300, 800 or 2,000 UDI-DIs, entering them by hand is not a realistic plan. And Swissmedic has been clear on one point: there is no Excel bulk upload template.

With the transition period ending on 31 December 2026, large portfolios need a bulk route that works the first time. This guide explains your options, the technical rules that cause rejections, and a workflow that keeps you in control.

Key takeaways

  • There is no Excel bulk upload template in swissdamed.
  • Bulk routes are XML upload (EUDAMED XSD format, up to 300 UDI-DIs per file) or the M2M REST API.
  • POST DEVICE files accept the device:Device element only.
  • Uploading is not enough. Registration is complete only once the Swiss market status is set.
  • Test in the swissdamed playground before uploading to production.

Three ways to register devices in swissdamed

Route

How it works

Best for

Watch out for

Online editor

Manual entry in the swissdamed user interface

Fewer than ~20 UDI-DIs, corrections, discarding records

Slow and prone to errors at scale

XML upload

Upload XML files in EUDAMED format (GET DEVICE or POST DEVICE)

Medium to large portfolios, data already in EUDAMED

Strict schema and business rules, 300 UDI-DIs per file

M2M (machine to machine)

REST API exchanging JSON, live in production since 5 June 2026

Very large portfolios, frequent updates, IT-mature organizations

Needs development and testing. Swissmedic advises it only for actors with extensive IT expertise or an experienced provider.

For most manufacturers, XML upload is the sweet spot: it scales, it reuses data you may already have, and it does not require building an integration.

swissdamed XML upload rules that cause rejections

swissdamed accepts XML files that comply with the EUDAMED XSD schema (Swissmedic’s sample files reference XSD version 3.0.30). Every file is checked for both format and business rules. The rules that matter most:

1. Two accepted formats only.

  • GET DEVICE: XML downloaded from the restricted area of EUDAMED. The fastest route if your devices are already registered in the EU.
  • POST DEVICE: XML you generate yourself, following EUDAMED’s device service definition.

Other EUDAMED services, such as the Basic UDI-DI service, are not accepted.

2. POST files accept the `device:Device` element only.

Files built around device:BasicUDI or device:UDIDIData will be rejected.

3. Maximum 300 Basic UDI-DI/UDI-DI pairs per file.

A 900-device portfolio means at least three files, and each one is validated separately.

4. One-to-one pairing for manual XML uploads.

Each Basic UDI-DI must map to one UDI-DI per entry in the file.

5. Upload does not mean registered.

After a successful upload, the Swiss market status must still be set for registration to be complete.

6. Some mistakes cannot be edited.

If a non-updateable field is wrong, the UDI-DI has to be discarded with a stated reason, and that can only be done in the user interface. Getting the data right before upload saves real time.

7. Drafts expire.

Draft UDI-DIs are deleted automatically 30 days after their last update.

Use the playground first

Swissmedic provides a playground environment that mirrors production. Its technical documentation applies to both. Before you send hundreds of records to production, run a representative sample through the playground: one device per regulation (MDR, IVDR, legacy), one system or procedure pack if you have them, and your most complex product families.

One exception: Master UDI-DI registration is not yet available in the playground, so devices that need one are registered directly in production.

A practical bulk registration workflow

Step 1: Gather your data.

If your devices are in EUDAMED, export them via GET DEVICE. If not, consolidate your master data (Basic UDI-DI, UDI-DI, risk class, regulation, nomenclature codes, trade names, certificates) into one controlled source.

Step 2: Clean and check.

Check against Swissmedic’s UDI Data Dictionary and Business Rules documents. Look for missing mandatory fields, broken Basic UDI-DI/UDI-DI pairings and legacy devices that are easy to miss.

Step 3: Build and split the XML.

Generate POST DEVICE XML (or use your GET DEVICE export) and split it into files of 300 or fewer UDI-DIs.

Step 4: Validate before you upload.

Validate every file against the XSD. A file that fails here would fail in swissdamed too.

Step 5: Test in the playground.

Upload a representative sample and fix any business rule errors.

Step 6: Upload to production.

Via the account that holds the registration rights: the Swiss manufacturer’s account, or the CH-REP’s account for foreign manufacturers.

Step 7: Complete and reconcile.

Set the Swiss market status, then compare what is registered against your master list. Keep the evidence.

Should you use the swissdamed M2M API?

Probably not yet. M2M makes sense if you have thousands of UDI-DIs, frequent changes and an in-house IT team that can build, test and maintain an API integration. For a one-off push to meet the 31 December deadline, a validated XML process gets most manufacturers there faster and with less risk. You can move to M2M later, once your data is stable.

Frequently asked questions

No. Swissmedic has confirmed there is no Excel bulk upload template. Bulk registration uses XML (EUDAMED format) or the M2M API.

Up to 300 Basic UDI-DI/UDI-DI pairs per file.

Yes. XML downloaded from EUDAMED using GET DEVICE can be uploaded to swissdamed. You will still need to complete the Swiss-specific fields and set the Swiss market status.

swissdamed follows the EUDAMED XSD. Swissmedic’s sample files reference version 3.0.30. Always check the current version on Swissmedic’s technical documentation page.

Yes. The swissdamed playground mirrors production and is recommended for testing XML and M2M uploads.

Large portfolio, tight deadline?

RegTrac provides swissdamed bulk registration support. Our regulatory team will:

  • Review your device data for completeness and swissdamed business rule issues
  • Prepare and structure your XML files to the EUDAMED schema
  • Test a representative sample in the swissdamed playground
  • Guide your upload and market status completion, and help you reconcile the result

You stay in control of your data. We help you get it right the first time.