On June 21, 2026, Saudi Arabia’s Standards, Metrology and Quality Organization (SASO) issued technical bulletin SASO/TB/2026/019, setting a new market-entry requirement for Mobile Credentials systems. From December 1, 2026, products entering the Saudi market must natively support the electronic identity mutual recognition protocol EID-IRP v2.1 under the EU eIDAS 2.0 framework. Because the requirement applies to access control, visitor management, and government service access scenarios, the update deserves close attention from product suppliers, exporters, procurement teams, certification-related service providers, and project delivery parties that rely on SASO SABER approval.

What the bulletin changes in practical terms

The confirmed facts are limited but clear. SASO released technical bulletin SASO/TB/2026/019 on June 21, 2026. The bulletin requires all Mobile Credentials systems entering the Saudi market to provide native support for EID-IRP v2.1 within the eIDAS 2.0 framework starting on December 1, 2026. The stated scope covers access control, visitor management, and government service access use cases. The summary also makes clear that incompatible solutions will not be able to pass SASO SABER certification.

Where pressure is likely to emerge across the chain

Products aimed at Saudi market access

From an industry perspective, companies supplying Mobile Credentials systems to Saudi Arabia may face the most direct compliance pressure because compatibility is tied to SABER certification access. The likely impact is not only on product design, but also on technical specification alignment, pre-delivery compliance review, and whether an offering can remain eligible for import and project acceptance after the December 1, 2026 date.

Export and channel transactions linked to certification timing

Analysis shows that exporters, distributors, and channel partners may need to pay closer attention to the certification status of the solutions they handle. Where contracts, quotations, or shipment plans involve Mobile Credentials for the covered scenarios, the practical issue becomes whether the supplied configuration can meet the new native-support requirement before submission to SASO SABER-related processes.

Procurement and project-side specification management

Buyers, integrators, and project delivery teams involved in access control, visitor management, or government service access deployments may need to review whether technical requirements and bid documents remain aligned with the new rule. What deserves closer attention is the risk of selecting solutions that appear commercially available but later face certification barriers because they are not compatible with the required protocol framework.

Certification and technical documentation workflows

Certification-related service providers and teams responsible for compliance files may also be affected at the documentation stage. Observably, once a requirement is linked to SABER certification, attention typically shifts to how product claims, technical descriptions, and conformity materials are prepared and checked. In this case, the confirmed fact is only that incompatible systems cannot pass certification; the detailed review method is not provided in the input and therefore remains a point for follow-up.

What companies should review now

Check whether product architecture meets the native-support requirement

Companies with Mobile Credentials offerings for Saudi-bound projects should first verify whether their current systems natively support EID-IRP v2.1 under eIDAS 2.0, rather than assuming that partial compatibility or later adaptation will be sufficient. The input does not provide SASO’s detailed testing or interpretation criteria, so this should be treated as a compliance review priority rather than as a settled technical conclusion.

Revisit certification preparation and submission materials

Businesses preparing for SASO SABER-related approval should review whether existing technical files, product descriptions, declarations, and related compliance materials clearly match the new requirement. Analysis shows that gaps at the documentation stage can become a commercial issue when certification eligibility determines whether a product can enter the market.

Review procurement, contract, and delivery schedules

Where shipments or deployments are planned around the December 1, 2026 effective date, procurement and delivery teams may need to reassess timing assumptions. It is more appropriate to understand this as a point of coordination between product readiness, certification planning, and project milestones, especially for covered use cases where a non-compliant configuration could interrupt acceptance or market entry.

Monitor later clarifications and execution language

The input confirms the requirement and effective date, but it does not provide further execution detail. For that reason, companies should keep watching for later official wording, certification interpretation, and how the requirement appears in tender specifications, customer compliance checklists, or certification handling practice. This is a monitoring need, not a confirmed change beyond the bulletin itself.

How this signal should be read at this stage

Observably, this update is more than a general policy direction because it links a specific technical compatibility requirement to a defined effective date and to SASO SABER certification outcomes. At the same time, it should not yet be overstated as a fully mapped execution regime, because the input does not include detailed implementation guidance, review criteria, or market feedback. From an industry perspective, the development is best understood as a concrete compliance signal with immediate relevance for planning, while some operational details still require continued verification.

Why this matters beyond a single notice

The practical significance of this development lies in the fact that a standards-related requirement now directly affects certification access for Mobile Credentials systems entering Saudi Arabia in the covered scenarios. Analysis shows that the issue is not limited to product engineering; it also touches export readiness, procurement screening, technical documentation, and delivery planning. At present, it is more appropriate to view the bulletin as an implemented rule change with clear market-entry implications, while still maintaining a cautious watch on how certification practice and project documents reflect it in the months ahead.

Basis of this article and what still needs verification

This article is generated from the user-provided news title, event date, and event summary. For developments of this type, relevant source categories usually include official notices, regulator releases, trade or customs authority information, industry association updates, standards organization documents, and reporting from authoritative media. No specific official source link was provided in the input, so the exact source document path still needs to be verified on an ongoing basis. Continued attention should also be given to later policy detail, certification interpretation, tender document changes, industry feedback, and how companies implement the requirement in practice.