Why Renewal Matters
The Product Certificate of Conformity (PCoC) is not permanent. It is issued for a specific product model and is valid for up to 12 months. During that window you can raise as many Shipment Certificates of Conformity (SCoC) as you need, one per consignment. Once the PCoC expires, that link breaks: no new SCoC can be issued against a lapsed PCoC, and without a valid SCoC, Saudi customs will not clear the shipment.
For any exporter with an ongoing Saudi trade, renewal is therefore not optional housekeeping — it is what keeps the pipeline open. A lapsed certificate discovered when goods are already at the port is one of the most disruptive and expensive situations in Saudi compliance, because it stops shipments dead while a fresh certification is arranged. Renewal exists to prevent exactly that.
When Should You Renew?
The certificate itself shows its issue and expiry dates, and the practical rule is to begin renewal well before expiry rather than on it. We recommend starting the renewal 4 to 6 weeks ahead of the expiry date. That buffer absorbs any surprises — an updated Technical Regulation, a document that needs refreshing, or a query from the certification body — without leaving a gap in which you cannot ship.
If your shipments to Saudi Arabia are frequent, treat the expiry date as a hard deadline in your logistics calendar. If they are occasional, still renew on time if you expect to keep supplying that product; letting the certificate lapse means starting closer to a first-time registration when the next order arrives.
Set a reminder: The most common cause of a shipment being blocked is a PCoC quietly expiring while no shipments were being made. When a new order then comes in, there is no active certificate to raise an SCoC against. Track the expiry date even during quiet periods.
The Renewal Process
-
Step 1 — Review the Current Certificate and Regulation
We check the existing PCoC, the product model it covers, and — importantly — whether the applicable Technical Regulation has changed since it was issued. Renewals are usually straightforward, but if the regulation or the required standards have been updated, the renewal must reflect the new requirements.
-
Step 2 — Confirm Documentation and Test Reports
Existing test reports and technical documents are reviewed to confirm they are still valid and still meet the current requirements. If the standard has moved on, or reports have lapsed, updated testing may be needed — but in a clean renewal with no regulatory change, most of the file simply carries over.
-
Step 3 — Submit the Renewal on SABER
The Saudi importer submits the renewal application through their SABER account, supported by the confirmed documentation. Because the product is already known to the system, this is generally quicker than the original registration.
-
Step 4 — New PCoC Issued
The Conformity Assessment Body reviews and issues a renewed PCoC with a fresh validity period of up to 12 months. Shipments — and their SCoCs — continue without interruption.
What If the Certificate Has Already Lapsed?
If the PCoC has already expired, you cannot simply "extend" it retroactively — you arrange a new certification for the product model. Where the previous documentation and test reports are still valid and the Technical Regulation is unchanged, much of that file can be reused, so it is faster than a genuine first-time registration. But it is still slower and more disruptive than a timely renewal, and it can hold up shipments in the meantime.
If you are in this situation with goods waiting, contact us immediately with the product details and the old certificate. We assess what can be reused and move to reinstate a valid certificate as quickly as the requirements allow.
Renewal vs New Certification — the Cost and Time Difference
A timely renewal is generally quicker and less costly than a first-time certification, because the product is already characterised and, in most cases, no new testing is required. You are refreshing an existing, valid file rather than building one from scratch. See our certificate cost page for how the fees are structured and our timeline page for how the durations compare.
The exception is when the Technical Regulation has changed. If SASO has updated the standards or requirements for your product category since the last certificate, the renewal effectively brings the product up to the new baseline, which may involve fresh testing or additional documentation. We flag this at the review stage so there are no surprises.
Frequently Asked Questions
How long is a SABER certificate valid?
The Product Certificate of Conformity (PCoC) is valid for up to 12 months from issue. The exact validity is shown on the certificate. Within that period you can raise unlimited Shipment Certificates of Conformity (SCoC), one per consignment. The SCoC itself relates to a single shipment and is not renewed — it is the PCoC that carries the 12-month validity and must be renewed to keep exporting the product.
When should I start the renewal?
Begin 4 to 6 weeks before the expiry date. That buffer covers any updated Technical Regulation, refreshed documentation or queries from the certification body without creating a gap in which you cannot ship. If you export the product frequently, treat the expiry as a fixed deadline in your logistics planning.
What happens if my PCoC expires?
Once the PCoC expires you can no longer raise an SCoC against it, and without a valid SCoC your shipment will not clear Saudi customs. You cannot retroactively extend a lapsed certificate; you arrange a new certification for the model. If the old documentation is still valid and the regulation is unchanged, much of it can be reused, but it is slower and more disruptive than renewing on time.
Do I need to re-test my product to renew?
Not usually. In a clean renewal where the Technical Regulation and standards are unchanged and your existing test reports remain valid, the documentation carries over and no new testing is needed. Re-testing becomes necessary only if the applicable standard has been updated, the reports have lapsed, or the product has changed. We confirm this at the review stage before any renewal begins.
Is renewal cheaper than the original certification?
Generally yes, because the product is already characterised and, in most cases, no new testing is required — you are refreshing an existing valid file rather than building one from scratch. The main exception is when the Technical Regulation has changed since the last certificate, which may require fresh testing or additional documentation to meet the new baseline. We flag any such change at review so the cost is clear up front.