Türkiye type approval was withdrawn
Teams still budget months and a local agent for a Turkish radio approval that no longer exists. BTK stopped accepting type approval applications in May 2021. This is what actually applies now — and why the stale answer is so persistent.
What changed, and when
| Date | Change |
|---|---|
| 5 November 2020 | The Radio Equipment Directive (2014/53/EU) took effect in Türkiye. |
| May 2021 | BTK suspended type approval applications. |
| Now | No pre-market permit. Compliance enforced by market surveillance. |
BTK — the Bilgi Teknolojileri ve İletişim Kurumu, Türkiye's information and communications technologies authority — has clarified that there is no obligation to apply for a permit before placing a product on the market.
What you need instead
- CE marking demonstrating compliance with the Radio Equipment Directive.
- The relevant technical file, held and available on request.
- A user manual in Turkish. This one is routinely missed by teams who treat Türkiye as "just CE".
- Product labelling in line with the Consumer Protection Law.
No pre-approval is not no obligation. Market surveillance means the regulator checks products already on shelves, and penalties apply to non-compliance found after the fact. The evidence burden did not disappear — the queue did.
Why the stale answer persists
Three reasons, and they are instructive about market-access data generally.
Removals are published quietly. A new requirement generates alerts, webinars and consultancy marketing. A withdrawn one generates nothing — there is no service to sell against it.
Consultancy pages age in place. Country guides written before 2021 still rank, still describe a BTK submission, and still list the local-agent requirement that went with it. Nobody is paid to take them down.
Language models repeat the old answer confidently. They were trained on the pre-2021 corpus, which is far larger than the post-2021 corrections, and they will describe a Turkish type approval process in fluent detail.
This is the general case for dated, sourced market-access data rather than a summary: the expensive errors are not the rules you have never heard of, they are the rules that changed while your reference material did not.
What this is worth on a launch plan
If Türkiye was on your list with a type approval line item, you are carrying:
- a certification fee that no longer applies;
- a local agent appointment you may not need;
- weeks of assumed lead time on your critical path;
- and a launch date set later than it needs to be.
Removing an item from a launch plan is rarer and more valuable than adding one. It is also the kind of finding that only comes from data someone maintains on purpose.
How Conformant reports it
Türkiye returns local_testing_required: false and
accepts_foreign_reports: true, with the withdrawal explained in the
obligation notes and the source and date attached — so you can see both the answer and
what it rests on.
Crucially, the engine does not confuse "nothing required" with "nothing
known". Where a rule is genuinely unestablished, it says not_established and
the market's verdict drops to insufficient_data rather than reading as a
pass. An absence of evidence is never a permission.
Check Türkiye against the rest of your launch list in one call — no integration needed, bring your own API key.