Medical Devices

ÜTS Registration and Product–Label Matching

How ÜTS registration is built, when product data stops matching the label, and how a broken record jams the import. The practical rules of national traceability.

Authority
TİTCK / Ticaret Bakanlığı
Published
14 Aug 2026
Last reviewed
05 Sep 2026
Reading time
10 min
Quick answer

A ÜTS record is the device's identity card: product description, model and version, manufacturer and authorised representative, classification, conformity evidence and traceability data are defined in the system. The record's validity rests on two conditions: that the data was entered correctly and that the data matches the device's labelling, instructions for use and conformity documents. When matching breaks, the problem first appears at import: in an inspection the label is compared against the record, and on a discrepancy the transaction stops and the product goes into quarantine. Healthy practice rests on three disciplines: managing product master data from a single source, reflecting every product change into the record simultaneously, and cross-checking against record data before label printing. The record lives on after import as well: version transitions, representative changes and label updates renew it; a record left unrenewed is the next shipment's point of jamming.

A medical device's legal identity in Türkiye is born not from the label on the box but from its record in the national tracking system. ÜTS is the national system running the registration, traceability and market surveillance infrastructure of devices: without the record the importer cannot open the gate ahead of the flow; without the record the inspector cannot read the device's story. The record, however, is not a one-off intake form; it is a living data set that must continuously match the device's real-world shape, above all its label. If a model number differs by one letter, if the instructions for use lag behind the record's version, or if the manufacturer information on the label disagrees with the record, a device that exists in the system turns into a different device in the field. This article explains how a ÜTS record is built, how product identity fields are managed, why label matching breaks, and how the break jams the import flow.

Who is this for?

This guide is for every role touching ÜTS data. Manufacturer representatives carry the responsibility of establishing and updating the record. Distributors must correctly reflect the registration status of the products they supply and their own roles in the record. Importers cannot plan shipments without the record and must keep the record data consistent with the declaration. Regulatory teams carry classification and conformity information into the record. Quality units use record data as a checkpoint during label print approvals. Labelling and packaging processes are the last link of the data chain flowing from the design file into the system. Procurement and supply planning includes the registration time of new products in the calendar. Before an audit the question is the same for everyone: which record in the system corresponds to this device seen in the field? The answer to the matching question is the foundation of both import and market surveillance.

Which products does it cover?

The scope is all medical devices and IVD products carrying the national registration obligation. Diagnostic and treatment devices, surgical instruments, electromedical equipment, IVD kits and analysers, dental products, active implantable devices, accessories and software components. The registration obligation begins with entry into the device definition, independent of the product's risk class; the class determines the depth of the conformity assessment running alongside the record. The label-matching scope is broad as well: the device itself, packaging units, multipacks and instructions for use are bound to the same identity chain. The device's consumable components, for instance sensors or cartridges, must carry information relating them to the device's record. Non-device material shipped together with the device, for instance promotional content, sits outside the registration scope; but its placement inside the package must not confuse the label reading. For devices brought for investigation the registration requirement differs; that difference is shown by documenting the status.

When does it apply?

Record management applies across the whole placing-on-market life cycle of the device, but the critical moments are known. At a new product launch the record is the first stone of the import calendar, and if it delays the whole chain slides. On product revisions, on model or version changes, no new shipment can be made before the record is updated. A change in label content, for instance the manufacturer name, the symbol set or a Turkish-language update, requires the record data's renewal too. Changes in the authorised representative or manufacturer structure update the record's party information. At certificate renewals the conformity evidence is tied to the record in its refreshed form. At import inspection the label is compared with the record; market surveillance makes the same comparison. In periods of rising stock turnover, old-labelled and new-labelled products circulating together call for transition planning. The short rule: whatever changed on the product or the label, the record must be spoken to the same day.

Legal framework and authority

The legal basis of ÜTS lies in the registration and traceability provisions of the medical device legislation. Since Türkiye applies the European device regulations nationally, the registration obligations arise from that frame; the national system processes this data for device monitoring and market surveillance. The competent authority is TİTCK: it operates the registration system, sets the data standards, holds the authority to correct faulty records and runs market surveillance over this data. On the import side the record information enters the inspection document set and is presented in the customs control. The labelling rules also come from the same legislation: the mandatory label content, identity information and language requirements are defined; consistency between the record data and the label content is the shared expectation of both regimes. System user guides and data standards are published and updated on the authority's official pages; registration operations run according to the current guide. This article summarises how the system works; case-specific rules must be verified from the current guide.

Step-by-step process

  1. Build product master data from a single source: description, model, version, manufacturer and representative details gathered in one master data table.
  2. Verify classification and conformity information with the regulatory team: class, applied rules, conformity assessment route and evidence.
  3. Prepare the registration application: master data, evidence set and party details merged in the system format.
  4. File the registration output: the record number and the content screen become the product file's reference document.
  5. Cross-check the label design against record data: model spelling, manufacturer name, symbols and mandatory information must match exactly.
  6. Set up the change flow: when product, label or party changes, the record update must be tied to the same change request.
  7. Define the pre-import checkpoint: no shipment order is approved without querying the record status and the label version.
  8. Verify after shipment: at customs and in the depot, label-to-record matching is checked by sampling.
  9. Build the archive and reporting order: record history, label versions and change records kept traceable in a single file.

Document checklist

  • Product master data table: description, model, version, barcode/UDI information.
  • Classification rationale and the conformity assessment route applied.
  • Manufacturer and authorised representative appointment documents.
  • ÜTS registration output and record number.
  • Label designs, approved versions and the Turkish-language information check.
  • Instructions for use version and its matching record.
  • Declaration of conformity and certificate copies, currently dated.
  • Change management records: what changed, when the record was updated.
  • Pre-import control outputs, shipment by shipment.
  • Audit support file: record history and label version chronology.

Parties and responsibilities

Party Responsibility
Manufacturer / Authorised representative Accuracy of master data; establishing and updating the record
Distributor Accuracy of its own role in the record data, label control
Importer Checking record existence as a pre-import condition
Regulatory unit Carrying classification and conformity data into the record
Quality / labelling unit Cross-check against record data at label approvals
TİTCK Operating the system, data standards and market surveillance
Depot operation Sampling check of label-record matching at receipt

The chain's fragile link is usually data transfer: the model spelling in the manufacturer's technical file, the label print and the registration entry must be fed from the same source. Freely typed data is matching's most common enemy.

Exceptions and edge cases

Recurring questions sit at the edges of registration practice. Do variants of the same device family require one record or separate records; the rule is the traceability of every variant carrying a separate identity on the label. For products delivered as sets, the main device and its components enter the record with an identity hierarchy. For products with digitally delivered instructions, the matching of the paper label's minimum content with the digital content is documented separately. Free software updates are assessed for classification as to whether they change the device's version identity; if they do, the record is renewed. Sales of old-labelled stock during a transition period are managed as part of the transition plan. Products manufactured for export and not entering the domestic market stay outside the registration scope; but batches mistakenly routed to the domestic market produce serious noncompliance. Sample and demo devices have their status documented; an investigation device's registration proceeds under a different rule from a commercial device. In every edge case the answer rests on the same principle: every device carrying an identity in the field must be findable in the system.

Common mistakes

The most common mistake is typing the model number by hand; a one-letter difference breaks the match. The second is running label approval independently of record data; the design is beautiful but does not match the record. The third is failing to sequence the record update in version transitions; a new product ships on an old record. The fourth is reporting the representative change late to the record; the party chain breaks. The fifth is applying the Turkish-language update only to the label; the record content lags behind. The sixth is not archiving the registration output; the record's state on a given day cannot be shown at audit. The seventh is never doing the label-record check at depot receipt; the error is found in the market after shipment and the cost multiplies.

Important notice

This article is general information, not legal or customs advice; for registration transactions, TİTCK system guides and current legislation must govern. Product examples and GTİP information in the text are for orientation; the GTİP examples are not binding. System requirements can change; official sources must be checked before any transaction.

Frequently asked questions

At which stage should registration be done: in production or at import?

In the production and market-planning stage, before import. Since the record operates as a precondition of import, registration time must be added to the shipment calendar. The correct order is this: product definition and classification settle, conformity evidence completes, the record is established, label approval is made against record data, and only then is the shipment planned. The reverse order produces goods waiting at the port and record data entered in haste; hasty data is the source of matching errors.

When does the label stop matching the record?

Concrete differences break the match: a different spelling of the model or catalogue number, the manufacturer name missing or differently translated, a serial number format that does not fit, the instructions for use version differing from the one defined in the record, the production site information on the label disagreeing with the record. In a physical inspection the inspector compares these fields one by one; a single critical difference can lead to the device being treated as unregistered. The practical remedy is pre-print control: no label proof goes to print without being checked side by side with the registration output.

How long does a record update delay a shipment?

It depends on the nature of the change: party information corrections stay limited to a data update, while changes affecting the product definition or classification can trigger an assessment process and extend the time. The planning rule is this: in the change impact assessment, the record update is treated as a separate line, and no shipment order is given before it completes. The frequent mistake is considering the job done once the change is applied to the label; a shipment whose system side stays open jams at inspection.

How is registration history shown at an audit?

The registration history is presented together with the device's change chronology in the system: initial record, updates, their reasons and dates. The label version chronology is matched to it: which label circulated in which period. These two chronologies explain the legitimacy of any device found in the field. The archive is therefore built by design: registration screen outputs are kept dated, label approvals are versioned, and change records are tied to both. If this file is not ready at the audit, the defence is weak from the start.

Official sources

  1. TİTCK Medical Device Clinical ResearchTİTCK / Ticaret Bakanlığı · verified 07 Sep 2026
  2. Medical Device Regulation (EU) 2017/745, EUR-LexTİTCK / Ticaret Bakanlığı · verified 07 Sep 2026
  3. Product Safety and Inspection Communiqué AnnouncementsTİTCK / Ticaret Bakanlığı · verified 07 Sep 2026
Important: This operational overview is not legal or customs advice. Product classification, GTİP, origin and intended use can change the applicable procedure. Verify the current text with the authority before shipment.

Revision history

v1.1 · 07 Sep 2026 — Content import: external full text applied.

v1.0 · 14 Aug 2026 — Initial source-backed publication.