Radio equipment conformity rests on three columns of evidence. First, radio tests: the device's operating frequency bands, transmission power, bandwidth and unwanted emission values are shown with laboratory reports. Second, frequency compatibility: the bands the device uses must match the bands open to use and harmonised in Türkiye; bands within the European harmonisation frame are generally suitable, while non-harmonised bands require additional assessment. Third, the common conformity layer: electrical safety and electromagnetic compatibility enter the file together with SAR assessment for devices used near the body. The technical file contains the product description, block diagram, frequency and power information, test reports, declaration of conformity and instructions for use, and is kept on the manufacturer's side. Products using non-harmonised frequencies can require notified body assessment. At import inspection a summary of this file is carried into the TAREKS application and matched with the physical check.
Most of the products around us are, without our noticing, radio equipment: beyond phones and tablets, a Wi-Fi-capable home appliance, a Bluetooth headset, a wireless driver, a smart watch and even some toys transmit over radio frequencies. Radio transmission uses the frequency spectrum, a limited public resource; that is why every radio product carries an extra conformity layer beyond electromagnetic compatibility and electrical safety: frequency compatibility, transmission power limits and spectrum use rules. In Türkiye this layer operates through the regulation on radio equipment and the import inspection communiqué; the radio section of the technical file behind the CE mark is inspection's most question-producing area. This article explains what radio equipment conformity requires, which sections the technical file consists of, frequency compatibility verification and the import practice.
Who is this for?
This guide is for every party importing, producing and selling radio-enabled products. Importers and distributors must request the technical file's radio section from the supplier; the CE mark alone does not show radio conformity. Manufacturer representatives keep the technical file current for the Turkish market. Regulatory teams read the frequency tables and test reports and identify borderline products. Quality units manage file versions and changes. Customs brokers reflect the radio equipment communiqué's inspection route into the document set. Retail and e-commerce verify, without assuming, that the sold product's radio features are usable in Türkiye. Engineering and product development teams watch the frequency plan at design stage: a product designed on the wrong band is learned, at the latest, at customs. At audit the question descends into the file: on which bands does this device operate, what are the power limits, and who produced the reports?
Which products does it cover?
The scope is all products transmitting over radio frequencies. Phones, tablets and all modem variants; Wi-Fi and Bluetooth-enabled computers, printers and home appliances; wireless audio and video products: headsets, speakers, cameras; wearables and smart watches; wireless control and automation products: doorbells, alarm systems, sensors; radio-controlled toys and drones; professional radios and industrial data transfer equipment; logistics tracking and payment terminals. Products with receiver-only capability, merely receiving broadcasts, also count as radio equipment; products not transmitting are assessed in the extended scope. If a radio module was added to the product later, the whole is re-assessed. Those at the border: non-transmitting variants of the same hardware, products with the module disabled, and test-purpose prototypes; their statuses are determined by hardware and software reality. GTİP classification distributes by product family; the conformity regime looks at transmission capability independently of the tariff position.
When does it apply?
The radio conformity rules apply to the import and placing on the market of every radio-enabled product; the critical moments are these. When a new product file is built, the frequency table and test reports are among the first annexes. On model revisions, if the antenna structure, power level or software parameters changed, the radio tests must be renewed; the most frequently missed point is a software update changing transmission behaviour. On supplier change, the test evidence is re-assessed even for the same model. For products using non-harmonised bands, the notified body process comes onto the agenda and must be planned from the start. At import inspection, products within the radio equipment communiqué are assessed through TAREKS, and if a sample is selected, frequency and marking control is done. In market surveillance, interference and spectrum violation complaints are the file's real-world exam. Products manufactured for export mistakenly entering the domestic market combine with non-harmonised band risk. The common rule: if transmission behaviour changed, the file is discussed.
Legal framework and authority
The frame comes from the national application in Türkiye of the European regulation on radio equipment and from the import inspection communiqué published under that frame. The regulation defines the product's essential requirements regarding spectrum use, electrical safety and the protection of human health, and determines the conformity assessment routes. Products applying harmonised standards carry the CE mark under the presumption of meeting the requirements within the standard's scope; products using non-harmonised bands or non-standard solutions require notified body assessment. The management of the frequency spectrum and the national frequency plan sit with the competent authority: BTK regulates the availability of bands, monitors spectrum violations and runs the radio conformity regime. On the import inspection side, the Ministry of Trade runs the control through TAREKS within the communiqué frame. Preparing and keeping the technical file is the manufacturer's obligation; the importer secures access to the file. Standard lists and communiqué annexes are updated annually and periodically; official sources must be tracked.
Step-by-step process
- Extract the product's radio feature inventory: frequency bands, transmission power, modulation and antenna structure.
- Compare the frequency table with nationally usable bands; if a non-harmonised band exists, determine the notified body requirement.
- List the applicable harmonised standards and plan the test programme.
- Collect the test reports from accredited laboratories: radio, electromagnetic compatibility, safety and, where required, SAR.
- Build the technical file: product description, diagrams, frequency and power declaration, reports, declaration of conformity, instructions and labelling.
- Tie the file version to the product version; update the file on hardware and software changes.
- Prepare the file summary and document set for the TAREKS application.
- Secure the match with the physical check at import inspection: label, marking, model identity.
- Monitor market surveillance and complaint processes; record spectrum-related notifications.
- Track standard and communiqué updates; review the file annually.
Document checklist
- Product radio feature table: bands, power, modulation, antenna.
- Frequency compliance comparison and its rationale.
- List of applied standards, with version numbers.
- Radio test reports, from accredited laboratories.
- Electromagnetic compatibility and safety reports.
- SAR assessment report, for body-worn devices.
- Declaration of conformity, signed and matching the product version.
- Technical file index and content list.
- Label and instructions for use samples, with the mandatory information.
- Change records: hardware, software and antenna revisions.
Parties and responsibilities
| Party | Responsibility |
|---|---|
| Manufacturer | Preparing, keeping current and storing the technical file |
| Importer | Guaranteeing access to the file and market responsibility |
| Notified body | Conformity assessment for non-harmonised solutions |
| Accredited laboratory | Running and reporting the test programme |
| Regulatory unit | Frequency analysis, standards tracking and borderline assessments |
| BTK | Spectrum management, frequency plan and the radio conformity regime |
| Ministry of Trade | Applying the import inspection communiqué |
| Quality unit | File version management and change control |
The chain's heart is the test report: the report proves that the product is the same device described in the file. The gap between the report and the product version weakens the entire file.
Exceptions and edge cases
The edge of radio conformity practice is full of technical questions. Receiver-only products are still within the regulation's scope but the requirement set differs. In software-defined radios, bands and power can be changed by software; the file should explain the device's configuration on the Turkish market and its restriction mechanisms. For products carrying a module certificate, an assessment is required for the whole into which the module is mounted; the module report alone does not cover the finished product. An antenna change alters transmission behaviour and can require retesting. In headsets and wearables the SAR limit is assessed by use distance. In toys, power limits and distance conditions are strict. Military and amateur bands have special rules and are not suitable for commercial products. Single devices brought personally are assessed separately, outside commercial inspection, though carrying use risk. Every solution stepping outside harmonised standards opens the notified body's door. In every edge case the basis is written: the standard provision, the authority's opinion or the test report.
Common mistakes
The most common mistake is taking the CE mark as proof of radio conformity; the mark means something only with the file behind it. The second is using the test report from an old version; the product was revised, the report stayed behind. The third is never making the frequency table; a product whose operating bands are unknown cannot have its conformity proven. The fourth is presenting the module report as a finished-product report; the coverage falls short. The fifth is leaving the software update outside the file; transmission behaviour silently changes. The sixth is ignoring the antenna change; power and emission have changed. The seventh is noticing the notified body requirement at the last moment; the calendar collapses. The eighth is leaving the file at the manufacturer without securing access; at inspection the file is unreachable.
Important notice
This article is general information, not legal or customs advice; for radio equipment conformity, the applicable legislation, harmonised standard lists and current communiqué annexes must govern. GTİP codes and frequency and power examples in the text are for orientation and are not binding. Standards and communiqués are updated; official sources must be checked before any transaction.
Frequently asked questions
Does the CE mark prove radio conformity?
Not on its own. The CE mark is the visible sign that the manufacturer declares the product meets all applicable requirements; the proof is the technical file behind the mark. In radio equipment that file's radio section contains the frequency and power declaration with the test reports. A device carrying the mark but with a missing file or one not matching the product is found nonconforming at inspection. The importer's task is to request not the mark but the file: without reports, declaration and frequency table, CE is a label. When market surveillance requests the file and it cannot be presented, the mark cannot carry the product's validity alone.
How is frequency compatibility verified?
The device's operating bands are listed and compared with the usable bands in the national frequency plan. Bands harmonised within the European harmonisation frame are generally usable; non-harmonised bands require additional assessment and, in most cases, a notified body process. Verification is done over the frequency and power values in the test report; the declaration and the report must match. In software-defined radios, the device's market configuration and band restrictions are shown in the file. The verification's output is the frequency compliance table: with rows for band, power, standard and result. This table is a fixed annex of the import file and the TAREKS application.
What should the technical file contain?
The core set is known: product description and intended use; block diagram and component list; frequency, power and modulation declaration; list of applied standards; radio, electromagnetic compatibility and safety test reports; SAR report where required; risk analysis; signed declaration of conformity; label and instructions for use samples. The file is prepared by the manufacturer and kept for a defined period from the product's last manufacturing date. The content deepens by product group; for products using modules, the module documents are tied to the whole. The file's index is the first document requested at audit; a file without an index means scattered evidence.
Does a software update change conformity?
If it touches transmission behaviour, yes. If the update changes frequency, power, modulation or band use, the product's declaration in the file is no longer valid and the relevant part of the tests is renewed. If the update is limited to interface or functional change and does not touch transmission parameters, a change record may suffice; the assessment is made through change management. The manufacturer's update policy should be defined in the file: which updates affect conformity and how they are recorded. A product distributing uncontrolled updates cannot be defended at inspection with an old file. The rule is simple: if a transmission parameter changes, the file is discussed.
Official sources
- Product Safety and Inspection Communiqué AnnouncementsBTK / Ticaret Bakanlığı · verified 07 Sep 2026
- BTK Central Device Registration SystemBTK / Ticaret Bakanlığı · verified 07 Sep 2026
- TAREKS Product Safety Inspection SystemBTK / Ticaret Bakanlığı · verified 07 Sep 2026
Revision history
v1.1 · 07 Sep 2026 — Content import: external full text applied.
v1.0 · 26 Aug 2026 — Initial source-backed publication.