SABER DESKSaber Desk · Free article
HS-code waves 2025–2026 — revalidating your codes before they cost you
Why the code decides everything
In the Saudi conformity system the HS code is not a customs formality you fix at the end — it is the first decision everything else reads from. The code determines whether the product is regulated at all, which technical regulation applies, which prerequisites exist (CST, IECEE via JEEM, RoHS, energy efficiency), and what the PCoC and SCoC will be issued against. SABER's product registry keys on it; Saudi Customs clears against it through FASAH; ZATCA's integrated tariff defines it.
What changed in the 2025–2026 waves
Tariff codes were replaced in waves in January 2025 and again in January 2026. For the 2026 wave, SASO notified users on 18 November 2025 that several existing customs tariff codes would be removed and replaced in SABER from 1 January 2026, aligning SABER's registry with ZATCA's customs tariff list. Affected categories in that notification explicitly include electrical appliances, machinery, ICT devices and electric vehicles — squarely the electronics importer's territory — alongside textiles, building materials, pressure equipment and vehicle spare parts.
The consequence is blunt: the code you registered under last year may simply no longer exist. New registrations must use the current codes, and a registration attempted against a removed code goes nowhere.
What happens to existing certificates
The transition rule is more forgiving than people fear: Product and Shipment Certificates issued under the old codes remain valid until their expiry date, and when presented after the change Saudi Customs reassigns the new tariff codes during clearance. So a valid PCoC does not die with its code. What does bite: renewals and new product entries must use the current code, and any mismatch between the code on your commercial invoice and the code logic in SABER is exactly the kind of documentary inconsistency that stalls clearance — the most-cited delay cause in the seven customs traps.
The revalidation routine
Once per cycle — at minimum every January, and before every new registration or renewal:
- Pull your product list with the codes you registered under. The SABER registry view is the source of truth for what you hold.
- Check each code against ZATCA's integrated tariff (zatca.gov.sa) — is the code still current, split, or replaced?
- For changed codes: plan the new registration/renewal under the current code, and check whether the new code moves the product's regulatory status or prerequisites (a code change can change which technical regulation applies).
- Update the paperwork chain: tell the factory the current code so invoices and packing lists carry it, and keep the wording identical across invoice, packing list and SABER — line by line.
- Log the check with a date. When a shipment stalls in February, the log is how you prove the code was verified in January.
Keeping documents aligned
Code discipline is document discipline. The invoice, the packing list, the SABER registration and the B/L must tell one story: same product names, same models, same quantities, same codes, and a Consignee that matches the Commercial Registration behind the SABER account. The cheapest prevention in the whole Saudi pathway is sending your supplier the exact registered strings and requiring them verbatim.
Failure patterns
- Renewing into a dead code — the renewal stalls, then every shipment behind it.
- Assuming customs remapping covers new registrations — it covers existing certificates at clearance, nothing else.
- Missing a scope change hidden in a code change — a new code can pull the product into a prerequisite it never needed before.
- Invoice code ≠ SABER code — the classic mismatch stall, entirely preventable.
Frequently asked questions
My PCoC was issued under a code that changed in January. Is it void?
No — certificates issued under old codes stay valid until expiry, and customs reassigns the codes at clearance. Renewals and new registrations must use the current code.
Where do I check the current Saudi tariff codes?
Against ZATCA's integrated customs tariff (zatca.gov.sa); SABER's registry is aligned to it. Your Certification Body can confirm the regulatory consequences of a code change.
How often do the codes change?
Recent practice has been January waves — 2025 and 2026 both saw replacements, the 2026 wave announced by SASO on 18 November 2025. Build the check into every renewal cycle rather than assuming stability.
Can a code change make my product newly regulated?
Yes — scope follows the code. That is why the revalidation routine includes rechecking regulatory status and prerequisites, not just the number.
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.