Shipping Restrictions and Export Licensing: A Practical Walkthrough

Here’s the reassuring news and the catch, in one breath: the large majority of U.S. exports — well over 95% — ship with no license required. And proving that you’re in that 95% is the entire job.

“Do I need an export license?” is rarely answered by a gut feel about whether a product seems sensitive. It’s answered by a determination — a defined sequence that checks your item, your destination, your buyer, and the intended use against the rules. Most of the time the answer is “no license needed.” But the exceptions are exactly where exporters get caught, because a restriction can come from a direction you weren’t looking.

This is a practical walkthrough of how shipping restrictions actually work and how to run a license determination end to end: where restrictions come from, the step-by-step determination, when a license exception saves you, and what it takes to file when a license really is required.

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

The short version: A license requirement can be triggered by any of four things — the item, the destination, the end user, or the end use. Run them in order: classify the item to get its reasons for control, check those against the destination on the Commerce Country Chart, then check end-user and end-use restrictions that override the chart. If a license is required, look for a license exception before you file — and if none fits, apply through SNAP-R and build the timeline into your commitments.

The mental model: restrictions come from four directions

The single most useful thing to internalize is that a license requirement isn’t one gate — it’s four, and any one of them can stop you:

1. The item — what you’re shipping. Its export control classification (ECCN) 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 — even an everyday EAR99 product to a listed entity needs a license.
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.

The license determination, step by step

Step 1 — Confirm jurisdiction (EAR, ITAR, or neither)

Before anything else, establish which rulebook applies. Most commercial and dual-use goods fall under the EAR (administered by BIS). Defense articles fall under the ITAR (administered by the State Department’s DDTC), which is 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 Is my product ITAR or EAR?)

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

Step 2 — Classify the item (ECCN or EAR99)

Determine the item’s ECCN on the Commerce Control List, or confirm it’s EAR99 (subject to the EAR but not listed). This is the foundation: 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 so on — which drive everything downstream.

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 — Run the Commerce Country Chart

This is the heart of the destination check. Take each reason for control from your ECCN (e.g., “NS Column 1,” “AT Column 1”) and find your country of ultimate destination on the Commerce Country Chart (Supplement No. 1 to Part 738 of the EAR). An “X” at the intersection of a reason-for-control column and the destination row means a license is required to that destination for that reason.

If your item is EAR99, there’s no ECCN reason to check against the chart — which is why most EAR99 goods to most destinations come out as “No License Required.” But “no ECCN reason” does not mean “done” — you still have Steps 4 and 5.

Step 4 — Check end-user restrictions (Part 744)

This is 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 against a presumption of denial. And the bar moved recently: as of a 2025 rule (the “Affiliates Rule”), screening must also account for entities that are 50% or more owned in aggregate by listed parties, even if the entity itself isn’t named. Your “no license required” answer from one quarter can become wrong the next simply because a counterparty was added to a list.

Step 5 — Check end-use restrictions (Part 744)

Finally, the use. Certain end uses — specific WMD, missile, military, or other sensitive applications — can require a license or prohibit the export, even when the item, destination, and parties otherwise look clear. This is also where know-your-customer diligence and red flags live: a use that doesn’t fit the customer, evasive answers about the end application, and similar warning signs create a duty to inquire before you proceed.

The output

After five steps you land on one of three answers:

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

License exceptions: check before you file

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

There are many, each narrow and condition-laden. A few you’ll encounter:

• LVS (Limited Value Shipments) — small-value 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, like tools or demo units.
• STA (Strategic Trade Authorization) — for 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 purely practical: filing a license application costs you weeks to months, so exhausting exception eligibility first can save the whole timeline. But exceptions are conditional — read the eligibility and reporting requirements carefully, because using one you don’t qualify for is itself a violation.

Applying for a license: the SNAP-R process

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

A few realities worth planning around:

• Interagency review. BIS often refers applications to other agencies (Defense, State, Energy). You’re not waiting on one desk.
• Timelines. BIS’s statutory target is to process or refer most applications within 90 calendar days of registration (15 CFR 750.4). In practice, routine applications often run roughly 2–3 months, while sensitive ones — advanced computing, certain destinations, certain end uses — can run 6–12 months.
• Provisos. An approved license can come with conditions (provisos) you must comply with, plus value and quantity limits and an expiration. The license is permission within boundaries, not a blank check.
• Build it into 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 — is known before you sign.

ITAR licensing is a separate path

If your item turned out to be ITAR-controlled back in Step 1, the licensing path is different: register with the State Department’s DDTC and file through the DECCS portal, where generally all exports of defense articles require an authorization. Same principle — classify and determine first — but a different agency, system, and rulebook. (See Is my product ITAR or EAR?)

Restrictions that bypass the chart entirely

It’s worth stating plainly: some restrictions don’t care 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. As covered, 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 now requires licenses for advanced computing items to certain destination groups and entities, including based on an entity’s ultimate parent, with some categories moving to case-by-case review rather than outright denial. (We traced this in The New Iron Curtain Is Made of Silicon.)

The lesson: the Country Chart answers the item × destination question, but it’s never the whole question. The end-user and end-use checks, and these special restrictions, are what catch the shipments that “looked fine.”

Managing licensing in the real world

A few principles separate teams that handle this smoothly from teams that lurch from shipment to shipment:

• Classification is the foundation. Every license question starts with knowing your ECCN. Get classification right and current, and the rest of the determination has solid ground. Get it wrong, and you’re screening and licensing against the wrong control profile.
• Determinations expire quietly. Restricted-party lists change constantly — entities are added in large batches throughout the year. A clean determination is a point-in-time result; you have to 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 under the EAR. This is what demonstrates reasonable care.
• Automate the volume, keep humans on the judgment. 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 is the same model that works across trade compliance generally.

The determination, at a glance

Frequently asked questions

How do I determine if I need an export license? Run the determination in order: confirm jurisdiction (EAR vs ITAR), classify the item (ECCN or EAR99) to get its reasons for control, check those reasons against the destination on the Commerce Country Chart, then check end-user and end-use restrictions under Part 744, which can require a license regardless of the chart. If a license is required, check for a license exception before filing.

Do most exports require a license? No — over 95% of U.S. exports ship with No License Required, because most goods are EAR99 or uncontrolled to most destinations. The work is proving you’re in that category by running the determination, and catching the cases where a destination, party, or end use triggers a requirement.

What is the Commerce Country Chart and how do I use it? It’s the BIS table (Supplement No. 1 to Part 738) that cross-references an item’s reasons for control against destination countries. You match each reason-for-control column from your ECCN to the destination row; an “X” at the intersection means a license is required to that destination for that reason. It’s essential but not sufficient — end-user and end-use checks still apply.

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

What is a license exception and when can I use one? A license exception (Part 740) authorizes an export that would otherwise need a license, provided you meet its specific conditions — examples include LVS, GBS, TMP, STA, ENC, and GOV. Always check exception eligibility before filing an application, since a license can take months. But use one only if you genuinely qualify; the conditions are strict.

How long does an export license take? BIS’s statutory target is to process or refer most applications within 90 calendar days, but in practice routine applications often run about 2–3 months and sensitive ones (certain advanced-computing items, destinations, or end uses) can run 6–12 months due to interagency and case-by-case review. Classify early and build the timeline into commercial commitments.

Where do I apply for an export license? For EAR items, through BIS’s electronic SNAP-R system. 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.

The honest bottom line

Export licensing sounds like a wall and is really a determination. A license requirement can come from the item, the destination, the end user, or the end use — so you check all four, in order, with the Country Chart in the middle and the Part 744 end-user and end-use controls as overrides that catch what the chart misses. Most of the time you land on No License Required. When you don’t, look for an exception before you file, and if you must file, plan for the timeline. And remember the determination is only as current as your lists — re-check, especially 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.