Saudi Arabia’s SABER 3.0 Launches AI Pre-Review, Making Independent Website APIs the New Certification Requirement

On August 16, the Saudi Standards, Metrology and Quality Organization launched the SABER 3.0 system and added a large language model-based AI pre-review function to the certification process. According to the information disclosed so far, the independent websites of all Chinese suppliers applying for SABER certification must provide structured product data to SASO in real time via a RESTful API. The fields include material, voltage, energy efficiency rating, country-of-origin code, and a total of 17 items. For cross-border sellers and foreign trade suppliers, this means that certification preparation is shifting beyond document submission toward data interface capabilities and website system standardization.

The most direct impact of this change is that whether a structured product data API is available is no longer merely a technical issue, but also an issue affecting certification efficiency. Websites without an open API will not be directly excluded from the certification process, but they will trigger manual review, extending the certification period to 21 working days. For companies that rely on certification timelines to arrange shipments, product launches, or channel integration, the time cost itself may become a source of operational pressure.

Behind AI Pre-Review, Certification Audits Are Shifting Toward Machine-Readable Data

Based on the current information, the newly added AI pre-review module in SABER 3.0 is not simply the introduction of an automated tool. More importantly, it is driving product information to shift from being “visible on a page” to being “readable by systems.” The requirement to provide fields such as material, voltage, energy efficiency rating, and country-of-origin code in a structured format and in real time indicates that the review logic is becoming more dependent on standardized, comparable, and callable data interfaces, rather than relying solely on manual reviews of website descriptions or scattered documents.

Such changes generally raise the requirements for information consistency. For independent website operators, if inconsistent field naming, unsynchronized content updates, or non-standard specification descriptions have long existed among product detail pages, backend product databases, and certification application materials, these issues may be more likely to be exposed in an AI pre-review environment.

The Impact Extends Beyond the Website Department

At first glance, the new requirement concerns whether an independent website has RESTful API capabilities, but in practice, the affected areas are not limited to the technical team. Product information maintenance, compliance applications, website architecture, and product data governance may all become part of the same workflow.

For Chinese suppliers, three points may be particularly important to monitor in the short term: first, whether the existing independent website has already accumulated structured product fields that can be called; second, whether the 17 fields have stable and consistent definitions across the website; and third, whether the data can be provided in real time rather than being compiled temporarily. If a company still mainly relies on manually organizing spreadsheets, supplementing parameters on a temporary basis, or preparing certification materials in batches, its internal coordination costs may increase under the new mechanism.

Certification Timelines May Begin to Diverge

Websites without an open API will undergo manual review, extending the certification period to 21 working days. This means that certification timelines may diverge more noticeably among different companies. Suppliers that already have a relatively complete product data system and can output standardized fields through an interface should, in theory, be better adapted to the new review method. By contrast, companies with scattered basic data and disconnected website systems and compliance processes may face disadvantages in scheduling and procedures in the short term.

However, based on the information itself, it is still necessary to continue observing the stability of AI pre-review in actual operation, as well as how the 17 fields will be further defined during implementation. The public information worth monitoring in the future mainly includes further explanations from regulatory authorities, platform rule updates, and feedback from companies during actual applications.

Based on the information currently available, it can be determined that this adjustment to SABER 3.0 has moved “product information structuring” and “interface availability” higher on the agenda. For Chinese suppliers applying for certification for the Saudi market, the next priority may no longer be merely completing the application materials, but first organizing product data into a format that can be continuously called and verified by systems.

This article was generated based on the information provided in the stated source materials. Specific implementation requirements should still be subject to relevant official announcements and subsequent public rule explanations.