Saudi CST and SASO Approval Planning for Android Devices

Two tracks, one shipment

Saudi Arabia splits device market entry across two tracks that must both be satisfied for one shipment: CST covers telecom equipment licensing and compliance, while SASO’s technical regulations and the Saber platform govern broader product conformity and import clearance keyed to HS codes. A telecom-ready model can still be held up by a missing conformity certificate covering the charger, battery or packaging scope, so the two tracks need to be planned together rather than discovered sequentially. The importer or local representative role is structural here — Saber workflows are driven by the party bringing the product in, not by the overseas factory. Programs that span more than one Gulf market are scoped in device programs across the GCC.

Takeaway. Plan CST and SASO/Saber as two tracks that join at shipment. Each step’s time is still to be confirmed.

Takeaway. Both tracks apply only to the HS code, device, and accessories in scope. CST, Saber, the lab, and the importer are separate confirmations. This page does not publish a 2–8 week band.

What this guide is and is not

This guide helps buyers prepare a device brief before formal approval work begins. It is not legal advice, not an authority filing and not a promise of approval. The useful output is a model-to-market evidence pack: exact model, radios, test reports, certificate holder, importer role, labels, manuals and known limitations.

CST and SASO official checkpoint

Two official checkpoints anchor this guide: CST equipment licensing for the telecom track, SASO for technical regulations, and the Saber conformity platform for the product and import track. Open the current regulation entry for the HS code you are assuming; this guide does not freeze an HS range. Verify the certificate-of-conformity workflow with the importer before quoting, because telecom, EMC, electrical safety, charger, and packaging rules are checked together at import. A charger, battery, or accessory is in scope only when its own rule says so.

Saudi ICT equipment licensing and conformity planning process map

The Saudi sequence is best planned backwards from the shipment: what will customs and Saber expect, which certificates must exist by then, and which CST evidence supports them. The rows below order that into a forward path from classification to shipment handoff.

Send a redacted brief. We reply within 1 business day.

Spectrum and network considerations

Saudi operators have deployed 5G extensively in cities alongside wide 4G coverage, while connectivity at industrial and remote sites should be validated per deployment rather than assumed. Radio-variant fit is a model-selection decision: confirm the exact variant’s band support against the target operator’s published information for the regions where the fleet will run. Use CST as the reference for current spectrum and equipment rules, and log any unresolved connectivity dependency in the known limitations record before batch staging.

Planning ranges and cost checkpoints

This guide does not state a week count. Each CST step and each SASO/Saber step still needs its own time confirmation from the party who runs it. New lab work, a missing conformity certificate, or importer registration can change that time. Confirm fees with CST and with the importer on Saber before quotation.

How Vantora prepares the device packet

Vantora does not replace the local applicant, authority, importer or accredited lab. We help prepare the build evidence those parties need: model/variant, radio list, OS and firmware note, app and policy state, photos, label/packaging assumptions, sample acceptance result and known limitations. The same packet feeds market-specific testing, customs or shipment release review. The capability behind it, including how test houses, certificate holders and importer roles are coordinated, is described in testing and certification.

The rest of the certification series

Device programs rarely stop at one market, and the sequencing between markets is usually what decides the schedule: approvals that can run in parallel, evidence that can be reused across filings, and the one market whose lead time sets the shipment date. The companion guides cover ANATEL homologation in Brazil, CRT homologation in Mexico, TDRA type approval in the UAE, NTRA type approval in Egypt, SDPPI certification in Indonesia. Read them together when a single build is destined for more than one market — the model identity, radio list, label artwork and test reports are largely shared inputs, while the applicant, certificate holder and local representative are usually not, and it is the second set that determines who can file at all. Where the same build serves several markets, record the union of their requirements in the device build spec and keep unresolved market questions in the known limitations library rather than resolving them optimistically at quotation time.