SABER DESKSaber Desk · Free article
The 7 customs traps that stop electronics shipments in Saudi Arabia
Why certified shipments still get stuck
Most Saudi customs holds on electronics are not about a product failing a test. They are about paperwork and sequencing: a certificate that lapsed, a document that doesn’t match another document, an approval that should have existed months earlier. The product is fine; the file around it is not.
Since January 2025 the cost of these mistakes went up sharply. Both certificates — the Product Certificate of Conformity (PCoC) and the Shipment Certificate of Conformity (SCoC) — must exist before the goods arrive, Letters of Undertaking are no longer accepted, and post-arrival certification is treated as a violation with re-export among the possible outcomes. There is no catch-up lane. Below are the seven failures that strand the most shipments, why each happens, and the fix. Every one of them is checkable before the vessel sails.
Trap 1 · The PCoC expired at the moment the SCoC was requested
What it looks like: the shipment certificate request cannot be completed. The goods are already booked, sometimes already at sea.
Why it happens: the PCoC is valid for one year and covers repeat shipments of the same model by the same importer — so it drifts out of daily attention. Nobody owns the renewal date. The rule that bites: an SCoC can only be issued while the PCoC is valid at that moment.
The fix: put every PCoC expiry in a shared calendar and renew about 30 days early. Before booking any vessel, check that the PCoC will still be valid on the day you plan to request the SCoC — and remember the SCoC itself is valid for only 60 days, so it is timed against the sailing schedule, not requested months ahead.
Trap 2 · The commercial invoice doesn’t mirror the SABER registration
What it looks like: the SCoC request or the clearance stalls on a mismatch — product names, model numbers, quantities or HS codes on the invoice that differ from what was registered in SABER. This is the single most-cited cause of delay.
Why it happens: the factory issues the invoice from its own ERP naming, the importer registered the product in SABER months earlier with different wording, and nobody compares the two before the goods ship.
The fix: a line-by-line match of invoice and packing list against the SABER product entries — names, models, quantities, HS codes — before the supplier finalises the documents. Send the supplier the exact registered strings and ask for them verbatim.
Trap 3 · Test reports to a standard that is no longer accepted
What it looks like: the PCoC application is rejected or stalls at the Certification Body because the safety report is against a withdrawn standard — most often IEC 60950-1 for IT and audio/video equipment, where IEC 62368-1 is now required. Energy-efficiency standards move too, and certificates tied to an old version can be terminated when the standard transitions.
Why it happens: factories reuse old reports (“it passed last year”), and the buyer only discovers the problem at the PCoC stage — after paying for testing.
The fix: confirm the currently required standard with your Certification Body before commissioning any lab work, and ask the factory for the report’s standard and edition, not just “a CB report”. A full test against the wrong standard is simply money burned.
Trap 4 · The Bill of Lading Consignee is not the SABER account holder
What it looks like: clearance stalls because the Consignee on the B/L is a different legal entity from the Commercial Registration behind the SABER account that holds the certificates.
Why it happens: the forwarder puts its own entity or a group company as Consignee; the Notify Party is often the forwarder anyway. The Notify Party doesn’t save you — the Consignee is the binding field.
The fix: align the importing entity across SABER, the commercial invoice and the B/L before booking. One name, one CR, on all three.
Trap 5 · Certifying after arrival
What it looks like: the container arrives; the PCoC or the SCoC — or both — do not yet exist. The importer tries to file now.
Why it happens: old habits. Before 2025 a Letter of Undertaking could bridge the gap. Since January 2025 that route is closed: certificates must exist before arrival, post-arrival certification is a violation, and re-export is among the possible outcomes.
The fix: the certificates belong on the pre-shipment checklist, not on the port checklist. If goods are already at sea without them, work with your Certification Body to limit the damage — do not plan on a quick clearance.
Trap 6 · A prerequisite discovered only when the PCoC stalls
What it looks like: the PCoC application stops because something that must exist first doesn’t: CST type approval for a wireless device, IECEE recognition through JEEM for an in-scope product, a RoHS file per IEC 63000, or energy-efficiency registration through SLS.
Why it happens: SABER is treated as step one when, for electronics, it is usually step three or four. The account and the product entry are the fast parts — officially immediate and free — so the missing approval only surfaces when the Certification Body reviews the file.
The fix: map the prerequisites at the classification stage, from the HS code, and run the tracks in parallel. Budget realistic lead times: a CST type approval typically runs about 3–4 weeks; IECEE recognition via JEEM officially runs 5–21 working days. Neither can be compressed once your goods are already sitting at the port.
Trap 7 · Labeling gaps and stale HS codes
What it looks like: a hold for missing or non-compliant labeling, or a registration under an HS code that no longer exists.
Why it happens: HS codes were replaced in waves in January 2025 and January 2026. Certificates issued under old codes stay valid until expiry and customs remaps them at clearance — but new registrations must use the current code, and last year’s code may simply be gone. Labeling requirements are checked against the technical regulation for the product’s category, not against what the factory usually ships.
The fix: re-validate HS codes at each renewal cycle and before every new registration, and confirm the labeling requirements for your category with your Certification Body before production, not after.
What a trap actually costs
Not a fine you pay and move on. A stuck container accrues daily storage and demurrage while the problem is fixed — and some problems cannot be fixed quickly. A missing CST approval is about 3–4 weeks; IECEE recognition is 5–21 working days officially; a PCoC renewal follows the Certification Body’s review time (officially 5–6 working days, commonly 10–14 in practice). The meter runs the whole time, the sales window closes, and re-export is on the table for goods that arrived without certificates.
Five checks before you book the vessel
- PCoC valid through the planned SCoC request date — renewal booked 30 days early.
- Standards current — every test report names the standard and edition your Certification Body confirmed (IEC 62368-1 for IT/AV, not 60950-1).
- Prerequisites in hand — CST, IECEE via JEEM, RoHS file, SLS registration, whichever apply to your HS code.
- Documents mirror SABER — invoice and packing list match the registered names, models, quantities and HS codes line by line; B/L Consignee = the CR behind the SABER account.
- SCoC timed to the sailing — requested so it is valid on arrival (60-day window), never planned post-arrival.
The full pre-departure sequence, the invoice-matching checklist and the one-page process checklist are inside the free bilingual sample and the full Compliance Guide.
Frequently asked questions
Which trap is the most common?
The invoice that doesn’t mirror the SABER registration — names, models, quantities, HS codes. It is the single most-cited cause of delay and the cheapest to prevent: match the documents line by line before the supplier finalises them.
Can a Letter of Undertaking still bridge a missing certificate?
No. Since January 2025 Letters of Undertaking are no longer accepted; both certificates must exist before arrival.
My PCoC was issued under an HS code that changed. Is it void?
No — certificates issued under old codes stay valid until expiry, and customs remaps the codes at clearance. New registrations and renewals must use the current code.
Do non-regulated electronics escape these traps?
Not the shipment step: since October 2025 an SCoC is required on every import, with non-regulated goods going through self-declaration. Confirm the regulated status from the HS code first — electronics are almost always regulated.
Go deeper, in both languages
The free sample covers the prerequisite stack, PCoC basics and 3 of the 7 traps — one English PDF and one Arabic PDF. The full Compliance Guide has the whole enforced path, every fee and timeline, all 7 traps with fixes, the invoice-matching checklist and a first-year budget worksheet.
Saber Desk is an independent reference — not a certification body, and not affiliated with SASO. We do not issue certificates. Fees and processing times are the official figures published on saber.sa unless marked as observed practice; confirm HS codes and required standards for a specific shipment with your Certification Body. Edition: August 2026.