Reference
Export-Control Coverage
What the export-control candidate layer covers today across EU, UK, US, Japan and Taiwan sources, verified live — and what's still genuinely on the roadmap.
1. The Core Idea
A CN/TARIC code is a risk signal, not a final export-control classification.
The same CN heading can cover a dozen different real products with completely different export-control status. Take CN 8542 — electronic integrated circuits:
- an ordinary commercial chip → no export controls, EAR99-equivalent
- radiation-hardened → EU Dual-Use 3A001
- general-purpose high-performance computing → 3A501
- with cryptography → EU Dual-Use 5A002 / EAR 5A002
- military-designed → EU Military List ML11 / US Munitions List Category XI
The final classification depends on product characteristics the CN code alone cannot carry: radiation hardening, performance grade, temperature range, encryption, military design, end-use, destination. That is why CN/TARIC and export-control classifications are not one-to-one — a single CN heading can map to dozens of candidate entries across several control lists, and a code-only lookup misses almost all of them. Searching by product description or a chemical identifier finds far more — see §4.
2. The Four-Level Model
| Level | Input | Output | Confidence | Decision-maker |
|---|---|---|---|---|
| 1. CN/TARIC scope | CN/TARIC code | List of possibly relevant regimes | Low — signal only | Automated |
| 2. Description match | + product description, datasheet text | Candidate control-list entries with reasoning | Medium — textual match | Automated, keyword/text search |
| 3. Rule match | + technical specs, end-use, destination | Narrowed candidates with rule evidence | Higher — parameters satisfy specific rule text | Automated + analyst |
| 4. Analyst decision | + supplier declaration, licence, internal review | Confirmed classification, licence required y/n, evidence pack | Auditable | The customer's export-control analyst |
The platform automates levels 1–2 today, with level 3 depending on how much specification text is supplied. Level 4 — the final "licence required / not required" call — stays with the customer's analyst; nothing here issues a determination on its own.
3. What Is Live Today
The platform's export-control candidate search now spans 30 control-list sources across five jurisdictions — European Union, United Kingdom, United States, Japan and Taiwan:
| Jurisdiction | Sources |
|---|---|
| European Union | EU Dual-Use Annex I, EU Common Military List, EU/G7 Common High Priority Items, plus 20 further goods-control regimes — carbon border adjustment, deforestation, conflict minerals, cultural goods, firearms, drug and explosives precursors, and more (see the full list via /sources) |
| United Kingdom | UK Strategic Export Control List |
| United States | US Commerce Control List (EAR), US Munitions List (ITAR), plus the US Consolidated Screening List for named entities |
| Japan | METI End User List (named entities) |
| Taiwan | MOEA Strategic High-Tech Commodities Entity List (named entities) |
Goods/control-entry sources (Dual-Use, Military List, CCL, ITAR, the EU's own regime-specific lists) are searched through search_export_control_candidates. Named-party lists — entities and end-users rather than goods — route through screen_entities instead, using the same sanctions-screening engine described in Entity Screening Algorithms.
This is meaningfully broader than a EU-only tool: a single query can surface matching entries across EU, UK and US regimes at once, because the same restricted item is very often controlled in more than one jurisdiction's list at the same time.
4. What Actually Finds A Candidate
Three ways to search, and they are not equally powerful:
By CN/TARIC code alone. Weak. Most CN headings have no or very sparse direct correlation to a control-list entry — CN 8542 alone returns nothing. A bare code is a starting point for level 1 screening, not a way to reach a candidate classification.
By product description text. This is where the real coverage is. Searching "integrated circuits" returns dozens of relevant entries across EU Dual-Use, the UK list and the US CCL in one call — the exact ECCN-style codes from the §1 example (3A001, 3A501, and their EAR/UK counterparts) come back this way, not from the CN code.
By chemical identifier (CAS RN, CUS, EC number, InChIKey). Strongest signal available. An exact CAS match returns candidates across every regime that controls the substance simultaneously — zirconium powder (CAS 7440-67-7), for instance, returns matching entries from the EU Military List, the UK list, the US CCL and the US Munitions List in a single call, each with the exact regulatory citation.
The practical conclusion: ask with product description text or a chemical identifier, not a bare CN code. The get_compliance_report / check_trade_compliance tools already do this automatically when product-text fields are supplied alongside the CN code.
5. What The Result Looks Like
A goods compliance result stacks four layers:
- Customs classification — CN/TARIC
- Duties / measures — TARIC
- RU/BY goods sanctions
- Export controls (candidate layer)
- EU Dual-Use, EU Military List, EU/G7 CHPL, and 20 further EU regimes
- UK Strategic Export Control List
- US Commerce Control List (EAR) and US Munitions List (ITAR)
- Japan METI and Taiwan MOEA end-user lists (named entities)
- CAS-based chemical candidate search across all of the above
- Analyst decision: licence required / not required / needs review
Every result carries review_required when a candidate surfaces, source evidence, and the regulatory citation it came from. It should always be read as "possible export-control review required" — never as a final Dual-Use, Military List, ITAR or ECCN classification.
6. Why This Is Harder Than Goods Sanctions
| Goods sanctions | Export controls |
|---|---|
| One CN code → one measure/prohibition | One product description → candidates across several regimes at once |
| Binary: allowed / forbidden | Depends on specs, end-use, destination |
| Source: TARIC measures + EUR-Lex | Sources: EU regimes, UK list, US CCL/ITAR, Japan and Taiwan entity lists — and growing |
| Needs the code only | Needs code + description + technical characteristics + end-use + destination |
| High confidence | Multi-level confidence; always needs a human for the final call |
7. Still Genuinely On The Roadmap
- Wassenaar Arrangement, MTCR, NSG and Australia Group — the multi-national supplier-group frameworks that sit alongside, and partly inform, the national/regional lists already covered
- End-use / end-user catch-all rules beyond the named-entity lists already screened
- Deeper rule-level matching (§2's level 3) for control-list entries that currently only match by keyword rather than by structured technical parameter
8. Why This Matters
Most classification tools stop at TARIC and hand back ten digits and a list of customs measures. Export-control screening is a genuinely different, harder problem — and a real compliance requirement, not a nice-to-have, for customers in electronics, chemicals, optics, aerospace and cryptography. The cost of getting it wrong is real: export-control violations carry multi-million euro or dollar fines and can reach criminal liability for company officers.
The honest position to hold: today's coverage spans 30 sources across five jurisdictions and finds real candidates reliably by description or chemical identifier — but every result is a review signal for an analyst, not an automated licence decision. The rule-based classification and end-use catch-all layers in §7 are what would close that last gap.
9. Related Material
- HS / CN / TARIC Classification — the customs-classification layer this sits on top of
- Entity Screening Algorithms — the engine behind named-entity export-control lists (METI, MOEA, UFLPA, the US Consolidated Screening List)