SASO Tightens Cooling Tower Test Proof for Saber

On June 23, 2026, Saudi Arabia’s Standards, Metrology and Quality Organization (SASO) revised the cooling tower registration guidance on the SABER platform, shifting the compliance focus from calculated performance claims to measured thermal-loss evidence. For cooling tower exporters, manufacturers, certification teams, laboratories, distributors, and buyers tied to the Saudi market, the update is worth close attention because it changes what documentation is acceptable, compresses compliance timing, and also affects certificates that were already approved.

What the revised Saber guidance now requires

According to the provided information, SASO made an urgent revision on June 23, 2026 to the SABER platform guidance for cooling tower product registration.

From July 1, all newly declared cooling towers must be supported by measured full-load and part-load thermal-loss test reports completed under EN 13859-2:2025.

The requirement also states that third-party laboratory raw data must be included. Simulation-based calculation is no longer accepted as a substitute.

For certificates that had already been approved before this revision, supplementary documentation must be submitted by September 30. If that is not completed by the deadline, the certificate will automatically become invalid.

Where the pressure is likely to appear first

Export and market-access teams face a documentation reset

From an industry perspective, companies selling cooling towers into Saudi Arabia may be affected first at the registration stage. The immediate issue is not only whether a product can be filed, but whether the filing package now contains measured reports that match the new rule and include third-party laboratory raw data.

Manufacturers may see compliance work move closer to testing capacity

Analysis shows that the operational impact for manufacturers is likely to center on product qualification, technical file preparation, and submission timing. Where a company previously relied on simulation output for part of its evidence set, that route is no longer available under the updated guidance described in the input.

Certification and supply-chain coordinators need to track existing approvals

Observably, the update does not apply only to future registrations. Because previously approved certificates must be supplemented by September 30 or they lapse automatically, compliance managers, distributors, and supply-chain service providers may need to review active certificates, identify affected models, and check whether the required test package is already available.

Buyers and project-side stakeholders may need earlier document checks

For procurement teams and downstream users connected to Saudi-bound cooling tower deliveries, the practical concern may be document validity at the point of ordering or shipment planning. What deserves closer attention is whether the seller’s approval status remains valid under the revised timeline, especially where existing certificates are part of the commercial assumption.

What companies should watch now

Separate confirmed rules from internal assumptions

Companies should anchor their next steps in the confirmed elements of the update: the June 23 revision date, the July 1 start for new declarations, the EN 13859-2:2025 full-load and part-load measured report requirement, the inclusion of third-party laboratory raw data, and the September 30 deadline for previously approved certificates. Any broader reading should be treated as analysis rather than settled fact.

Review whether existing files rely on simulation evidence

Analysis shows that one practical checkpoint is the evidence structure inside current registration files and product dossiers. If any submission logic depends on simulation replacing measured thermal-loss data, that approach is no longer aligned with the rule described in the provided summary.

Check certificate portfolios against the September deadline

For businesses already holding approved certificates, the urgent issue is timeline control. The update indicates that supplementary submission is required before September 30, otherwise the certificate becomes invalid automatically. That makes portfolio screening and document-gap identification a priority area.

Align customer communication with document readiness

Observably, commercial teams may need to coordinate more closely with technical and compliance functions. Where Saudi deliveries, quotations, renewals, or registration planning are underway, customer-facing communication should reflect the actual status of test reports and raw data availability rather than legacy assumptions about accepted evidence.

Why this reads as more than a routine filing change

As an editorial observation, this update is better understood as a compliance-evidence shift rather than a simple wording adjustment. The core change in the provided information is the move away from simulation as an acceptable substitute and toward measured performance data with third-party laboratory raw records.

It is also more appropriate to understand this as an active market-access development with immediate deadlines, not only a long-term policy signal. At the same time, any broader conclusions about enforcement intensity, market scale, or commercial outcomes would require further verified information and should remain under observation.

How to interpret the update at this stage

At this stage, the most balanced reading is that SASO has introduced a tighter proof standard for cooling tower registration on SABER, with direct implications for both new applications and existing approvals. The confirmed facts point to a near-term compliance adjustment, while the wider business impact still depends on how companies, laboratories, and filing teams respond within the stated deadlines.

In that sense, this is best treated as an immediate operational change with broader signaling value, rather than as a fully settled indicator of longer-term market outcomes.

Basis of this article and points for continued verification

This article is based on the user-provided news title, event date, and event summary. For this type of development, source categories typically relevant to verification may include official notices, platform guidance updates, company disclosures, industry association information, authoritative media reporting, and standard-related documentation.

A specific official source link was not provided in the input, so the underlying wording and any subsequent clarifications still need continued verification. What deserves closer attention going forward is whether additional official explanations, implementation notes, or further adjustments to filing practice are issued after the stated deadlines and requirement change.