IMEI, MCKS and Device Registration

In Türkiye a cellular device's access to the network is managed through its hardware identity: the unique identity every device carries is processed into the central registration system, and an unregistered device is not recognised by the networks. The regime's purpose is traceability: registering the devices on the market, preventing unregistered and undocumented product from appearing on the networks, and securing the usability of the device sold to the consumer. The regime operates through two separate gates: in commercial import, registration runs tied to the import flow, batch by batch; in personal arrivals, registration is done through the individual process within defined limits. Confusing the two gates produces problems on both the importer and the consumer side. This article explains how the device registration system works, the commercial and personal registration processes, the deadline and access rules, and the management of registration data.

Who is this for?

This guide is for every role touching cellular devices. Importers and distributors own the commercial registration process; they know the risk of selling without registration. Retail and e-commerce sellers must query the registration status of the devices they supply; selling unregistered stock produces returns and complaints. Customs brokers remind the registration requirement into the declaration chain within the import flow. Consumers should know the registration obligation of devices they bring from abroad; the aware consumer asks whether the device they buy is registered. Service and technical support units distinguish a device arriving with a registration restriction from a technically faulty device. Second-hand market operators check the device's registration history; the registration history is part of the device's second-hand value. Finance and logistics teams plan the alignment of the registration process with the shipment calendar. At audit the question turns to the registration ledger: was this batch registered, when, with which identities.

Which products does it cover?

The scope is all devices connecting to cellular networks. Phones; tablets working with SIM and eSIM; other portable devices carrying cellular modules; dongles and modems for mobile data; cellular-connected models of wearables; cellular-connected readers and terminals. The decisive feature is the device's ability to connect to the mobile network: devices working via Wi-Fi do not enter the registration system. A device carrying dual SIM does not change the registration logic; registration runs identity-based. Virtual eSIM configurations sit in the same regime: eSIM does not replace the device identity; registration works together with the device identity. Modules arriving with the device that can establish cellular connectivity on their own count as separate devices and require separate registration. On the GTİP side this product family gathers in the communication devices position; the classification record feeds the declaration, but the registration regime looks at the device's connectivity capability independently of the tariff position.

When does it apply?

The registration regime shows itself at every entry of a cellular device into Türkiye and at ownership changes. In commercial import registration runs tied to the import transaction and must be complete before sale. In passenger accompanying arrivals registration is done by the person bringing the device and is assessed within personal-use limits; arrivals exceeding the quantity limit count as commercial intent. For devices arriving by cargo from abroad, the registration obligation falls to the recipient; without registration the device faces access restriction after the defined period. Devices brought in a company's name for testing are assessed separately. When a device is sold, registration is not transferred from carrier to buyer: registration attaches to the device, not the person; but use access can differ by registration type. In second-hand sale the registration history is the indicator of the device's validity. If a device is lost or stolen, notification is made through the registration system and the device is traced. In service exchanges a mainboard change can produce an identity change; this requires a registration update. In every case the regime's language is the same: registration is the device's legal access document.

Legal framework and authority

The legal basis of the device registration regime rests on the electronic communications legislation: managing network access and registering devices are defined within the electronic communications arrangements. The system is operated centrally by the competent authority; registration, query and access restriction processes run through this system. The competent authority is BTK: it operates the registration system, regulates the personal and commercial registration procedures, sets the deadline and quantity limits and enforces the access restrictions. On the commercial import side registration runs alongside the customs and foreign-trade processes: the surveillance document, TAREKS control and registration are three separate functions of the same shipment. In personal registration, fee and identity verification procedures apply as defined by the system. The protection of registration data runs consistent with the general arrangements on processing personal data. Procedures and limits can be updated over time; current rules must be tracked from the authority's official pages. This article summarises the regime's operation; case-specific processes must be verified from current sources.

Step-by-step process

1. Build the device inventory identity-based: model, variant and device identity list.
2. Obtain the batch-based identity lists from the supplier in writing and add them to the order.
3. In commercial import, tie the registration plan to the import calendar: registration completes at the import stage, not at sale.
4. Proceed in step with the surveillance and inspection document processes; registration is part of the declaration chain.
5. Run the registration transactions batch by batch and file the registration outputs.
6. Verify the identity match at acceptance: invoice, box and registration list must show the same devices.
7. Add a registration status field to the stock system; do not open unregistered devices to sale.
8. Query the device's registration status at the pre-sale check and record the result.
9. Recognise the possibility of identity change in service processes and tie the registration update into procedure.
10. Archive the registration history device by device; use this history in second-hand and return processes.

Document checklist

• Device identity lists, batch and model based.
• Supplier correspondence: delivery and confirmation of identity lists.
• Registration application and outcome outputs, dated.
• Import file: surveillance document, TAREKS outcome and declaration matching.
• Acceptance control minutes, with identity verification.
• Stock system registration status reports.
• Pre-sale registration query records.
• Service registration update requests and outcomes.
• Loss-theft notifications and tracking records.
• Registration history documents in return and second-hand processes.

Parties and responsibilities

The chain's fragile point is the identity list: a list arriving incomplete or wrong from the supplier stops registration and breaks the import calendar. List delivery should be a contractual condition of the order.

Exceptions and edge cases

The edge of the registration regime is full of practical questions. In passenger arrivals the quantity limit rests on the personal-use presumption; repeated breaches produce a commercial-intent interpretation and the registration procedure changes. Personal registration is fee-based and runs within defined periodic limits per person; the limits are set by current rules. In temporary arrivals no registration obligation arises; but the device must leave at the end of the period. In transit shipments registration is not at issue. Devices arriving for repair are assessed in temporary status. A mainboard change can change the device identity; if the change is under the manufacturer's control, the registration update procedure operates. Test and development devices are assessed separately with non-commercial status documentation. Gift and promotional devices, if cellular-connected, are still subject to the registration regime. The registration status of devices found after loss-theft is managed separately. In every edge case the basis is the system itself: the registration status query replaces all interpretation.

Common mistakes

The most common mistake is postponing registration until after sale; the device does not work and a return is born. The second is requesting the identity list from the supplier without a contract; the list is late and registration blocks. The third is keeping no registration status field in the stock system; which device is registered is unclear. The fourth is sending Wi-Fi and cellular devices in a mixed batch under a single list; registration is rejected. The fifth is skipping the registration update in a service mainboard change; the device later meets an access restriction. The sixth is using passenger-arrival quantity limits in a commercial flow; the procedure is different. The seventh is not archiving registration outputs; at audit the fact of registration cannot be shown.

Important notice

This article is general information, not legal or customs advice; for registration transactions, the registration system's current rules, the authority's announcements and customs legislation must govern. The deadline, quantity and fee applications mentioned in the text are variable and not binding. Official sources must be checked before any transaction.