The decisive feature is the cellular module. A tablet connecting to the network with SIM is assessed as a communication device: it does not work on Turkish networks without IMEI registration, and the surveillance mechanism and registration processes run similarly to the phone's. A Wi-Fi-only tablet requires no registration; its regime is product safety inspection and conformity evidence. But both variants are radio equipment: every device transmitting over Wi-Fi and Bluetooth frequencies enters radio conformity scope and carries radio test evidence in its technical file. Under the CE-required products scope both variants are imported via the TAREKS conformity application. On the GTİP side cellular devices gather in the communication devices position; for Wi-Fi-only devices the assessment follows the device's function, and the classification file should be kept separately by variant. In the ordering process the variant code must be a mandatory line: Wi-Fi or cellular, how many units and with which document.
Two tablets that look the same can turn into two different products at the import desk: one, with its cellular module, is a network device tied to the registration system; the other runs Wi-Fi only and is exempt from the registration burden. The difference hides not in the box but in the hardware, and one of the importer's most expensive mistakes is missing that difference at the order stage: a wrongly imported variant batch becomes stock that either cannot be registered or needs no registration. Two regimes run side by side in tablet import: while cellular devices go through a phone-like registration and surveillance chain, Wi-Fi-only devices pass product safety and radio conformity controls. Both variants count as radio equipment: Wi-Fi and Bluetooth are also radio transmission. This article explains the import differences of the two variants, the registration and conformity rules, and the mistakes possible in ordering and acceptance.
Who is this for?
This guide is for every party importing and selling tablets. Procurement teams must verify the supplier list before writing the variant code into the order line; the most frequent mistake happens exactly there. Importers and distributors manage the two variants' document chains in separate files. Customs brokers set the declaration lines and GTİP matching variant by variant. Retail and e-commerce teams check the cellular variant's registration status before sale; a tablet whose SIM does not work is the fastest return reason. Technical teams verify the devices' module configuration and software status. The regulatory unit keeps the two variants' conformity files separate. Service units know the registration and warranty processes in cellular module failures. Finance teams carry the cost risk of wrong-variant stock into ordering policy. At audit the question is variant-focused: how many cellular and how many Wi-Fi devices are in this batch, and through which document chain did each enter?
Which products does it cover?
The scope is all portable computing devices separating by connectivity structure. Cellular tablets: models connecting to the mobile network with SIM or eSIM, carrying voice call and data features. Wi-Fi-only tablets: models without a cellular module, connecting via Wi-Fi and Bluetooth. Border products: devices whose cellular module can be added later, mobile data dongles and devices with modem function; their status is assessed by hardware structure. E-book readers and portable readers fall under the same distinction: the cellular variant enters the registration system. Connected consumer devices in general are read with the same logic: every product using radio frequencies for communication relates to the radio legislation, and every device connecting to the cellular network relates to the registration regime. Accessories in the box, adapters and cables pass through their own regimes. GTİP classification arises from the combination of function and hardware; since the variant difference can change the position, the classification file must be reasoned separately by variant.
When does it apply?
The variant distinction applies to every tablet import; the critical moments are known. In new model imports the two variants arriving together is frequent, and the in-batch distinction must be correctly reflected into the customs file. Supplier revisions changing the variant code break the order-acceptance match; acceptance control must verify the variant through hardware. When market demand shifts and calls for cellular instead of the Wi-Fi variant, stock conversion is solved through the registration process; selling without registration is a consumer problem. If a software update of the cellular device changes modem behaviour, the conformity file is refreshed. At sample inspection the module structure cannot be disassembled but is verified through label and model identity. In campaign periods mixed batches increase; acceptance lists must keep the variant line mandatory. At import inspection, if the declaration and the actual batch disagree, whether the discrepancy stems from a variant error is investigated and the answer must be written. The common rule: the variant information lives with the same term from order to declaration.
Legal framework and authority
The frame comes from three layers. The first is foreign trade: cellular communication devices are monitored within the surveillance mechanism and the Import Regime Decision; surveillance document processes run through the Ministry of Trade. The second is product safety: the import inspection communiqué for products requiring CE marking governs both variants' import via the TAREKS conformity application; safety, electromagnetic compatibility and label controls operate in that frame. The third is the radio and registration legislation: the radio equipment import inspection and the radio arrangements cover the conformity of all radio-transmitting devices, including Wi-Fi and Bluetooth; cellular devices' network access ties to the registration regime, an area within BTK's competence. Radio frequency compatibility, in the sense of the device supporting usable bands in Türkiye, is part of the technical file. The competent authorities are the Ministry of Trade and BTK. At annual communiqué renewals the numbers and annex lists change; current texts must be tracked from official sources.
Step-by-step process
- Write the variant code into the order line as a mandatory field: cellular or Wi-Fi, together with model and quantity.
- Obtain the variant-based technical sheet and module structure information from the supplier.
- Reason the classification file separately by variant; if the position differs, set up two files.
- Collect conformity evidence: safety, electromagnetic compatibility, radio tests and SAR where required.
- For the cellular variant, prepare the surveillance document and IMEI registration plan.
- Create the TAREKS conformity applications variant by variant and upload the documents.
- Build the customs declaration line by line: each variant with its own position and document.
- Verify the variant at acceptance: model code, module information and label control.
- Complete the cellular devices' registrations and bind the pre-sale SIM check into the procedure.
- Archive the records variant by variant; refresh the documents at communiqué renewals.
Document checklist
- Variant-based order table: model, connectivity type, quantity.
- Technical sheet and module structure declaration, for the variant.
- Classification rationales, separate by variant.
- Test reports: safety, EMC, radio; SAR where required.
- Declaration of conformity and CE marking information, matching the model version.
- Surveillance document, for the cellular variant.
- IMEI lists and registration outputs, cellular batch based.
- TAREKS application and outcome records, for each variant.
- Acceptance control minutes, with variant verification.
- Declaration line matching table: variant, position, document.
Parties and responsibilities
| Party | Responsibility |
|---|---|
| Procurement | Accuracy of the variant code in the order and supplier confirmation |
| Importer | The whole of the variant-based document and declaration chain |
| Customs broker | Line-based declaration, position and document matching |
| Regulatory unit | Variant-based conformity and classification files |
| Retail / e-commerce | Pre-sale registration and SIM check |
| Technical service | Module configuration and after-sales processes |
| BTK / Ministry of Trade | Registration, radio conformity and inspection regimes |
The chain's first link is procurement: the variant error is made there and its cost is paid at customs or on the shelf. Adding a variant verification step to the order approval is the cheapest insurance.
Exceptions and edge cases
The edge of variant practice produces real questions. A device whose cellular module will in fact never be used is still tied to the registration regime if the module is in the hardware; usage intent does not change the status. For devices with a later-added module the status is re-assessed on the post-change hardware; if the change was made by the manufacturer, not the importer, the file must be updated. Devices using cellular data only for navigation are also within registration; a data connection is a cellular connection as much as a voice one. In reader devices the Wi-Fi variant is exempt from registration but not from radio conformity. Prototypes brought for testing and development are assessed in their non-commercial status. Personal-use arrivals proceed under passenger accompanying rules; a cellular device's personal registration is done through the individual process. In transit and temporary arrivals there is no registration obligation, but there is an exit obligation. In a mixed batch a declaration error can become a correction matter; correction is done through administrative processes with written rationale. In every edge case the answer rests on the hardware reality: is there a cellular module in the device or not.
Common mistakes
The most common mistake is not writing the variant code in the order; the arriving batch is the opposite variant of the market need. The second is importing both variants under a single document set; the cellular variant's registration and surveillance chain does not fit the Wi-Fi set. The third is gathering the declaration lines under a single position; if the variant changes the position, the declaration is wrong. The fourth is not verifying the variant at acceptance; the stock records do not reflect reality. The fifth is dropping the radio test evidence for the Wi-Fi device; Wi-Fi is also radio transmission. The sixth is selling cellular stock unregistered; the consumer puts in a SIM and the device does not work. The seventh is treating the variant difference as a mere technical detail and not informing marketing and sales; the return reason is born on the shelf.
Important notice
This article is general information, not legal or customs advice; for tablet imports, the current surveillance and inspection communiqués, radio legislation and registration system rules must govern. GTİP codes and communiqué numbers mentioned here are illustrative; the GTİP examples are not binding, and the numbering changes annually. Official sources must be checked before any transaction.
Frequently asked questions
Does a Wi-Fi tablet require IMEI registration?
No. The registration regime covers devices connecting to cellular networks; a tablet working via Wi-Fi and Bluetooth has no IMEI, so no registration obligation arises. This exemption, however, does not remove the device's other obligations: radio conformity, CE-scope inspection and labelling rules apply in full. If the device has a cellular module, the status changes even if unused: if the module is in the hardware, the device is tied to the registration regime. The practical test is simple: if the device has a SIM slot or eSIM configuration, think on the registration side.
Which common documents are required for both variants?
The conformity chain is common: safety and electromagnetic compatibility tests, radio test reports, the manufacturer's declaration of conformity and CE marking information, label samples and Turkish-language usage information. The TAREKS conformity application is made for both variants. In the customs file the invoice, declaration and acceptance records share the common skeleton. The difference lies in the cellular variant's additional load: the surveillance document and IMEI registration processes belong to it alone. The file architecture should be built accordingly: common evidence set plus variant annexes.
What happens if the wrong variant was imported?
First the status determination is made: is the arriving batch Wi-Fi or cellular, what does the declaration say, which variant does the document set belong to? If the declaration and the actual situation match, the problem is commercial; the product is managed according to market need. If they do not match, that is, if cellular devices arrived under a Wi-Fi declaration or with missing documents, corrections and additional processes come onto the agenda at customs. Cellular devices cannot be sold without registration; the stock waits until the registration process completes. The financial outcome varies batch by batch: waiting cost, correction process and possible administrative proceedings. The prevention sits in the order: the variant code is a mandatory field of the order line.
Is a cellular tablet's registration the same as a phone's?
Same regime, similar process. The device registration system covers all cellular-connected devices; a tablet is treated as a phone for registration. IMEI registration is the precondition of network access; an unregistered device does not connect to mobile networks. The surveillance mechanism also operates through the communication device family. The difference arises in practice from the device's use: data-focused use is common on tablets but this does not change the registration burden. In commercial import registration runs tied to the import flow; in personal arrivals the individual process applies. The rule is clear: every device working with SIM must be registered.
Official sources
- BTK Central Device Registration SystemBTK / Ticaret Bakanlığı · verified 07 Sep 2026
- Product Safety and Inspection Communiqué AnnouncementsBTK / 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 · 24 Aug 2026 — Initial source-backed publication.