Assessment — days
Code confirmation, regulation identification and an evidence audit. Fast once the product data is complete.
Seven stages from the HS code check to the shipment certificate. Send your product and model list — we run the application end to end.

Quick Answer
What it is: A seven-stage application that ends in the PCoC, then an SCoC per shipment.
Who needs it: Any exporter shipping regulated products to Saudi Arabia.
Before what: Registration on SABER comes first — the certificate is raised against the product record.
To start an application we need:
The SABER application looks long on paper. In practice it runs in seven stages, and most of the time sits in only two of them: testing and review.
This page walks through all seven stages, then shows what speeds them up and what slows them down.

Follow them in order. The first two decide everything downstream, and no care later recovers a wrong answer there.
Confirm the tariff code to full Saudi depth. The code decides which rule applies, so settle it first.
Read the regulation behind the code and note the standards and editions in force. It also tells you if the product is regulated at all.
Assemble test reports, datasheets, the model list, artwork and the manufacturer declaration. Gaps are found here, not at review.
Only where evidence is missing. Samples go to an ISO/IEC 17025 accredited laboratory for the standards the regulation names.
The importer registers the product under their account with the HS code, model list and origin details.
A SASO-approved conformity body reviews the file and issues the Product Certificate. It stays valid for one year.
For every consignment, raise the Shipment Certificate against the live PCoC before the goods depart.
None of these is a product failure. All six are preparation failures.
Tip
Indicative, on a complete file. The variance sits almost entirely in testing and reviewer queries.
With a complete and current file, the Product Certificate takes about three to ten working days. New testing adds one to three weeks. The Shipment Certificate is usually same or next working day.
From HS code check to first shipment certificate, the whole path typically runs four to six weeks when testing is needed — and under two weeks when it is not.
After that the rhythm changes. Once the PCoC is live, each SCoC takes a day or two. Start renewal about ninety days before the product certificate expires.
Code confirmation, regulation identification and an evidence audit. Fast once the product data is complete.
Only where gaps exist. Sample despatch and laboratory queue are usually the slow part, not the test.
Only where the scheme requires one. Scheduling lead time is the binding constraint.
From a complete, current file. Reviewer queries are what stretch this.
Against a live product certificate, with documents that match. Raised per shipment.
Standards editions move. Starting late means finding a retest with stock already committed.
Send the product, the model list and the HS code. We confirm the regulation and give you a realistic application schedule — usually within one working day.
Tip
An application assembled from these moves in days. One built while these are still being chased takes weeks.
Applications stall when both sides assume the other is handling a step. This is the split we work to.
A reviewer does not re-test your product. They check that the evidence covers the product being certified: the laboratory was accredited for the standard it signed, the edition is current, the model on the report is the model on the list, and the label says what the file says.
Which is why we audit the file before submission, not after a query arrives. A clean first submission is usually the difference between a certificate in a week and a certificate in a month.

What comes before the application, what you supply during it, and what you hold at the end.
Procedure, timing and cost. Certificate scope and validity are answered on the SABER certificate page.
Confirm your Saudi importer and HS code, identify the technical regulation, register the product under the importer’s SABER account, close any testing gaps, then submit the technical file to a SASO-approved body. The Product Certificate is issued after review, and a Shipment Certificate follows for each consignment.
The importer files it, because the account is tied to their Commercial Registration. The exporter supplies the product file and test evidence. We coordinate both sides so neither waits on the other.
As a foreign exporter you cannot file directly — the application needs a Saudi importer’s account. An importer with good technical support can run it; most use a consultant, because the failure points sit in the evidence, not the form.
With a complete, current file the Product Certificate usually takes three to ten working days. Add one to three weeks if new testing is needed, plus scheduling time where an audit applies. The Shipment Certificate is usually same or next working day.
Yes. The Shipment Certificate can only be raised against a live Product Certificate. Without one, the goods cannot clear on a conformity route.
Accredited test reports, datasheets, the full model list, label and packaging artwork, the manufacturer’s declaration and country of origin evidence. The exact set depends on the technical regulation.
It depends on the regulation, the evidence you already hold, how many product families are involved and whether an audit applies. We quote the assessment first and itemise the certification cost before you commit.
Send the product, the model list and the HS code. We confirm the regulation, audit your evidence, file under your importer’s account and handle the reviewer queries.