An obligations register
Every product line set against the authority that governs it, the regulation it falls under and the approval it needs. One table, the whole range, rather than an answer per email thread.
Saudi Regulatory Assessment
One product is a question. A catalogue is a position.
Ranges built up over years accumulate codes assigned by different people, certificates nobody diarised and lines that quietly changed regulator when the packaging copy changed. A regulatory assessment reads the whole range together and returns one register: what governs each line, what evidence is missing, what contradicts what, and the order to fix it in.
To scope an assessment we need:
- Your product list or catalogue
- Codes and certificates you already hold
- Which markets you ship today
The Premise
Some problems are only visible across the whole range
Checked one at a time, a catalogue almost always looks fine. Each line has a code, most have a certificate, and nothing has been stopped recently. The defects that matter are relational — the same product classified two ways in two places, a family certificate that does not name half the family, an approval sitting in an account you no longer have access to. None of those are visible from inside a single-product check.
This engagement reads the range together and writes down one position for all of it. Where a single product needs settling, a classification opinion is the cheaper and better answer, and we will tell you so rather than sell you this.
The Deliverable
What the assessment hands you
One document covering the whole range, written so someone who was not in the room can act on it.
What is not required
The regulators ruled out, stated explicitly per line. Knowing a scope does not apply is what lets you stop paying to defend against it.
Gap analysis
Where evidence is missing, expired, held in someone else’s name, or describes a model you no longer make. Graded by whether it stops a shipment or merely should be tidied.
Contradictions surfaced
The same product classified two ways across your own records, or a certificate that disagrees with the invoice it travels with. These only become visible when the range is read together.
A sequenced plan
What to do first, what can wait, and what depends on something else finishing. Ordered by shipment risk and lead time, not by how easy each item is.
A position you can hand over
Written so a broker, a buyer or an incoming compliance manager can act on it without reconstructing how the conclusions were reached.
Method
How the range is worked through
Grouping before classifying is the step that makes a large catalogue tractable — SKUs on a shared technical platform share a determination.
Scope the range
Which lines are in, which are dormant, which are sold under more than one brand. Portfolios are almost always larger than the list that arrives first.
Group by technical platform
SKUs that share a platform usually share a determination. Grouping before classifying is what keeps a 400-line catalogue from becoming 400 assessments.
Classify each group
Codes confirmed at Saudi tariff depth per group, with divergences from your existing codes recorded rather than silently overwritten.
Screen every regulator
Each group run against SASO, SFDA, MIM and the sector scopes — including the ones that turn out not to apply, which are recorded as cleared rather than left unmentioned.
Audit the evidence you hold
Existing certificates and test reports checked for validity, scope, model coverage and whose name they are in. This is where most of the findings come from.
Rank by exposure
Findings graded: stops a shipment now, will stop one soon, or is housekeeping. Without this a register is a list rather than a plan.
Issue the register
The full position across the range, the gaps, the contradictions and the order to close them, in one document.
Review on change
Regulations are revised and catalogues move. The register is worth rereading when either happens, not once and then archived.
Assumed vs Assessed
What a range assumes, and what it can show
Everything on the left is reasonable. None of it is evidence, and all of it is regularly untrue somewhere in a long catalogue.
What a range usually assumes
- The codes on file are correct because they have cleared before
- One certificate covers the family, because the family looks alike
- What applied at first import still applies now
- Everything sits with the same regulator
- The certificates are in our name
What an assessment establishes
- Each code confirmed at Saudi depth, with divergences recorded
- Model coverage checked line by line against what you actually ship
- Current regulation and certificate validity as at today
- Every regulator screened, including the ones ruled out
- Whose account each approval sits in, and what happens if that changes
Findings
What assessments usually turn up
Six recurring findings. Each one is invisible line by line and obvious once the range is read as a whole.
The same product, two codes
Classified one way for one market and another way for Saudi, or differently by two people in the same office. Neither is wrong on its face; they cannot both be right.
Certificates that lapsed quietly
Still cited in clearance documents, still assumed live by the sales team, expired for months. Nobody owns an expiry date that nobody diarised.
Models shipped but never certified
A variant added to the range, sold on the strength of the family certificate, never actually named in it.
A line in the wrong regulator
Usually a product with a claim on the pack that moves it into SFDA scope. Almost never noticed until it is the line that gets stopped.
Approvals in a former partner’s name
The relationship ended; the certificates did not come with you. Discovered when the new distributor tries to use them.
Evidence against a superseded standard
Testing that was correct when commissioned, against a revision of the regulation that has since moved on.
Engagements
When an assessment is worth running
Six situations where the range, rather than any single product, is the thing in question.
Pre-entry assessment
Before the first shipment. What the whole range will require in Saudi Arabia, so the launch is planned against real lead times rather than hopeful ones.
Catalogue audit
An established range built up over years by different people. The findings are usually drift, duplication and a handful of lines nobody has looked at since launch.
Post-hold review
A consignment was stopped. Beyond fixing that container, the question is which other lines share the same defect and have simply not been checked yet.
Regulation-change recheck
A technical regulation or tariff schedule has moved. Which of your lines are affected, which certificates need reissuing, and by when.
Supplier or distributor change
Certificates sit in an account you are leaving, or arriving into. What transfers, what must be reissued, and what quietly stops being valid.
Due diligence
Assessing someone else’s range — an acquisition, a new principal, a private-label partner — before you inherit their regulatory position along with their stock.
What We Need
What the assessment runs on
Incomplete is workable and is itself a finding. A tidied list hides the inconsistencies the engagement exists to find.
The range
- Product or SKU list, including variants and private-label versions
- Datasheets or technical specifications per platform
- Composition breakdown, where materials decide the classification
- Catalogue pages or listings as published, with any claims made
- Which lines are active, dormant or being discontinued
What you already hold
- Existing HS codes and who assigned them
- Certificates held, with the account or consignee named on each
- Test reports and the standards they were issued against
- Any customs query, reassessment or hold previously received
- Codes used in other export markets, for comparison
Commercial context
- Saudi importers or distributors you ship through
- Which lines ship most often, and which are highest value
- Planned additions to the range in the next year
- Any launch dates already committed
- Who owns compliance internally, if anyone does
Catalogue Audit
210 SKUs, eight years, no single record
A household goods supplier with 210 active SKUs across four categories, eight years of Saudi shipments, and no single record of what had been approved.
- The 210 SKUs grouped down to 31 technical platforms — so 31 determinations, not 210.
- Nineteen lines carried codes that contradicted codes used for the same goods elsewhere in the business.
- Six certificates had expired, and two more named a distributor the company had stopped working with.
- Four lines carried claims on the pack that put them in SFDA scope; none had ever been notified.
- The remaining majority were sound — and recording that explicitly was what let the team stop re-checking them each quarter.
Keep Going
Related services
The map above this engagement, and the determinations underneath it.
FAQs
Assessment questions
Scope and method questions. Single-product classification questions live on the HS code page.
How is this different from the HS code assessment?
Scope. The HS assessment is a determination for one product — the code, the reasoning under the interpretative rules, and what that code triggers. A regulatory assessment takes a whole range and produces a register: what governs each line, where the evidence is missing or contradictory, and what order to fix it in. Classification is one input to it rather than the output.
How is it different from the product compliance page?
That page explains how the chain works — authority, regulation, certificate — so you can understand your own position. This is the engagement where we establish that position across your range and write it down. One is the map; this is the survey of your particular ground.
We only have one product. Do we need this?
Probably not, and we will say so. A single product is better served by a classification opinion and a compliance route check. This engagement earns its cost where there is spread — multiple lines, multiple regulators, or history nobody has audited.
How long does an assessment take?
It follows the grouping rather than the SKU count, because products sharing a technical platform share a determination. A range that collapses into a dozen platforms moves quickly; one with genuine variety, or with evidence that has to be chased from several suppliers, takes longer. We scope it before starting and tell you which you have.
What if the assessment says our current codes are wrong?
Then you get both positions side by side with the consequence of each, rather than a silent correction. Where a code has been used on previous consignments, changing it has implications worth deciding deliberately — we set those out instead of making the choice for you.
Do you handle the fixes as well?
Testing, certification, labelling and filing are separate services and the register is deliberately usable without them. Most clients ask us to continue; some take it to their existing provider or run it in-house. Either is fine, which is rather the point of writing it down properly.
Can you assess a range we are about to acquire?
Yes, and that is a common use. Inheriting a catalogue means inheriting its regulatory position — lapsed approvals, contested codes and certificates in someone else’s name all transfer with the stock. Better to know the liabilities before the deal closes than after.
Will you tell us if most of our range is already fine?
Plainly, and it happens often. A clean finding is a real outcome: it retires a standing worry and stops the team re-checking the same lines every quarter. We would rather report that than manufacture work.
Send the product list and get one register for the whole range
A catalogue, the codes you use and the certificates you hold is enough to scope it. You get the obligations, the gaps and the order to close them.