CITC Type Approval

If it transmits, it needs two approvals

A connected product answers to two regulators at once: the telecom authority for the radio, and the conformity system for the product. The radio side turns almost entirely on which bands the device uses and at what power — a question worth answering before the production run, not after it.

An unbranded connected device on a turntable in a radio test setup

Send to check a connected device:

  • Frequency bands and power
  • Radio module details
  • Existing RF reports
Check My Device Bands

What type approval actually covers

Six things that decide a radio file, and the last one is a commercial decision rather than a technical one.

A second approval, not an alternative one

A connected product needs telecom approval for the radio and conformity certification for the product itself. Neither substitutes for the other, and a file that answers only one is half finished.

The bands decide everything

Approval turns on which frequencies the device transmits in, at what power. A band that is licence-exempt elsewhere can be restricted or prohibited here, and no amount of test evidence changes that.

Approval is per model, by radio configuration

Two variants that share a case but carry different radio modules are two approvals. Conversely, a range built on one certified module is usually one file with the variants declared against it.

Radio, EMC and safety, all three

The radio report covers spectrum behaviour, EMC covers interference, and safety covers the product as electrical equipment. Body-worn and handheld devices add an exposure assessment on top.

The approval is marked on the product

Once granted, the registration is reflected on the device or its packaging as the rules require. It is also what a customs officer or an inspector looks up when the goods arrive.

Someone local has to hold it

Applications run through a Saudi entity — importer, distributor or a local representative. Overseas manufacturers do not file into this system directly, which is a sequencing problem when no importer is appointed yet.

Which devices need approval

If there is an antenna in the product, assume it is in scope until the classification says otherwise.

Wi-Fi and Bluetooth devices

Routers, access points, speakers, headphones, wearables and the enormous long tail of consumer electronics with a short-range radio inside.

Cellular equipment

Phones, modems, routers and any module connecting to a mobile network, assessed against the bands the Saudi networks actually operate.

IoT and telemetry modules

Metering, tracking, sensing and industrial telemetry, including low-power wide-area technologies whose band availability varies more between markets than manufacturers expect.

RFID and NFC equipment

Readers, gates, tags and payment terminals. Reader power and frequency are the questions here, and they differ by region more than the technology suggests.

Drones and remote control

Unmanned aircraft and their controllers carry aviation and security requirements alongside the radio approval, and the combination should be scoped before any purchase commitment.

Two-way radios and repeaters

Professional radio equipment, where licensed spectrum brings the end user’s licence into the picture as well as the equipment approval.

Satellite terminals

Ground equipment of any kind, assessed more strictly than consumer radio and normally involving additional authorisation for the service as well as the hardware.

Appliances that happen to connect

Televisions, air conditioners, white goods and toys with a radio module inside. The radio still needs approval even when connectivity is a minor feature of the product.

Bands first, everything else after

Five steps. Step two is where a programme is saved or lost, and it costs nothing but an afternoon.

  1. Establish exactly what the device transmits

    Frequency bands, channel plan, output power, antenna gain, duty cycle and the module part number. This is the technical core of the application, and it comes from the radio module maker rather than from marketing material.

  2. Check the bands against Saudi allocation

    Each band is compared with the local spectrum position, including power limits and any local restrictions. Where a band is unavailable, the answer is a firmware or hardware change, not a stronger application.

  3. Assemble the test evidence

    Radio, EMC and safety reports, plus an exposure assessment for body-worn and handheld products. Existing reports from recognised schemes are often usable if they cover the bands and the configuration actually shipped.

  4. File through a Saudi entity

    The importer, distributor or appointed representative submits with the technical file, product photographs, manuals, block diagrams and the declaration set. Appointing that entity early keeps this from becoming the bottleneck.

  5. Mark, and run the conformity file alongside

    The approval is reflected on the product as required, and the SABER product certificate for the electrical side proceeds in parallel so both are in hand before the goods ship.

What the application needs

Ten items. Most exporters hold seven of them already, for another market, in a configuration that has to be checked.

  • Radio test report covering every band and mode the device transmits in
  • EMC test report for the product as sold
  • Electrical safety report for the host product
  • RF exposure assessment for handheld and body-worn devices
  • Radio module identification, including the module approval where one exists
  • Block diagram and antenna specification with declared gain
  • Declared output power per band, with any regional firmware settings stated
  • Product photographs, internal and external, with the label position shown
  • User manual as supplied, including the frequency and power statements
  • Saudi applicant details — importer, distributor or appointed representative
Unbranded radio modules and antennas laid out for assessment

Four products, six radios

A smart home manufacturer shipping four connected devices — two Wi-Fi, one with an additional sub-GHz radio, one with a cellular module — into Saudi Arabia for the first time.

  1. Radios itemised

    The four products carried six distinct radio configurations between them, not four. The file was scoped on the radios rather than on the product count.

  2. Bands checked

    The sub-GHz product used a band unavailable locally. The manufacturer had an alternative regional variant and switched the model offered here to it.

  3. Evidence mapped

    Existing radio and EMC reports covered most configurations. Only the regional variant needed new radio testing, in its as-shipped firmware setting.

  4. Filed locally

    The appointed distributor submitted as applicant, with photographs and manuals prepared in advance so the filing itself took days rather than weeks.

  5. Shipped once, not twice

    Telecom approvals and SABER certificates landed in the same fortnight because they were run in parallel from the start.

Where radio files come unstuck

Six failures. The first is a design problem, the fourth is a contract problem, and the fifth stops a container.

A band that is not available here

A device built around spectrum that is licence-exempt in its home market and restricted in Saudi Arabia. Discovered after production, it is a firmware change at best and a redesign at worst.

Power above the local limit

The same band, permitted, but at a lower ceiling than the device transmits at. Regional firmware exists for exactly this reason — it just has to be set and declared before testing, not afterwards.

A module swapped mid-production

A second-source radio module fitted for supply reasons. The approval describes the configuration that was tested, and a different module is a different product.

No Saudi applicant appointed

The technical file is complete and nobody can submit it. Where the importer is still being negotiated, the approval waits on a commercial decision rather than a technical one.

Treating approval as covering conformity

The telecom approval is granted and the shipment is still stopped, because the product also needed its SABER certificate. Two regulators, two files, one consignment.

Marking left off the production run

The approval is granted but the required marking never reaches the artwork. It is checked at the port and in the market, and correcting it after the run means relabelling stock.

Type approval questions

The radio side specifically. The product conformity it runs beside is answered on the SABER pages.

What is CITC type approval?

It is the approval a radio or telecom device needs before it can be imported and used in Saudi Arabia, covering the frequencies it transmits in, the power it transmits at and its behaviour on the spectrum. The regulator is now the Communications, Space and Technology Commission — the successor to CITC, which is still the name most exporters search for.

Which products need it?

Anything that transmits: Wi-Fi and Bluetooth devices, cellular equipment, IoT and telemetry modules, RFID and NFC readers, drones and their controllers, two-way radios, satellite terminals, and ordinary appliances that happen to have a radio inside. If there is an antenna in the product, assume it is in scope until the classification says otherwise.

Does type approval replace SABER certification?

No, and this is the most expensive misunderstanding in the category. The telecom approval covers the radio; the SABER product certificate covers the product as regulated goods. A connected appliance needs both, and a consignment arriving with only one of them does not clear.

Can I use my FCC or CE radio test reports?

Often, in substantial part. What matters is whether the reports cover the exact bands, power settings and configuration being shipped here. Where the device is sold with regional firmware, the evidence has to describe the setting that will actually leave the factory for this market.

What if my device uses a band that is not permitted in Saudi Arabia?

Then the device as built cannot be approved, and the route forward is technical rather than administrative — a firmware restriction, a regional variant or a different module. This is why the band check is the first step rather than a formality after testing, and why it should happen before production for this market is committed.

Do I need a local representative to apply?

Applications run through a Saudi entity — normally the importer, the distributor or an appointed representative. An overseas manufacturer does not file directly. Where the importer has not been appointed yet, the approval effectively waits on that commercial decision, so it is worth settling early.

Is approval given per model or per radio module?

Per product model, described by its radio configuration. A range built around one certified module is usually handled as a single file with variants declared against it, while two models carrying different modules are two separate approvals even when they look identical from the outside.

What happens if we change the radio module during production?

It is a new configuration and needs its own approval. Second-sourcing a module for supply reasons is common and entirely legitimate, but the approval describes what was tested, and shipping a different module against it is shipping an unapproved product.

How long does type approval take?

With complete evidence covering the right bands, filing and assessment is usually a matter of weeks. The delays that actually occur are upstream: a band problem found late, a missing Saudi applicant, or radio reports that cover a different regional setting from the one being shipped.

Does the approval have to appear on the product?

The approval is reflected on the device or its packaging as the rules require, and it is checked at the port and in the market afterwards. Because it affects artwork and tooling, the marking requirement is settled before the production run rather than after approval is granted.

Check the bands before you build for this market

Send the frequency bands, the declared power and the radio module details. We check them against the Saudi position, tell you which existing reports are usable, and scope the conformity file that has to run alongside.