Export licensing
Catalogue of goods subject to export licensing
Organises structurable fields from the catalogues — goods name, commodity code, licence administration method, effective information and source file.
China Import/Export Licensing & Dual-Use Controls Data API
Turn public trade control rules into data that can enter enterprise systems.
The Ministry of Commerce, General Administration of Customs and other departments continuously publish import/export licensing and dual-use control information through catalogues, notices and web pages. GooFuture collects, parses, standardises and links the public data by source, helping companies cut duplicated work and feed rule data into internal screening, review and business systems.
From "looking up catalogues by hand" to "systems calling data".
Structured JSON dataBuilt for enterprise system integrationRetains rule source and effective information
Query conditions
- Commodity code
85********- Goods name
- Industrial electronic components
- Query date
This button only illustrates the static data structure and does not run a real query.
Find related rule records
Pending further verification- Rule type
- Dual-use items / licence catalogues
- Commodity code
- Shown when a mapping exists
- Control code
- Shown when present
- Item description
- Structured summary
- Effective date
- YYYY-MM-DD
- Issuing authority
- Ministry of Commerce / General Administration of Customs
- Data source
- Original notice
- Match status
- Pending further verification
The sample only illustrates the data structure.An actual control determination may also involve technical parameters, use, end user, destination and current regulatory requirements.
Public rules are searchable, but hard for enterprise systems to use directly
The real problem for companies is usually not whether public data exists, but how to get it reliably into order review, product management, customs, supply chain or internal compliance systems.
Public rule sourcesStructures vary
001Annual cataloguePDF / spreadsheets
002Policy noticesHTML / attachments
003Rule descriptionWeb pages / files
GooFuture data layerUnified fields and source relationshipsContinue screening and verification inside enterprise systems
- 01
Data lives in different formats
Catalogues, notices, HTML and PDF are not uniformly structured.Business impact:Systems cannot consume them directly; teams must keep downloading, parsing and standardising fields.
- 02
A commodity code is not a control conclusion
Commodity codes, control codes, item descriptions and technical parameters may need to be used together.Business impact:A simple HS code hit cannot replace professional item identification and compliance judgement.
- 03
Rules have versions and effective dates
The annual catalogue is updated, and new notices and adjustments may appear in between.Business impact:Keeping just one static table makes it hard to say when a rule was in force or which file it came from.
- 04
Manual lookups rarely enter business processes
One-off lookups can be done manually, but large volumes of products, orders or system requests create repetitive work.Business impact:Product, compliance and technology teams must maintain their own rule data layer.
GooFuture does not replace regulators, nor does it replace your own compliance judgement.We solve the collection, organisation, maintenance and system delivery of rule data.
Continuous organisation of public China trade licensing and export control data
Retains catalogue entries, timing information and source files so structured records can always be traced back to the original public information for verification.
Import licensing
Catalogue of goods subject to import licensing
Organises import-licensed goods and related catalogue information while retaining the corresponding rule source and effective period.
Dual-use items
Catalogue of dual-use items and technologies subject to import/export licensing
Organises queryable data around control codes, item descriptions, commodity code mappings, technical descriptions and source files.
Data comes mainly from information publicly published by government departments including the Ministry of Commerce and the General Administration of Customs of the People's Republic of China. GooFuture is an independent third-party data service provider.
From public documents to machine-readable trade controls data
Catalogues, notices and web pages are processed uniformly into data records that can enter enterprise screening, review and data governance workflows.
Collect
Continuously compiling catalogues, notices and related rule documents published by government departments.
source.capture()Parse
Extracts structurable catalogue and rule fields from PDF, HTML and similar sources.
document.parse()Normalize
Unifies field formats for dates, commodity codes, control codes, rule types and source information.
schema.normalize()Rule normalisation
Organises the catalogue entries, notices, codes and descriptions for one rule into a unified data record.
record.resolve()Version linking
Records source files, effective periods and identifiable version relationships between rules.
version.link()Data delivery
Integrate into the customer’s existing systems through structured data or API per the project plan.
data.deliver()Customers no longer need to maintain the original web pages and PDFs,Free up more effort for actual screening, verification and business decisions.
One data layer covering multiple trade controls lookup needs
Data scope, fields, delivery method and update requirements are governed by the service plan both sides finally confirm.
API 01
Import/export licence catalogue data
Converts the annual import/export licensing catalogues into uniformly structured data records.
Organisable fields
- Import/export direction
- Goods name
- Commodity code
- Licence type
- Administration notes
- Effective date
- Source notice
- Data version
Applies to:ERP, customs systems, order review, product management and internal trade rule libraries.
API 02
Dual-use items control data
Organises dual-use related control codes, item descriptions, technical conditions and public sources into searchable data records.
Organisable fields
- Control code
- Item category
- Item description
- Commodity code mapping (when provided in the source data)
- Technical conditions
- Control notes
- Effective date
- Source file
Identifying dual-use items is not simply HS code matching.For specific products, further verification against technical parameters and current regulatory requirements is still required.
Applies to:Manufacturers, export compliance systems, product master data systems and trade review workflows.
DATA 03
Rule source and version data
Retains rule source, effective date, publish information and version relationships in the structured record.
Organisable fields
- File name
- Issuing authority
- Publish date
- Effective date
- Lapsed / supersession relationship
- Data source link
- Data update time
Applies to:Internal audit, rule traceability, historical review and data governance.
Explore the data structureMore than a "hit or no hit" answer
Retains the context needed for further business judgement.
The field structure is organised around rule type, import/export direction, commodity and control codes, technical conditions, effective dates and source information, so teams can continue screening, verifying and linking.
Actual fields depend on the specific data source and service plan.Fields not present in the source file are not filled in without basis.
TradeControlRecordField structure
record_id- —
rule_type- Dual-use items / licence catalogues
trade_direction- Export / import
commodity_name- Industrial electronic components
hs_code- 85********
control_code- —
control_description- Structured summary
technical_conditions- —
license_type- —
effective_from- YYYY-MM-DD
effective_to- —
source_authority- Ministry of Commerce / General Administration of Customs
source_document- Original notice
source_url- —
data_version- —
updated_at- —
Getting trade controls data into real business processes
Connect public rule data into existing order, product, supply chain and customs workflows, and route candidate records to business or compliance staff for further review.
Foreign trade companies | before order review
Before accepting export orders or arranging shipment, look up the relevant licence catalogues and control rules based on product information, and pass records that may need further verification to business or compliance staff.
ResultReduces the work of opening catalogues and notices one by one to search manually.
Manufacturers | product classification and maintenance
Maintain commodity codes, control codes, related rules and the reasoning behind them around your product library, using public rule data as one of the foundations for internal item classification.
ResultHelps product, legal and compliance teams share a single set of rule data.
ERP / SaaS｜System integration
Integrates trade licensing and dual-use item data into order, product, supply chain or customs features.
ResultAvoids SaaS teams maintaining multiple government data sources long term themselves.
Customs and trade service platforms | bulk screening
Match rules against customer product data and route records that may involve licensing or dual-use requirements into manual review.
ResultTurns public rule lookups from one-off manual work into a repeatable data process.
Trade controls data is not a static table
The following is a snapshot of public information at the time the page was produced, to illustrate catalogue counts, effective dates and the update characteristics of the original data sources.
Export goods subject to licence administration listed when the 2026 export licence catalogue was published
Based on the Catalogue of Goods Subject to Export Licensing (2026) issued by the Ministry of Commerce and the General Administration of Customs.
Main implementation dates of the relevant 2026 annual catalogues
Different specific policies and subsequent notices may have their own effective dates; the corresponding document prevails.
The import/export licence catalogue update frequency shown on the Ministry of Commerce open data platform
This is the update characteristic of the original public data source and does not represent GooFuture service sync frequency.
The above is a snapshot of public information at the time the page was produced, solely to illustrate the characteristics of the data.For specific business determinations, the laws, regulations, regulatory requirements and government-published information in force at the time prevail.
What GooFuture really handles is "data usability"
From multi-source parsing and field standardisation to organising source and effective information — so public rules can be used continuously by enterprise systems.
Multi-source structure unification
Subject:PDF, HTML, notices, annual catalogues. Reduces duplicated parsing logic across business systems for different web pages and files.
Different formats → unified fieldsCode field standardisation
Subject:Commodity codes, control codes and other identifiable codes — for queries, filtering and internal data linking.
Scattered fields → unified structureSource retained
Subject:Each structured rule record. Query results can always be traced back to the original document for further verification.
Isolated data → traceable sourceEffective date organisation
Subject:Publish date, effective date and clearly identifiable repeal or supersession information, so you can tell which version of the rules you are looking at.
Static files → time-dimensioned dataOngoing maintenance
Subject:Catalogue and rule changes published later by the public data sources — reducing the cost of maintaining public data sources internally.
One-off download → continuously maintained data serviceFrom data requirements to system integration
Confirm the actual data scope and delivery conditions first, then integrate into your existing systems per the project plan.
- 01
Contact a consultant
Tell us the data scope you need, your business scenario, expected usage and your current systems.
- 02
Confirm the data plan
Both sides confirm data scope, fields, delivery method, call volume, update requirements and technical support needs.
- 03
Start integration
Provide the data description and delivery method per the final plan, for the customer to integrate into existing systems.
Confirmed jointly before integration
- Data scope and fields
- Delivery method and call volume
- Update requirements
- Technical support needs
Choose a plan by data scope and usage
Pricing depends on data scope, call volume, update requirements, delivery method and technical support needs.
Basic
A single data catalogue or low-frequency business lookups.
Contact a consultant
- Data scope confirmed per plan
- Structured data delivery
- Base field description
- Call volume as agreed in the plan
Standard
Companies that need to integrate multiple trade licensing datasets into internal systems.
Contact a consultant
- Multiple catalogue data types
- Unified field structure
- Source information
- Call volume as agreed in the plan
- Update requirements as agreed in the plan
Professional
ERP, SaaS, supply chain or trade service platforms.
Contact a consultant
- Multiple trade controls data types
- Rule source and version fields
- System integration support
- Higher-volume plans
- Technical integration support
Enterprise
Large enterprises, platforms or customers with special data requirements.
Contact a consultant
- Custom data scope
- Custom fields and delivery plan
- Enterprise usage plan
- Data update plan
- Technical support plan
FAQ
Straight answers on public sources, query boundaries, system integration, historical versions and billing.
Why not just use the Ministry of Commerce or Customs public data directly?
You can query the public data directly. GooFuture’s value is not in replacing government websites but in organising catalogues, notices and differently formatted data into a unified structure that makes system integration, bulk processing and internal data maintenance easier.
Where does the data come from?
Data is mainly compiled from catalogues, notices and related information publicly published by government departments including the Ministry of Commerce and the General Administration of Customs of the People's Republic of China. Each record retains the corresponding source file and timing information wherever possible for further verification.
Can I determine whether a product is a dual-use item from its HS code?
A final conclusion cannot be drawn from an HS code alone. Some public data maps commodity codes to control information, but identifying a specific item may also involve control codes, technical parameters, performance, use and other regulatory conditions. GooFuture can provide the relevant rule data for enterprise screening and further review.
Can I query the Catalogue of Goods Subject to Export Licensing?
We can organise structured data around the public export licensing catalogue, including fields that can be confirmed in the source document such as goods name, commodity code, administration requirements, effective information and source. The exact queryable fields depend on the final data plan.
Does it include the Catalogue of Goods Subject to Import Licensing?
We can include the public import licensing catalogue in the data scope and use a unified data structure with export licensing and related trade controls data. Exact coverage is governed by the service plan both sides confirm.
How often is the data updated?
Government data is not published on a fixed schedule. GooFuture maintains the data as the public sources change; the exact sync frequency and update service are agreed in your data plan. This page does not promise unconfirmed real-time or fixed hourly updates.
Can it be integrated into ERP or SaaS systems?
Structured data delivery suited to system integration can be provided per the project plan. REST API, JSON data, call volumes and other technical requirements are confirmed before integration, per the actual technical proposal.
Can GooFuture query results be used directly as an export compliance conclusion?
No. GooFuture provides a structured data service based on public trade control information for lookup, screening and business process reference. It does not constitute legal advice and does not replace a company’s professional verification of commodity classification, technical parameters, end user, end use, destination and current regulatory requirements.
Do you support historical rule and version lookups?
The data model can retain source files, publish dates, effective dates and clearly identifiable rule version information. The exact historical coverage and queryable range should be confirmed during project integration; this page does not promise data ranges that have not been organised.
How is pricing calculated?
We currently work on a consultative enterprise basis. Pricing depends on data scope, call volume, update requirements, delivery method and technical support needs — contact a GooFuture consultant for a proposal.
No more re-organising public trade controls data for every system
From catalogue collection and field cleaning to organising rule sources and versions, GooFuture converts scattered public trade licensing and dual-use item data into a data layer suited to enterprise systems.