SABER and SASO Conformity: Product Registration and the Data Behind It
PCoC certifies the product, SCoC the consignment. Validity, fees, the technical file, and the item-master data that stops the wrong certificate shipping.
SABER and SASO Conformity: Product Registration and the Data Behind It
SABER is the SASO platform on which products entering the Saudi market are registered. Regulated products need a Product Certificate of Conformity from an accepted conformity assessment body, valid one year. Every consignment then needs a Shipment Certificate, valid 60 days, issued before the customs declaration. One certifies the product, the other certifies the consignment.
This is for plant and production managers whose products ship into or inside Saudi Arabia and who own the consequence when a container sits at the border. After reading it you should be able to say which certificate applies to each item, what the conformity assessment body will ask for, and which fields must exist in your item master before a hundred variants become unmanageable. The certificate mechanics are documented; the part that actually breaks is not, being the relationship between a certificate and a specific model number when the production catalogue changes faster than the certificates do.
What SABER is, and the two certificates it issues
SABER is "an electronic platform that facilitates the user's journey in product registration, conformity certificates, and shipment certificates", supervised by the Saudi Standards, Metrology and Quality Organization (SASO). It serves importers, local manufacturers, individuals and government entities across three paths: commercial products, products not intended for consumer display, and vehicle importation.
Most confusion traces back to treating the two certificates as one document.
The Product Certificate of Conformity (PCoC on SABER, registered as a "product conformity certificate") attaches to a product and its model numbers: this design, with these models, meets the applicable Saudi technical regulation. It is issued by an accepted conformity assessment body and, per SABER's service pages for both importers and local factories, is valid for one year at a fee of 500 SAR excluding VAT, with a service duration of five to six business days.
The Shipment Certificate (SCoC) attaches to a consignment: this container, against these invoices, holds these quantities of models covered by a valid product certificate or self-declaration. SABER states a validity of 60 days, a fee of 350 SAR excluding VAT and a service duration of five business days.
They answer different questions. The product certificate answers "is this design compliant". The shipment certificate answers "is what is physically in this container the thing that was certified". A product certificate alone does not get goods across the border, and a shipment certificate cannot be issued for a regulated product without one behind it.
| Certificate | Scope | Validity | What triggers a new one |
|---|---|---|---|
| Product Certificate of Conformity (importer) | A registered product and its listed model numbers, regulated products | One year | Expiry; a new model number; a change in the regulation applying to the HS code; a design change affecting the test reports |
| Product conformity certificate (local factory) | Same, for locally manufactured regulated products | One year | As above, plus a change of manufacturing site or process affecting the technical file |
| Importer self-declaration | Imported commercial products not subject to a technical regulation | [NEEDS SOURCE: published validity of the importer self-declaration. The local version states one year.] | Expiry; product moving into a regulated category |
| Local self-declaration | Locally manufactured commercial products not subject to a technical regulation | One year, fee 500 SAR excluding VAT, issued immediately | Expiry; new model numbers; reclassification |
| Shipment Certificate | One consignment, tied to specified invoices, models, quantities and barcodes | 60 days | Every consignment; any change to invoice, quantity or model set after issue |
| Shipment certificate, products not for consumer display | Non-display consignment; requires product data, bill of lading and the imported product invoice | [NEEDS SOURCE: whether the 60-day validity applies here] | Every consignment |
Regulated or not, and how you actually find out
The determination is made by HS code, not by opinion. SABER maps customs tariff codes to SASO technical regulations: enter the code, and the platform returns the regulations that apply and therefore the certification, quality mark or energy efficiency label required. SABER lists 61 technical regulations grouped under textiles, construction materials, mechanics, electrical equipment and chemistry, each published as a PDF.
Two consequences follow. The HS code is a compliance field, not just a customs field. If logistics classifies a product one way and the compliance registration used another, the two records describe different regulatory obligations for the same physical item, which is the most common root cause of a shipment stopped with paperwork that looks complete. And regulated status is not permanent: SASO publishes technical regulations with an approval date, a publication date and a mandatory application date, so a product that was non-regulated last year can need a product certificate this year rather than the self-declaration it has been shipping against. Nobody writes to you about your specific item.
Where no technical regulation applies, the route is a self-declaration: importer self-declaration for imported goods, local self-declaration for locally manufactured goods. The local version requires product registration, model numbers and product photographs, and issues immediately.
Since 1 October 2025 that distinction no longer determines whether you need a shipment certificate. SASO announced that suppliers must issue one before submitting the customs declaration, covering all products "whether subject to technical regulations or not", with the stated aim of raising product reliability and reducing re-export of non-compliant goods into the Saudi market. Non-regulated goods reach it through the self-declaration service; regulated goods through the product certificate and conformity assessment body review.
[NEEDS SOURCE: any transition arrangements, grace period or penalty regime attached to the 1 October 2025 requirement. The SASO announcement sets out the mechanism but states no penalties.]
The conformity assessment body and the technical file
SABER's register lists 115 conformity assessment bodies accepted by SASO to carry out conformity assessment and issue product certificates under Saudi technical regulations. They filter by geographic region and by technical regulation, and both filters matter: a body accepted for low-voltage electrical equipment is not automatically accepted for your product. You select region then office inside the certificate request.
The body works from a technical file whose contents vary by regulation. SASO's Technical Regulation for Glue and Adhesive Materials requires the supplier declaration of conformity in the annexed form, the risk assessment document, the certificate of origin, "the testing reports requested in the technical regulation", the list of specifications applicable to the product, and the product-marking manual where the label cannot be affixed. It sets two assessment routes for different product groups (Type 1A and Type 3, both requiring a certificate from a body accredited by SASO) and requires suppliers to retain documents "for a period of ten (10) years, at least, after placement of the product in the market". Read your own regulation, but plan for those six components, the ten-year retention, and Arabic or bilingual marking.
[NEEDS SOURCE: whether test reports must come from a laboratory with specific accreditation, and whether reports have a maximum age. Requirements are set per technical regulation and were not verified across the set.]
The registration procedure, end to end
Drawn from SABER's own training guides for certificates of conformity and shipment certificates.
- Register the establishment and a facility delegate account on SABER.
- Add the product, classified by its customs tariff code. The platform returns the applicable technical regulations and the route: certificate or self-declaration.
- From "New Request", choose "Product Conformity Certificate Request", then "Product Certificate of Conformity (CoC)". The guide notes that "only the products require the certificate of conformity will be displayed to choose from", so a product missing from the list is a classification problem, not a platform fault.
- Add model numbers, individually or by downloading the Excel template, populating it and uploading it. Every model that will ever ship must appear here.
- Clear any additional requirement first. The guide is explicit: "If the product is required any additional requirement (power efficiency certificate, water consuming) the user will not be able to complete the request until the additional requirement is issued." Discovering this here costs weeks.
- Select a geographic region, then a conformity assessment body office within it, and send the request.
- Once the body accepts, create and pay the invoice (Sadad, Mada, Visa, MasterCard or Apple Pay). Request a tax invoice before payment; once paid, modifications are not possible.
- The status moves to "waiting for conformity assessment body decision". The body reviews the technical file and issues, queries or rejects.
- For the consignment, open "New shipment request". The platform shows regulated products holding a valid certificate and non-regulated products holding self-declarations. Anything absent has no valid cover.
- Enter a shipment reference name, select products (or upload product numbers by Excel), then click "Validate certificates". The status moves from "adding products to the shipment request" to "request ready to complete".
- Add the bill or bills. Multiple invoices can be attached, with products allocated across them, each line carrying a unit and an item price.
- Open "Manage Models" and enter, per model, the quantity and the barcode. This is where the certificate meets the physical consignment, and where mismatches are created.
- Select the country of shipment, accept the commitment and send. The request goes "to the Conformity assessment body who issued the product conformity certificate", and "the certificate will not be issued for the regulated products unless the conformity assessment body approves the request".
- On approval, create the certificate, pay the fee and download it, before the customs declaration is filed.
What happens at the border when the certificate does not match
The timing pressure changed twice in late 2025. SASO requires the shipment certificate to exist before the customs declaration is submitted. Separately, ZATCA made advance submission of the manifest and customs declarations mandatory for goods arriving through sea ports from 29 October 2025, requiring importers, shipping agents and brokers to file the bill of lading, invoices and all necessary approvals before arrival, in support of its "Clearance Within Two Hours" initiative. Together these remove the window teams used to rely on. The specific failures:
- Model number not on the certificate. Production released variant
-Bof an approved item and shipped it; the model list carries only-A. The shipment request will not validate. - HS code mismatch. The declaration classifies the goods under a code whose technical regulation differs from the one the certificate was issued against.
- Quantity or invoice mismatch. Quantities entered under "Manage Models" do not agree with the commercial invoice or packing list. The certificate is bound to specified invoices, so a last-minute part-shipment invalidates it.
- Expired product certificate. The one-year validity lapsed between order confirmation and dispatch, which on a long lead-time item is normal.
- Expired shipment certificate. A certificate issued optimistically at production completion can lapse before a delayed vessel arrives.
- Additional requirement outstanding. An energy efficiency or water consumption certificate was never obtained, so the product certificate request cannot complete.
[NEEDS SOURCE: the specific customs treatment, storage charges and re-export consequences where goods arrive without a valid shipment certificate. SASO's announcement sets the requirement without describing the consequence, and charges are levied by port and customs operators rather than by SASO.]
The master data that makes this survivable at scale
One product with three models is a manual task. Two hundred SKUs across eleven regulations, with variants added quarterly, is a data problem, solved in the item master or not at all.
| Field | Why it exists | What goes wrong without it |
|---|---|---|
| HS code, per item | Determines the applicable regulation and the certification route | Compliance registers one code, the declaration uses another, the shipment stops |
| Regulated flag and regulation reference | Records which of the 61 technical regulations applies | Nobody notices a new regulation captured the item until a shipment fails |
| Model or variant identifier, exactly as registered | The certificate covers listed model numbers, not product families | A new variant ships against a certificate that never named it |
| Certificate type held | PCoC, local certificate, or self-declaration | The wrong SABER path is opened and the request is rejected |
| Certificate number and issuing body | The shipment request routes to the issuing body | Time lost identifying which of 115 bodies holds the file |
| Certificate expiry date | One year for product certificates | Expiry discovered at dispatch rather than at order entry |
| Barcode per model | Entered per model in the shipment request | Transcribed by hand at consignment level under time pressure |
| Additional requirement status | Energy efficiency, water consumption and similar prerequisites | The certificate request cannot complete and the reason is not obvious |
| Technical file location and version | Ten-year retention obligation | The file cannot be reproduced when the body queries a report |
Two rules make the difference. Treat a new model number as a compliance event rather than a catalogue event: item creation should refuse to release a variant of a regulated product until the certificate is extended or the variant is flagged as not shippable to Saudi Arabia. And run certificate expiry against the order book rather than the calendar, so the flag appears when an order is confirmed for a product whose certificate expires before the ship date.
Where teams get this wrong
Treating the product certificate as permanent. One year. Long lead-time production routinely crosses that boundary, and the failure appears at dispatch when there is no time to fix it.
Letting variants outrun the model list. Engineering adds a suffix, production runs it, sales sells it, and nobody tells whoever holds the certificate. The model list is the operative record and it does not update itself.
Registering the HS code once and never again. Classification is revisited when duty rates change and almost never when technical regulations change, even though SASO publishes mandatory application dates well in advance.
Issuing the shipment certificate too early. Sixty days is a real constraint on any route with transhipment or port congestion.
Assuming non-regulated means nothing to do. Since 1 October 2025 a self-declaration and a shipment certificate are still required before the customs declaration.
One person holding the SABER relationship. Delegate account, body relationships and certificate register often sit with one individual, and the process stops when that person is on leave in a shipping week.
What to automate, and what not to
Automate the register and the alerts. Certificate number, type, issuing body, covered model numbers and expiry belong on the item master, with expiry checked at sales order confirmation against the promised ship date, not at picking. Automate the extract that feeds the shipment request too: model, quantity and barcode against invoice lines is data your despatch documents already hold, and rekeying it by hand is where quantity mismatches are born.
Do not automate the classification decision. Deciding which technical regulation captures a borderline product is a judgement with a regulator on the other end, and a mapping table applied blindly will register a product under the wrong regulation with complete confidence. Agree borderline cases with your conformity assessment body, record the reasoning against the item, and re-examine them when a regulation is published rather than when a shipment fails. Do not automate the technical file either: it is a controlled document set with a ten-year retention obligation and it needs a named owner.
FAQ
Do we need both certificates? For regulated products, yes. The product certificate covers the design and its model numbers for one year. The shipment certificate covers one consignment for 60 days and cannot be issued for a regulated product unless the body that issued the product certificate approves the request.
Our product is not covered by any technical regulation. Are we exempt? Not from the shipment certificate. Since 1 October 2025 SASO requires one before the customs declaration for all products, regulated or not. Non-regulated goods route through the self-declaration service instead.
How long does certification take? SABER states five to six business days for the product conformity certificate and five for the shipment certificate. Those are platform service durations and exclude assembling the technical file and obtaining test reports, which dominate the real timeline. Note also that the shipment request routes to the body that issued the product certificate, so changing body in practice means a new product certificate. [NEEDS SOURCE: SABER's rules on transferring a certificate between accepted bodies.]
We shipped a partial quantity. Is the certificate still valid? The shipment certificate is bound to specified invoices, models and quantities. [NEEDS SOURCE: SABER's rules on amending a shipment certificate after issue for a reduced quantity. The guide states that once the bill is paid the tax invoice cannot be modified, but does not address quantity amendment.]
Where a system helps
Everything above resolves to fields on an item and a link between item and certificate: HS code, regulation reference, registered model identifiers, certificate number and expiry, issuing body, barcode by model. Where those live on the item master, the shipment request is an extract from the sales order and the expiry warning fires at order confirmation. Where they live in a compliance spreadsheet maintained alongside the ERP, the two drift, and the drift is invisible until a container is already at sea.
OptiForge carries product, variant, certificate and document references on one item record, and that record drives production, despatch documentation and the export pack. See OptiForge for manufacturing. Certificates are issued by conformity assessment bodies accepted by SASO through SABER, and no software changes that.
Related reading: "What Is Fatoora? Saudi Arabia's E-Invoicing Platform, Explained" (KB-013).
Sources
- SABER platform (SASO), home
- SABER, product conformity certificate registration service, importers
- SABER, product conformity certificate registration service, local factories
- SABER, shipment certificate issuance service
- SABER, local self-declaration certificate service
- SABER, Training Guide for Certificates of Conformity (PDF)
- SABER, Training Guide for Shipment Certificate (PDF)
- SABER, conformity assessment bodies register
- SABER, technical regulations
- SABER, HS codes
- SASO, shipment certificate required before the customs declaration from 1 October 2025
- SASO, Technical Regulation for Glue and Adhesive Materials (PDF)
- SASO, technical regulations index
- SASO, certificates of conformity
- ZATCA, mandatory advance submission of customs declarations for sea ports from 29 October 2025