SABER DESKSaber Desk · Free article
CST type approval for wireless devices — the complete path
Who needs CST approval
The Communications, Space & Technology Commission (CST) regulates every device that talks over radio or connects to telecom networks in Saudi Arabia. If your product transmits — Wi-Fi, Bluetooth, cellular, NFC, LoRa, GPS-assisted trackers, any IoT radio — it needs CST type approval before it can be legally imported. That covers the obvious categories (phones, tablets, routers, access points) and the less obvious ones: smart-home sensors, wireless headphones, POS terminals, drones' radio modules, laptops and smart TVs with Wi-Fi cards.
The governing text is the Saudi Technical Regulation for Communication and Information Technology Devices, applied through CST's equipment-licensing services. Wired-only electronics with no radio and no telecom-network connection sit outside CST's scope — their path runs through SASO's regulations only.
One firm boundary that surprises people: since May 2022, individuals cannot self-import private wireless devices — CST licensing applies even to personal shipments. The non-commercial routes described on the platforms do not bypass it.
Why it comes before SABER
For wireless electronics, CST type approval is a prerequisite of the Product Certificate of Conformity (PCoC): the Certification Body reviewing your SABER technical file expects the CST approval to already exist. Importers who start at the SABER account and discover CST later stall the PCoC application with a shipment date already moving — and a CST approval cannot be compressed once the goods are at the port.
The practical rule from the two-certificate path: map every prerequisite at the classification stage, from the HS code, and run the tracks in parallel. CST is usually the longest prerequisite track for a wireless product.
The path, step by step
- Confirm scope. Establish from the product's radio bill of materials whether it transmits, on which bands, at what power. Anything with an RF module is in scope.
- Assemble the technical file. RF test reports against the applicable standards (and safety/EMC where required), product specifications and photos, the declaration of conformity. Reports come from recognized labs — on-site Saudi testing is generally not required for type approval.
- Apply through CST's electronic services. The application is filed by the Saudi-registered entity (a valid Commercial Registration behind the account). CST's own service listing describes the compliance-verification service as electronic and free of service fees; the costs sit in the testing and in any category-specific licensing.
- Respond to technical queries. The reviewer may ask for band plans, power tables or additional reports — the completeness of the RF file is the real variable.
- Receive the approval and carry it into SABER. The approval is what the Certification Body checks before issuing the PCoC — and during 2026, CST-linked conformity certificates have been moving into the SABER flow itself (see below).
Realistic timing
A CST type approval typically runs about 3–4 weeks in practice. Compliance-service firms report a wider observed range — roughly 2 to 8 weeks depending on the device category and how clean the RF file is. Neither figure is an official service commitment, so plan on the longer end and start CST first among your prerequisite tracks: on the full from-zero timeline for a wireless product (7–12 weeks before the vessel on practice figures), CST is usually the critical path.
Validity and renewal
Published guidance on validity is inconsistent — sources cite one year for some categories and up to two for others. The honest planning rule: treat the validity as typically 1–2 years depending on device category, and confirm the exact term at application. Put the expiry in the same shared calendar as your PCoC renewals; an expired type approval resurfaces as a stalled PCoC renewal at the worst possible time. Hardware changes that touch the radio (new module, new bands, higher power) need re-approval even inside the validity window.
Fees
CST fees vary by device class, and CST's electronic compliance-verification service itself is listed without service fees. The real money is in lab testing — budget for RF, EMC and safety testing through your Certification Body or lab, and remember these are separate from the SABER platform fees (500 SAR + VAT for the PCoC, 350 SAR + VAT per shipment certificate).
2026: the CST–SABER integration
During 2026, CST device-approval workflows have been progressively integrated with the SABER platform: compliance-industry updates describe the CST platform transitioning to SABER under the Technical Regulation for Communications and IT Devices, and SABER's official training channel published a user guide for issuing a CST product certificate of conformity through SABER in August 2026. The substance of the requirement is unchanged — a wireless device still needs its type approval — but the filing route now runs closer to the rest of your SABER work. Confirm the current filing route with your Certification Body at application time; this page states the integration as the direction of travel, not a completed migration.
The mistakes that cost weeks
- Discovering CST at the PCoC stage. The classic sequencing failure — trap 6 of the seven customs traps.
- Assuming a CE/FCC file is enough. International reports help, but the approval is Saudi-specific; band allocations and power limits differ.
- Changing the radio module mid-production. A "same product" with a different RF module is a different approval.
- Letting the approval expire quietly. It blocks the next PCoC renewal, which blocks every shipment behind it.
Frequently asked questions
My device has Bluetooth only — does it still need CST approval?
Yes. Any RF transmitter is in scope, including Bluetooth-only audio devices and BLE sensors.
Does a wired-only product need CST?
No — a product with no radio and no telecom-network connection sits outside CST's scope. Its Saudi path is SASO's regulations (and prerequisites like RoHS or energy efficiency where applicable).
Can I import first and get the approval later?
No. The approval must exist before import — and since January 2025 the SABER certificates that depend on it must exist before arrival, with no post-arrival catch-up lane.
Who files the application — my factory or my Saudi entity?
The application is filed by the Saudi-registered entity holding the Commercial Registration. Your factory supplies the RF test reports and technical documentation.
How does CST approval relate to the PCoC?
It is a prerequisite: the Certification Body expects the type approval to exist before it issues the Product Certificate of Conformity — and every shipment then needs its own Shipment Certificate. The two-certificate mechanics are covered in PCoC vs SCoC, explained.
Go deeper, in both languages
The free sample covers the prerequisite stack, PCoC basics and 3 of the 7 traps — one English PDF and one Arabic PDF. The full Compliance Guide has the whole enforced path, every fee and timeline, all 7 traps with fixes, the invoice-matching checklist and a first-year budget worksheet.
Saber Desk is an independent reference — not a certification body, and not affiliated with SASO. We do not issue certificates. Fees and processing times are the official figures published on saber.sa unless marked as observed practice; confirm HS codes and required standards for a specific shipment with your Certification Body. Edition: August 2026.