1. Why "we said EAR99" is not enough
The most common pain in export-control routine is rarely that a product is controlled. It is that you say it is not, and then you have to prove it. Customer questionnaires want your basis. Auditors want the record from the year in question. Customs wants a classification code with a story behind it. EAR99 is a conclusion that the item falls under no control-list entry, and proving a negative takes more process than proving a positive. You have to show which entries you examined, which thresholds you compared, and why each was ruled out.
2. What self-classification is, and whether it is legitimate
The Export Administration Regulations allow exporters to determine their products' ECCN or EAR99 status themselves. This is called self-classification. It is entirely legitimate and it is how most companies operate daily. The alternative is requesting an official classification from BIS. The freedom comes with responsibility: the consequences of a wrong call sit with the exporter, so deciding correctly and proving it are inseparable. One reminder. Self-classified items shipped under encryption license exceptions carry additional procedural duties, such as the annual self-classification report. Classification done does not mean obligations done.
3. The official order of review: classification is a walked process, not a guessed entry
The Commerce Control List's official order of review gives a path you can retell and record:
- Find candidate entries from product characteristics: by category and technical parameters, list every entry that could plausibly apply. That includes the inconvenient ones, not just the favorable ones.
- Compare thresholds entry by entry: put the product's actual parameters (performance, key lengths, frequency, process node and so on) against each entry's thresholds and notes. Every "met / not met" needs a parameter source.
- Handle exclusion and relief notes: many entries carry exclusion notes or chapter-level carve-outs. Whether an exclusion applies deserves the same verbatim reading as the threshold itself.
- Only when nothing captures the item is it EAR99: after walking every relevant entry with a stated reason for each "not captured", the EAR99 conclusion can stand.
Each step of this walk produces recordable intermediates: the candidate list, the threshold comparison, the exclusion analysis. Those intermediates are your evidence. A conclusion reached by skipping the walk can only be reconstructed from memory when challenged.
4. What a defensible classification record contains
- Inputs and their sources: the value and provenance of every technical parameter used (spec-sheet version, engineering confirmation).
- Regulation version and date: which revision of the text you compared against. Regulations change, and a record without a version cannot be reproduced.
- Threshold-by-threshold comparison: met / not met / insufficient for each relevant threshold, with grounds, including exclusion notes.
- Conclusion and scope: the classification, which part numbers it covers, and an explicit statement of what this determination does not cover (for example, no transaction review).
- People and time: who decided, who reviewed, and when. Names and timestamps turn notes into evidence.
5. Five common mistakes
- Judging new shipments against old text: carrying conclusions across amendments without re-review. Records must pin the regulation version, and amendments must trigger re-checks.
- Recording the conclusion but not the basis: a one-line "this item is EAR99" is, under questioning, the same as no record.
- Treating EAR99 as "no obligations at all": EAR99 is only a classification conclusion. Destination, party and end-use screening still apply, as do embargoes and restricted-party lists.
- Missing procedural duties on encryption items: many encryption items shipped under license exceptions still carry annual self-classification reports or semiannual sales reports. Right classification with missed procedure is still a finding.
- Concluding from "approximately": when a threshold parameter is uncertain, the honest move is to record "insufficient information, pending" rather than pick the value convenient for the conclusion.
6. Disclaimer
This guide is general information, not legal advice. For case-specific classification and obligations, consult your counsel. The process described reflects a general reading of public regulations, and you should always cite the current official text.