How to Classify Dual-Use Products

A practitioner’s guide to ECCN determination under the Export Administration Regulations

An eccn.help educational reference. Citations are to 15 CFR Chapter VII, Subchapter C (the EAR), current as of early 2026. Verify against the live eCFR and the most recent Federal Register amendments before relying on any specific control parameter, list entry, or country designation — these change frequently.

The word “dual-use” causes more classification errors than any technical parameter

Most people learn the term “dual-use” before they learn how the EAR actually works, and the phrase quietly installs a false mental model. It suggests there is a category of “dual-use products” that the Commerce Department controls, sitting next to a category of “military products” that the State Department controls, with a clean line between them.

That is not how the regulation is built, and a classifier who carries that model will misjudge cases at the margin.

The EAR’s own introductory section is explicit about this. A “dual-use” item is one that has civil applications as well as terrorism and military or weapons-of-mass-destruction (WMD)-related applications — but the term is a colloquial description, not a jurisdictional boundary. The precise description of what is subject to the EAR lives in § 734.3, and that section does not limit the EAR to dual-use items. In the regulation’s own words, items subject to the EAR include purely civilian items, items with both civil and military applications, and items that are exclusively military but that do not warrant control under the ITAR (§ 730.3).

So “dual-use classification” is really shorthand for a much larger task: determining where any non-ITAR item sits in the U.S. export control system. The skill this article teaches is not “how to classify dual-use products” as a special category — it is how to run the classification analysis correctly for any item that lands on the Commerce side of the line.

The cardinal rule: three sequential questions, never one merged judgment

The single most common structural error in classification — the one that produces confident, well-written, and wrong answers — is collapsing three distinct regulatory questions into a single “what’s the ECCN and do I need a license?” reflex.

The EAR is built around three questions that must be answered in order, because each one is a precondition for the next:

1. Jurisdiction — Is the item subject to the EAR at all? (Part 734.) If another agency has exclusive jurisdiction, or the item is excluded from the EAR, you stop here and apply that agency’s rules. The EAR’s entire control apparatus is irrelevant to an item it does not reach.
   
2. Classification — What is it on the Commerce Control List? (Part 774, using the Order of Review in Supplement No. 4, and the Country Chart referenced in Part 738.) This produces an ECCN, or the designation EAR99. Classification by itself imposes no license requirement; it is a descriptive finding.
   
3. Licensing — Given the classification, the destination, the end-user, the end-use, and conduct, does anything require a license? (Parts 736, 738, 740, 744, 746.) This is where a control becomes an obligation.
   

These map directly onto the EAR’s “five facts” that determine your obligations: what the item is, where it is going, who will receive it, what they will do with it, and what else they do (§ 732.1(b); § 736.2(a)). Classification answers only the first of the five. A specialist who treats the ECCN as the answer has answered one-fifth of the question.

Keep these three separate on paper. Most defensible classification memos are organized exactly this way, and most enforcement findings trace back to two of them being silently merged.

Question 1 — Jurisdiction: Is the item subject to the EAR?

You cannot classify an item on the CCL until you have confirmed the CCL is the right list. Part 732 puts this first for a reason — Steps 1 and 2 are the only scope steps that matter for a U.S.-origin export, and they come before any look at the CCL.

Step 1 — Is the item under the exclusive jurisdiction of another agency?

The threshold question is whether the item is subject to the exclusive jurisdiction of another Federal agency (§ 732.2(a); § 734.3(b)). If it is, you comply with that agency’s regulations and skip the EAR entirely.

For most dual-use classification work, the agency that matters is the Department of State’s Directorate of Defense Trade Controls (DDTC), which administers the ITAR and its United States Munitions List (USML) at 22 CFR Part 121. The defining principle:

If an item is a defense article enumerated on the USML, it is ITAR-controlled, and it is not subject to the EAR — regardless of how “commercial” it may seem.

This is where the EAR/ITAR boundary lives, and it is the boundary that the CCL’s own structure constantly references. Open almost any “600 series” ECCN (military items moved to the CCL under export control reform) and you will see “Related Controls” notes pointing back to the corresponding USML category — for example, ECCN 9A610 (military aircraft and related commodities) carries the note that aircraft enumerated in USML Category VIII, and technical data directly related thereto, are subject to the ITAR; only the items not enumerated there fall to Commerce. Military electronics in 3A611, military vehicles in 0A606, military gas turbine engines in 9A619 — all are written as “what’s left after the USML.”

The practical test: read the USML category first. If your item is specifically enumerated, the analysis ends — it is ITAR. If it is military in character but not enumerated, it likely lands in a “600 series” or “9×515” ECCN on the CCL. The “specially designed” definition (discussed below) is the hinge that moves items across this line.

When the line is genuinely unclear, do not guess. The EAR tells you the formal mechanisms (§ 734.6):

• To test whether something is subject to the ITAR, review the USML (22 CFR 120.3, 120.6, 121.1) and, if needed, request a Commodity Jurisdiction (CJ) determination from DDTC (22 CFR 120.4).
• To confirm a Commerce classification, request a commodity classification (CCATS) from BIS through SNAP-R (§ 748.3). You have a right to request the classification of your item from BIS, and BIS has a corresponding duty to provide it (§ 732.3(b)(2)).

One caution the regulation states outright: a BIS commodity classification determination or advisory opinion is not a determination that the item is “subject to the EAR” — it cannot be relied on for the jurisdiction question itself (§ 734.3(d); § 734.6(b)). Jurisdiction and classification are different findings even when the same agency speaks to them.

Step 2 — Is the technology or software publicly available / published?

For technology and software, there is a second scope filter. Unclassified “technology” or “software” that has been published — made available to the public without restriction on further dissemination — is not subject to the EAR (§ 734.7; § 732.2(b)). The published-information channels the EAR recognizes include open subscriptions, public libraries, unlimited distribution at conferences, public posting on the internet, and submission for publication, among others. Fundamental research and information in published patents are treated in §§ 734.8 and 734.10.

There are important carve-outs the classifier must not miss:

• Encryption is the major exception. Encryption software classified under ECCN 5D002 remains subject to the EAR even when publicly available, except for publicly available object code whose corresponding source code meets the criteria in § 742.15(b) (§ 734.3(b)(3) note; § 732.2(b)).
• Firearms production “software”/”technology” under ECCNs 0A501, 0A506, 0A507, or 0A509 remains subject to the EAR (§ 732.2(b), referencing § 734.7(c)).

A principle that prevents half the panic in this field

The regulation states it plainly, and it is worth internalizing before you ever open the CCL:

The term “subject to the EAR” should not be confused with licensing or other requirements. Just because an item is subject to the EAR does not mean a license automatically applies (§ 734.2(a)(3)).

“Subject to the EAR” is a jurisdictional finding — it means BIS has authority over the item. Whether anything is actually required is the third question, decided later by classification, destination, end-user, end-use, and conduct. Conflating “subject to the EAR” with “controlled” or “license-required” is the jurisdiction-stage version of the merged-question error.

Question 2 — Classification: Finding the ECCN

Once you have confirmed the item is subject to the EAR and not exclusively another agency’s, you classify it against the Commerce Control List (CCL) — Supplement No. 1 to Part 774. The exporter, reexporter, or transferor is responsible for correctly classifying the item; doing it yourself without BIS assistance is permitted, but failure to classify correctly does not relieve you of a license obligation that the EAR imposes (§ 732.3(b)(1)).

Anatomy of an ECCN

An Export Control Classification Number is a five-character alphanumeric code. Reading it is the first skill:

3   A   0   0   1

│   │   └───┴───┴── entry number within the product group

│   └────────────── Product Group (A–E)

└────────────────── CCL Category (0–9)

First character — the Category (what kind of item it is):

Second character — the Product Group (what form the item takes):

These two characters already tell you a great deal. A piece of software for producing a controlled machine is a “D” entry; the machine itself is “A”; the underlying know-how is “E.” The same physical capability can appear in multiple entries across product groups, and the right one depends on the form you are exporting — hardware, software, or technology.

Third character — the reason-for-control grouping. Conventionally, the third digit reflects the multilateral regime or control rationale behind the entry (for example, items implementing Wassenaar national-security controls, Missile Technology Control Regime controls, Nuclear Suppliers Group controls, or the Australia Group/chemical-biological controls; “9” entries are typically unilateral or “other” controls). Treat this as orienting context, not as the operative control — the binding reasons for control are stated explicitly in each entry’s License Requirements section, not inferred from the digit.

Special series worth recognizing on sight:

• “600 series” (third character “6,” e.g., 0A606, 3A611, 9A610) — military items moved from the USML to the CCL.
• “9×515” — spacecraft and related items moved from the USML.
• “.y” paragraphs — specifically enumerated lower-sensitivity parts/components that are carved out of the broader control.
• “.x” / catch-all paragraphs — “specially designed” parts and components not elsewhere specified (see below).

The Order of Review: enumerated entries before catch-alls

The CCL must be read in a disciplined order. Supplement No. 4 to Part 774 — the Commerce Control List Order of Review — establishes the sequence you must follow when classifying an item subject to the EAR (§ 732.3(b)(1)). The discipline it enforces, and the single most-violated rule in classification:

Look for a specific, enumerated description of your item before you fall back on a catch-all “specially designed” control, and only designate EAR99 after you have ruled out every applicable ECCN.

A workable practitioner sequence:

1. Confirm scope (already done — Question 1). The Order of Review presumes the item is subject to the EAR and not on the USML.
2. Identify the candidate Category and Product Group from the item’s function and form. Use the BIS Interactive CCL or a keyword search as a finding aid, but never as the classification itself — keyword tools match headers and headings and will miss matches buried in subparagraphs.
3. Read the full entry, in order, for each candidate ECCN. An ECCN is not just its heading. You must work through:
   • the heading (the scope of the entry);
   • the License Requirements block (Reasons for Control and the Country Chart columns);
   • List Based License Exceptions;
   • and the List of Items Controlled, which contains the three pieces that decide most close cases — Related Controls (pointers to the USML or other ECCNs that take priority), Related Definitions, and the Items paragraphs (the actual technical parameters, a. through y.).
4. Match against the technical parameters. Control thresholds are decisive. An item is controlled by an ECCN only if it meets the specific parameters in the Items paragraphs — a stated performance level, dimension, concentration, frequency, accuracy, and so on. If the item falls below every threshold in an otherwise-relevant entry, that entry does not control it.
5. Resolve catch-all vs. enumerated. If a specific paragraph enumerates your item, use it. Only reach the catch-all “.x” (“parts and components specially designed for…”) when nothing more specific applies. The Related Controls notes routinely tell you which entry wins — e.g., an electronic component “specially designed” for a military aircraft controlled under USML Category VIII or ECCN 9A610 is controlled by the catch-all in 9A610.x, not by the general military-electronics entry 3A611 (3A611 Related Controls note).
6. If, and only if, no ECCN applies — EAR99.

“Specially designed”: the term that moves items across entries

A large share of dual-use parts-and-components classification turns on the defined term “specially designed” (defined in Part 772). It is the hinge that decides whether a generic-looking part is controlled because of what it was designed for. Catch-all paragraphs throughout the CCL (“…’parts,’ ‘components,’ ‘accessories,’ and ‘attachments’ that are ‘specially designed’ for a commodity controlled by this ECCN or a defense article…”) rely on it, as do the USML/CCL boundary notes.

Because the definition contains a multi-prong “catch” and “release” structure, you must apply the actual regulatory definition — not the colloquial sense of “made specially for this.” Two parts that look identical can classify differently based on their design history and whether they meet a release paragraph. When a classification depends on “specially designed,” cite the definition and walk each prong; do not assert the conclusion.

EAR99 is a residual designation, not a safe harbor

For items subject to the EAR but not listed on the CCL, the proper classification is EAR99 — a “basket” that appears at the end of each Category for items not specified under any ECCN (§ 732.3(b)(3); § 734.3(c)).

Two things every classifier must hold simultaneously:

1. EAR99 is a legitimate, affirmative classification — but only after the Order of Review has been run. “It’s probably EAR99” reached by skipping the CCL is not a classification; it is a guess wearing a label.
2. EAR99 is not an exemption from the EAR. This is the myth that produces the most expensive surprises. An EAR99 item is still subject to the EAR, and it remains fully exposed to the end-use, end-user, embargo, and conduct controls discussed under Question 3. General Prohibitions Four through Ten apply to all items subject to the EAR — both items on the CCL and items within EAR99 (§ 732.3(m); § 736.2(b)(4)–(10)). An EAR99 widget shipped to an Entity-List party, or to a prohibited military end-user, or for a WMD end-use, can require a license — and a denied one — exactly as a controlled item would.

A correct classification, in other words, never ends the risk analysis. It only finishes the second of three questions.

Question 3 — Licensing: From classification to a license decision

Classification produced a finding (“this is ECCN 3A001.a” or “this is EAR99”). Whether anything is required depends on combining that finding with destination, end-user, end-use, and conduct.

The list-based path: Reasons for Control + the Country Chart

For items on the CCL, the license requirement under General Prohibitions One, Two, and Three (the core “product” controls) is determined by reading the ECCN’s Reasons for Control together with the Commerce Country Chart (Supplement No. 1 to Part 738) — Steps 8–9 of Part 732.

Every controlled ECCN states one or more Reasons for Control, each tied to a Country Chart column. Common ones: NS (national security), MT (missile technology), NP (nuclear nonproliferation), CB (chemical/biological), RS (regional stability), CC (crime control), AT (anti-terrorism), FC (firearms convention), SS (short supply), UN (United Nations). For example, ECCN 6A007 is controlled for national security, missile technology, and anti-terrorism reasons (§ 732.3(d)(1)) — three columns to check.

The mechanic is precise (§ 732.3(d)(2)):

1. Note each Country Chart column identifier from the ECCN’s License Requirements (e.g., “NS Column 1,” “MT Column 1”).
2. On the Country Chart, find your destination row and read across to each relevant column.
3. An “X” in the cell for that country and that reason-for-control column means a license is required under General Prohibitions One, Two, and Three — unless a License Exception applies.
4. No “X” in any relevant column means no license is required under the CCL and Country Chart for that destination (the other prohibitions still must be checked).

Two situations where the Country Chart does not govern, and you go straight to the controlling part:

• Short supply (SS) controls — self-contained in Part 754.
• Certain ECCNs that state their own destination rules and carry no Country Chart column (e.g., 0A981 equipment for the execution of human beings — licensed to all destinations regardless of end-use; 0A982 law-enforcement restraint devices — all destinations except Canada). Read the entry; it tells you when the chart is bypassed (§ 732.3(d)(3); § 738.3(a)).
• Embargoed destinations — Cuba, Iran, North Korea, and Syria are governed by Part 746, not the Country Chart (§ 732.3(d)(4)).

License Exceptions

If the Country Chart says a license is required, a License Exception (Part 740) may overcome that requirement (Steps 20–24). Eligibility depends on the item, the destination, the end-use, and the end-user, and each exception has its own conditions; the List Based License Exceptions block in the ECCN (LVS, GBS, STA, etc.) tells you which are even potentially available for that entry. Note the critical limit: License Exceptions generally are not available to overcome General Prohibitions Four through Ten (§ 732.4(a)) — the end-use/end-user/embargo/conduct controls. You cannot exception your way past an Entity List requirement.

The override layer: why classification never closes the file

This is the section that separates a classifier from a compliance analyst. A low ECCN or an EAR99 designation tells you the item is not, by its nature, sensitive. It tells you nothing about whether the transaction is prohibited. The EAR layers a second control system on top of classification — end-use and end-user controls (Part 744) plus embargoes (Part 746) and the conduct prohibitions — and these apply in addition to, and independent of, the CCL.

Every one of these provisions uses the same construction: “In addition to the license requirements for items specified on the CCL…” That phrase is the regulation telling you classification is not the end of the analysis.

• Entity List (§ 744.16). A license is required to export, reexport, or transfer any item to a listed entity, per the License Requirement column of that entry — in addition to CCL requirements. Most listed entities carry a license requirement reaching items down to and including EAR99, and License Exceptions are generally unavailable. The 50% ownership rule extends these restrictions to majority-owned affiliates, and “knowledge” that a listed entity owns a transaction party triggers an affirmative duty to resolve the ownership question or obtain a license (§ 744.16; Red Flag 29, Supp. No. 3 to Part 732).
• Military end-use / end-user (§ 744.21). For specified destinations (including China, Russia, Belarus, Burma, Cambodia, Nicaragua, Venezuela), a license is required for listed items destined to a “military end use” or “military end user,” regardless of where the item sits on the CCL. “Military end use” reaches not only incorporation into military items but anything that supports or contributes to the operation, maintenance, development, or production of military items (§ 744.21(f)). (Note: portions of § 744.21 are subject to a stay running until November 2026 — confirm current text before applying.)
• Military-intelligence end-use / end-user (§ 744.22) and military end-use of microprocessors (§ 744.17) add further end-use controls; Supplement No. 1 to Part 744 gives concrete examples (a general-purpose microprocessor classified 3A991.a.1 used in cruise missiles, military radar, UAVs, etc.).
• Proliferation controls (§§ 744.2–744.6). Nuclear, chemical/biological, missile, and WMD-related end-use prohibitions reach items subject to the EAR — again, including EAR99 — when you know the item will be used in a prohibited activity.
• Embargoes (Part 746) and the conduct prohibitions — General Prohibition Four (denial orders), Five (prohibited end-use/end-user), Six (embargo), Seven (U.S.-person proliferation support), Eight (in-transit), Nine (license/exception terms and conditions), and Ten (proceeding with knowledge that a violation has occurred or is about to occur) — apply to all items subject to the EAR, not merely those on the CCL (§ 732.3(m); § 736.2(b)). General Prohibition Ten, and the “Know Your Customer” / red-flag guidance in Supplement No. 3 to Part 732, are the catch-all that converts ignored warning signs into liability.

The takeaway for training data and for human classifiers alike: the ECCN answers only one of the five facts. A complete analysis screens the destination against the Country Chart and Part 746, the parties against the Entity List, MEU List, and the Consolidated Screening List, and the end-use against Part 744 — every time, including when the item is EAR99.

The classification errors that recur

The following are the failure patterns that show up repeatedly in enforcement and in audits. They are worth memorizing as anti-patterns.

Treating “dual-use” as a jurisdiction. It is a colloquial description (§ 730.3), not a list. The jurisdiction question is answered by Part 734 and the USML, not by how civilian the item feels.

Merging jurisdiction, classification, and licensing. The most consequential structural error. Run them as three sequential questions and write them up separately.

Confusing “subject to the EAR” with “controlled” or “license-required.” Subject-to-EAR is a jurisdictional finding; license requirements are decided later by classification + destination + parties + end-use (§ 734.2(a)(3)).

Jumping to EAR99 (or to a catch-all) without running the Order of Review. EAR99 is the residual after the CCL has been checked, not a shortcut around it (Supp. No. 4 to Part 774; § 732.3(b)(3)).

Classifying off the heading and skipping the Items parameters. Control turns on the specific technical thresholds in the List of Items Controlled, not on the entry’s title or a keyword hit. Read the whole entry, including Related Controls and Notes.

Treating a low ECCN or EAR99 as a safe harbor. General Prohibitions Four through Ten — and the Entity List, MEU List, and proliferation end-use controls — apply regardless of classification (§ 736.2(b)(4)–(10); § 744.11; § 744.16; § 744.21).

Asserting “specially designed” by intuition. Apply the defined term’s catch-and-release prongs from Part 772; do not paraphrase it into “made for this.”

Relying on a stale CCL, Country Chart, or entity list. The lists, country groups, and control parameters change constantly — and several provisions are currently under temporary stays with hard expiration dates. A classification is only as current as the regulatory text it was run against.

A defensible classification workflow

A repeatable, auditable sequence — the structure a well-built classification memo (and a well-built training record) should follow:

1. Describe the item precisely. Function, form (commodity / software / technology), and the specific technical specifications that map to control parameters. An imprecise item description produces an indefensible classification.
2. Jurisdiction. Confirm the item is not exclusively controlled by another agency. Read the relevant USML category. For technology/software, screen for published/publicly-available status and the encryption and firearms carve-outs. Document the basis. Where unclear, note whether a CJ (DDTC) or CCATS (BIS) is warranted (§ 734.6; § 748.3).
3. Order of Review. Identify candidate Category/Product Group; read each candidate ECCN in full; match against the Items parameters and thresholds; resolve enumerated-vs-catch-all using Related Controls notes; reach EAR99 only after ruling out every ECCN (Supp. No. 4 to Part 774).
4. Record the classification finding with the controlling Items paragraph and the Reasons for Control, or an affirmative EAR99 determination with the basis for exclusion.
5. License determination. Apply the Reasons for Control against the Country Chart for the destination; check Part 746 for embargoed destinations; identify any potentially available License Exception and its conditions (Parts 738, 740, 746).
6. Override screening — every transaction, including EAR99. Screen all parties against the Entity List, MEU List, and Consolidated Screening List; screen the end-use against Part 744 (military, military-intelligence, and proliferation controls); resolve any red flags before proceeding (Part 744; Supp. No. 3 to Part 732).
7. Documentation and recordkeeping. Retain the analysis, sources, and dates of the regulatory text consulted (Part 762). The defensibility of a classification rests on the contemporaneous record, not on the conclusion.

Key takeaways

• “Dual-use” is a description, not a jurisdiction. The EAR controls far more than dual-use items, and the boundary that matters is EAR-vs-ITAR, decided by Part 734 and the USML — not by how commercial an item appears (§ 730.3; § 734.3).
• Three sequential questions, never merged: Is it subject to the EAR? What is it on the CCL? Does anything require a license? Classification answers only the second.
• Classification is a disciplined read, not a keyword match. Run the Order of Review; read the full entry; match the specific technical thresholds; prefer enumerated entries over catch-alls; reach EAR99 only as a residual (Supp. No. 4 to Part 774).
• The ECCN plus the Country Chart give you the list-based license requirement — but only for General Prohibitions One through Three (§ 732.3(d); § 738.4).
• Classification never closes the file. End-use, end-user, embargo, and conduct controls apply in addition to the CCL and reach EAR99 items, where License Exceptions generally are not available (§ 736.2(b)(4)–(10); §§ 744.16, 744.21; Part 746).
• A correct answer is a current answer. Verify against the live eCFR and the latest Federal Register actions; control parameters, country groups, list entries, and even active stays change on a rolling basis.

This article is educational and does not constitute legal advice. Export control classification and licensing determinations should be made against the current text of the EAR (15 CFR Parts 730–774) and the ITAR (22 CFR Parts 120–130), and, where the analysis is close or high-stakes, with formal BIS (CCATS) or DDTC (CJ) determinations and qualified counsel.

— eccn.help · TariffWolf