Turkey's ÜTS registration is the approval, not proof of one

This blog has already covered a registry entry that looks like clearance but isn't one — New Zealand's WAND listing records a device, and nothing in that record constitutes Medsafe's approval of it. Turkey's own system runs the opposite case. A device entered into the Ürün Takip Sistemi (ÜTS), the product-tracking system every device sold in Turkey has to clear, isn't a record filed after an approval happens somewhere else. The ÜTS entry is the approval. TİTCK, Turkey's Medicines and Medical Devices Agency, issues no separate certificate behind it.

A system that replaced a predecessor, not a blank slate

ÜTS wasn't Turkey's first device-tracking system. It replaced TİTUBB, the Türkiye İlaç ve Tıbbi Cihaz Ulusal Bilgi Bankası, which stopped accepting new device entries in June 2017 as ÜTS opened to take them over. Existing TİTUBB registrations didn't vanish on that date; they carried forward for manufacturers and importers to re-activate inside ÜTS using their old TİTUBB numbers, rather than starting every file over from nothing. A registration tracker still citing TİTUBB as a device's current system of record is citing a database that stopped taking new entries years ago.

The company registers before the device does

ÜTS runs on a two-step sequence, and the steps aren't interchangeable. A manufacturer or importer first establishes its own firm record inside the system; only once that firm record exists can it go on to register a specific device under it, attaching the device's EC certificate, its ISO 13485 certificate, its declaration of conformity, and the barcodes carried on its own labeling. Each distinct barcode gets registered as its own entry, which means a single device family sold under several package sizes or configurations clears ÜTS as several separate records, not one filing covering the line.

No separate certificate, because the registration is the certificate

Once a device's dossier clears ÜTS review and the entry is accepted, that acceptance is the device's market authorization in Turkey. There's no additional document TİTCK issues alongside it, the way an EU notified body issues a CE certificate distinct from whatever national registry later lists the device. A regulatory file still waiting for a Turkish approval certificate to arrive separately from the ÜTS record is waiting for paperwork the system was never built to produce; the record itself is the only artifact there is.

A foreign manufacturer still needs a local name on the record

A manufacturer without its own legal entity in Turkey can't register directly. It has to appoint a local Authorized Representative first, and that representative is the party ÜTS actually records against the device, not a formality running alongside the filing. The role does similar work to an EU Authorised Representative or a Canadian importer of record, but it attaches to whoever is registered in ÜTS specifically — a manufacturer's existing EU-based AR doesn't automatically carry the same standing inside Turkey's own system.

Classification follows EU categories, until TİTCK disagrees

Devices entering ÜTS carry the same classification scheme their CE certificate already assigned them — Class I, IIa, IIb, or III — and most dossiers pass through on that basis without dispute. The classification isn't rubber-stamped on arrival, though: TİTCK can and does revisit it during its own review, particularly for devices sitting close to a class boundary. A dossier that assumes its EU classification simply carries into Turkey unchanged has skipped a review step the agency reserves for itself.

The record is only as current as the certificate behind it

An ÜTS entry doesn't stand apart from the CE certificate and declaration of conformity it was built from. Those documents carry their own expiry and renewal cycle at the EU side, set by whichever notified body issued them, on a timeline that has nothing to do with Turkey's own system. A registration tracker that logs the ÜTS entry once and leaves it alone has no mechanism for noticing when the certificate underneath it lapses — and because ÜTS issues nothing of its own to expire, there's no second, independent clock inside the Turkish system that would flag the gap on its own.

Where this meets the file

A Turkey row in a cross-border registration tracker needs the ÜTS entry carried as the device's own authorization record — not a pending field waiting on a certificate that isn't coming — alongside the registered local Authorized Representative and the barcode-level entries a multi-configuration device actually requires. A registration tracker built around that structure, alongside the launch catalog's other cross-border templates, is previewed there now. If your program has tracked ÜTS differently, the shelf takes that correction directly.