Direct answer

Identify, list-screen, catch-all, record the date — then licence or stop.

Step 1: write a technical identity (not the SKU nickname). Step 2: screen the current dual-use list and any other applicable China catalogues or temporary notices. Step 3: if unlisted, run end-user and end-use catch-all. Step 4: record the list version, the conclusion, and who signed. Step 5: if controlled, apply for a licence; if prohibited, do not export. Repeat when specs, user, destination or the list change. Foreign-list screening is extra if the group has US/EU exposure. This is a method page; it does not classify your SKU.

The classification screen

4 questions before you choose the route.

This page identifies the right question and evidence. It does not determine the legal outcome on a reader’s facts.

01

Can engineering describe the item in list language?

Parameters, software functions, materials.

Identify
02

What official list version did you open today?

Save the extract.

List
03

What are the end user and end use?

Catch-all even if list-negative.

Catch-all
04

Who owns the memo?

A named exporter, not the forwarder.

Owner

Working rule: Map the regulated role before marketing or launch in China.

What changes the answer

The signal ledger.

These facts move the question beyond a label and into a product, money-flow and control analysis.

Signal
Ask the operating question
Why it changes the route
Forwarder HS only
Is the ‘check’ a customs broker email?
That is not a control-list classification.
Spec change
Did R&D raise a parameter after the memo?
Re-check; old memos die.
No date
Can you show which list version you used?
Undated clearance is indefensible.
Prepare before you escalate

Bring a compact evidence docket—not a pitch deck.

Give a compliance team or counsel the operating facts that reveal the perimeter.

01Technical identityDatasheet and the engineer’s note.
02List extractsDated official catalogue and notices.
03User/use KYCCatch-all file.
04Signed memoConclusion, author, shipment or deal ID.
Common confusions

Questions people ask before they build.

Short answers for orientation. The right result can change with the service model and current rules.

Can AI or a public chart classify for us?

Not as the record. Tools can assist. The exporter signs the memo against official texts.

How often do we re-check?

On every spec, user or destination change, and whenever the tracker shows a list amendment that could touch your catalogue.

Primary authorities

Reviewed sources support orientation, not a fact-specific assessment.