Time
Click Count
Starting April 16, 2026, Saudi Standards, Metrology and Quality Organization (SASO) will enforce new requirements under SASO IEC 62368-3:2026 for guestroom automation and smart lighting devices entering Gulf Cooperation Council (GCC) markets—particularly impacting manufacturers, exporters, and system integrators supplying to Saudi hotels. This regulatory shift directly affects product compliance, market access, and cloud interoperability, making it critical for stakeholders across the hospitality technology supply chain.
On April 16, 2026, SASO’s updated supplementary clause SASO IEC 62368-3:2026 enters into effect. It mandates that all Guestroom Automation and Smart Lighting equipment intended for the GCC market must ship with pre-installed Arabic-language graphical user interfaces (GUIs) and firmware digitally signed by a SASO-authorized local Certificate Authority (CA). Devices failing to meet both conditions will be denied SASO import registration and barred from connecting to the Saudi National Smart Hotel Cloud Platform (SAUDI-HOTEL CLOUD).
These companies face immediate compliance risk: non-conforming devices cannot clear Saudi customs or obtain mandatory SASO certification. Since SAUDI-HOTEL CLOUD integration is required for many government-aligned hotel tenders and national smart infrastructure programs, exclusion may result in lost contracts—even if hardware otherwise meets safety standards.
Integrators deploying end-to-end room automation solutions must now verify firmware authenticity and UI language support at the device level—not just at the central management platform. Pre-certified CA signatures and Arabic GUIs are no longer optional features; they are embedded prerequisites for system-level acceptance in Saudi projects.
Teams responsible for device firmware must adapt development workflows to accommodate SASO-authorized CA signing pipelines and dual-language (Arabic + English) UI resource bundling. This includes localization QA for right-to-left (RTL) rendering, Arabic text truncation behavior, and context-sensitive date/number formatting—all verified prior to CA signing.
Local agents and conformity assessment bodies assisting foreign suppliers must now validate two distinct technical criteria: (1) presence and functional completeness of Arabic GUI across all user-facing interfaces, and (2) cryptographic validity of the CA signature against SASO’s published root certificate list. Neither criterion can be retrofitted post-import.
While the regulation is effective April 16, 2026, SASO has not yet publicly released its final list of accredited local CAs or detailed technical specifications for Arabic GUI compliance (e.g., font support, RTL behavior, accessibility requirements). Current more appropriate action is to monitor SASO’s official portal and engage certified local representatives for updates—not assume equivalence with existing GCC or ISO localization practices.
Manufacturers should map current product lines against known Saudi hotel procurement channels (e.g., Ministry of Tourism–affiliated properties, NEOM-linked developments). Devices scheduled for shipment to Saudi Arabia after April 16, 2026—including samples, pilot units, or replacement modules—must undergo full Arabic GUI implementation and CA signing before factory release. Delaying this until post-order confirmation risks shipment rejection.
This requirement reflects SASO’s broader push toward digital sovereignty and localized trust infrastructure—not merely language accommodation. Analysis来看, it signals a structural shift where firmware integrity and regional digital identity are becoming non-negotiable entry conditions, separate from traditional safety or EMC testing. Compliance cannot be treated as a documentation add-on; it must be embedded in the software build process.
Engaging a SASO-recognized local representative early enables parallel tracking of CA accreditation status and Arabic UI validation protocols. From industry angle, lead times for CA enrollment and test report issuance are currently unconfirmed but historically range from 4–12 weeks. Starting alignment before year-end 2025 avoids bottlenecks during final pre-compliance verification.
This regulation is better understood as an enforcement milestone—not an isolated rule change. Observation来看, SASO is consolidating control over both human-machine interaction (via mandatory Arabic UI) and machine-machine trust (via local CA signing), effectively creating a dual-gate compliance framework for smart building hardware. It does not replace existing IEC 62368-1 safety requirements but layers new digital governance conditions atop them. The linkage to SAUDI-HOTEL CLOUD further indicates that cloud interoperability is now a de facto regulatory dependency—not a commercial differentiator. Industry needs to track whether similar requirements emerge in other GCC states (e.g., UAE’s ESMA or Qatar’s QMRA), though no such announcements have been confirmed to date.

Conclusion
This update marks a formalization of localization and digital trust expectations for smart hospitality systems in Saudi Arabia. It is neither a temporary pilot nor a narrow labeling requirement—it establishes baseline technical conditions for market participation. Current more appropriate interpretation is that SASO is treating firmware-level language and cryptographic provenance as foundational elements of product conformity, alongside physical safety and electromagnetic compatibility. Stakeholders should treat it as an integrated part of their GCC product roadmap—not a standalone certification task.
Information Sources
Primary source: Saudi Standards, Metrology and Quality Organization (SASO) official announcement of SASO IEC 62368-3:2026, effective April 16, 2026.
Note: SASO’s list of authorized local Certificate Authorities and detailed Arabic GUI technical specifications remain pending publication and are subject to ongoing observation.
Recommended News
Join 50,000+ industry leaders who receive our proprietary market analysis and policy outlooks before they hit the public library.