The container is at Jeddah Islamic Port. The goods are genuine, the factory is reputable, the test reports are real, and the Product Certificate of Conformity was issued months ago and has not expired. The Shipment Certificate of Conformity still will not issue, and the demurrage clock is running at a few hundred riyals a day per container.
At this point most importers reach for a clearance agent or a Saber consultancy, pay a fee, and get the shipment moving. That works once. It works again the next month, and the month after, because nothing about the underlying situation has changed.
Saber does not evaluate whether your product is safe. It evaluates whether four descriptions of the same product agree with each other. When they disagree by one tariff digit or one word of product description, the application is rejected — and the physical goods sit at the port while a human retypes a form.
That is not a compliance problem. It is a master-data problem that happens to surface at customs.
What Saber actually verifies
Saber, run by the Saudi Standards, Metrology and Quality Organization (SASO), issues two things, and importers routinely conflate them:
- PCoC — Product Certificate of Conformity. Tied to a product model. Valid for one year. Proves the model itself meets the applicable Saudi technical regulation.
- SCoC — Shipment Certificate of Conformity. Issued per consignment. Proves that this shipment contains the products already registered under a valid PCoC.
The SCoC is where things break, because it is the step that performs a match. To issue it, the platform reconciles:
- The shipment declaration against the PCoC — is every item in the consignment covered by a live product certificate, under the same model designation?
- The declared tariff code against the certificate's tariff code — the HS code on the shipment must be the HS code the product was registered under.
- The product description against the registered description — name and description in both Arabic and English, trademark, country of origin, and the manufacturer's name and address as registered.
- The importer's identity against the Commercial Registration — the party of record must hold a valid Saudi CR, and both importer and manufacturer must be registered on the platform.
Note what none of those four steps asks. None of them asks whether the product is compliant — the PCoC settled that. All four ask whether your data is internally consistent across systems that do not talk to each other: your PIM or ERP, your supplier's documentation, your clearance agent's declaration, and the Saber record itself.
The 12-digit tariff migration quietly invalidated a lot of catalogues
The single biggest source of new rejections in 2026 is structural, and many importers walked into it without noticing.
As of the start of 2026, Saber uses the 12-digit Saudi customs tariff code, synchronised with the list published by the Zakat, Tax and Customs Authority (ZATCA). Applications submitted against the older, shorter codes are rejected by the platform, and certificates carrying superseded codes are treated as invalid. Some existing tariff codes were removed outright and replaced with new ones.
The practical consequence for a business with a real catalogue: every SKU whose tariff classification lives in your ERP as a 6-digit or 8-digit code is now a latent rejection. Saber offers an HS code lookup on its own site — you enter the first six digits of your domestic code and it returns the Saudi 12-digit equivalent — but that is a one-at-a-time browser form. For 40 SKUs that is an afternoon. For 4,000 it is a project nobody has budgeted, so it gets done reactively, one blocked container at a time.
There is a second layer worth flagging: a wrong HS code is not only a Saber problem. Customs may treat a misclassification as a mis-declaration, which affects the duty rate applied and can carry consequences well beyond a delayed certificate.
Where rejections are actually born
Every item on this list originates inside your own records or your supplier's paperwork, before anything reaches SASO:
- A tariff code that was never migrated to 12 digits, or migrated by guessing the trailing digits.
- Product description drift — the PCoC says "LED panel light 36W recessed", the invoice says "LED ceiling light 36 watt", and the two do not reconcile.
- Arabic fields left machine-translated or blank. Both Arabic and English product data are required, and a weak Arabic description is a rejection waiting to happen.
- An expired PCoC. It is valid for one year. Nobody owns the renewal calendar, so it lapses silently and is discovered by a shipment.
- Test reports from a laboratory that is not accredited for the relevant scope, or whose scope does not cover the full range of the model being registered.
- Manufacturer name and address that differ between the test report, the invoice, and the Saber registration — a legal-entity rename or a factory address change is enough.
- The SCoC applied for after the vessel has arrived, rather than before. This one is pure sequencing, and it is expensive.
- Labelling in English only, where Arabic safety marking is required.
- An insufficient Saber wallet balance blocking payment at the moment of issuance.
Read that list again and notice how few of the entries are about the product. Nearly all of them are about a field being different in two places.
The cost is not the certificate fee
The registration fee for a product subject to a technical regulation is in the region of SAR 500 before VAT. Importers benchmark Saber against that number, and it makes the whole thing look like a minor administrative line item.
The actual cost sits elsewhere:
- Demurrage and port storage accruing per container, per day, for the entire duration of a data dispute.
- Expedited re-testing when a laboratory scope gap is discovered at the port rather than at product-registration time.
- Working capital frozen in goods you have paid for and cannot sell.
- Retail commitments missed, which in a channel like a Saudi marketplace or a large retailer means penalties or lost shelf placement.
- Staff time — the hidden line. Someone senior spends a week per incident chasing a supplier for a corrected document.
A single held consignment routinely costs more than migrating the tariff classification of an entire catalogue would have.
There is no bulk Saber API — and that determines the fix
This is the part most importers discover late, so it is worth stating plainly: Saber does not publish a general-purpose integration API that lets you push product registrations from your ERP in bulk. Registration and shipment certificates are worked through the platform interface, by a person.
There is machine integration behind the scenes — ZATCA and SASO connected Fasah, the single-window trade platform, with Saber so that customs procedures pick up conformity status automatically. But that link runs between government systems. It does not extend an endpoint to you.
So the leverage is not "integrate with Saber". The leverage is everything that happens in the ten minutes before a human opens the Saber form. If the data handed to that person is already correct, complete, bilingual, and current, the platform issues in minutes. If it is not, no amount of consultancy fixes it — the consultant just retypes the same wrong field faster.
This is exactly the shape of the problem we described in Saudi WPS violations are a data problem, not payroll: a government platform performing a strict multi-source match, a private business assuming the platform is the obstacle, and the real defect sitting three systems upstream.
The fix: a validation layer in front of the platform
The build is unglamorous and small. It is a service that sits between your product master data and whoever submits to Saber, and it does five things:
1. Hold a Saber-shaped product record. For each SKU: 12-digit Saudi tariff code, Arabic and English name, Arabic and English description, trademark, country of origin, manufacturer legal name and address exactly as they appear on the test report, applicable technical regulation, and the PCoC number with its expiry date. This is a table, not a platform. Most importers do not have it, which is the whole problem.
2. Reconcile tariff codes once, deliberately. Map every catalogue SKU from its legacy code to the current 12-digit ZATCA code, flag the ones where the mapping is ambiguous, and route those to a customs broker for a judgement call rather than a guess. Ambiguous is fine. Silently wrong is what costs money.
3. Diff the shipment against the registry before booking. Take the supplier's proforma invoice or packing list and compare, line by line, against the product registry: is every line covered by a live PCoC, does the description match, does the tariff code match, is the certificate going to still be valid on the projected arrival date? Anything that fails becomes a task with a deadline, weeks before the vessel sails.
4. Run an expiry calendar. PCoCs expire annually. Renewal should be triggered by a date, not by a container. Ninety days out, sixty, thirty.
5. Track regulation changes against your own SKUs. Requirements move. In 2026 alone, importers have had to absorb the tariff-code migration; a Product Declaration requirement, issued through the Ministry of Industry and Mineral Resources, that became a prerequisite for the shipment certificate on certain listed product categories from mid-June; new air-conditioner energy-efficiency standards phasing in through the end of the year; and a USB Type-C interface requirement on certain portable electronics from April. Each of those affects a subset of catalogues. The question that matters is not "what changed?" but "which of my SKUs does it hit?" — and only a product registry can answer that.
None of this requires an API you do not have. It requires knowing what you sell, in the exact vocabulary SASO uses, before a ship leaves port.
What to check this week
Three questions, answerable without a project:
- Can you produce a single list of every SKU you import, with its 12-digit Saudi tariff code and its PCoC expiry date? If that list has to be assembled by asking three people and opening the Saber portal, it does not exist.
- How many of your live PCoCs expire in the next 90 days? If the answer is unknown, at least one shipment this quarter is going to find out the hard way.
- When a certificate was last rejected, was the reason recorded anywhere? Rejection reasons are the highest-value data an importer throws away. Logged for six months, they tell you precisely which field in which system is broken.
The same reasoning applies across the Saudi platform estate — the mechanics differ, the failure mode does not. We have written up the equivalent analysis for healthcare in NPHIES claim denials, for HR in Qiwa integration and Nitaqat, and for tax in the ZATCA e-invoicing guide.
If shipments are being held and nobody can say which field caused it, the useful first step is not a compliance retainer. Send us a sample of your product catalogue and the last few rejection notices, and we will map where your SKU data diverges from what Saber expects — and what a validation layer would need to cover. Talk to us.