Most export violations start with a wrong ECCN. Under the EAR the ECCN classification feeds every later decision (licence, licence exception, screening, filing), so an early mistake carries all the way through. Below are the ECCN classification mistakes we see most often and how to avoid each one.
The cost runs both ways. An export may go without a required licence, which can lead to civil penalties, loss of export privileges and, for wilful violations, criminal liability. A wrong ECCN can also cause unnecessary licence applications and delays.
1. Classifying from the heading
The heading of 5A001 says telecommunications systems, but the item is 5A001 only if it meets a paragraph. Headings describe a family; paragraphs classify. An item can fit a heading and still meet no paragraph, or meet a different entry entirely. Always compare the item's parameters with the Items paragraph and name the paragraph in your record. See how to read an ECCN entry.
2. Assuming EAR99
"It's a commercial product, so it must be EAR99" is the single most expensive assumption in export control. Laptops, routers, oscilloscopes and industrial sensors are usually not EAR99. They are caught by 9xx entries such as 4A994, 5A992, 3A992 or 6A993. Treat EAR99 as a conclusion and run the EAR99 check before you record it.
3. Skipping jurisdiction
If an item is on the U.S. Munitions List, no ECCN applies. Items developed for military programmes, or parts specially designed for defense articles, need an ITAR check first. Start with ITAR vs. EAR.
4. Ignoring the Order of Review
Supplement No. 4 to Part 774 requires checking the 600 series and 9x515 entries before the rest of the CCL. A component that looks generic may be a 600 series ".x" item because it is specially designed for a military end item. Follow the order every time. The 600 series ECCN guide shows how those entries work.
5. Misreading "specially designed"
Treating "specially designed" as "designed for" catches too much, and ignoring it catches too little. The definition in § 772.1 is a two-step test. Paragraph (a) catches, and paragraph (b) releases (for example standard parts, items in production with EAR99 or AT-only equivalents, general-purpose items). Apply both steps in order, as set out in the specially designed definition.
6. Skipping notes and technical notes
Notes exclude items ("does not control…"), and technical notes define how parameters are measured. An item that seems caught may be released by a note. A value may be caught once it is measured the prescribed way. Read every note attached to the paragraph.
7. Getting units and thresholds wrong
Boundary errors are common: Kelvin vs. Celsius, TOPS vs. TPP, "exceeding" vs. "equal to or more than". Convert to the entry's units and apply the comparison exactly as written.
8. Using the wrong product group
Typical cases are classifying software in group A because the hardware is 5A002, or classifying technology as software. Classify what you export. Product groups A–E explains the split.
9. Relying blindly on someone else's ECCN
A manufacturer's ECCN covers the product as they sell it. Once you modify, integrate or re-program it, that ECCN no longer covers it. Check it against the entry and record the source; see where manufacturers publish their ECCNs.
10. Never revisiting the classification
The CCL changes: new entries (such as 3A090 and 4A090 for advanced computing), revised thresholds, items moved from the USML. Products change too. Review classifications when either changes, and record which version of the regulation each one was made against.
11. Confusing classification with licensing
An ECCN does not mean a licence is needed, and EAR99 does not mean no licence is needed. The licence decision combines the ECCN's reasons for control, the destination on the Commerce Country Chart, the end use and the end user.
A checklist for catching ECCN classification mistakes
Use these questions when you review a classification record, your own or someone else's:
- Is jurisdiction documented (not on the USML)?
- Was the Order of Review followed, with the 600 series and 9x515 checked first?
- Does the record name the paragraph as well as the entry?
- Were the item's parameters compared in the entry's units?
- Were notes, technical notes and "specially designed" applied?
- If EAR99, are the categories and 9xx entries reviewed listed?
- Is the source recorded (own analysis, manufacturer, CCATS)?
- Is the regulation version and date recorded?
- Has anything changed since: the product, the CCL, the customer's use?
What to do when you find a mistake
Correct the classification in your records and systems straight away, so future shipments are right. Then look back. Were any past exports made under the wrong classification that required a licence? If so, take legal advice on a voluntary self-disclosure to BIS under Part 764. Disclosure is treated as a significant mitigating factor in penalty decisions. Finally, fix the cause, whether that is a missing step in the procedure, a training gap or an outdated source. Self-classification vs. a BIS request covers how to build a sound internal procedure.
How ECCN.help handles these checks
The ECCN.help Classification Workflow is built around these mistakes. It checks the ITAR before the EAR and follows the Order of Review. It classifies on paragraphs, applies the "specially designed" test step by step and converts units before comparing figures. EAR99 comes only after every entry is ruled out, and the workflow keeps a dated record of every answer and the regulation version behind it. It is rule-based, with no AI, so it cannot invent an ECCN that does not exist.
ECCN.help provides research and assistance, not legal advice. Verify every result against the regulation.