Key Capabilities

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

How It Works

01
processing

Ingest item specs and intended destinations/end-use.

02
truck

Run CCL decision trees to assign ECCN or confirm EAR99.

03
calculate

Calculate license needs using reasons for control + Country Chart.

04
success

Check screening hits; apply license exceptions where eligible.

05
file

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

Free Resource: Export Classification Playbook

Templates for ECCN logic capture, license exception checks, and documentation standards.

Download Guide
ebook

Operational Benefits

shield

Defensible, repeatable ECCN/EAR99 decisions with full audit trails

goods

Faster shipment releases and fewer export holds

Centralized evidence and license tracking across SKUs

Export Classification Implementation & Advisory Services

download

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.

success

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.

manage services

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.

Download the Playbook

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

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

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

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.
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.
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.
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.
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.
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.

Standardize Export Classification

Move from fragmented decisions to auditable, automated ECCN/EAR99 workflows.

See Pricing