top of page

ÜTS Bulk Product Registration

Your catalogue has hundreds of products and entering each one by one on the ÜTS screen takes weeks. The TİTCK Guide defines a separate route for this job: a template Excel file is filled in, zipped together with label and packaging images, and uploaded to the system in one go

ÜTS Bulk Product Registration: Notifying Multiple Devices With an Excel Template and ZIP Package

Your catalogue has hundreds of products and entering each one by one on the ÜTS screen takes weeks. The TİTCK Guide defines a separate route for this job: a template Excel file is filled in, zipped together with label and packaging images, and uploaded to the system in one go. The method works, but a single Turkish character in a file name or a single folder inside the zip can invalidate the entire upload.

This page explains all the bulk operation screens, the template rules, the zip limits and the application step that must be taken after a bulk upload, together with the relevant articles of the Guide. The references belong to TİTCK's "Guide on Registration Processes of Medical Devices to the Product Tracking System" (TCKKD-KLVZ-03).

Where Do You Enter the Bulk Operation Screens?

All bulk operations start from one place. The second paragraphs of Articles 31, 32, 33 and 34 of the Guide describe the same path: from the "Bulk Operations" area on the "List My Medical Devices" screen, you enter the relevant bulk operation screen. The same entry point applies to the other bulk screens defined in Articles 35, 36, 37 and 38 of the Guide.

All the bulk operation screens are built on the same logic: a template Excel file is downloaded from the screen, filled in and uploaded back to the relevant upload area. The difference is which screen serves which framework and which data group. Choosing the screen is therefore the first decision of the job.

  • Bulk Add/Update MDD/AIMDD/IVDD Medical Device: device registrations under the old regulations, Article 31 of the Guide

  • Bulk Add/Update MDR Medical Device: device registrations under MDR, Article 32 of the Guide

  • Bulk Add/Update IVDR Medical Device: device registrations under IVDR, Article 33 of the Guide

  • Bulk Delete Device: deleting records or setting them to "Deleted" status, Article 34 of the Guide

  • Bulk Update Product Without Application: updating fields that do not require an application, Article 35 of the Guide

  • Bulk Add Market Placement Information: linking box and container barcodes, Article 36 of the Guide

  • Bulk Add Storage/Usage Conditions to Devices: conditions that are not present as parametric fields in the template, Article 37 of the Guide

  • Bulk Add Dimensions to Devices: dimension information not present in the template, Article 38 of the Guide

Three Separate Bulk Add/Update Screens

There are three separate screens for the device registration itself, and they are divided by framework. The Guide regulates each in a separate article; there is no data transfer between the screens.

The first paragraph of Article 31 of the Guide says that the information to be entered into the system for device registration under the old Medical Device Regulations can be entered one by one for each device as described in Article 25, or in bulk through the "Bulk Add/Update MDD/AIMDD/IVDD Medical Device" screen. The same structure is repeated in the first paragraph of Article 32 for MDR with reference to Article 27, and in the first paragraph of Article 33 for IVDR with reference to Article 30.

This means that the bulk template is the file version of the fields on the one-by-one registration screen. A field that is mandatory in one-by-one registration is also mandatory in the bulk template. Changing the screen does not lighten the information requested.

Where Is the Template Excel File Downloaded?

You do not create the template yourself; the system provides it. The third paragraphs of Articles 31, 32 and 33 of the Guide state that the template Excel file prepared for bulk notification is downloaded from the "Download Template Excel File" area on the relevant screen. The same area exists on the other bulk screens: the third paragraph of Article 34 defines the same download step for the bulk delete template, the second paragraph of Article 35 for the update-without-application template, the third paragraph of Article 36 for the market placement template, the third paragraph of Article 37 for the storage/usage condition template and the third paragraph of Article 38 for the dimension template.

Templates are specific to the screen. The column structure of a template downloaded from the MDR screen is not the structure that the IVDR screen expects. In practice, keeping an old template and reusing it is a common habit; if the template has been updated, this habit leads directly to errors. The safe way is to download the template again from the screen before each bulk job.

What Do the Red and Yellow Columns Mean?

The colors in the template are not decoration; they carry rules. The fourth paragraph of Article 31 of the Guide defines this explicitly: in the template Excel file, red columns indicate mandatory fields, and yellow columns indicate fields that are mandatory depending on the entry of another field. The same sentence is repeated in the fourth paragraphs of Articles 32 and 33 and in the third paragraph of Article 35.

  • Red column: a field that must be filled in on every row; it cannot be left empty

  • Yellow column: a conditionally mandatory field; it becomes mandatory depending on the value entered in another field

  • Uncolored column: filled in according to the status of the device

The same paragraphs say one more thing: those fields are filled in for every device for which bulk information entry is requested, in line with the explanations for the relevant fields in the template file. That is, the explanatory texts inside the template are part of the rule. Under which condition a yellow column becomes mandatory is often written only in that explanation.

Notification Information File: What Goes Inside the Zip?

In a bulk device registration, what you upload is not a single Excel file but a package. The fifth paragraph of Article 31 of the Guide defines this package: the Notification Information File is created by compressing, in zip format, the template Excel file in which the notification information is entered together with the label information files and the different packaging image files of the relevant devices, and this zip file is uploaded to the "Zip File" area on the screen. The same provision is repeated for the MDR and IVDR screens in the fifth paragraphs of Articles 32 and 33.

The files in the package do not have to be of a single type. The sixth paragraphs of the same articles state that the files that make up the Notification Information File can be in different formats (excel, pdf, jpg, jpeg, png and similar) depending on their type. The restriction is not in the format but in how the package is built.

Files Must Be Directly in the Zip, Without Folders

This is the most frequently encountered structural error. The sixth paragraphs of Articles 31, 32 and 33 of the Guide make the same statement: these files must be directly inside the zip file to be uploaded to the "Zip File" area, not in separate folders inside the zip. The seventh paragraph of Article 35 repeats the same rule for the zip file to be uploaded to the "Bulk Update Product Without Application" screen.

In practice the error mostly arises from the behavior of the archive program. When you right-click a folder and compress it, the folder remains as a directory inside the archive and the files appear one level down. The correct way is to select the files inside the folder, not the folder, and compress them. When the zip is opened, the Excel and image files should appear directly at the root level.

Maximum 200 MB

The size limit is written. The seventh paragraphs of Articles 31, 32 and 33 of the Guide state that the size of the Notification Information File to be uploaded to the "Zip File" area can be at most 200 MB.

What pushes the limit is almost always the images; the Excel file itself is small. High-resolution packaging photographs and scanned label files easily exceed 200 MB when spread across a few hundred products. The practical solution is to split the product list into several batches and upload each batch as a separate zip. When splitting, making sure the batches are consistent with the application grouping makes the work easier later.

No Turkish Characters in File Names

The eighth paragraphs of Articles 31, 32 and 33 of the Guide and the eighth paragraph of Article 35 carry the same provision: Turkish characters (Ç/ç, Ğ/ğ, İ/ı, Ö/ö, Ş/ş and Ü/ü) cannot be used in file names.

The ban concerns file names and covers every file inside the zip. In practice, this error appears when file names are derived from the product name: a name such as "ölçüm-cihazı-görsel1.jpg" contains "ö", "ç" and "ı" all at once. When writing the image name in the template, the same name must also be kept; the name written in Excel and the file name in the zip must match.

"Bulk Update Product Without Application": Fields Not Requiring an Application

Not every update requires a new application. The first paragraph of Article 35 of the Guide describes the scope of this screen: device information for which updates without application are allowed, such as linking a new catalogue to the relevant device in ÜTS or uploading a new product image, can be entered in bulk through the "Bulk Update Product Without Application" screen.

All three device registration articles direct to this screen. The ninth paragraphs of Articles 31, 32 and 33 of the Guide state that fields that can be updated without application can be updated through the "Bulk Update Product Without Application" screen mentioned in Article 35. That is, which field will be updated from which screen is determined not by the framework of the record but by whether the field requires an application.

If the Catalogue Field Is Left Empty, the Link Is Severed

This is the behavior of the screen that demands the most attention. The fourth paragraph of Article 35 of the Guide states that in the "Product Catalogue List" field of the template, the names of all product catalogues that are requested to be linked to the device and that were registered in ÜTS under Article 24 of the Guide are entered, giving the format 1234567-KT6 and 1234567-KT10 as an example.

The continuation of the same paragraph carries the critical sentence: if this field is left empty and the device had a linked product catalogue before the operation, the link between the device and that catalogue is severed. The paragraph also says the field is left empty if the device has no document of the "Catalogue" type.

This is the opposite of the assumption "if I leave it empty, I won't have touched it". If the catalogue column is left empty in a file prepared only to add images, the existing catalogue link of every device in that file is broken. For devices with a catalogue link, the field must be filled in with the existing catalogue names.

If Health Market Is Selected, at Least 3 Images

The fifth paragraph of Article 35 of the Guide sets a numerical rule: if the field "Will It Be Sold in Health Market / Will SGK Reimbursement Be Made?" in the template Excel file is marked "Yes", there must be at least 3 images in total for the device, including the new images requested to be added.

The paragraph also gives the format rule: it is enough to enter the file names of the new images requested to be added in the relevant field, and these names are written separated by commas; the Guide shows the format "resim1.jpg, resim2.jpg" as an example. The number refers to the total image count of the device together with the newly uploaded ones; if the device already has two images, one new one is enough.

The sixth paragraph of the same article defines the packaging step: the template Excel file and the new product image files requested to be added are compressed in zip format, and this zip file is uploaded to the "Upload zip file" area on the screen.

The "Bulk Delete Device" Screen and the Reason Column

Deletion can also be done in bulk. The first paragraph of Article 34 of the Guide states that deletion can be made for all device types within the scope of Articles 25 to 30 of the Guide (medical devices under the old Medical Device Regulations, MDR and IVDR, SİP and custom-made medical devices). The second paragraph says the bulk form of this operation is carried out from the "Bulk Delete Device" screen.

The content of the file is defined in the fourth paragraph: in the fields of the template Excel file, the primary product numbers of all devices requested to be deleted and the reasons for deletion are entered, and the Bulk Device Deletion File is created. The fifth paragraph states that this file will be in Excel format; there is no zip upload step here.

Which records can be deleted is also limited. The sixth paragraph of Article 34 of the Guide says that the device records requested to be deleted in ÜTS must be in "Draft", "Ready for Application", "Registered" or "Rejected" status. Under the seventh paragraph, records in "Draft" and "Ready for Application" status are deleted from ÜTS. Under the eighth paragraph, records in "Rejected" status, except for "Registered" ones and those with a Reject-3 decision, are not deleted from ÜTS but set to "Deleted" status. The ninth paragraph clarifies the authority: device records can be deleted only by the relevant company; the Agency does not perform device record deletion in ÜTS.

"Bulk Add Market Placement Information"

This screen is for linking box and container barcodes to the device's unique product barcode. The first paragraph of Article 36 of the Guide describes the operation: box/packaging and container barcodes containing multiple products are linked to the unique product barcode (Primary Product Number or UDI-DI Number) of a device for which a device record was created under Articles 25, 27 and 30 of the Guide and which became "Registered" after the application made to the Agency under Article 39 was concluded positively.

The order here is important. Market placement information is not added to a device whose registration is not yet completed; the application of the device must have concluded positively and the record must be in "Registered" status. Under the fourth paragraph, the fields in the template Excel file are filled in completely in line with the explanations in the template and uploaded in Excel format to the "Upload the Excel file" area.

"Bulk Add Storage/Usage Conditions to Devices"

Bulk device templates do not carry all data. The first paragraph of Article 37 of the Guide defines this gap: just as device information can be entered in bulk under Articles 31, 32 and 33, storage/usage condition values that are not present as parametric data fields in the template files mentioned in the relevant articles can also be added to ÜTS in bulk. The second paragraph says that the "Bulk Add Storage/Usage Conditions to Devices" screen is entered for this.

There is no package in this operation. The fourth paragraph of Article 37 of the Guide states that the fields in the template Excel file are filled in completely and uploaded in Excel format to the "Upload the Excel file" area. That is, the zip, the 200 MB limit and the no-folder rule do not apply on this screen but on the device registration screens.

"Bulk Add Dimensions to Devices"

The same structure has been set up for dimension information. The first paragraph of Article 38 of the Guide states that dimension information values that are not present as parametric data fields in the template files within the scope of Articles 31, 32 and 33 can be added to ÜTS in bulk. The second paragraph defines the "Bulk Add Dimensions to Devices" screen and the third paragraph the area from which the template is downloaded.

The fourth paragraph again foresees only an Excel upload: the fields in the template file are filled in completely and uploaded in Excel format to the "Upload the Excel file" area.

A Bulk Upload Does Not Complete the Registration: An Application Is Required

A bulk upload gets the data into the system; it does not get the record assessed by the Agency. The tenth paragraph of Article 31 of the Guide writes this explicitly: for the device registration or update notification to be made under this article to be assessed for conformity with the old Medical Device Regulations and the provisions in the Guide, a device application must be made to the Agency as mentioned in Article 40 of the Guide.

The same provision is repeated in the tenth paragraph of Article 32 for MDR and in the tenth paragraph of Article 33 for IVDR. The fifth paragraph of Article 37 and the fifth paragraph of Article 38 of the Guide also impose the same application obligation for storage/usage condition and dimension additions.

This is the most common misconception of companies that do bulk uploads. When the upload concludes successfully, the products appear on the "List My Medical Devices" screen; but appearing is not being registered. Unless an application is sent, the device does not enter the Agency's assessment.

One by One or in Bulk? Decision Guide

The Guide does not regulate this preference; it offers the bulk route as an option and always keeps the one-by-one route open. The assessment below is guidance based on practical experience, not a legal provision.

Three things are decisive in practice. The first is the number of products: below fifteen or twenty products, the cost of filling in the template and preparing the zip often does not exceed the cost of entering them one by one. The second is data quality: if your product list is already in a clean Excel with barcodes and variants, the bulk route works fast; if the data is scattered across different files, filling in the template becomes the main job. The third is whether the image and label files are ready: if the file names have not been organized, the most time-consuming part of the bulk route starts here.

Screen selection, on the other hand, is not a preference but a rule. Articles 31, 32 and 33 of the Guide tie three separate screens to three separate frameworks. Trying to upload an MDR device from the old regulations screen results in the rejection not of a single row but of the whole file.

Five Frequent Mistakes in Bulk Uploads

The five headings below correspond directly to the relevant paragraphs of the Guide. All five appear at the upload stage and all five require repackaging.

  • Wrong framework screen: if the framework of the device and that of the screen do not match, the file is not valid. The screens are defined separately in Articles 31, 32 and 33 of the Guide.

  • Zip with folders: under the sixth paragraphs of Articles 31, 32 and 33 of the Guide, the files must be directly inside the zip file, not in separate folders inside the zip.

  • Exceeding 200 MB: under the seventh paragraphs of the same articles, the size of the Notification Information File can be at most 200 MB.

  • File names with Turkish characters: under the eighth paragraphs of the same articles, the characters Ç/ç, Ğ/ğ, İ/ı, Ö/ö, Ş/ş and Ü/ü cannot be used in file names.

  • Leaving the catalogue field empty: under the fourth paragraph of Article 35 of the Guide, if the "Product Catalogue List" field is left empty, the link between the device and the existing catalogue is severed.

Checklist After a Bulk Operation

When the upload is finished, the job is not finished. The three steps below turn a bulk upload into a completed record.

  • Read the upload result: the system reports whether the rows in the file were processed. Unless faulty rows are corrected and uploaded again, those devices do not enter the system.

  • Check the status: sub-item (a) of the tenth paragraph of Article 25 of the Guide defines the "Ready for application?" field. If this field is selected as "No", the status of the notification is saved in ÜTS as "Draft"; if "Yes", the status is saved as "Ready for Application" and the record is listed on the "List My Medical Devices" screen. Before sending an application, verify that the relevant devices are in "Ready for Application" status.

  • Send the application: under the tenth paragraphs of Articles 31, 32 and 33 of the Guide, a device application must be made to the Agency under Article 40 for the notification to be assessed. In applications under the old regulations, under the seventh paragraph of Article 40, only devices linked to the same GMDN code can be gathered in a single application; plan the application grouping accordingly.

A bulk upload, when set up correctly, moves hundreds of products into the system in a single pass; when set up wrongly, it leads to the same file being prepared again and again. Companies can also carry out this work by opening user authorization to a consultant from their own ÜTS company page. The consultant prepares the templates, builds the zip packages and creates the device records with the "Medical Device Registration Officer" authorization; the person who signs the application electronically remains the company's authorized signatory, and responsibility for the accuracy of the data entered in the template remains with the company.

ÜTS Registration

Medical Device ÜTS Registration Consultancy

Request an ÜTS registration consultancy quote

Ehlibeyt Mahallesi, Tekstilciler Caddesi No: 35/7 06520 Çankaya / Ankara - TÜRKİYE

Cevizli Mahallesi, Zuhal Caddesi Ritim İstanbul B Blok, No:44 Maltepe / İstanbul - TÜRKİYE

info@medexmedikal.com
+90 505 580 4622
+90 312 389 1354

ÜTS Guides · Legislation Calendar · Glossary · ÜTS Guide Index · Frequently Asked Questions

Services: ÜTS Consultancy · Who Carries Out the ÜTS Registration? · ÜTS Document Registration Consultancy · ÜTS Product Registration Consultancy · Importer ÜTS Registration Consultancy · Sales Centre Authorisation Certificate · EUDAMED Registration Consultancy · MDR/IVDR Declaration of Conformity · Technical File Preliminary Review · Label and Instructions for Use Check · PRRC Service · PMS and PSUR · Clinical Evaluation · EMDN and GMDN Code Determination · Certificate of Free Sale · EUDAMED XML Generator · ÜTS Registration Training · Correction of a Rejected ÜTS Application

KVKK and Privacy Policy | Cookie Policy | Accessibility Statement

© 2026 Medex Kurumsal Danışmanlık Ltd. Şti.

bottom of page
WhatsApp Hemen Ara