Saudi SASO / SABER Market Access Pages on Changzhou Manufacturer Websites: How Should They Be Accepted?

Direct answer: Saudi Arabia is not "CE/IEC report is enough". Products subject to Saudi technical regulations must complete product registration, a Product Certificate (PC) and a Shipment Certificate (SC) for each shipment through SABER, the platform supervised by SASO. A PC is usually reviewed by a SASO-accepted conformity assessment body (CAB); at the time of review the platform showed a one-year validity, 5–6 working days and SAR 500 (excluding VAT). An SC is used for a commercial import shipment; the platform showed 90 days, 1–2 working days and SAR 350 (excluding VAT). From 1 October 2026, 10 technical regulations require the supplier's name (importer or local manufacturer) and commercial registration number on the product; the SC validity has been extended from 60 to 90 days; from 1 May 2026 some ICT products have a unified charging-port requirement. The website page should state product/HS/technical regulation, registration, PC/SC, labelling, changes and records—not "SABER = customs clearance guaranteed". Information is current to 2026-11-06. This is a review of public rules and page practice, not legal, certification, testing or customs advice; the latest SABER/SASO rules, technical regulations, CAB and contract control.

This guide is for export, quality, regulatory, procurement and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas. SABER pages most often miss product/HS/technical regulation, product registration, the PC/SC distinction, the 2026 labelling changes and shipment consistency, leaving only "we have SABER".

How does this page relate to CE, IEC, GCC and Korea KC pages?

The Saudi SASO/SABER page answers "is the product subject to a technical regulation, how to register, how to obtain PC/SC, and what to put on the label"; the CE page answers EU regulation/DoC; an IEC/CB report is one piece of test evidence but not a SABER PC; GCC is a Gulf-level conformity mark/system, while each member state/product may still have national requirements; the Korea KC page answers Korean safety certification/confirmation/supplier conformity; the Japan PSE page answers DENAN; the India BIS page answers ISI/CRS. Saudi Arabia cannot be covered by CE/KC.

Common breakpoints: treating SABER as one certificate; product registration treated as PC; PC treated as each shipment's SC; SC still written as 60 days; missing the 1 October 2026 label requirement; wrong HS/TR mapping; unclear PC model coverage; incomplete CAB technical file; label without supplier name/CR; invoice/packing list not matching SC. Separate "product—HS/TR—registration—PC—SC—label—shipment"; then export, quality, regulatory and the forwarder share one playbook.

This page map is editorial; SABER/SASO, technical regulations and the contract control.

What is SABER, and who uses it?

According to SABER, it is an electronic platform under the Saudi Product Safety Programme, supervised by SASO, that helps beneficiaries register their establishments/products (imported or locally manufactured) and obtain the required certificates. Users include individuals, importers, local factories and government entities; commercial imports are mainly handled by importers/local factories, while individuals have a separate shipment-certificate service for personal use that cannot be used for commercial sale. The platform is available 24/7; each service has its own processing time, fee and validity.

Acceptance checks: who registers; who holds the PC; who applies for the SC; importer/local factory; commercial vs personal use; service type; account permissions. Common gaps: personal use treated as commercial import; trader without an importer account; factory/importer responsibility unclear; account entity inconsistent with invoice/label.

Roles/services follow SABER's platform description; the service pages control.

How should product registration be accepted?

According to SABER's product registration service, an importer/local factory logs in, selects "add new product", enters the HS code and product data: product name, country of origin, brand, factory name, product images, model type and model name. At the time of review the platform showed instant processing, free of charge and unlimited validity. Product registration is the basis for a later PC/SC, but it is not a conformity certificate; the HS code and product description must match the technical regulation, invoice and packing list.

Acceptance checks: HS code; product name; country of origin; brand; factory; images; model; registration entity; validity. Common gaps: wrong HS; brand/factory inconsistent with label; incomplete models; images not matching the product; registration entity is not the importer; product registration treated as a PC.

Product registration follows SABER's service page; at review it showed instant, free and unlimited validity; the platform controls.

How should the PC (Product Certificate) be accepted?

According to SABER's "register product conformity certificate" service, an importer/local factory logs in, selects the service, adds model numbers and submits through a SASO-accepted CAB; the CAB reviews the technical file and registers the PC. Requirements include product registration, model numbers and a technical file per the technical regulation/product type. At the time of review the platform showed one-year validity, 5–6 working days and SAR 500 (excluding VAT). A PC covers the registered model/product scope; it is not "one certificate for all products" and not a per-shipment certificate.

Acceptance checks: product registration; models; CAB acceptance; technical file; test reports; PC number/validity; covered models; correspondence with the SC. Common gaps: no product registration; incomplete models; CAB outside its scope; missing technical file; expired PC; PC models not matching the SC.

PC follows SABER's service page; at review it showed one year, 5–6 working days and SAR 500 (excluding VAT); the platform/CAB control.

How should the SC (Shipment Certificate) be accepted?

According to SABER's commercial-import shipment-certificate service, an importer logs in, selects the SC service, selects products, fills in the shipment data and submits; a technical team reviews and issues the SC. Requirements include product registration and a PC or self-declaration (for products not subject to a technical regulation). At the time of review the platform showed 90-day validity, 1–2 working days and SAR 350 (excluding VAT). SABER's homepage notice says the SC validity has been extended from 60 to 90 days. An SC is a per-shipment certificate, not a substitute for a PC; invoice, packing list, bill of lading and SC should match on product/model/quantity/value.

Acceptance checks: product registration; PC/self-declaration; shipment; invoice/packing list; SC number/90-day validity; product/model/quantity/value; customs use. Common gaps: still using 60 days; SC not matching the invoice shipment; expired PC; self-declaration used for a TR product; quantity/value mismatch; one SC for multiple shipments.

SC follows SABER's service page and homepage notice; at review it showed 90 days, 1–2 working days and SAR 350 (excluding VAT); the platform controls.

How do technical regulations, HS codes and CABs map?

SABER defines a technical regulation as a document approved by the board that sets product characteristics, related processes and production methods; the HS code classifies the product and determines customs duty; a CAB is a body accepted by SASO to carry out conformity assessment. A product must first be checked for whether it is subject to a technical regulation, which TR applies, whether the HS code is within scope, and then a CAB and technical file are selected. SABER's homepage notice of 2 November 2026 says some customs codes will become subject to technical regulations within 30 days; the platform's updated list controls.

Acceptance checks: product/TR; HS; CAB scope; technical file; test standard; exemption/non-regulated; update date. Common gaps: HS not matching TR; a non-regulated product given a PC; CAB without the product scope; wrong standard in the technical file; customs-code update not followed.

TR/HS/CAB follow SABER's description and platform notices; the latest TR, HS list and CAB scope control.

How should the 1 October 2026 labelling requirement be accepted?

SABER's homepage notice states that from 1 October 2026, for 10 technical regulations, the supplier's name (importer or local manufacturer) and commercial registration number (CR) must be marked on the product as part of the explanatory data. The page should state which TR, which product, label location, language/format, supplier name/CR, and consistency with registration/PC/SC. This is not optional information; it is a 2026 labelling requirement. The exact list of 10 TRs and format details follow the SABER notice/technical regulations.

Acceptance checks: applicable TR; supplier name; CR; label location; language/format; consistency with registration/PC/invoice; old-label stock. Common gaps: only the manufacturer, not the importer; missing/wrong CR; label on the packaging but not the product; 10 TRs not checked; old labels still used; label entity inconsistent with registration.

Labelling follows SABER's 1 October 2026 homepage notice; the 10 TR list and format follow the notice/technical regulations.

What other 2026 changes should be tracked?

SABER's homepage also lists: the SC validity has been extended from 60 to 90 days; from 1 May 2026, digital cameras, e-readers, speakers, keyboards, mice, portable navigation devices, portable speakers and wireless routers must meet a unified charging-port requirement under SASO IEC 62680-1-2:2023 and SASO IEC 62680-1-3:2023; SASO 3114:2026 updates the standard in Annex 1 of the ICT/telecom technical regulation; a 2 November 2026 notice says some customs codes will become subject to technical regulations within 30 days. The page should state product scope/standard/effective date/old stock/supplementary testing, not old standards or validity.

Acceptance checks: charging-port product scope; standard version; test report; SASO 3114:2026; HS update; SC 90 days; old stock/certificates. Common gaps: still writing 60 days; old charging-port standard; ICT product not updated; HS update not followed; old test report reused.

Changes follow SABER homepage notices; the scope/standard/effective date follow the platform and technical regulations.

How should records and shipment consistency be accepted?

The SABER page should support traceability from "product registration—PC—SC—invoice/packing list/BL—label—customs". Keep at least: product registration, PC (number/validity/models), SC (number/validity/shipment), technical file/test reports, CAB review record, invoice/packing list/BL, label artwork, CR/supplier information, and change/update records. SC is per shipment, PC is one year; they cannot substitute for each other, and one document set cannot cover every shipment.

Acceptance checks: registration; PC; SC; technical file; CAB; documents; label; CR; changes. Common gaps: expired PC; SC shipment mismatch; invoice/packing/SC quantity/value mismatch; label without CR; missing technical file; missing CAB record; change not updated.

Records/consistency are editorial; retention and document requirements follow the platform, SASO and contract.

How should responsibility and evidence be split?

SABER places importers/local factories at the operating position; the CAB reviews the PC technical file; SASO supervises the platform and technical regulations; the forwarder/customs broker uses the SC for clearance but does not replace the importer's/factory's compliance responsibility. The page should state who registers, who holds the PC, who applies for the SC, who provides the technical file, who applies the label and who handles changes—not "the forwarder guarantees clearance / the certification body does everything".

Acceptance checks: importer; local factory; CAB; SASO; forwarder; label responsibility; change notice. Common gaps: all responsibility pushed to the forwarder; CAB assumed to handle labelling; importer/factory entity mismatch; no owner for changes; missing SC discovered at customs.

The responsibility matrix is editorial; SABER/SASO, the CAB and the contract control.

How should the SASO/SABER page be written?

Suggested content: (1) product/HS/technical regulation; (2) importer/local factory/CR; (3) product registration (fields/status); (4) PC (CAB, technical file, models, one year, number); (5) SC (shipment, 90 days, documents); (6) label (supplier name/CR, from 1 October 2026 for 10 TRs); (7) 2026 changes (charging port, SASO 3114, HS update); (8) records/traceability; (9) contact/version/update date. The public page explains rules, routes, evidence types and capability; it should not publish customer data, full technical files or prices; do not write "SABER = customs clearance guaranteed / one certificate for everything".

Use consistent English terms (SABER, SASO, technical regulation, product registration, Product Certificate (PC), Shipment Certificate (SC), conformity assessment body (CAB), commercial registration (CR), HS code) and state the review date. Link to the CE, IEC/CB, GCC and Korea KC pages, but do not present CE/KC as SABER.

This structure is editorial; external statements must be truthful and verifiable, per SABER/SASO, the CAB and the contract.

What must not be written?

High-risk claims: "SABER certification = one certificate" (product registration/PC/SC are three things); "PC can serve as each shipment's SC" (SC is per shipment); "SC validity is 60 days" (extended to 90 days in 2026); "product registration is the PC" (registration is only the basis); "one PC covers all models" (model scope is limited); "CE/IEC report is enough to sell" (TR/PC/SC are still needed); "the 1 October 2026 label can be ignored" (10 TRs require supplier name/CR); "SABER = customs clearance guaranteed" (the forwarder/broker does not replace compliance); "old standards/reports can be used forever" (charging port/SASO 3114/HS change). These are inaccurate or misstate the stage, scope or responsibility.

Safer wording: "This product HS [code] is subject to [TR]; importer [name/CR] has completed product registration; PC [number/validity/models]; SC [number/90 days/shipment]; label includes supplier name/CR [location]; 2026 changes [charging port/SASO 3114/HS] assessed; records [list]. SABER/SASO, the CAB and the contract control." External promotion must comply with advertising and fair-competition rules; customer/price/technical files need authorisation or redaction.

Go-live acceptance checklist

Ten checks: product/HS/TR, entity/CR, product registration, PC, SC, label, 2026 changes, records/documents, responsibility, page wording/date. Each needs an owner, evidence and review date. The pass condition is not "the page says SABER", but that a customer or internal team can find registration, PC, SC, label and shipment evidence.

Before go-live, run one real export model through: TR → HS → entity/CR → product registration → PC → SC → label → 2026 changes → records → page wording. Any step that fails is a gap in the page or compliance.

This checklist is editorial; SABER/SASO, the CAB and the contract control.

Who should read this, who should not, and what decisions does it support?

It suits export, quality, regulatory, procurement and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas; also companies doing Saudi SABER for the first time, or facing PC expiry, SC shipment mismatch, the 2026 label/charging-port changes, or customer requests to update. It does not suit domestic-only sellers, products outside Saudi TR scope, or teams wanting one page to replace testing/CAB/customs/legal advice.

Read it if you export to Saudi Arabia; the product is subject to a TR; product registration/PC/SC are unclear; the PC is expiring; the SC shipment does not match; the 1 October 2026 label/charging-port changes apply. Skip it if you treat SABER as one certificate, PC as SC, still write 60 days, or want the page to guarantee customs clearance. It supports self-review of product/HS/TR, entity/CR, product registration, PC, SC, label, 2026 changes, records and responsibility.

FAQ

What is the relationship between SABER and SASO?

SASO is the Saudi Standards, Metrology and Quality Organization, responsible for technical regulations/standards and supervision; SABER is the electronic platform under the Saudi Product Safety Programme, supervised by SASO, used to register establishments/products and obtain PC/SC. Exporters usually operate on SABER, while technical regulations and CAB acceptance remain SASO's.

What is the difference between product registration, PC and SC?

Product registration records the HS code, product and model data (at review: free, instant, unlimited validity); PC is the Product Certificate (reviewed by a CAB, one year at review); SC is the Shipment Certificate for each shipment (90 days at review). Product registration is the basis for PC/SC and cannot replace either.

What are the PC validity, fee and processing time?

At the time of review SABER's service page showed one-year validity, 5–6 working days and SAR 500 (excluding VAT). The platform/CAB's latest fee and timing control; a PC covers the registered model scope, not every product.

Is the SC validity 60 or 90 days?

In 2026 SABER's homepage notice says the shipment-certificate validity has been extended from 60 to 90 days; the service page at review also showed 90 days, 1–2 working days and SAR 350 (excluding VAT). Old materials saying 60 days should be updated.

What is the 1 October 2026 labelling requirement?

SABER's homepage notice states that from 1 October 2026, 10 technical regulations require the supplier's name (importer or local manufacturer) and commercial registration number (CR) on the product as part of the explanatory data. The exact 10 TR list, location, language and format follow the SABER notice and technical regulations.

What other changes are there in 2026?

SABER's homepage also lists: from 1 May 2026, some ICT products (digital cameras, e-readers, speakers, keyboards, mice, portable navigation, portable speakers, wireless routers) need a unified charging port under SASO IEC 62680-1-2:2023 and -1-3:2023; SASO 3114:2026 updates the ICT/telecom TR annex; a 2 November 2026 notice says some HS codes will become subject to TRs within 30 days. The platform/TR control the scope.

One-sentence takeaway

A Changzhou manufacturer's Saudi SASO/SABER page is not about "we have SABER". It should turn product/HS/TR, entity/CR, product registration, PC, SC, the 2026 label/charging-port changes, records and responsibility into a reviewable checklist—so a customer or internal team can find registration, PC, SC, label and shipment evidence.

Method and limitations

This is a review of public rules and page practice, not an audit, certification, testing or customs opinion on any company, product or certificate. No undisclosed customer, price, certificate or test data were used. Processes, fees/timing, tables and acceptance items are editorial; the latest SABER/SASO pages, technical regulations, CAB and contract control. Fees, processing times and validity shown on SABER service pages are as displayed at review and may change; the scope of 2026 notices follows the platform text.

Sources and scope

Information is current to 2026-11-06. The following are official SABER pages; their text controls.

1. SABER homepage (2026 notices: supplier name/CR label, SC 90 days, unified charging port, SASO 3114:2026, HS update): saber.sa.
2. SABER "About SABER" (platform positioning/SASO supervision/product registration and certificates): SABER About.
3. SABER product registration service (HS/product data/free/instant/unlimited validity): SABER Product Registration.
4. SABER Product Certificate (PC) service (CAB/models/technical file/one year/5–6 working days/SAR 500): SABER PC.
5. SABER commercial-import Shipment Certificate (SC) service (product registration + PC/self-declaration/90 days/1–2 working days/SAR 350): SABER SC.