Short answer: A pre-shipment export compliance check is a short, repeatable sequence of seven checks an exporter runs before releasing a shipment: classify the item, screen every party, vet the destination, verify end use and end user, determine whether a license is needed, get the documents right, and keep the record. Run it before the goods move. Before they leave, a misclassification or a missed screening hit is a correction; after they leave, the same problem is a potential violation, with penalties, denied-party exposure and an enforcement file attached.
This guide goes through the seven checks in the order that makes sense and shows how to keep the check repeatable when you ship more than you can vet by hand.
(This is the export-specific version. For the broader, shipment-level view that covers import and export, see the five compliance checks every shipment should pass before it leaves the dock.)
The short version: a pre-shipment export check answers five questions in sequence. What is it? Who’s receiving it? Where’s it going? What’s it for? Do I need a license? Then it makes sure the paperwork and records back those answers up. Run it before the goods move, because afterward it stops being a checklist and becomes an enforcement problem.
Why run the export check before shipment rather than after?
The pre-shipment check is worth far more before the shipment leaves than after, because the cost of the same mistake changes once the export has happened:
- Before: you catch a wrong classification, a sanctioned consignee or a missing license, and you fix it. The cost is a delay.
- After: the export has occurred. A denied-party shipment, an unlicensed controlled export or a prohibited end use is now a violation you have to disclose and remediate. The cost is penalties, scrutiny and a much worse week.
Export penalties are not trivial, and responsibility sits with the exporter, whoever handles the freight and whatever software is used. The dock is the last point where fixing a problem costs only time.
What are the seven steps of a pre-shipment export check?
The seven steps of a pre-shipment export check are classify, screen, vet the destination, verify end use, determine the license, document, and record. Run them in order. Each depends on the one before: you can’t assess controls on an item you haven’t classified, and you can’t license a shipment whose parties you haven’t screened.
Check 1: How do you classify the item for export?
Classifying an export item means assigning it two codes, because everything downstream depends on knowing exactly what you’re shipping:
- The export control classification. An ECCN (Export Control Classification Number) applies if the item is on the Commerce Control List (CCL); EAR99 is the designation for items subject to the Export Administration Regulations (EAR) but not listed on the CCL. This code tells you whether the item is controlled and why, through its reasons for control.
- The commodity code for the export declaration (Schedule B or HTS).
Get this wrong and every later check is built on sand: you’ll screen and document against the wrong control profile. If there’s any doubt that the item falls under Commerce jurisdiction rather than being ITAR-controlled, resolve that first. (For the classification itself, see the free ECCN classification tool; for doing tariff and export classification together, see HS and ECCN classification in one workflow.)
Check 2: Which parties need restricted-party screening?
Every party to the transaction needs screening: the consignee, the end user, any intermediate consignee and the freight forwarder. Screen them against the relevant restricted-party lists, among them the BIS Entity List, Denied Persons List and Unverified List, the OFAC sanctions lists, and the State Department’s debarred list. Many of these lists are combined in the Consolidated Screening List.
“Every party” is the important part. A clean consignee with a sanctioned intermediate consignee is still a problem. Screening flags risk for a person to adjudicate, so a possible match means stop and verify, not an automatic block. (Screening is one of the eight AI-assisted functions covered in best AI tools for trade compliance teams.)
Check 3: How do you vet the destination country?
Vetting the destination means asking whether the country is embargoed or sanctioned. Country-based controls can prohibit or heavily restrict exports to certain destinations regardless of the item. The gate is fast but not optional: a permissible item sent to a prohibited destination is still a prohibited export.
Check 4: What does end-use and end-user verification involve?
End-use and end-user verification asks what the item will be used for and by whom, because even a permissible item, party and destination can be blocked by the end use. Certain end uses, such as specific military, nuclear, missile, or chemical and biological applications, trigger controls or outright prohibitions. This is also where “know your customer” due diligence sits. Watch for the classic red flags: a customer reluctant to give end-use information, a product that doesn’t match the customer’s line of business, requests to route shipments oddly, or a buyer unfamiliar with the product’s normal use. Red flags don’t end the transaction; they create a duty to inquire before you proceed.
Check 5: How do you know if an export license is required?
You know whether an export license is required by cross-referencing the item’s reasons for control (from its ECCN in Check 1) against the destination (from Check 3) on the Commerce Country Chart. Where they intersect, a license may be required, unless a license exception applies. The result is one of three answers: ship with no license required, ship under a named license exception, or apply for a license first. The walkthrough of shipping restrictions and export licensing covers this step in more detail.
This is the step most often skipped under time pressure, and it has the sharpest consequences. An unlicensed controlled export is a violation even if everything else was clean.
Check 6: Which export documents need to be in order?
The export documents need to be complete and consistent with each other, because a compliant shipment with wrong paperwork is still a problem at the border. Confirm you have:
- A commercial invoice and packing list that match the goods and the classification.
- Electronic Export Information (EEI) filed through the Automated Export System (AES) where required, generally for shipments above the value threshold per commodity line, or whenever a license is required.
- License or license-exception citations where applicable.
- A Destination Control Statement on the required documents for controlled exports.
- Any certificates (origin, end use) the transaction calls for.
The paperwork should tell the same story the earlier checks established. Inconsistencies are what auditors notice first.
Check 7: How long must export records be kept?
Under 15 CFR 762.6, records the EAR requires you to keep must be retained for five years, counted from the latest relevant event, such as the export itself or a known reexport. The check isn’t finished when the goods leave; it’s finished when the evidence is filed. Keep the classification and its rationale, the screening results, the license determination and the export documents. That is the audit trail that shows you exercised reasonable care if anyone asks, and it’s the reason to document the check as you run it.
Which export red flags should your team memorize?
Export red flags are warning signs in a transaction, and most enforcement problems show up first as one that someone ignored. Train your team to stop on these:
- A customer or agent reluctant to offer information about the product’s end use.
- Product capabilities that don’t fit the buyer’s line of business.
- Routing that doesn’t make sense: odd shipping routes, freight-forwarding addresses given as a final destination, or requests to under-declare.
- A buyer with little familiarity with the product who is still ordering sophisticated items.
- Reluctance to provide end-user or end-use certifications.
- Requests to skip the installation, training or maintenance the product normally requires.
A red flag isn’t proof of anything. It is a trigger to inquire and resolve the concern before shipping, and to document how you resolved it.
Why does the pre-shipment check break down at high volume?
The pre-shipment check breaks down at high volume because the manual steps don’t scale. For a handful of shipments a week, a careful person with a checklist is enough. As volume rises:
- Classification becomes the bottleneck (you can’t license what you haven’t classified).
- Screening every party on every shipment by hand stops being possible.
- Re-checking as control lists and the CCL change becomes impossible to keep up with manually.
- The documentation and record trail gets thin exactly when you most need it.
The fix is to make the repeatable parts repeatable, with no steps skipped: automate the high-volume groundwork (classification and screening), keep a human in the loop on the judgment calls (red flags, borderline license determinations, possible-match adjudication), and let the system keep the audit trail by design. Software handles volume and people handle judgment, the same model that holds across the rest of trade compliance. Classification at the front of the check can run in bulk or via API, so a growing shipment volume doesn’t outrun your ability to vet it.
Why does the pre-shipment check matter more in 2026?
The pre-shipment export check matters more in 2026 because BIS (the US Bureau of Industry and Security) has widened export controls, especially around advanced computing, semiconductors and AI. Items that were comfortably EAR99 a couple of years ago now carry controlled ECCNs. For many exporters the check used to be lighter, because fewer of their items were controlled. More controlled items means more shipments where Checks 4 and 5 (end use and licensing) actually bite, and a higher cost for getting Check 1 (classification) wrong. Exporters who treated the check as a formality are the most exposed as the controls widen. (For more on that shift, see TariffWolf’s export control overview.)
The pre-shipment check at a glance
| # | Check | The question it answers | Stop if… |
| 1 | Classify | What am I shipping? (ECCN/EAR99 + commodity code) | You don’t actually know what it is |
| 2 | Screen parties | Who’s involved? | Any party hits a restricted list (verify) |
| 3 | Vet destination | Where’s it going? | Destination is embargoed/sanctioned |
| 4 | End-use / end-user | What’s it for, and for whom? | Prohibited use or unresolved red flag |
| 5 | License determination | Do I need a license? | A license is required and you don’t have it |
| 6 | Documentation | Does the paperwork match? | EEI, citations, or DCS are missing/wrong |
| 7 | Record | Can I prove it later? | The audit trail isn’t captured |
Run it in order, every time, before the goods move.
Frequently asked questions
What should an export compliance checklist include?
An export compliance checklist should include, at minimum, classification (ECCN or EAR99 plus the commodity code), restricted-party screening of every party, a destination and embargo check, and end-use and end-user verification with red-flag due diligence. It should also cover the license determination, complete and consistent export documents (commercial invoice, EEI filing through AES, license citations, Destination Control Statement), and record retention.
Who is responsible for export compliance, the exporter or the freight forwarder?
The exporter (the principal party in interest) is legally responsible for export compliance, even when a freight forwarder handles logistics or filing. That is why the exporter has to own the pre-shipment check and can’t delegate it and forget it.
Do I need to file EEI through AES for every export?
Not every export needs an EEI filing through AES, but it is common: generally when the value per commodity line exceeds the threshold, or when a license is required. Confirm the requirements for your specific shipment. Missing a required EEI filing is itself a compliance failure.
Does an export red flag mean I have to cancel the shipment?
An export red flag does not automatically stop a shipment. It creates a duty to inquire and resolve the concern before exporting, and to document how you resolved it.
How do I run the pre-shipment check at high shipment volume?
At high shipment volume, automate the repeatable groundwork (classification and screening), keep people on the judgment calls (red flags, borderline licensing, match adjudication), and let the system retain the audit trail. The answer to volume is faster steps, with none skipped.
Pick a time on the calendar that loads next — no email back-and-forth.
The honest bottom line
Export controls keep widening, so the pre-shipment check stops being a formality. It is the thing that keeps a correction from turning into an enforcement file.
TariffWolf handles the front of that check: export control classification with reasoning you can read, ready to run in bulk or via API, with a human kept 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. For specific shipments, consult the current EAR, OFAC regulations and AES requirements, or speak with qualified trade compliance counsel.