About 95% of items exported from the United States do not require a specific export license. That statement from the U.S. Department of Commerce should reassure most exporters, but it does not mean the decision is automatic. A minority of transactions carry real legal exposure, and the exporter, not the freight forwarder or the buyer, bears full responsibility for getting it right.
Your immediate next steps are straightforward:
Pro Tip: If you are unsure which agency has jurisdiction over your item, register for SNAP-R at no cost through the Bureau of Industry and Security (BIS) and submit a commodity classification request before booking the shipment. It is far easier to resolve jurisdiction questions before the cargo is at the port.
Most U.S. exporters do not need a formal export license, but every transaction requires classification, party screening, and accurate AES filing to confirm that conclusion legally.
PointDetailsClassify before bookingFind your ECCN on the Commerce Control List or confirm EAR99 status before committing to a shipment date.Screen every partyRun buyers, end users, and intermediaries against the CSL and OFAC SDN list on every transaction, not just the first.Match documents to AESLicense numbers, ECCNs, and exception codes must appear identically on the invoice, shipping papers, and AES EEI.Know your agencyBIS handles EAR items via SNAP-R; DDTC handles ITAR items via D-Trade; OFAC governs sanctions-based restrictions separately.Keep records five yearsThe EAR requires exporters to retain all export-related documents for five years from the date of export.
For exporters who need third-party support coordinating AES filings and licensed shipments with carriers, USI’s customs clearance services offer licensed brokerage support across U.S. ports of export.
This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about your own circumstances before acting on anything here.
Whether a license is required depends on three variables: the product, the buyer, and the destination. Work through each axis in sequence, and you will arrive at a clear answer for most transactions.
Item classification is the starting point. Every product subject to U.S. export control law falls into one of three categories: it carries an ECCN under the Export Administration Regulations (EAR), it is listed on the U.S. Munitions List (USML) and controlled under the International Traffic in Arms Regulations (ITAR), or it is EAR99, meaning it is not specifically listed on either control list. The classification determines which agency has jurisdiction and which license requirements apply.
Destination is the second axis. Under 15 CFR § 738.4, you must combine your ECCN’s License Requirements section with the Commerce Country Chart to determine whether a license is required for a given country. A dual-use item classified as 3A001 (integrated circuits) may export freely to Germany but require a license to a country subject to regional stability controls.
End use and end user are where most exporters make mistakes. A product can be EAR99 and still require a license if the buyer is on a denied-parties list, the transaction involves a prohibited end use such as weapons of mass destruction development, or OFAC sanctions apply to the destination country or the party receiving the goods.
Three scenarios illustrate the decision path clearly:
When classification is genuinely ambiguous, stop and request a formal commodity classification from BIS or a commodity jurisdiction (CJ) determination from DDTC before filing anything. Misrouting an application to the wrong agency creates immediate processing failures and can delay shipments by weeks.
Classification is a technical exercise, but it follows a repeatable process. Work through these steps before touching any application portal:
EAR99 is not a safe harbor. The same item can become license-controlled depending on who is buying it, what they plan to do with it, and where it is going. Due diligence and screening are mandatory for every transaction, regardless of classification.
License exceptions under Part 740 of the EAR allow exporters to ship certain controlled items without a formal license application, provided specific conditions are met and documentation is maintained. Using the wrong exception, or assuming an exception applies without verifying eligibility, is a compliance failure.
The most commonly used exceptions include:
When you use a license exception, the commercial invoice and shipping documents must state the applicable ECCN and the exception symbol (for example, “EAR99” or “ECCN 5A002, License Exception ENC”). In AES, you enter the exception code rather than a license number. For items that are EAR99 with no license required, the standard AES entry uses “NLR” as the license code. Keep all supporting documentation for a minimum of five years from the date of export, as BIS audits routinely request it.
Pro Tip: Before claiming an exception, read the specific ECCN entry’s license exception eligibility column. Not every exception in Part 740 applies to every ECCN, and the eligibility rules are item-specific.
Getting jurisdiction right before you file is the single most consequential decision in the export licensing process. Three federal agencies handle the vast majority of U.S. export licenses, and each operates a separate portal with distinct requirements.
AgencyWhat it controlsGoverning regulationApplication portalBureau of Industry and Security (BIS)Dual-use goods, commercial items, some military items not on USMLExport Administration Regulations (EAR)SNAP-RDirectorate of Defense Trade Controls (DDTC)Defense articles, defense services, technical data on the USMLInternational Traffic in Arms Regulations (ITAR)D-TradeOffice of Foreign Assets Control (OFAC)Sanctions-based controls by country, entity, or transaction typeOFAC sanctions programsOFAC Online / specific license petition
Three additional agencies control specific commodity categories:
To determine jurisdiction, ask two questions in sequence. First, is the item on the USML? If yes, DDTC controls it under ITAR, and you register and apply through D-Trade. If no, check whether the item has an ECCN on the CCL; if it does, BIS has jurisdiction under the EAR, and SNAP-R is your portal. Then, regardless of which agency controls the item, run the transaction through OFAC’s sanctions screening. Sanctions can block a shipment even when BIS has issued a license.
DDTC registration is mandatory for any U.S. company that manufactures, exports, or brokers defense articles or services, even before a specific license application is filed. Registration fees apply and must be renewed annually.
BIS administers the EAR and SNAP-R is the electronic system for submitting license applications and commodity classification requests; SNAP-R registration is free. The application process follows these steps:
ITAR-regulated exporters must register with DDTC before filing any license application. Applications are submitted through D-Trade, DDTC’s electronic portal. The most common license type is a DSP-5 (permanent export of unclassified defense articles). Technical Assistance Agreements (TAAs) and Manufacturing License Agreements (MLAs) cover the transfer of technical data and manufacturing rights. DDTC processing times vary by complexity, but routine DSP-5 applications typically take 30 to 60 days when documentation is complete.
OFAC licenses are specific authorizations to engage in transactions that would otherwise be prohibited under a sanctions program. They are not filed through SNAP-R or D-Trade; instead, you submit a specific license application through OFAC Online or by written petition, depending on the sanctions program. OFAC evaluates applications on a case-by-case basis and may take several months to respond. General licenses, by contrast, are pre-authorized categories of transactions published in OFAC’s regulations that do not require individual applications.
Pro Tip: Before submitting any application, run a final check of all parties against the Consolidated Screening List. A sanctions hit discovered after submission will halt the application and may trigger a voluntary self-disclosure obligation.
SNAP-R registration carries no fee, and BIS does not charge a fee to submit a license application or commodity classification request. DDTC registration fees are assessed annually based on the number of registrants and the company’s export activity tier. OFAC does not charge application fees for specific license petitions.
Processing time is where expectations often diverge from reality. BIS targets a 90-day review period for most license applications under the EAR, though applications involving sensitive technologies, multiple agencies, or end users in high-risk destinations routinely exceed that window. Commodity classification requests typically resolve in 30 to 90 days for straightforward items. DDTC’s DSP-5 processing averages 30 to 60 days for complete applications. OFAC specific license decisions can take several months, particularly for complex sanctions programs.
The most common causes of delay are predictable and preventable:
If your application is denied, BIS will issue a written denial with a reason code. You may request reconsideration by submitting additional information that addresses the stated basis for denial. A formal appeal to the Export Administration Review Board is available for BIS decisions. For DDTC denials, a written appeal to the Assistant Secretary of State for Political-Military Affairs is the standard path.
The most persistent compliance failure is treating product classification as the end of the analysis. Classification tells you which agency has jurisdiction and which license requirements apply, but it says nothing about whether the specific buyer, end use, or destination triggers additional controls. End-user and end-use due diligence is the step most exporters skip, and it is precisely where enforcement actions originate.
A practical due-diligence checklist for every export transaction:
Most U.S. export transactions do not require a license, but that statistic does not reduce the exporter’s due-diligence obligation. The responsibility for screening, classification, and recordkeeping sits with the U.S. principal party in interest, regardless of whether a license is ultimately required.
Freight forwarding inefficiencies caused by missing or incorrect license data are among the most costly and avoidable operational problems in international logistics. Errors discovered at the port of export trigger holds, fines, and potential loss of export privileges.
CBP requires all export information to be filed through the Automated Export System, and enforces export regulations on behalf of licensing agencies. AES filing is mandatory for most shipments valued above $2,500 per Schedule B number and for all shipments requiring an export license, regardless of value.
The Electronic Export Information (EEI) filed in AES must include the ECCN or EAR99 designation, the license number or exception code, and the license value when a license applies. BIS guidance confirms that classification and license numbers must appear on export documentation and in AES when required. Specifically:
For freight forwarders and customs brokers, the practical obligation is to verify that the carrier’s AES entries match the commercial invoice, packing list, and any license documentation. Discrepancies between the invoice description and the AES filing are a red flag for CBP and can result in shipment holds. Reconcile all documents before the cargo reaches the port of export, not after.
Section 758.1 of the EAR specifies which transactions require AES filing and what information must be included. Exporters who use licensed customs clearance services to manage AES filings should confirm that the broker has the correct license number and ECCN before submission, since the exporter remains legally responsible for the accuracy of the EEI.
Export licensing is not a standalone compliance task. It is a workflow that runs parallel to carrier booking, document preparation, and AES filing, and when it is disconnected from those operational steps, delays are almost inevitable. The operational sequence looks like this:
Classify the item and confirm jurisdiction, then screen all parties against the CSL and OFAC lists, then apply for a license or confirm the applicable exception, then attach the license number or exception code to the shipment record and all export documents, then file AES and obtain the ITN, then release the shipment to the carrier.
Each of those steps generates data that must flow accurately into the next. A transport management system that handles this workflow natively, rather than through disconnected spreadsheets and email threads, reduces the risk of a mismatch between the license application and the AES filing.
The automation benefits that matter most to logistics teams are:
FreightSuite’s air freight management capabilities and ocean freight platform are built to support exactly this kind of integrated compliance workflow, connecting shipment records, documentation, and AES filing in a single system rather than across separate tools. For teams managing high volumes of international shipments, logistics automation at the classification and screening stage is where the operational leverage is greatest.
Logistics teams that want to see how FreightSuite handles export documentation, AES reconciliation, and compliance screening in a live environment can book a demo or review FreightSuite’s pricing plans to find the right fit for their operation.
An export license is a government-issued authorization that permits the export of specific goods, software, or technology to a particular destination or buyer. Under U.S. law, BIS, DDTC, and OFAC are the primary issuing authorities, depending on what is being exported and to whom.
BIS does not charge a fee to apply for an export license or commodity classification through SNAP-R, and SNAP-R registration itself is free. DDTC charges annual registration fees for companies that manufacture, export, or broker defense articles; OFAC does not charge application fees for specific license petitions.
Items with an ECCN on the Commerce Control List that trigger a license requirement based on destination, end use, or end user require a license. Defense articles on the USML always require DDTC authorization. EAR99 items generally do not require a license, but can if the buyer is on a restricted list or the destination is subject to sanctions.
Classify your item (ECCN or EAR99), screen all parties against the CSL and OFAC lists, determine whether a license or exception applies, obtain any required license before shipment, prepare export documents with the correct ECCN and license information, and file the AES EEI to obtain an ITN before the cargo departs.
BIS issues a written denial with a reason code; you may submit additional information to request reconsideration or file a formal appeal with the Export Administration Review Board. For DDTC denials, a written appeal to the Assistant Secretary of State for Political-Military Affairs is the standard path. OFAC denials can be appealed through OFAC’s administrative reconsideration process.
