Shipping Restrictions and Export Licensing: A Practical Walkthrough

Short answer: A U.S. export license requirement under the Export Administration Regulations (EAR) can be triggered by any of four things: the item, the destination, the end user or the end use. Check them in order. Classify the item to get its reasons for control, check those against the destination on the Commerce Country Chart, then check the end-user and end-use restrictions in Part 744, which override the chart. If a license is required, look for a license exception before you file; if none fits, apply through SNAP-R and build the timeline into your commitments.

Here is the reassuring news and the catch together: the large majority of U.S. exports, well over 95%, ship with no license required. Proving that you are in that 95% is the entire job.

“Do I need an export license?” gets answered by a determination, a defined sequence that checks your item, destination, buyer and intended use against the rules. Most of the time the answer is “no license needed.” The exceptions are where exporters get caught, because a restriction can come from a direction they weren’t watching. This walkthrough covers where restrictions come from, the determination step by step, when a license exception saves you, and what filing takes when a license really is required.

(This is the deep licensing dive. For the full sequence you run before every shipment, covering classification, screening, documentation and records, see the pre-shipment compliance check every exporter should run.)

What can trigger an export license requirement?

An export license requirement can come from four directions, and any one of them can stop a shipment:

1. The item: what you’re shipping. Its Export Control Classification Number (ECCN), the code that places it on the Commerce Control List, carries reasons for control that may require a license to certain destinations.
2. The destination: where it’s going. Some countries are embargoed or sanctioned; others trigger controls in combination with the item.
3. The end user: who receives it. A party on a restricted list can require a license regardless of the item, so even an everyday EAR99 product going to a listed entity needs one.
4. The end use: what it’s for. Prohibited uses (weapons of mass destruction, certain military applications and others) can require a license or bar the export outright.

Most license determinations go wrong because someone checked one or two of these and stopped. The item looked harmless, so they shipped, and missed a listed consignee. The walkthrough below checks all four in the order that works.

How do you run an export license determination?

An export license determination runs in five steps: jurisdiction, classification, the Country Chart, end-user checks and end-use checks.

Step 1: Is the item under the EAR, the ITAR or neither?

Jurisdiction comes first, because it decides which rulebook applies. Most commercial and dual-use goods fall under the EAR, administered by the Bureau of Industry and Security (BIS). Defense articles fall under the International Traffic in Arms Regulations (ITAR), administered by the State Department’s Directorate of Defense Trade Controls (DDTC), a separate regime with its own licensing. Some items fall under other agencies entirely. Get this wrong and the rest of the walkthrough is the wrong walkthrough. (If there’s doubt, start with our primer on whether a product is ITAR or EAR.)

The rest of this walkthrough assumes your item is subject to the EAR.

Step 2: What is the item’s ECCN, or is it EAR99?

Classification means finding the item’s ECCN on the Commerce Control List or confirming it is EAR99 (subject to the EAR but not listed). Everything downstream depends on it, because the ECCN tells you the item’s reasons for control: National Security (NS), Anti-Terrorism (AT), Nuclear Nonproliferation (NP), Missile Technology (MT), Regional Stability (RS) and others.

Don’t assume EAR99 because a product “feels commercial.” A component can look like ordinary industrial equipment and still fall under a controlled entry once you check its technical parameters against the CCL. (Use the free ECCN tool to get a reasoned classification, or do tariff and export classification together.)

Step 3: How do you read the Commerce Country Chart?

The Commerce Country Chart (Supplement No. 1 to Part 738 of the EAR) is where the destination check happens. Take each reason for control from your ECCN (for example “NS Column 1” or “AT Column 1”) and find your country of ultimate destination on the chart. An “X” where the reason-for-control column meets the destination row means a license is required to that destination for that reason.

An EAR99 item has no ECCN reason to check against the chart, which is why most EAR99 goods to most destinations come out as “No License Required.” Steps 4 and 5 still apply to EAR99 items.

Step 4: Are any parties restricted? (Part 744 end-user checks)

End-user restrictions are the override people miss: independent of the Country Chart, the parties to your transaction can require a license on their own. Screen every party (consignee, end user, intermediate consignee, freight forwarder) against the restricted-party lists:

• The BIS Entity List, Denied Persons List and Unverified List
• The Military End-User (MEU) List
• OFAC’s sanctions lists

A hit here can require a license regardless of the item or destination. Shipping even an EAR99 item to a party on the Entity List typically requires a license, often reviewed under a presumption of denial. Ownership matters too. BIS’s “Affiliates Rule” (interim final rule, 30 September 2025, 90 FR 47201) extended end-user controls to entities 50% or more owned, in aggregate, by listed parties, even when the entity itself isn’t named. BIS then suspended that rule from 10 November 2025 through 9 November 2026 (90 FR 50857); it is scheduled to return on 10 November 2026 unless the suspension is extended. Either way, your “no license required” answer from one quarter can become wrong the next simply because a counterparty was added to a list.

Step 5: Is the end use restricted? (Part 744 end-use checks)

End-use restrictions in Part 744 can require a license or prohibit the export for certain uses (specific WMD, missile, military or other sensitive applications), even when the item, destination and parties look clear. Know-your-customer diligence and red flags belong here too. A use that doesn’t fit the customer, or evasive answers about the end application, create a duty to inquire before you proceed.

What are the possible outcomes of a license determination?

A license determination ends in one of three answers:

• No License Required (NLR): ship, with the correct AES/EEI designation.
• License exception applies: ship under that exception’s conditions (next section).
• Individual license required: apply before you ship.

When can you use a license exception instead of a license?

A license exception (Part 740 of the EAR) is an authorization to export without an individual license, provided you meet its stated conditions. If Steps 3 to 5 say a license is required, don’t file yet. First check whether an exception covers your specific combination of item, destination and end use.

There are many exceptions, each narrow and full of conditions. Some you’ll meet:

• LVS (Limited Value Shipments): small shipments of certain controlled items, under net-value limits tied to the CCL entry.
• GBS (Shipments to Country Group B): for items controlled for national-security reasons only, to a defined group of destinations.
• TMP (Temporary imports/exports): items leaving and returning, such as tools or demo units.
• STA (Strategic Trade Authorization): exports to a group of trusted destinations, under conditions.
• ENC (Encryption): for qualifying encryption items.
• GOV: certain shipments to or for governments.

The reason to check exceptions first is practical: a license application costs weeks to months, so ruling out exceptions first can save the whole timeline. But read the eligibility and reporting requirements carefully, because using an exception you don’t qualify for is itself a violation.

How do you apply for a BIS export license?

You apply for a BIS export license electronically through SNAP-R (the Simplified Network Application Process Redesign), the same system used for commodity classification (CCATS) requests, when a license is required and no exception fits. The application captures the full transaction: the item and its ECCN, the parties, the destination, the end use, quantities and values, and supporting documents such as technical specs, end-use statements and any required end-user certificates.

Plan around these realities:

• Interagency review. BIS often refers applications to other agencies (Defense, State, Energy), so you are not waiting on one desk.
• Timelines. Under 15 CFR 750.4, license applications must be resolved or referred to the President within 90 calendar days of registration. In practice, routine applications often take roughly 2–3 months, and sensitive ones (advanced computing, certain destinations, certain end uses) can take 6 to 12 months.
• Provisos. An approved license can carry conditions (provisos) you must follow, plus value and quantity limits and an expiration date.
• Commitments. Promising a customer 30-day delivery on a transaction that needs a sensitive license is a commercial mistake. Classify early, so the license question and its realistic timeline are known before you sign.

How is ITAR licensing different?

ITAR licensing runs through a different agency and system. If your item turned out to be ITAR-controlled in Step 1, you register with the State Department’s DDTC and file through the DECCS portal, where generally all exports of defense articles require an authorization. The principle is the same (classify and determine first), but the rulebook is different. (See how to tell whether a product is ITAR or EAR.)

Which restrictions apply regardless of the Country Chart?

Some restrictions apply no matter what the Commerce Country Chart says:

• Embargoes and comprehensive sanctions. OFAC-administered embargoes can prohibit or tightly restrict exports to certain destinations regardless of the item’s ECCN.
• Listed parties. An Entity List or denied-party match imposes its own license requirement on top of everything else.
• Targeted item-and-destination rules. Recent controls on advanced computing and semiconductors are a live example: BIS requires licenses for advanced computing items to certain destination groups and entities, including based on an entity’s ultimate parent, with some categories moved to case-by-case review instead of a presumption of denial. (We traced this in The New Iron Curtain Is Made of Silicon.)

The Country Chart answers the item-by-destination question. The end-user and end-use checks, and these special restrictions, catch the shipments that “looked fine.”

How should a team manage export licensing day to day?

Teams that handle export licensing smoothly, without lurching from shipment to shipment, follow a few principles:

• Classification comes first. Every license question starts with knowing your ECCN. Get it right and current, and the rest of the determination stands on solid ground; get it wrong, and you screen and license against the wrong control profile.
• Determinations expire without warning. Restricted-party lists change constantly, and entities are added in large batches throughout the year. A clean determination is a point-in-time result, so re-screen, especially the parties, on each shipment.
• Keep the evidence. Retain the classification rationale, the Country Chart determination, the screening results, the exception or license used, and the documents for five years, as 15 CFR 762.6 requires. This is what shows reasonable care.
• Automate the volume and keep people on the judgment calls. Classification and screening scale with software; license determinations on borderline items, red-flag resolution and exception eligibility need people. That human-in-the-loop, audit-ready split works across trade compliance generally.

The license determination at a glance

Frequently asked questions

What is an EAR license exception?

An EAR license exception, listed in Part 740 of the EAR, authorizes an export that would otherwise need an individual license, provided you meet its conditions. Examples include LVS, GBS, TMP, STA, ENC and GOV. Check exception eligibility before filing an application, and use one only if you qualify, because using an exception you don’t qualify for is itself a violation.

Can an EAR99 item ever require an export license?

Yes. EAR99 items have no ECCN-based reasons for control, but a license can still be required because of the destination (embargoes), the end user (a listed or restricted party) or the end use (a prohibited application). EAR99 means “not on the control list,” not “free to ship anywhere.”

What is the Commerce Country Chart?

The Commerce Country Chart is the BIS table in Supplement No. 1 to Part 738 of the EAR that cross-references an item’s reasons for control against destination countries. An “X” where your ECCN’s reason-for-control column meets the destination row means a license is required for that reason. End-user and end-use checks still apply after the chart.

How long does a BIS export license take?

Under 15 CFR 750.4, BIS must resolve license applications, or refer them to the President, within 90 calendar days of registration. BIS often refers applications to other agencies (Defense, State, Energy) for review, so classify early and build the license timeline into commercial commitments.

Where do I apply for an export license?

For EAR items, apply through BIS’s electronic SNAP-R system, after checking whether a Part 740 license exception covers the shipment. For ITAR-controlled items, register with the State Department’s DDTC and file through the DECCS portal. The right portal depends on the jurisdiction you established in Step 1.

Where TariffWolf fits

Export licensing comes down to a determination, and the determination is only as current as your lists, so re-check your parties every time. The part that has to be right first, every time, is classification, and that’s what TariffWolf does: export control classification with reasoning you can read, kept current as the rules change, with a human in the loop and a record you can defend.

Don’t take our word for it. Don’t Trust Us. Try Us.

This article is for general information and is not legal advice. Export controls and restricted-party lists change frequently. Verify against the current EAR, OFAC regulations and BIS guidance, or consult qualified trade compliance counsel for specific transactions.