Export Classification — ECCN, EAR99, NLR & CCL

Regilient codifies Commerce Control List logic to classify products, compute license requirements per destination/end-use, and produce auditable justifications with reviewer sign-offs.

ECCN

EAR99

NLR

CCL

Country Chart

License Exceptions

Key Capabilities

1Decision flows for ECCN determination by CCL category & product attributes
2EAR99 handling with automatic NLR vs License Required evaluation
3Country Chart mapping, reasons for control, and license exceptions
4Denied party/end-use/end-user screening integration
5Evidence, notes, and 4-eyes approval with change history

How It Works

Ingest item specs and intended destinations/end-use.

Run CCL decision trees to assign ECCN or confirm EAR99.

Calculate license needs using reasons for control + Country Chart.

Check screening hits; apply license exceptions where eligible.

Publish classification pack (rationale, controls, approvals) to ERP/TMS.

Operational Benefits

Defensible, repeatable ECCN/EAR99 decisions with full audit trails

Faster shipment releases and fewer export holds

Centralized evidence and license tracking across SKUs

Export Classification Implementation & Advisory Services

Implementation (3–6 weeks)

CCL decision-tree configuration by product family
Country Chart & license exception logic setup
ERP/TMS integration and reviewer workflows

Outcome:

Live classification process with first item set approved.

Advisory (Quarterly)

Regulatory updates and ECCN migration support
License exception eligibility reviews
Audit prep and documentation remediation

Outcome:

Reduced audit risk and consistent decision quality.

Managed Service (MSP)

Bulk classification for catalogs/BOMs
License determination and exception checks
Screening review and escalation handling
SLA: classification pack in 5 business days

Outcome:

Scalable export compliance without headcount spikes.

Export Classification: Manual vs Software

ECCN Logic

Manual (Spreadsheets)

Expert-only narratives

Software (Regilient)

Codified decision trees & notes

License Needs

Manual (Spreadsheets)

Ad-hoc lookups

Software (Regilient)

Automated Country Chart + exceptions

Screening

Manual (Spreadsheets)

Separate systems

Software (Regilient)

Integrated hits & escalation workflows

Evidence

Manual (Spreadsheets)

Unstructured folders

Software (Regilient)

Linked rationale, dates, and approvals

Process Area	Manual (Spreadsheets)	Software (Regilient)
ECCN Logic	Expert-only narratives	Codified decision trees & notes
License Needs	Ad-hoc lookups	Automated Country Chart + exceptions
Screening	Separate systems	Integrated hits & escalation workflows
Evidence	Unstructured folders	Linked rationale, dates, and approvals

Typical Roles & Actions

Trade Compliance

Typical Actions (examples)

Own ECCN logic, approve classifications, oversee licenses

Engineering

Typical Actions (examples)

Provide technical parameters (encryption, performance, materials)

Logistics

Typical Actions (examples)

Apply NLR/license flags on shipments, retain records

Role	Typical Actions (examples)
Trade Compliance	Own ECCN logic, approve classifications, oversee licenses
Engineering	Provide technical parameters (encryption, performance, materials)
Logistics	Apply NLR/license flags on shipments, retain records

Confirm current EAR/CCL rules and destination controls before export. When in doubt, seek a commodity classification (CCATS) or legal opinion.

Export Classification Checklist

Gather item specs and destinations/end-use
Run ECCN decision tree or confirm EAR99
Evaluate license needs (Country Chart & exceptions)
Screen parties and end-use; resolve hits
Publish classification pack and retain records

FAQs for Export Classification

What is the difference between an ECCN and EAR99 classification?

An ECCN (Export Control Classification Number) is a five-character alphanumeric code for items specifically listed on the Commerce Control List (CCL) based on their technical parameters, performance characteristics, or designed end-use. EAR99 is the catch-all designation for items subject to the EAR but not listed on the CCL. Most commercial products are EAR99 and generally do not require a license, though restrictions still apply for embargoed countries, prohibited end-users, or prohibited end-uses.

When is an export license required for EAR99 items?

Even though EAR99 items are low-control, a license may be required if the item is destined for a comprehensively sanctioned country (e.g., Cuba, Iran, North Korea, Syria), a restricted end-user on the Entity List, or a prohibited end-use such as weapons of mass destruction. Exporters must perform due diligence screening before every shipment. Regilient integrates denied party and end-use screening into the classification workflow.

How do I determine if my product needs an ECCN?

Start by reviewing the Commerce Control List (CCL) categories 0 through 9 for descriptions that match your product's technical specifications. If your item is not described in any ECCN, it is classified as EAR99. You can also contact the manufacturer, check BIS's Classification Information Table, or submit a formal Commodity Classification Request (CCATS) to BIS. Regilient codifies CCL decision trees to automate this process.

What is the Commerce Country Chart and how does it affect licensing?

The Country Chart (EAR Part 738, Supplement 1) maps reasons for control against destination countries to determine whether a license is needed. Each ECCN lists its reasons for control. If a controlled reason and destination intersect with an "X" on the chart, a license is required unless a license exception applies. Regilient automates this cross-referencing and evaluates applicable license exceptions.

What happens if an export is misclassified?

Misclassification can result in penalties ranging from civil fines to criminal prosecution under the Export Administration Regulations. Penalties can reach up to $300,000 per violation for civil cases, or higher for willful violations. Companies may also face denial of export privileges. Regilient produces auditable classification packs with rationale, evidence, and 4-eyes approvals to demonstrate compliance.

Can export classifications sync with our ERP or trade management system?

Yes. Regilient publishes classification results, license requirements, and screening outcomes to ERP and TMS platforms via APIs and file feeds. This ensures logistics teams apply the correct NLR or license flags on shipments without manual re-entry, and compliance records are retained centrally.