SABER Application

How to apply for a SABER certificate

Seven stages from the HS code check to the shipment certificate. Send your product and model list — we run the application end to end.

The stages of an application laid out in order along a long table

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:

  • Product + model list
  • HS code (or we confirm it)
  • Saudi importer CR
Apply With Our Help

An overview of the process

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.

Application stages ordered from left to right on a workbench

The seven stages, in detail

Follow them in order. The first two decide everything downstream, and no care later recovers a wrong answer there.

  1. HS code check and product assessment

    Confirm the tariff code to full Saudi depth. The code decides which rule applies, so settle it first.

  2. Technical regulation identification

    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.

  3. Document preparation

    Assemble test reports, datasheets, the model list, artwork and the manufacturer declaration. Gaps are found here, not at review.

  4. Product testing

    Only where evidence is missing. Samples go to an ISO/IEC 17025 accredited laboratory for the standards the regulation names.

  5. Product registration on SABER

    The importer registers the product under their account with the HS code, model list and origin details.

  6. PCoC issuance

    A SASO-approved conformity body reviews the file and issues the Product Certificate. It stays valid for one year.

  7. SCoC per shipment

    For every consignment, raise the Shipment Certificate against the live PCoC before the goods depart.

Where exporters get stuck

None of these is a product failure. All six are preparation failures.

  • The HS code is still in dispute: Files filed while the classification is unsettled get reworked. Settle the code first — it is the cheapest week you will spend.
  • Reports against an old edition: A good test result loses to a superseded standard edition. Caught early it costs a week; caught at review it costs the schedule.
  • The model list keeps moving: Variants added after submission restart parts of the review. Freeze the list before you file.
  • Artwork not ready: Arabic labelling done after the print run means relabelling a consignment at the port, at the worst moment.
  • Importer not confirmed: Filing under a placeholder distributor and switching later means starting the certificate again from the beginning.
  • Paperwork that disagrees: Model numbers or descriptions that differ between file, invoice and label cause reviewer queries — the largest cause of avoidable delay.

Tip

Almost every delay traces back to one thing: documents that disagree. Settle the HS code and freeze the model list before you file.

How long the whole process really takes

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.

Assessment — days

Code confirmation, regulation identification and an evidence audit. Fast once the product data is complete.

Testing — one to three weeks

Only where gaps exist. Sample despatch and laboratory queue are usually the slow part, not the test.

Factory audit — scheme dependent

Only where the scheme requires one. Scheduling lead time is the binding constraint.

PCoC — three to ten working days

From a complete, current file. Reviewer queries are what stretch this.

SCoC — same or next working day

Against a live product certificate, with documents that match. Raised per shipment.

Renewal — start at 90 days

Standards editions move. Starting late means finding a retest with stock already committed.

Need a timeline for your products?

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.

What speeds it up

  • HS code confirmed before anything else starts
  • Existing test reports checked for scope and edition early
  • Model list frozen before the file is submitted
  • Label artwork ready in editable form, with Arabic text
  • One contact who answers reviewer queries the same day

What slows it down

  • HS code still in dispute when the file is filed
  • Test reports written against a superseded standard edition
  • Models added after submission, restarting parts of review
  • Artwork finished after the print run, forcing relabelling
  • Importer not confirmed, so the file is raised twice
  • Model numbers and descriptions that disagree across documents

Tip

Almost every delay traces back to one thing: documents that disagree. Settle the HS code and freeze the model list before you file.

Gather these first

An application assembled from these moves in days. One built while these are still being chased takes weeks.

  • A Saudi importer with an active Commercial Registration, agreed in writing
  • The Saudi HS code for each product, confirmed rather than assumed
  • A full model list — every variant you intend to ship this year
  • Product datasheets, catalogue and technical specifications
  • Any existing test reports, with the laboratory’s accreditation certificate
  • IECEE CB certificate and report, if you hold one
  • Label, rating plate and packaging artwork in editable form
  • Manufacturer details, factory address and country of origin evidence

Who does what

Applications stall when both sides assume the other is handling a step. This is the split we work to.

You and your factory

  • Confirm the full model list and product specifications
  • Provide test reports, or make samples available for testing
  • Update artwork, rating plates and Arabic labelling before print
  • Host the factory audit where the scheme requires one
  • Keep invoice and packing list consistent with the certified models

Us, with your Saudi importer

  • Confirm the HS code and name the technical regulation in writing
  • Audit existing evidence and quote only the genuine gaps
  • Raise the product record and certificate request on the platform
  • Select a conformity body holding approval for that regulation
  • Handle reviewer queries, then raise each shipment certificate

What technical review actually checks

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.

A reviewer holding two sheets up to a window to compare them

SABER application questions

Procedure, timing and cost. Certificate scope and validity are answered on the SABER certificate page.

How do I apply for a SABER certificate?

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.

Who starts the SABER certification process — the exporter or the importer?

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.

Can I apply for a SABER certificate myself?

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.

How long does the SABER application take?

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.

Do I need a PCoC before I can raise an SCoC?

Yes. The Shipment Certificate can only be raised against a live Product Certificate. Without one, the goods cannot clear on a conformity route.

What documents do I submit with the application?

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.

What does the application cost?

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.

Let us run the application end to end

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.