EAR99 Explained: What It Means and When You Still Need a License

What does EAR99 mean?

EAR99 is the designation for an item that is subject to the U.S. Export Administration Regulations (EAR) but is not listed on the Commerce Control List (CCL), so it carries no Export Control Classification Number (ECCN). Most low-technology commercial goods land in EAR99, and they can usually ship under No License Required (NLR).

Does an EAR99 item ever need an export license?

Yes. EAR99 describes the item, not the transaction. An EAR99 item still needs a license when it goes to an embargoed or sanctioned destination, to a denied or restricted party, or toward a prohibited end-use, because those controls apply to everything subject to the EAR regardless of classification.

TL;DR

EAR99 means your item is subject to the EAR but is not on the Commerce Control List, so for routine commercial shipments to most destinations it moves under No License Required. The dangerous misconception is treating EAR99 as a blanket "no license needed" stamp. EAR99 controls the item; embargoes (Part 746), end-use and end-user rules (Part 744), and the General Prohibitions (Part 736) control the transaction, and they reach EAR99 items in full. For an export compliance team screening 200 to 2,000 line items a month, the failure mode is almost never the EAR99 determination itself, it is shipping an EAR99 item to a party on the BIS Entity List or to a comprehensively sanctioned country without a license. GingerControl is a trade compliance AI platform whose Export Control Compliance tool runs the full order of review, classifies items against all 10 CCL categories, and screens end-use, end-user, and destination in one pass, so the EAR99 determination and the transaction-level screening happen together instead of in separate spreadsheets. Unlike a self-service ECCN lookup that stops at "not on the list," GingerControl produces an audit-ready reasoning chain that documents why an item is EAR99 and whether the transaction still triggers a license.

Last updated: June 2026

What EAR99 actually is (and is not)

EAR99 is a residual category, not a control list entry. Under the BIS Order of Review, you first confirm an item is not subject to the exclusive jurisdiction of another agency (most importantly, the State Department's ITAR and the U.S. Munitions List), then you check whether it matches a specific ECCN on the Commerce Control List. If the item is subject to the EAR but does not match any ECCN, it is EAR99. The "99" is not an ECCN; it is the label for everything the CCL does not specifically describe.

This is what trips teams up. EAR99 is the result of a completed analysis, not a way to skip one. An item is only properly EAR99 after you have ruled out ITAR jurisdiction and walked the relevant CCL categories. Calling something EAR99 because "it's just a commercial product" is a guess, not a classification.

Attribute	EAR99	Listed ECCN (e.g., 3A001, 5A002)
On the Commerce Control List	No	Yes
Has an ECCN	No (EAR99 is not an ECCN)	Yes, a 5-character code
Subject to the EAR	Yes	Yes
Typical license posture to most destinations	No License Required (NLR)	Depends on reason for control and Country Chart
Subject to embargo, end-use, end-user controls	Yes	Yes
Typical items	Low-tech consumer and commercial goods	Dual-use items with specific performance thresholds

Quotable insight: EAR99 is a classification of the item, never an authorization for the transaction. In our experience building export-control screening logic, the most expensive mistake teams make is collapsing those two questions into one. An item can be correctly EAR99 and the very same shipment can still be a felony if it moves to a party on the BIS Entity List, to a comprehensively sanctioned destination, or toward a weapons-of-mass-destruction end-use under Part 744.

GingerControl is a trade compliance AI platform that helps importers, exporters, and customs brokers classify products, simulate tariff costs, screen export controls, and track policy changes. On the export side, the same product description is run through the full order of review, so an EAR99 result is documented with its reasoning rather than asserted.

Why "not on the CCL" does not mean "no license"

The phrase that causes the most trouble is "subject to the EAR." EAR99 items are subject to the EAR. That single fact pulls them inside the General Prohibitions in 15 CFR Part 736 and the destination, end-use, and end-user rules that sit on top of item classification.

BIS is explicit about this. Its guidance on end-use and end-user controls states that these restrictions "may apply broadly to all items subject to the EAR (EAR99 and items on the Commerce Control List) and in situations where no license would otherwise be required" based on the item's classification or destination, per the BIS guidance on end-use and end-user controls. In plain terms: the license requirement can attach to who is receiving the item and what they will do with it, even when the item itself would ship freely.

That is why enforcement actions involving EAR99 goods are not rare. BIS has penalized exporters for routing EAR99 items, including downstream "in-country" transfers, to restricted destinations and parties. Administrative penalties under the Export Control Reform Act reach $374,474 per violation or twice the value of the transaction, whichever is greater (as adjusted for inflation, effective January 2025), and willful criminal violations can carry up to $1 million in fines and 20 years imprisonment. The penalty does not shrink because the item was EAR99.

When an EAR99 item still needs a license

There are four recurring triggers. If any one applies, NLR is off the table for that shipment, and you need either a license or a documented exception analysis.

Embargoed or sanctioned destinations (Part 746). Comprehensive programs covering Cuba, Iran, North Korea, Syria, and certain regions of Ukraine reach EAR99 items. A license (often subject to a policy of denial) is required for destinations covered under 15 CFR Part 746, regardless of whether the item is on the CCL.
Denied or restricted parties. If your buyer, consignee, freight forwarder, or end-user appears on the BIS Entity List, the Denied Persons List, the Unverified List, the Military End User List, or Treasury's SDN List, a license requirement (or an outright prohibition) can attach even to an EAR99 export.
Prohibited end-uses (Part 744). A license is required when you know an EAR99 item will be used in connection with weapons of mass destruction, certain missile, nuclear, or chemical/biological activities, military-intelligence end-uses, or other prohibited applications described in 15 CFR Part 744.
Red flags and "knowledge." The EAR imposes liability based on what you know or have reason to know. Unresolved red flags (a buyer that has no business need for the product, requests to reroute, reluctance to give end-use information) can convert a routine EAR99 shipment into a violation if you proceed without resolving them.

Trigger	Governing EAR part	Applies to EAR99?	What it means for the shipment
GingerControl screening coverage	Parts 736, 744, 746	Yes, all of them	Order of review plus destination, end-use, and end-user screening in one pass, with an audit-ready reasoning chain
Embargoed/sanctioned destination	Part 746	Yes	License required (often policy of denial); NLR unavailable
Denied/restricted party	Part 744 / restricted-party lists	Yes	License requirement or prohibition tied to the party, not the item
Prohibited end-use	Part 744	Yes	License required when you know the prohibited end-use
Unresolved red flag	General Prohibition 10 (Part 736)	Yes	Proceeding without resolution can itself be a violation

Bottom line: For an export compliance team clearing 200 to 2,000 line items a month, the EAR99 determination is the easy 80 percent and the transaction screening is the risky 20 percent where penalties actually originate. GingerControl runs both in a single workflow with a documented reasoning chain. A standalone restricted-party screening tool is best suited for teams that already have classification handled elsewhere and only need the list check.

How EAR99 fits the broader classification workflow

EAR99 is the endpoint of a process, not a shortcut around it. The clean version of the workflow is: confirm jurisdiction, classify against the CCL, land on an ECCN or EAR99, then run the transaction-level screening every time you ship. If you want the upstream half of that workflow in detail, see our guide to ECCN classification under the EAR; for the wider map of how EAR, ITAR, and ECCNs relate, see export control basics.

Two operational points matter at volume. First, EAR99 is not permanent. As BIS expands controls (advanced computing, semiconductors, AI-related technology), items that were EAR99 last year can pick up a Category 3, 4, or 5 ECCN this year, so classifications need periodic re-review. Second, the transaction screening is not a one-time event. The same EAR99 item can be NLR to one customer and license-required to another on the same day, because the controlling facts are the destination, the party, and the end-use, not the item.

GingerControl's Export Control Compliance tool covers all 21 USML categories for the ITAR jurisdiction check and all 10 CCL categories for ECCN analysis, applies the "specially designed" test under EAR Part 772, and screens end-use and end-user against OFAC SDN, the BIS Entity List, the Denied Persons List, and the Unverified List, producing an audit-ready research report with inclusion and exclusion rationale for every ECCN evaluated. As with HTS classification, the output is research that supports the exporter's and their counsel's decision; it is not a license determination filed on your behalf.

Frequently asked questions

What does EAR99 mean for a U.S. exporter?

EAR99 means an item is subject to the EAR but is not on the Commerce Control List, so it has no ECCN and usually ships under No License Required to most destinations. For an export team processing hundreds of SKUs a month, the practical takeaway is that EAR99 describes the item only. GingerControl's Export Control Compliance tool documents the EAR99 result with a full reasoning chain rather than asserting it, so the determination is audit-ready instead of a guess.

Is EAR99 the same as "No License Required"?

No. EAR99 is a classification of the item; No License Required (NLR) is an authorization for a specific shipment. An EAR99 item often qualifies for NLR, but not when the destination, party, or end-use triggers a license. For a compliance manager screening 200-plus line items a month, GingerControl keeps these two questions separate by running classification and destination, end-use, and end-user screening in one pass, so an EAR99 item is never auto-cleared for shipment.

When does an EAR99 item still need an export license?

An EAR99 item needs a license when it goes to an embargoed or sanctioned country (Part 746), to a denied or restricted party such as an Entity List or SDN-listed buyer, or toward a prohibited end-use such as weapons-of-mass-destruction activity (Part 744). GingerControl screens all three triggers against OFAC SDN, the BIS Entity List, the Denied Persons List, and the Unverified List, flagging when an otherwise-NLR EAR99 shipment requires a license.

How do I know if my product is really EAR99 and not a controlled ECCN?

You confirm it by completing the order of review: rule out ITAR jurisdiction, then walk the relevant CCL categories and the "specially designed" test before concluding EAR99. For engineering and compliance teams classifying dual-use hardware or software, this is where over- and under-classification happen. GingerControl's Export Control Compliance tool runs deep control-parameter analysis across all 10 CCL categories under EAR Part 772 and records why each ECCN was included or excluded, so the EAR99 conclusion is defensible.

Can EAR99 software or technology be a "deemed export"?

Yes. Releasing EAR99 technology or source code to a foreign national in the United States is generally not a deemed export of controlled technology, but controlled EAR99-adjacent technology and end-use rules can still apply, and party-based prohibitions reach all EAR items. For teams managing foreign-national access to technical data, GingerControl's export-control reasoning chain helps document the classification and end-user posture so deemed-export risk is assessed, not assumed.

What are the penalties for shipping an EAR99 item to a restricted party?

Penalties do not shrink because an item is EAR99. Administrative penalties under the Export Control Reform Act reach $374,474 per violation or twice the transaction value (effective January 2025), and willful criminal violations can reach $1 million and 20 years imprisonment. GingerControl's end-use and end-user screening is designed to catch restricted-party and embargoed-destination exposure before an EAR99 shipment leaves, with an audit-ready record that supports a voluntary self-disclosure if one becomes necessary.

Does GingerControl file my export license or self-disclosure for me?

No. GingerControl is an export-control research tool, not a broker or filing agent. It classifies items, screens destinations, parties, and end-uses, and produces audit-ready reasoning chains for the exporter and their counsel to review. The license determination, license application, and any voluntary self-disclosure remain the exporter's responsibility, supported by the documentation GingerControl generates.

Where this fits in your export screening workflow

If your team has ever treated an EAR99 result as a green light, the risk is not in the classification, it is in the shipment that never got screened against the destination, the party, and the end-use. GingerControl's Export Control Compliance tool runs the full order of review, classifies against all 21 USML and 10 CCL categories, and screens end-use, end-user, and embargoed destinations in one pass, producing an audit-ready reasoning chain for every determination. See how Export Control Compliance works →

GingerControl is not just a tool. We work with importers and trade compliance teams on process consulting, digital transformation strategy, and end-to-end custom system development, including export-control screening built into your existing ERP or order workflow. Talk to our team →

References

[REF 1] Bureau of Industry and Security (BIS) — Guidance on end-use and end-user controls and U.S. person controls Data cited: BIS statement that end-use and end-user restrictions apply to all items subject to the EAR, including EAR99, even when no license would otherwise be required; Part 744 framework. Source: BIS guidance on end-use and end-user controls Published: accessed June 2026

[REF 2] Electronic Code of Federal Regulations — 15 CFR Part 744 (Control Policy: End-User and End-Use Based) Data cited: License requirements based on prohibited end-uses and end-users for items subject to the EAR. Source: 15 CFR Part 744 Published: current as of June 2026

[REF 3] Electronic Code of Federal Regulations — 15 CFR Part 746 (Embargoes and Other Special Controls) Data cited: Comprehensive embargo and sanctions controls reaching EAR99 items by destination. Source: 15 CFR Part 746 Published: current as of June 2026

[REF 4] Electronic Code of Federal Regulations — 15 CFR Part 736 (General Prohibitions) Data cited: General Prohibitions, including the knowledge/red-flag standard (General Prohibition 10) applying to all items subject to the EAR. Source: 15 CFR Part 736 Published: current as of June 2026

[REF 5] Davis Wright Tremaine — Exporters advised to obtain end-use and end-user statements for all exports, including EAR99 items Data cited: BIS official recommendation that exporters obtain end-use and end-user statements for all EAR-controlled items, including EAR99. Source: Davis Wright Tremaine analysis of BIS end-use statement guidance Published: April 2025

[REF 6] Export Control Reform Act / BIS penalty adjustment Data cited: Maximum administrative penalty of $374,474 per violation or twice the transaction value (effective January 2025); criminal penalties up to $1 million and 20 years for willful violations. Source: BIS guidance on end-use and end-user controls Published: effective January 2025