Device registration in swissdamed: when to use online forms, XML or M2M

This article is the 34th instalment of Volume 4, License-holder Import and Fees, of the Swiss Medical Device Registration 50-Article Series. Together with the remaining nine articles of this volume it forms a complete deliverable on this topic. The publication timestamp, article number, title and unique URL are set out in the table below, so that readers can cite this article unambiguously and locate its companion pieces.

1. Key takeaways

Registration in the UDI Devices module becomes mandatory with the definitive entry into force on 1 July 2026, with a transition period running to 31 December 2026; before that, the period from 18 August 2025 to 30 June 2026 was the voluntary registration phase. Devices that are subject to reporting of serious incidents, FSCA or trends have no transition period and must be registered at once from 1 July 2026. The three channels — the online form, XML upload and the M2M machine-to-machine interface — produce no difference whatsoever in legal effect once registration is complete. What differs are unit labour cost, error rate and the real-time quality of status maintenance, so the choice of channel should be decided by the number of UDI-DIs and their frequency of change, not by corporate IT preference.

2. Legal basis

3. Expert insights

1. A channel is a channel, not a tier. No provision states that registration via XML or M2M produces a stronger legal effect; completed registration constitutes fulfilment of the duty under Art. 108 regardless of channel. The real trade-off lies in the cost of errors: online entry remains manageable at a scale of dozens of items, but once volume grows, manual field errors — mixing up UDI-DI and Basic UDI-DI, mis-set status fields — become the main driver of rework. XML upload moves validation upstream to the local system, at the price of a one-off investment in templates and field mapping; M2M, once connected to the master data system, keeps status synchronized in real time, at the price of interface integration and change governance. The decision criterion is therefore the number of SKUs multiplied by the annual number of changes, not the existence of an IT budget.

1. The status field is a cost switch, not merely a data field. The billing logic of Annex 2 is: the first billing date is 31 December 2026, and only UDI-DIs whose status on that day is On the market are billed, while those marked No longer placed on the market on that day are not billed. Channel selection must therefore be bound to the frequency of status maintenance — a company that retires product lines frequently yet relies on a purely manual channel will see lagging status maintenance convert directly into registration fees paid for nothing. Looked at the other way round, this is also the most readily quantifiable benefit of the automated channels.

1. swissdamed and EUDAMED have no interface and no synchronization; a dual upload is mandatory. This negates a common idea: reusing the EUDAMED upload pipeline for Switzerland. The M2M interface can only ever be a Swiss-side interface. The other side of the coin is that this decoupling also means the Swiss side can set its fields and statuses according to national needs, and companies do not have to sacrifice compliant expression on the Swiss side for the sake of keeping both sides perfectly aligned.

4. Practical recommendations

1. Choose the channel by SKU scale (practical estimate): the online form for volumes in the dozens; XML batch upload for medium volumes; M2M for large volumes with high change frequency.
2. Whichever channel is chosen, first build a mapping table for the correspondence between UDI-DI, Basic UDI-DI and product master data, and forbid ad-hoc judgement at the point of data entry.
3. Write status maintenance into the SOP: when a product stops being placed on the market, its status must be switched to No longer placed on the market in the system at the same time, avoiding continued fees for retired UDI-DIs.
4. If the products fall into the categories subject to reporting of serious incidents, FSCA or trends, do not count on the transition period as a buffer: registration must be completed from 1 July 2026 onward without delay.
5. Clarify the division of labour with the EU-side team: the Swiss side is an independent upload, and the completion of EUDAMED must never be allowed to postpone registration in swissdamed.

5. Verification checklist

• □ The mandatory registration start date of 1 July 2026 and the transition end of 31 December 2026 for the UDI Devices module have been confirmed
• □ The channel (online / XML / M2M) has been selected by SKU scale and annual change frequency
• □ The mapping table for UDI-DI and Basic UDI-DI has been built and double-checked by two persons
• □ The status-maintenance SOP is live and retired products are marked No longer placed on the market
• □ Devices subject to serious incident/FSCA/trend reporting have been confirmed as having no transition period and are registered
• □ Dual upload to swissdamed and EUDAMED has been confirmed, with no shared pipeline

Regulatory information verified as of October 29, 2026.

GRZAN supports medical device manufacturers entering the Swiss market end to end. For device registration GRZAN provides Swiss authorized representative (CH-REP) services, plans and executes registration in the UDI Devices module of swissdamed across the online, XML and M2M channels, keeps UDI-DI statuses aligned with market reality before the first billing date of 31 December 2026, and prepares fee budget models covering registration fees and hourly-based charges so that the cost of Swiss market entry stays predictable. For CH-REP appointment, swissdamed registration management or fee budgeting support for the Swiss market, contact info@grzanglobal.com.