Pure Global AI
Turkey flag

Turkey medical device regulations

Official sources linked

TITCK rules and guidance for medical device market access, registration, and lifecycle compliance. Each code opens a metadata page with the official source and readable HTML when available.

5 documents2 categories100% linked to official sourcesauthority TITCK5 readable HTML
CodeRegulationCategoryEffectiveProvenance
IVD Medical Device Regulation, Official Gazette No. 31499
İn Vitro Tanı Amaçlı Tıbbi Cihaz Yönetmeliği — consolidated national body
Complete regulator-linked consolidated national regulation body, retaining all 60 physical PDF pages, amendment footnotes and publication/amendment table. The formal annexes are a separate official DOCX source; they are not contained in this body PDF. Later amendments/currentness require independent verification. The general-provision effective date is subject to the staged dates and electronic-system commencement conditions in Article 108; it is not a statement that every provision commenced on that date.
GeneralMay 26, 2022Official
Formal annexes to the Türkiye IVD Medical Device Regulation
Formal annexes to the Türkiye IVD Medical Device Regulation
Complete separate official Office annex file. Readable text and all 66 page renders preserve the original Office content; renders are labelled as Office reproductions rather than official PDF pages. No legal publication or effective date is inferred from the filename. Currentness remains unverified.
General—Official
TCKKD-KLVZ-03 Rev.0
Tıbbi Cihazların Ürün Takip Sistemine Kayıt Süreçlerine İlişkin Kılavuz
Complete317-physical-page official ÜTS registration guide, including tables, flowcharts, screenshots and appendices. The source prints Rev.0, first publication13May2026; V.4.0 occurs only in the download filename. Article69(a) defers Articles8,12,15 and39(4) until the stated technical ÜTS release; activation is not established here. The current local-manufacturer CFS sample workbook referenced by42(2)(h) is not included.
Registration—Official
Exports carry source + retrieval date

Changes after registration in Turkey

Source-linked rules for common changes to a registered IVD. Read the scope and conditions with each rule; unverified details are listed separately.

Does changing a device brand name or logo require an update?

A change to the registered brand name and a change to logo artwork can follow different rules. The legal manufacturer, device design and intended purpose remain the same.

  • Filing route and prior approval

ÜTS record updating and the application needed for registration

Fact-level verified

Choose the applicable individual legacy, MDR or IVDR device record route. A device registration/update notification governed by Arts 25–33/37–38 must be submitted for authority assessment under Art 40 to reach Registered status. The guide permits individual entry, so optional bulk-template availability is not required to describe the individual route. Art 35 separately permits specified updates such as catalogue-document association or new product images without an application; it does not equate a changed orderable REF with a catalogue document.

Conditions
  • Assess the actual changed record fields and applicable conformity/identifier consequences.
  • Individual entry is not permission to bypass document, UDI or registration requirements.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • First identify the actual changed ÜTS record fields and required conformity/identifier/document consequences; use Art 40 only where this registration/update application is required. Specified Art 35 no-application updates do not automatically cover an orderable REF change.
  • Filing route and prior approval
  • Change-specific government fees

Ordinary ÜTS application order and grouping limits

Fact-level verified

Maintain/register the supporting documents and link the appropriate declaration before the device application. For an ordinary Art 40 application select one declaration of conformity and the associated devices; the limit is 500 device notifications, with the same GMDN for legacy devices and the same Basic UDI-DI for new-regime devices except the stated ITC exception. Sign electronically and pay the applicable application fee before authority-review status. A document application is limited to 5 notifications; payment-required document types enter review after signature and payment. These limits do not authorize arbitrary change bundling or one overall fee/clock.

Conditions
  • Custom-made/system-procedure-pack applications have a separate maximum 5-device rule.
  • This is the ordinary document/device sequence; the CFS sequence is different.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only a required ordinary Art 39/40 document/device transaction: one linked declaration and applicable grouping limits, signature/payment before review. These are transaction steps, not permission to combine all proposed changes or a total project fee.
  • Supporting documents

Document authentication and translation require the activation qualification

Fact-level verified

The guide describes importer certificate/declaration authentication and Turkish translation procedures and a distinct authorised-representative mandate/EUDAMED actor-printout route. The mandate rule is not the same as certificate/declaration legalization. Articles 8,12,15 and 39(4) take effect only when the specified procedures become technically functional in a ÜTS release; other guide provisions take effect at publication. Select the operating document route and its physical-petition requirements accordingly.

Conditions
  • Use Articles 8, 12, 15 and 39(4) only after the specified procedures become technically functional in the relevant ÜTS release; other guide provisions apply from publication. Article 15 concerns the MDR system/procedure-pack declaration route, rather than a general IVD declaration rule.
  • A same-entity office update does not automatically require factory-relocation documents.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Select the actual role/document route and its operative stage. Article 15 applies to the MDR system/procedure-pack declaration route, rather than a general IVD declaration; mandate authentication differs from certificate/DoC legalization.
  • Change-specific government fees
  • Free sale certificate impact

CFS grouping, copies and the state at issuance

Fact-level verified

A CFS application contains no more than 1000 devices. Do not mix MDR, IVDR and legacy-regime groups; MDR/IVDR products in one application share the same Basic UDI-DI. Different destination-specific certificates require separate applications; English copies and an additional Turkish copy attract separate charges. Only devices Registered at the issuance date are included, so complete the affected identity/registration work before relying on the resulting CFS particulars.

Conditions
  • The former certificate’s eligibility or continued validity after a specific role/identity change is not automatically established.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if a new export CFS is actually requested by an eligible role, with the actual product/regime/Basic UDI-DI grouping, destination and copies. This does not determine whether a previous CFS survives a specific change.
  • Free sale certificate impact

CFS assessment precedes fee accrual and payment

Fact-level verified

For the local-manufacturer CFS, the sequence is upload → electronic signature/send → authority assessment → if suitable, fee accrual/payment reference → institutional payment → issuance. Pay within 10 days or ÜTS cancels automatically. The optional 3-working-day pickup hold follows payment/issuance arrangements; it is not a CFS assessment SLA.

Conditions
  • Use institutional collection via the stated Halkbank channel; ordinary remittance/EFT cannot be matched.
  • No universal administrative-change or CFS approval duration is stated by these payment/collection windows.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only a newly requested export CFS under the local-manufacturer route. Assessment precedes fee accrual; the 10-day payment and optional 3-working-day pickup windows are not approval durations or a sequence for every identity/transfer project.
  • Labels and identifiers

Record REF and model according to the actual label/documents

Fact-level verified

For MDR and IVDR records, enter version/model and reference/catalogue number exactly as declared in the linked documents or label. At least one of those two fields must be populated. If the same declared information serves as model in a document and REF on the label (or conversely), enter it in both fields. UDI-DI must not be entered as either model or reference/catalogue number. Multiple declared reference numbers are recorded as the guide specifies.

Conditions
  • The guide has a separate Art 25 legacy-device record route.
  • This rule does not establish that every internal sales code is registered device identity.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Map the actual orderable SMN/REF to the declared model/reference and barcode/UDI under the applicable record route; no identity between those fields is presumed.
  • Free sale certificate impact

Local-manufacturer CFS uses the current sample workbook

Fact-level verified

For an export CFS requested by a local manufacturer, use ÜTS’s CFS application and the sample Excel downloaded from that application. Populate device barcodes and English product names matching the registered Turkish names, upload the file and sign/send for authority assessment. Devices must be Registered; Rejected or System-has-individual-product statuses cause rejection. The current application workbook is required for that execution route.

Conditions
  • Only if an export CFS is requested by the local manufacturer.
  • The current sample workbook itself must be obtained from the designated application; historical workbook layouts are not certified substitutes.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if the actual local manufacturer requests a new export CFS; obtain the sample Excel from that designated application and use the currently Registered product particulars. Do not substitute an EU-AR application role.
  • Free sale certificate impact

Separate CFS route for a Türkiye-established EU authorised representative

Fact-level verified

A foreign manufacturer’s Türkiye-established EU authorised representative registered in the specified ÜTS activity category requests the export CFS by an EBS petition. Its product list is an applicant-prepared PDF containing device barcodes and English names matching ÜTS Turkish names. The authority assesses the application and provides fee instructions; after payment it issues only for devices still Registered at issuance.

Conditions
  • This requires the actual Türkiye-established EU-AR role. It is not an alternative role that a local manufacturer may select to avoid the sample Excel.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only the foreign manufacturer’s actual Türkiye-established EU authorised representative in the specified registered activity category, requesting a new export CFS; EBS petition/PDF is not a substitute for the local-manufacturer workbook.
  • Change-specific government fees

Conditions for this question

  • Only if the change actually requires this chargeable ÜTS device application or certificate/DoC document-registration transaction under Arts 39–40; not an overall modification/transfer price. Türkiye-produced support is product-eligibility dependent.
  • Change-specific government fees

Conditions for this question

  • Only if the change actually requires this chargeable ÜTS device application or certificate/DoC document-registration transaction under Arts 39–40; not an overall modification/transfer price. Türkiye-produced support is product-eligibility dependent.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Labels and identifiers

New UDI-DI test for trade name or model changes

Fact-level verified

A change that could cause misidentification or ambiguity in traceability requires a new UDI-DI, in particular a change in device name/trade name or device version/model. A commercial order code must first be mapped to the actual label and declared device identity; it is not automatically a UDI-DI or a model.

Conditions
  • Applies to devices in the national MDR/IVDR UDI regime; do not substitute this for the applicable legacy barcode route.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • A changed declared trade name/model or traceability ambiguity triggers the applicable new-UDI test; an internal orderable REF or logo edit must first be mapped to that identity.
  • Supporting documents
  • Labels and identifiers

Align changed identity across labels and declaration

Fact-level verified

Labels identify the device name or trade name and the manufacturer’s name, registered trade name or trademark and registered business address; an authorised representative is identified where applicable. The EU declaration of conformity identifies the responsible manufacturer, device/product or trade name, identification permitting traceability, catalogue reference where relevant and Basic UDI-DI. After an identity change these documents must describe the same responsible person and device.

Conditions
  • Read under the applicable national MDR/IVDR conformity regime; legacy devices require their applicable legacy documentation.
  • A logo-artwork change is not by itself proof of a change to the device name or legal manufacturer.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Use for the affected labels and declaration under the applicable conformity regime; this alignment rule alone gives no old-stock grace, first-placing permission or relabelling authorization.
  • Supporting documents

Notified-body involvement depends on the actual change

Fact-level verified

Under Annex IX the manufacturer informs its notified body of planned substantial changes to the approved QMS or device range. Changes to an approved device that may affect safety/performance or conditions of use require the technical-documentation certificate issuer’s approval; the body decides between a new conformity assessment and a certificate supplement. A same-entity office rename/address change is not automatically a factory, design or significant QMS change.

Conditions
  • Only when that notified-body conformity-assessment route and the relevant change trigger apply.
  • The IVD reference-laboratory 60-day consultation in Annex IX 4.11 is not a general administrative-change SLA.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if the device uses this notified-body conformity route and the actual change meets its QMS/device-range or safety/performance/use-condition trigger; no administrative-change review SLA follows.
  • Existing stock and transition

Separate existing placed stock from further legacy placing

Fact-level verified

The transitional provisions allow devices lawfully placed on the market under the applicable legacy provisions to continue being made available or put into service. Further legacy placing remains subject to the relevant class/date, valid-certificate, QMS and application conditions and absence of significant changes in design or intended purpose. This is not a general rename/transfer sell-through grace period or permission to first place changed devices under obsolete labels.

Conditions
  • Check actual placing date, device class, applicable legacy status, certificate, traceability and affected labels.
  • No universal stock duration following a brand, manufacturer, REF or legal-person change is established by this transition alone.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only eligible legacy devices with an established lawful placing date and the applicable class/date/certificate/QMS/application conditions. This is not a rename/transfer grace period or first-placing permission under an obsolete identity.

How do I update a manufacturer's name without changing the legal entity?

The same legal manufacturer changes its name, potentially alongside the device brand. A transfer to another legal entity is a separate question; permission to combine filings needs its own evidence.

  • Filing route and prior approval

ÜTS record updating and the application needed for registration

Fact-level verified

Choose the applicable individual legacy, MDR or IVDR device record route. A device registration/update notification governed by Arts 25–33/37–38 must be submitted for authority assessment under Art 40 to reach Registered status. The guide permits individual entry, so optional bulk-template availability is not required to describe the individual route. Art 35 separately permits specified updates such as catalogue-document association or new product images without an application; it does not equate a changed orderable REF with a catalogue document.

Conditions
  • Assess the actual changed record fields and applicable conformity/identifier consequences.
  • Individual entry is not permission to bypass document, UDI or registration requirements.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • First identify the actual changed ÜTS record fields and required conformity/identifier/document consequences; use Art 40 only where this registration/update application is required. Specified Art 35 no-application updates do not automatically cover an orderable REF change.
  • Filing route and prior approval
  • Change-specific government fees

Ordinary ÜTS application order and grouping limits

Fact-level verified

Maintain/register the supporting documents and link the appropriate declaration before the device application. For an ordinary Art 40 application select one declaration of conformity and the associated devices; the limit is 500 device notifications, with the same GMDN for legacy devices and the same Basic UDI-DI for new-regime devices except the stated ITC exception. Sign electronically and pay the applicable application fee before authority-review status. A document application is limited to 5 notifications; payment-required document types enter review after signature and payment. These limits do not authorize arbitrary change bundling or one overall fee/clock.

Conditions
  • Custom-made/system-procedure-pack applications have a separate maximum 5-device rule.
  • This is the ordinary document/device sequence; the CFS sequence is different.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only a required ordinary Art 39/40 document/device transaction: one linked declaration and applicable grouping limits, signature/payment before review. These are transaction steps, not permission to combine all proposed changes or a total project fee.
  • Supporting documents

Document authentication and translation require the activation qualification

Fact-level verified

The guide describes importer certificate/declaration authentication and Turkish translation procedures and a distinct authorised-representative mandate/EUDAMED actor-printout route. The mandate rule is not the same as certificate/declaration legalization. Articles 8,12,15 and 39(4) take effect only when the specified procedures become technically functional in a ÜTS release; other guide provisions take effect at publication. Select the operating document route and its physical-petition requirements accordingly.

Conditions
  • Use Articles 8, 12, 15 and 39(4) only after the specified procedures become technically functional in the relevant ÜTS release; other guide provisions apply from publication. Article 15 concerns the MDR system/procedure-pack declaration route, rather than a general IVD declaration rule.
  • A same-entity office update does not automatically require factory-relocation documents.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Select the actual role/document route and its operative stage. Article 15 applies to the MDR system/procedure-pack declaration route, rather than a general IVD declaration; mandate authentication differs from certificate/DoC legalization.
  • Change-specific government fees
  • Free sale certificate impact

CFS grouping, copies and the state at issuance

Fact-level verified

A CFS application contains no more than 1000 devices. Do not mix MDR, IVDR and legacy-regime groups; MDR/IVDR products in one application share the same Basic UDI-DI. Different destination-specific certificates require separate applications; English copies and an additional Turkish copy attract separate charges. Only devices Registered at the issuance date are included, so complete the affected identity/registration work before relying on the resulting CFS particulars.

Conditions
  • The former certificate’s eligibility or continued validity after a specific role/identity change is not automatically established.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if a new export CFS is actually requested by an eligible role, with the actual product/regime/Basic UDI-DI grouping, destination and copies. This does not determine whether a previous CFS survives a specific change.
  • Free sale certificate impact

CFS assessment precedes fee accrual and payment

Fact-level verified

For the local-manufacturer CFS, the sequence is upload → electronic signature/send → authority assessment → if suitable, fee accrual/payment reference → institutional payment → issuance. Pay within 10 days or ÜTS cancels automatically. The optional 3-working-day pickup hold follows payment/issuance arrangements; it is not a CFS assessment SLA.

Conditions
  • Use institutional collection via the stated Halkbank channel; ordinary remittance/EFT cannot be matched.
  • No universal administrative-change or CFS approval duration is stated by these payment/collection windows.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only a newly requested export CFS under the local-manufacturer route. Assessment precedes fee accrual; the 10-day payment and optional 3-working-day pickup windows are not approval durations or a sequence for every identity/transfer project.
  • Labels and identifiers

Record REF and model according to the actual label/documents

Fact-level verified

For MDR and IVDR records, enter version/model and reference/catalogue number exactly as declared in the linked documents or label. At least one of those two fields must be populated. If the same declared information serves as model in a document and REF on the label (or conversely), enter it in both fields. UDI-DI must not be entered as either model or reference/catalogue number. Multiple declared reference numbers are recorded as the guide specifies.

Conditions
  • The guide has a separate Art 25 legacy-device record route.
  • This rule does not establish that every internal sales code is registered device identity.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Map the actual orderable SMN/REF to the declared model/reference and barcode/UDI under the applicable record route; no identity between those fields is presumed.
  • Free sale certificate impact

Local-manufacturer CFS uses the current sample workbook

Fact-level verified

For an export CFS requested by a local manufacturer, use ÜTS’s CFS application and the sample Excel downloaded from that application. Populate device barcodes and English product names matching the registered Turkish names, upload the file and sign/send for authority assessment. Devices must be Registered; Rejected or System-has-individual-product statuses cause rejection. The current application workbook is required for that execution route.

Conditions
  • Only if an export CFS is requested by the local manufacturer.
  • The current sample workbook itself must be obtained from the designated application; historical workbook layouts are not certified substitutes.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if the actual local manufacturer requests a new export CFS; obtain the sample Excel from that designated application and use the currently Registered product particulars. Do not substitute an EU-AR application role.
  • Free sale certificate impact

Separate CFS route for a Türkiye-established EU authorised representative

Fact-level verified

A foreign manufacturer’s Türkiye-established EU authorised representative registered in the specified ÜTS activity category requests the export CFS by an EBS petition. Its product list is an applicant-prepared PDF containing device barcodes and English names matching ÜTS Turkish names. The authority assesses the application and provides fee instructions; after payment it issues only for devices still Registered at issuance.

Conditions
  • This requires the actual Türkiye-established EU-AR role. It is not an alternative role that a local manufacturer may select to avoid the sample Excel.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only the foreign manufacturer’s actual Türkiye-established EU authorised representative in the specified registered activity category, requesting a new export CFS; EBS petition/PDF is not a substitute for the local-manufacturer workbook.
  • Change-specific government fees

Conditions for this question

  • Only if the change actually requires this chargeable ÜTS device application or certificate/DoC document-registration transaction under Arts 39–40; not an overall modification/transfer price. Türkiye-produced support is product-eligibility dependent.
  • Change-specific government fees

Conditions for this question

  • Only if the change actually requires this chargeable ÜTS device application or certificate/DoC document-registration transaction under Arts 39–40; not an overall modification/transfer price. Türkiye-produced support is product-eligibility dependent.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Labels and identifiers

New UDI-DI test for trade name or model changes

Fact-level verified

A change that could cause misidentification or ambiguity in traceability requires a new UDI-DI, in particular a change in device name/trade name or device version/model. A commercial order code must first be mapped to the actual label and declared device identity; it is not automatically a UDI-DI or a model.

Conditions
  • Applies to devices in the national MDR/IVDR UDI regime; do not substitute this for the applicable legacy barcode route.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • A changed declared trade name/model or traceability ambiguity triggers the applicable new-UDI test; an internal orderable REF or logo edit must first be mapped to that identity.
  • Supporting documents
  • Labels and identifiers

Align changed identity across labels and declaration

Fact-level verified

Labels identify the device name or trade name and the manufacturer’s name, registered trade name or trademark and registered business address; an authorised representative is identified where applicable. The EU declaration of conformity identifies the responsible manufacturer, device/product or trade name, identification permitting traceability, catalogue reference where relevant and Basic UDI-DI. After an identity change these documents must describe the same responsible person and device.

Conditions
  • Read under the applicable national MDR/IVDR conformity regime; legacy devices require their applicable legacy documentation.
  • A logo-artwork change is not by itself proof of a change to the device name or legal manufacturer.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Use for the affected labels and declaration under the applicable conformity regime; this alignment rule alone gives no old-stock grace, first-placing permission or relabelling authorization.
  • Supporting documents

Notified-body involvement depends on the actual change

Fact-level verified

Under Annex IX the manufacturer informs its notified body of planned substantial changes to the approved QMS or device range. Changes to an approved device that may affect safety/performance or conditions of use require the technical-documentation certificate issuer’s approval; the body decides between a new conformity assessment and a certificate supplement. A same-entity office rename/address change is not automatically a factory, design or significant QMS change.

Conditions
  • Only when that notified-body conformity-assessment route and the relevant change trigger apply.
  • The IVD reference-laboratory 60-day consultation in Annex IX 4.11 is not a general administrative-change SLA.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if the device uses this notified-body conformity route and the actual change meets its QMS/device-range or safety/performance/use-condition trigger; no administrative-change review SLA follows.
  • Existing stock and transition

Separate existing placed stock from further legacy placing

Fact-level verified

The transitional provisions allow devices lawfully placed on the market under the applicable legacy provisions to continue being made available or put into service. Further legacy placing remains subject to the relevant class/date, valid-certificate, QMS and application conditions and absence of significant changes in design or intended purpose. This is not a general rename/transfer sell-through grace period or permission to first place changed devices under obsolete labels.

Conditions
  • Check actual placing date, device class, applicable legacy status, certificate, traceability and affected labels.
  • No universal stock duration following a brand, manufacturer, REF or legal-person change is established by this transition alone.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only eligible legacy devices with an established lawful placing date and the applicable class/date/certificate/QMS/application conditions. This is not a rename/transfer grace period or first-placing permission under an obsolete identity.

What changes when the manufacturer's office address changes?

An office address change for the same legal entity, potentially alongside name and brand changes. This does not cover moving a factory or manufacturing site, and a combined filing cannot be assumed.

  • Filing route and prior approval

ÜTS record updating and the application needed for registration

Fact-level verified

Choose the applicable individual legacy, MDR or IVDR device record route. A device registration/update notification governed by Arts 25–33/37–38 must be submitted for authority assessment under Art 40 to reach Registered status. The guide permits individual entry, so optional bulk-template availability is not required to describe the individual route. Art 35 separately permits specified updates such as catalogue-document association or new product images without an application; it does not equate a changed orderable REF with a catalogue document.

Conditions
  • Assess the actual changed record fields and applicable conformity/identifier consequences.
  • Individual entry is not permission to bypass document, UDI or registration requirements.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • First identify the actual changed ÜTS record fields and required conformity/identifier/document consequences; use Art 40 only where this registration/update application is required. Specified Art 35 no-application updates do not automatically cover an orderable REF change.
  • Filing route and prior approval
  • Change-specific government fees

Ordinary ÜTS application order and grouping limits

Fact-level verified

Maintain/register the supporting documents and link the appropriate declaration before the device application. For an ordinary Art 40 application select one declaration of conformity and the associated devices; the limit is 500 device notifications, with the same GMDN for legacy devices and the same Basic UDI-DI for new-regime devices except the stated ITC exception. Sign electronically and pay the applicable application fee before authority-review status. A document application is limited to 5 notifications; payment-required document types enter review after signature and payment. These limits do not authorize arbitrary change bundling or one overall fee/clock.

Conditions
  • Custom-made/system-procedure-pack applications have a separate maximum 5-device rule.
  • This is the ordinary document/device sequence; the CFS sequence is different.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only a required ordinary Art 39/40 document/device transaction: one linked declaration and applicable grouping limits, signature/payment before review. These are transaction steps, not permission to combine all proposed changes or a total project fee.
  • Supporting documents

Document authentication and translation require the activation qualification

Fact-level verified

The guide describes importer certificate/declaration authentication and Turkish translation procedures and a distinct authorised-representative mandate/EUDAMED actor-printout route. The mandate rule is not the same as certificate/declaration legalization. Articles 8,12,15 and 39(4) take effect only when the specified procedures become technically functional in a ÜTS release; other guide provisions take effect at publication. Select the operating document route and its physical-petition requirements accordingly.

Conditions
  • Use Articles 8, 12, 15 and 39(4) only after the specified procedures become technically functional in the relevant ÜTS release; other guide provisions apply from publication. Article 15 concerns the MDR system/procedure-pack declaration route, rather than a general IVD declaration rule.
  • A same-entity office update does not automatically require factory-relocation documents.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Select the actual role/document route and its operative stage. Article 15 applies to the MDR system/procedure-pack declaration route, rather than a general IVD declaration; mandate authentication differs from certificate/DoC legalization.
  • Change-specific government fees
  • Free sale certificate impact

CFS grouping, copies and the state at issuance

Fact-level verified

A CFS application contains no more than 1000 devices. Do not mix MDR, IVDR and legacy-regime groups; MDR/IVDR products in one application share the same Basic UDI-DI. Different destination-specific certificates require separate applications; English copies and an additional Turkish copy attract separate charges. Only devices Registered at the issuance date are included, so complete the affected identity/registration work before relying on the resulting CFS particulars.

Conditions
  • The former certificate’s eligibility or continued validity after a specific role/identity change is not automatically established.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if a new export CFS is actually requested by an eligible role, with the actual product/regime/Basic UDI-DI grouping, destination and copies. This does not determine whether a previous CFS survives a specific change.
  • Free sale certificate impact

CFS assessment precedes fee accrual and payment

Fact-level verified

For the local-manufacturer CFS, the sequence is upload → electronic signature/send → authority assessment → if suitable, fee accrual/payment reference → institutional payment → issuance. Pay within 10 days or ÜTS cancels automatically. The optional 3-working-day pickup hold follows payment/issuance arrangements; it is not a CFS assessment SLA.

Conditions
  • Use institutional collection via the stated Halkbank channel; ordinary remittance/EFT cannot be matched.
  • No universal administrative-change or CFS approval duration is stated by these payment/collection windows.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only a newly requested export CFS under the local-manufacturer route. Assessment precedes fee accrual; the 10-day payment and optional 3-working-day pickup windows are not approval durations or a sequence for every identity/transfer project.
  • Labels and identifiers

Record REF and model according to the actual label/documents

Fact-level verified

For MDR and IVDR records, enter version/model and reference/catalogue number exactly as declared in the linked documents or label. At least one of those two fields must be populated. If the same declared information serves as model in a document and REF on the label (or conversely), enter it in both fields. UDI-DI must not be entered as either model or reference/catalogue number. Multiple declared reference numbers are recorded as the guide specifies.

Conditions
  • The guide has a separate Art 25 legacy-device record route.
  • This rule does not establish that every internal sales code is registered device identity.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Map the actual orderable SMN/REF to the declared model/reference and barcode/UDI under the applicable record route; no identity between those fields is presumed.
  • Free sale certificate impact

Local-manufacturer CFS uses the current sample workbook

Fact-level verified

For an export CFS requested by a local manufacturer, use ÜTS’s CFS application and the sample Excel downloaded from that application. Populate device barcodes and English product names matching the registered Turkish names, upload the file and sign/send for authority assessment. Devices must be Registered; Rejected or System-has-individual-product statuses cause rejection. The current application workbook is required for that execution route.

Conditions
  • Only if an export CFS is requested by the local manufacturer.
  • The current sample workbook itself must be obtained from the designated application; historical workbook layouts are not certified substitutes.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if the actual local manufacturer requests a new export CFS; obtain the sample Excel from that designated application and use the currently Registered product particulars. Do not substitute an EU-AR application role.
  • Free sale certificate impact

Separate CFS route for a Türkiye-established EU authorised representative

Fact-level verified

A foreign manufacturer’s Türkiye-established EU authorised representative registered in the specified ÜTS activity category requests the export CFS by an EBS petition. Its product list is an applicant-prepared PDF containing device barcodes and English names matching ÜTS Turkish names. The authority assesses the application and provides fee instructions; after payment it issues only for devices still Registered at issuance.

Conditions
  • This requires the actual Türkiye-established EU-AR role. It is not an alternative role that a local manufacturer may select to avoid the sample Excel.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only the foreign manufacturer’s actual Türkiye-established EU authorised representative in the specified registered activity category, requesting a new export CFS; EBS petition/PDF is not a substitute for the local-manufacturer workbook.
  • Change-specific government fees

Conditions for this question

  • Only if the change actually requires this chargeable ÜTS device application or certificate/DoC document-registration transaction under Arts 39–40; not an overall modification/transfer price. Türkiye-produced support is product-eligibility dependent.
  • Change-specific government fees

Conditions for this question

  • Only if the change actually requires this chargeable ÜTS device application or certificate/DoC document-registration transaction under Arts 39–40; not an overall modification/transfer price. Türkiye-produced support is product-eligibility dependent.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Labels and identifiers

New UDI-DI test for trade name or model changes

Fact-level verified

A change that could cause misidentification or ambiguity in traceability requires a new UDI-DI, in particular a change in device name/trade name or device version/model. A commercial order code must first be mapped to the actual label and declared device identity; it is not automatically a UDI-DI or a model.

Conditions
  • Applies to devices in the national MDR/IVDR UDI regime; do not substitute this for the applicable legacy barcode route.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • A changed declared trade name/model or traceability ambiguity triggers the applicable new-UDI test; an internal orderable REF or logo edit must first be mapped to that identity.
  • Supporting documents
  • Labels and identifiers

Align changed identity across labels and declaration

Fact-level verified

Labels identify the device name or trade name and the manufacturer’s name, registered trade name or trademark and registered business address; an authorised representative is identified where applicable. The EU declaration of conformity identifies the responsible manufacturer, device/product or trade name, identification permitting traceability, catalogue reference where relevant and Basic UDI-DI. After an identity change these documents must describe the same responsible person and device.

Conditions
  • Read under the applicable national MDR/IVDR conformity regime; legacy devices require their applicable legacy documentation.
  • A logo-artwork change is not by itself proof of a change to the device name or legal manufacturer.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Use for the affected labels and declaration under the applicable conformity regime; this alignment rule alone gives no old-stock grace, first-placing permission or relabelling authorization.
  • Supporting documents

Notified-body involvement depends on the actual change

Fact-level verified

Under Annex IX the manufacturer informs its notified body of planned substantial changes to the approved QMS or device range. Changes to an approved device that may affect safety/performance or conditions of use require the technical-documentation certificate issuer’s approval; the body decides between a new conformity assessment and a certificate supplement. A same-entity office rename/address change is not automatically a factory, design or significant QMS change.

Conditions
  • Only when that notified-body conformity-assessment route and the relevant change trigger apply.
  • The IVD reference-laboratory 60-day consultation in Annex IX 4.11 is not a general administrative-change SLA.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if the device uses this notified-body conformity route and the actual change meets its QMS/device-range or safety/performance/use-condition trigger; no administrative-change review SLA follows.
  • Existing stock and transition

Separate existing placed stock from further legacy placing

Fact-level verified

The transitional provisions allow devices lawfully placed on the market under the applicable legacy provisions to continue being made available or put into service. Further legacy placing remains subject to the relevant class/date, valid-certificate, QMS and application conditions and absence of significant changes in design or intended purpose. This is not a general rename/transfer sell-through grace period or permission to first place changed devices under obsolete labels.

Conditions
  • Check actual placing date, device class, applicable legacy status, certificate, traceability and affected labels.
  • No universal stock duration following a brand, manufacturer, REF or legal-person change is established by this transition alone.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only eligible legacy devices with an established lawful placing date and the applicable class/date/certificate/QMS/application conditions. This is not a rename/transfer grace period or first-placing permission under an obsolete identity.

Does a catalogue or reference code change affect registration or UDI?

Check which identifier actually changes. A commercial catalogue, REF or order code is not automatically a device model, registered identifier, GTIN or UDI-DI. Rules for one identifier do not establish the route for another.

  • Filing route and prior approval

ÜTS record updating and the application needed for registration

Fact-level verified

Choose the applicable individual legacy, MDR or IVDR device record route. A device registration/update notification governed by Arts 25–33/37–38 must be submitted for authority assessment under Art 40 to reach Registered status. The guide permits individual entry, so optional bulk-template availability is not required to describe the individual route. Art 35 separately permits specified updates such as catalogue-document association or new product images without an application; it does not equate a changed orderable REF with a catalogue document.

Conditions
  • Assess the actual changed record fields and applicable conformity/identifier consequences.
  • Individual entry is not permission to bypass document, UDI or registration requirements.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • First identify the actual changed ÜTS record fields and required conformity/identifier/document consequences; use Art 40 only where this registration/update application is required. Specified Art 35 no-application updates do not automatically cover an orderable REF change.
  • Filing route and prior approval
  • Change-specific government fees

Ordinary ÜTS application order and grouping limits

Fact-level verified

Maintain/register the supporting documents and link the appropriate declaration before the device application. For an ordinary Art 40 application select one declaration of conformity and the associated devices; the limit is 500 device notifications, with the same GMDN for legacy devices and the same Basic UDI-DI for new-regime devices except the stated ITC exception. Sign electronically and pay the applicable application fee before authority-review status. A document application is limited to 5 notifications; payment-required document types enter review after signature and payment. These limits do not authorize arbitrary change bundling or one overall fee/clock.

Conditions
  • Custom-made/system-procedure-pack applications have a separate maximum 5-device rule.
  • This is the ordinary document/device sequence; the CFS sequence is different.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only a required ordinary Art 39/40 document/device transaction: one linked declaration and applicable grouping limits, signature/payment before review. These are transaction steps, not permission to combine all proposed changes or a total project fee.
  • Supporting documents

Document authentication and translation require the activation qualification

Fact-level verified

The guide describes importer certificate/declaration authentication and Turkish translation procedures and a distinct authorised-representative mandate/EUDAMED actor-printout route. The mandate rule is not the same as certificate/declaration legalization. Articles 8,12,15 and 39(4) take effect only when the specified procedures become technically functional in a ÜTS release; other guide provisions take effect at publication. Select the operating document route and its physical-petition requirements accordingly.

Conditions
  • Use Articles 8, 12, 15 and 39(4) only after the specified procedures become technically functional in the relevant ÜTS release; other guide provisions apply from publication. Article 15 concerns the MDR system/procedure-pack declaration route, rather than a general IVD declaration rule.
  • A same-entity office update does not automatically require factory-relocation documents.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Select the actual role/document route and its operative stage. Article 15 applies to the MDR system/procedure-pack declaration route, rather than a general IVD declaration; mandate authentication differs from certificate/DoC legalization.
  • Change-specific government fees
  • Free sale certificate impact

CFS grouping, copies and the state at issuance

Fact-level verified

A CFS application contains no more than 1000 devices. Do not mix MDR, IVDR and legacy-regime groups; MDR/IVDR products in one application share the same Basic UDI-DI. Different destination-specific certificates require separate applications; English copies and an additional Turkish copy attract separate charges. Only devices Registered at the issuance date are included, so complete the affected identity/registration work before relying on the resulting CFS particulars.

Conditions
  • The former certificate’s eligibility or continued validity after a specific role/identity change is not automatically established.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if a new export CFS is actually requested by an eligible role, with the actual product/regime/Basic UDI-DI grouping, destination and copies. This does not determine whether a previous CFS survives a specific change.
  • Free sale certificate impact

CFS assessment precedes fee accrual and payment

Fact-level verified

For the local-manufacturer CFS, the sequence is upload → electronic signature/send → authority assessment → if suitable, fee accrual/payment reference → institutional payment → issuance. Pay within 10 days or ÜTS cancels automatically. The optional 3-working-day pickup hold follows payment/issuance arrangements; it is not a CFS assessment SLA.

Conditions
  • Use institutional collection via the stated Halkbank channel; ordinary remittance/EFT cannot be matched.
  • No universal administrative-change or CFS approval duration is stated by these payment/collection windows.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only a newly requested export CFS under the local-manufacturer route. Assessment precedes fee accrual; the 10-day payment and optional 3-working-day pickup windows are not approval durations or a sequence for every identity/transfer project.
  • Labels and identifiers

Record REF and model according to the actual label/documents

Fact-level verified

For MDR and IVDR records, enter version/model and reference/catalogue number exactly as declared in the linked documents or label. At least one of those two fields must be populated. If the same declared information serves as model in a document and REF on the label (or conversely), enter it in both fields. UDI-DI must not be entered as either model or reference/catalogue number. Multiple declared reference numbers are recorded as the guide specifies.

Conditions
  • The guide has a separate Art 25 legacy-device record route.
  • This rule does not establish that every internal sales code is registered device identity.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Map the actual orderable SMN/REF to the declared model/reference and barcode/UDI under the applicable record route; no identity between those fields is presumed.
  • Free sale certificate impact

Local-manufacturer CFS uses the current sample workbook

Fact-level verified

For an export CFS requested by a local manufacturer, use ÜTS’s CFS application and the sample Excel downloaded from that application. Populate device barcodes and English product names matching the registered Turkish names, upload the file and sign/send for authority assessment. Devices must be Registered; Rejected or System-has-individual-product statuses cause rejection. The current application workbook is required for that execution route.

Conditions
  • Only if an export CFS is requested by the local manufacturer.
  • The current sample workbook itself must be obtained from the designated application; historical workbook layouts are not certified substitutes.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if the actual local manufacturer requests a new export CFS; obtain the sample Excel from that designated application and use the currently Registered product particulars. Do not substitute an EU-AR application role.
  • Free sale certificate impact

Separate CFS route for a Türkiye-established EU authorised representative

Fact-level verified

A foreign manufacturer’s Türkiye-established EU authorised representative registered in the specified ÜTS activity category requests the export CFS by an EBS petition. Its product list is an applicant-prepared PDF containing device barcodes and English names matching ÜTS Turkish names. The authority assesses the application and provides fee instructions; after payment it issues only for devices still Registered at issuance.

Conditions
  • This requires the actual Türkiye-established EU-AR role. It is not an alternative role that a local manufacturer may select to avoid the sample Excel.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only the foreign manufacturer’s actual Türkiye-established EU authorised representative in the specified registered activity category, requesting a new export CFS; EBS petition/PDF is not a substitute for the local-manufacturer workbook.
  • Change-specific government fees

Conditions for this question

  • Only if the change actually requires this chargeable ÜTS device application or certificate/DoC document-registration transaction under Arts 39–40; not an overall modification/transfer price. Türkiye-produced support is product-eligibility dependent.
  • Change-specific government fees

Conditions for this question

  • Only if the change actually requires this chargeable ÜTS device application or certificate/DoC document-registration transaction under Arts 39–40; not an overall modification/transfer price. Türkiye-produced support is product-eligibility dependent.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Labels and identifiers

New UDI-DI test for trade name or model changes

Fact-level verified

A change that could cause misidentification or ambiguity in traceability requires a new UDI-DI, in particular a change in device name/trade name or device version/model. A commercial order code must first be mapped to the actual label and declared device identity; it is not automatically a UDI-DI or a model.

Conditions
  • Applies to devices in the national MDR/IVDR UDI regime; do not substitute this for the applicable legacy barcode route.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • A changed declared trade name/model or traceability ambiguity triggers the applicable new-UDI test; an internal orderable REF or logo edit must first be mapped to that identity.
  • Supporting documents
  • Labels and identifiers

Align changed identity across labels and declaration

Fact-level verified

Labels identify the device name or trade name and the manufacturer’s name, registered trade name or trademark and registered business address; an authorised representative is identified where applicable. The EU declaration of conformity identifies the responsible manufacturer, device/product or trade name, identification permitting traceability, catalogue reference where relevant and Basic UDI-DI. After an identity change these documents must describe the same responsible person and device.

Conditions
  • Read under the applicable national MDR/IVDR conformity regime; legacy devices require their applicable legacy documentation.
  • A logo-artwork change is not by itself proof of a change to the device name or legal manufacturer.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Use for the affected labels and declaration under the applicable conformity regime; this alignment rule alone gives no old-stock grace, first-placing permission or relabelling authorization.
  • Supporting documents

Notified-body involvement depends on the actual change

Fact-level verified

Under Annex IX the manufacturer informs its notified body of planned substantial changes to the approved QMS or device range. Changes to an approved device that may affect safety/performance or conditions of use require the technical-documentation certificate issuer’s approval; the body decides between a new conformity assessment and a certificate supplement. A same-entity office rename/address change is not automatically a factory, design or significant QMS change.

Conditions
  • Only when that notified-body conformity-assessment route and the relevant change trigger apply.
  • The IVD reference-laboratory 60-day consultation in Annex IX 4.11 is not a general administrative-change SLA.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if the device uses this notified-body conformity route and the actual change meets its QMS/device-range or safety/performance/use-condition trigger; no administrative-change review SLA follows.
  • Existing stock and transition

Separate existing placed stock from further legacy placing

Fact-level verified

The transitional provisions allow devices lawfully placed on the market under the applicable legacy provisions to continue being made available or put into service. Further legacy placing remains subject to the relevant class/date, valid-certificate, QMS and application conditions and absence of significant changes in design or intended purpose. This is not a general rename/transfer sell-through grace period or permission to first place changed devices under obsolete labels.

Conditions
  • Check actual placing date, device class, applicable legacy status, certificate, traceability and affected labels.
  • No universal stock duration following a brand, manufacturer, REF or legal-person change is established by this transition alone.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only eligible legacy devices with an established lawful placing date and the applicable class/date/certificate/QMS/application conditions. This is not a rename/transfer grace period or first-placing permission under an obsolete identity.

Can several changes be filed together?

Changes to brand, manufacturer name, office address and reference codes may occur together, including with a real transfer to another legal manufacturer, registration holder or owner. Assess transfer with each single change, and transfer with brand plus reference, manufacturer name plus reference, or office address plus reference changes: seven transfer combinations in total. Evidence must establish the exact combination and the order of filings and approvals. These combinations and their sequence are not all verified by the rules below; a rule for one change does not prove that a single application, fee or review period covers the combination.

  • Filing route and prior approval

ÜTS record updating and the application needed for registration

Fact-level verified

Choose the applicable individual legacy, MDR or IVDR device record route. A device registration/update notification governed by Arts 25–33/37–38 must be submitted for authority assessment under Art 40 to reach Registered status. The guide permits individual entry, so optional bulk-template availability is not required to describe the individual route. Art 35 separately permits specified updates such as catalogue-document association or new product images without an application; it does not equate a changed orderable REF with a catalogue document.

Conditions
  • Assess the actual changed record fields and applicable conformity/identifier consequences.
  • Individual entry is not permission to bypass document, UDI or registration requirements.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • First identify the actual changed ÜTS record fields and required conformity/identifier/document consequences; use Art 40 only where this registration/update application is required. Specified Art 35 no-application updates do not automatically cover an orderable REF change.
  • Filing route and prior approval
  • Change-specific government fees

Ordinary ÜTS application order and grouping limits

Fact-level verified

Maintain/register the supporting documents and link the appropriate declaration before the device application. For an ordinary Art 40 application select one declaration of conformity and the associated devices; the limit is 500 device notifications, with the same GMDN for legacy devices and the same Basic UDI-DI for new-regime devices except the stated ITC exception. Sign electronically and pay the applicable application fee before authority-review status. A document application is limited to 5 notifications; payment-required document types enter review after signature and payment. These limits do not authorize arbitrary change bundling or one overall fee/clock.

Conditions
  • Custom-made/system-procedure-pack applications have a separate maximum 5-device rule.
  • This is the ordinary document/device sequence; the CFS sequence is different.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only a required ordinary Art 39/40 document/device transaction: one linked declaration and applicable grouping limits, signature/payment before review. These are transaction steps, not permission to combine all proposed changes or a total project fee.
  • Filing route and prior approval

Local company master data and takeover account access

Fact-level verified

For company transfer/merger, update the authorised signatories and users defined in ÜTS so the company’s ÜTS activities can continue. Changes to responsible manager, company title and address update automatically in ÜTS when updated in ÇKYS. This local firm-data mechanism does not itself establish transfer of a foreign manufacturer’s conformity certificate or responsibilities.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only the local firm/account signatories or ÇKYS-linked title/address/responsible-manager data actually affected; this mechanism does not transfer a foreign manufacturer’s conformity responsibility or certificate.
  • Filing route and prior approval
  • Supporting documents

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only an actual change of the responsible legal manufacturer/certificate holder. Assess the new manufacturer obligations and applicable conformity/certificate route; no automatic transfer, inherited certificate or combined approval is established.
  • Supporting documents

Document authentication and translation require the activation qualification

Fact-level verified

The guide describes importer certificate/declaration authentication and Turkish translation procedures and a distinct authorised-representative mandate/EUDAMED actor-printout route. The mandate rule is not the same as certificate/declaration legalization. Articles 8,12,15 and 39(4) take effect only when the specified procedures become technically functional in a ÜTS release; other guide provisions take effect at publication. Select the operating document route and its physical-petition requirements accordingly.

Conditions
  • Use Articles 8, 12, 15 and 39(4) only after the specified procedures become technically functional in the relevant ÜTS release; other guide provisions apply from publication. Article 15 concerns the MDR system/procedure-pack declaration route, rather than a general IVD declaration rule.
  • A same-entity office update does not automatically require factory-relocation documents.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Select the actual role/document route and its operative stage. Article 15 applies to the MDR system/procedure-pack declaration route, rather than a general IVD declaration; mandate authentication differs from certificate/DoC legalization.
  • Change-specific government fees
  • Free sale certificate impact

CFS grouping, copies and the state at issuance

Fact-level verified

A CFS application contains no more than 1000 devices. Do not mix MDR, IVDR and legacy-regime groups; MDR/IVDR products in one application share the same Basic UDI-DI. Different destination-specific certificates require separate applications; English copies and an additional Turkish copy attract separate charges. Only devices Registered at the issuance date are included, so complete the affected identity/registration work before relying on the resulting CFS particulars.

Conditions
  • The former certificate’s eligibility or continued validity after a specific role/identity change is not automatically established.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if a new export CFS is actually requested by an eligible role, with the actual product/regime/Basic UDI-DI grouping, destination and copies. This does not determine whether a previous CFS survives a specific change.
  • Free sale certificate impact

CFS assessment precedes fee accrual and payment

Fact-level verified

For the local-manufacturer CFS, the sequence is upload → electronic signature/send → authority assessment → if suitable, fee accrual/payment reference → institutional payment → issuance. Pay within 10 days or ÜTS cancels automatically. The optional 3-working-day pickup hold follows payment/issuance arrangements; it is not a CFS assessment SLA.

Conditions
  • Use institutional collection via the stated Halkbank channel; ordinary remittance/EFT cannot be matched.
  • No universal administrative-change or CFS approval duration is stated by these payment/collection windows.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only a newly requested export CFS under the local-manufacturer route. Assessment precedes fee accrual; the 10-day payment and optional 3-working-day pickup windows are not approval durations or a sequence for every identity/transfer project.
  • Labels and identifiers

Record REF and model according to the actual label/documents

Fact-level verified

For MDR and IVDR records, enter version/model and reference/catalogue number exactly as declared in the linked documents or label. At least one of those two fields must be populated. If the same declared information serves as model in a document and REF on the label (or conversely), enter it in both fields. UDI-DI must not be entered as either model or reference/catalogue number. Multiple declared reference numbers are recorded as the guide specifies.

Conditions
  • The guide has a separate Art 25 legacy-device record route.
  • This rule does not establish that every internal sales code is registered device identity.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Map the actual orderable SMN/REF to the declared model/reference and barcode/UDI under the applicable record route; no identity between those fields is presumed.
  • Free sale certificate impact

Local-manufacturer CFS uses the current sample workbook

Fact-level verified

For an export CFS requested by a local manufacturer, use ÜTS’s CFS application and the sample Excel downloaded from that application. Populate device barcodes and English product names matching the registered Turkish names, upload the file and sign/send for authority assessment. Devices must be Registered; Rejected or System-has-individual-product statuses cause rejection. The current application workbook is required for that execution route.

Conditions
  • Only if an export CFS is requested by the local manufacturer.
  • The current sample workbook itself must be obtained from the designated application; historical workbook layouts are not certified substitutes.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if the actual local manufacturer requests a new export CFS; obtain the sample Excel from that designated application and use the currently Registered product particulars. Do not substitute an EU-AR application role.
  • Free sale certificate impact

Separate CFS route for a Türkiye-established EU authorised representative

Fact-level verified

A foreign manufacturer’s Türkiye-established EU authorised representative registered in the specified ÜTS activity category requests the export CFS by an EBS petition. Its product list is an applicant-prepared PDF containing device barcodes and English names matching ÜTS Turkish names. The authority assesses the application and provides fee instructions; after payment it issues only for devices still Registered at issuance.

Conditions
  • This requires the actual Türkiye-established EU-AR role. It is not an alternative role that a local manufacturer may select to avoid the sample Excel.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only the foreign manufacturer’s actual Türkiye-established EU authorised representative in the specified registered activity category, requesting a new export CFS; EBS petition/PDF is not a substitute for the local-manufacturer workbook.
  • Change-specific government fees

Conditions for this question

  • Only if the change actually requires this chargeable ÜTS device application or certificate/DoC document-registration transaction under Arts 39–40; not an overall modification/transfer price. Türkiye-produced support is product-eligibility dependent.
  • Change-specific government fees

Conditions for this question

  • Only if the change actually requires this chargeable ÜTS device application or certificate/DoC document-registration transaction under Arts 39–40; not an overall modification/transfer price. Türkiye-produced support is product-eligibility dependent.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Change-specific government fees

Conditions for this question

  • Only if a new export CFS is requested by an eligible local manufacturer or Türkiye-established EU-AR; apply the actual product band and separate copy/destination/regime/Basic UDI-DI rules. This does not price the underlying identity change.
  • Supporting documents

If the authorised representative changes, document the handover

Fact-level verified

The manufacturer, incoming authorised representative and, where practicable, outgoing representative agree the end/start of mandates, last date for the former representative in supplied information, transfer of documents including confidentiality/property rights, and forwarding of later complaints or suspected-incident reports. This handover concerns the authorised representative; it does not itself transfer the manufacturer’s legal responsibility or certificate.

Conditions
  • Use only if the representative actually changes.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only when the authorised representative actually changes as a separate role; this handover does not implement the manufacturer or approval-holder transfer.
  • Supporting documents
  • Labels and identifiers

Align changed identity across labels and declaration

Fact-level verified

Labels identify the device name or trade name and the manufacturer’s name, registered trade name or trademark and registered business address; an authorised representative is identified where applicable. The EU declaration of conformity identifies the responsible manufacturer, device/product or trade name, identification permitting traceability, catalogue reference where relevant and Basic UDI-DI. After an identity change these documents must describe the same responsible person and device.

Conditions
  • Read under the applicable national MDR/IVDR conformity regime; legacy devices require their applicable legacy documentation.
  • A logo-artwork change is not by itself proof of a change to the device name or legal manufacturer.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Use for the affected labels and declaration under the applicable conformity regime; this alignment rule alone gives no old-stock grace, first-placing permission or relabelling authorization.
  • Supporting documents

Notified-body involvement depends on the actual change

Fact-level verified

Under Annex IX the manufacturer informs its notified body of planned substantial changes to the approved QMS or device range. Changes to an approved device that may affect safety/performance or conditions of use require the technical-documentation certificate issuer’s approval; the body decides between a new conformity assessment and a certificate supplement. A same-entity office rename/address change is not automatically a factory, design or significant QMS change.

Conditions
  • Only when that notified-body conformity-assessment route and the relevant change trigger apply.
  • The IVD reference-laboratory 60-day consultation in Annex IX 4.11 is not a general administrative-change SLA.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only if the device uses this notified-body conformity route and the actual change meets its QMS/device-range or safety/performance/use-condition trigger; no administrative-change review SLA follows.
  • Labels and identifiers

New UDI-DI test for trade name or model changes

Fact-level verified

A change that could cause misidentification or ambiguity in traceability requires a new UDI-DI, in particular a change in device name/trade name or device version/model. A commercial order code must first be mapped to the actual label and declared device identity; it is not automatically a UDI-DI or a model.

Conditions
  • Applies to devices in the national MDR/IVDR UDI regime; do not substitute this for the applicable legacy barcode route.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • A changed declared trade name/model or traceability ambiguity triggers the applicable new-UDI test; an internal orderable REF or logo edit must first be mapped to that identity.
  • Existing stock and transition

Separate existing placed stock from further legacy placing

Fact-level verified

The transitional provisions allow devices lawfully placed on the market under the applicable legacy provisions to continue being made available or put into service. Further legacy placing remains subject to the relevant class/date, valid-certificate, QMS and application conditions and absence of significant changes in design or intended purpose. This is not a general rename/transfer sell-through grace period or permission to first place changed devices under obsolete labels.

Conditions
  • Check actual placing date, device class, applicable legacy status, certificate, traceability and affected labels.
  • No universal stock duration following a brand, manufacturer, REF or legal-person change is established by this transition alone.

Conditions for this question

  • Apply only to the actual affected device/document and its applicable national MDR, IVDR or legacy regime.
  • Only eligible legacy devices with an established lawful placing date and the applicable class/date/certificate/QMS/application conditions. This is not a rename/transfer grace period or first-placing permission under an obsolete identity.
Regulation codes

What these codes are

Each row above represents one regulatory instrument. Its code is the authority’s identifier. A regulation page collects the metadata and official source; when readable HTML is available, article links can open and highlight the exact cited passage.

Use this market context

Continue from regulations into practical research

Keep Turkey as the target market while you move into registration records, classification, cross-country product research, or pathway planning.

Keep researching this market
View the Turkey resource hub →
Compare regulations across all countries →
Tracked from official TITCK publications · row IDs are stable — cite as regulations:turkey:ivd-regulation-2021