There’s a specific moment in every export that’s easy to overlook: the last point at which a compliance problem is still cheap to fix. Before the goods 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.
A pre-shipment compliance check is the discipline of using that last cheap moment well. It’s a short, repeatable sequence an exporter runs before releasing any shipment, designed to catch the handful of things that turn a routine export into a serious problem. This guide walks the seven checks, in the order that makes sense, and shows how to make the whole thing repeatable when you’re shipping more than you can vet by hand.
(This is the export-specific deep dive. For the broader, shipment-level view that spans 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 makes sure the paperwork and records back it up. Run it before the goods move, because afterward it stops being a checklist and becomes an enforcement problem.
Why pre-shipment, specifically
Timing is the entire point. The same check is worth far more before the shipment leaves than after:
- Before: you catch a wrong classification, a sanctioned consignee, or a missing license — and you fix it. Cost: 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. Cost: penalties, scrutiny, and a much worse week.
Export penalties are not trivial, and the exporter — not the freight forwarder, not the software — is responsible. The pre-shipment check exists because the dock is the last place the cost is still measured in hours instead of consequences.
The seven-step pre-shipment export check
Run these in order. Each one depends on the one before it — 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 — Classify the item
Everything downstream depends on knowing exactly what you’re shipping. That means two codes:
- The export control classification — an ECCN if the item is on the Commerce Control List, or EAR99 if it’s subject to the EAR but not listed. This determines whether the item is controlled and why (its reasons for control).
- The commodity code for the export declaration (Schedule B / 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 the item is even Commerce-jurisdiction rather than ITAR-controlled, resolve that first. (For the classification itself, see the free ECCN tool; for doing tariff and export classification together, one unified workflow.)
Check 2 — Screen every party
Screen all parties to the transaction — consignee, end user, intermediate consignee, and the freight forwarder — against the relevant restricted-party lists: the BIS Entity List, Denied Persons List, and Unverified List; the OFAC sanctions lists; and the State Department’s debarred list, among others. Many of these are aggregated in the Consolidated Screening List.
“Every party” matters. A clean consignee with a sanctioned intermediate consignee is still a problem. Screening flags risk for a human to adjudicate — a possible match is a 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 — Vet the destination
Is the destination embargoed or sanctioned? Country-based controls can prohibit or heavily restrict exports to certain destinations regardless of the item. This is a fast but non-negotiable gate: a permissible item to a prohibited destination is still a prohibited export.
Check 4 — Verify end-use and end-user
Even a permissible item, party, and destination can be blocked by what it will be used for. Certain end uses — for example, specific military, nuclear, missile, or chemical/biological applications — trigger controls or outright prohibitions. This is also where “know your customer” due diligence lives: watch for the classic red flags — a customer reluctant to give end-use information, a product mismatch for 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 raise a duty to inquire before you proceed.
Check 5 — Determine the license requirement
Now combine what you’ve learned. Cross-reference the item’s reasons for control (from its ECCN in Check 1) against the destination (from Check 3) using the Commerce Country Chart. Where they intersect, a license may be required — unless a license exception applies. The output of this check is a clear answer: ship under no-license-required, ship under a named license exception, or apply for a license first.
This is the step that most often gets skipped under time pressure, and it’s the one with the sharpest consequences. An unlicensed controlled export is a violation even if everything else was clean.
Check 6 — Get the documentation right
A compliant shipment with wrong paperwork is still a problem at the border. Confirm the export documents are complete and consistent:
- Commercial invoice and packing list that match the goods and the classification.
- Electronic Export Information (EEI) filed through 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 your seven checks just established. Inconsistencies are what auditors notice first.
Check 7 — Keep the record
The check isn’t done when the goods leave — it’s done when the evidence is filed. Retain the records: the classification and its rationale, the screening results, the license determination, and the export documents. Under the EAR, export records must generally be kept for five years. This is the audit trail that proves you exercised reasonable care if anyone ever asks — which is the entire reason to run the check in a documented way rather than from memory.
The red flags worth memorizing
Most enforcement problems announce themselves first as a red flag someone ignored. Train your team to stop on these:
- A customer or agent reluctant to offer information about the product’s end use.
- The product’s capabilities don’t fit the buyer’s line of business.
- Routing that doesn’t make sense — odd shipping routes, freight-forwarding addresses for a final destination, or requests to under-declare.
- A buyer with little familiarity with the product yet ordering sophisticated items.
- Reluctance to provide end-user or end-use certifications.
- Requests to avoid the usual installation, training, or maintenance that the product normally requires.
A red flag isn’t proof of anything — it’s a trigger to inquire and resolve before shipping, and to document how you resolved it.
Why the check breaks down at scale — and how to fix it
For a handful of shipments a week, a careful person with a checklist is enough. The pre-shipment check breaks when volume rises:
- Classification becomes the bottleneck (you can’t license what you haven’t classified).
- Screening every party on every shipment by hand doesn’t scale.
- 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 isn’t to skip steps — it’s to make the repeatable parts repeatable. 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 retain the audit trail by design. That’s the same human-in-the-loop, audit-ready model that holds across every part of trade compliance — software for volume, people for judgment. Classification at the front of the check can run in bulk or via API so a growing shipment volume never outruns your ability to vet it.
Why this matters more in 2026
The pre-shipment export check used to be lighter for a lot of exporters, because fewer of their items were controlled. That’s changed. BIS has widened export controls — especially around advanced computing, semiconductors, and AI — so items that were comfortably EAR99 a couple of years ago now carry controlled ECCNs. More controlled items means more shipments where Checks 4 and 5 (end-use and licensing) actually bite, and more cost to getting Check 1 (classification) wrong. The exporters who treated the pre-shipment check as a formality are exactly the ones most exposed as the control net widens. (For more on that shift, see the export-control landscape.)
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 is a pre-shipment compliance check? It’s a repeatable set of checks an exporter runs before a shipment leaves: classify the item (ECCN/EAR99 and commodity code), screen all parties against restricted lists, vet the destination, verify end-use and end-user, determine any license requirement, confirm the documentation, and retain the records. The point is to catch problems while they’re still cheap to fix.
What should an export compliance checklist include? At minimum: classification, restricted-party screening of every party, destination/embargo check, end-use and end-user verification (including red-flag due diligence), license determination, complete and consistent export documents (commercial invoice, EEI/AES filing, 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, even when a forwarder handles logistics or filing. That’s why the pre-shipment check has to be owned by the exporter, not delegated and forgotten.
What are export “red flags”? Warning signs in a transaction — a customer vague about end use, a product that doesn’t fit the buyer’s business, strange routing, reluctance to provide certifications. Red flags don’t automatically stop a shipment, but they create a duty to inquire and resolve the concern before exporting.
Do I need to file EEI / use AES for every export? Not every shipment, but commonly — generally when the value per commodity line exceeds the threshold or when a license is required. Confirm the specific requirements for your shipment; missing a required EEI filing is itself a compliance failure.
How long do I have to keep export records? Under the EAR, export records generally must be retained for five years. Keep the classification rationale, screening results, license determination, and shipping documents together — that’s the audit trail that demonstrates reasonable care.
How do I run this check at high shipment volume? Automate the repeatable groundwork — classification and screening — keep humans on the judgment calls (red flags, borderline licensing, match adjudication), and let the system retain the audit trail. Skipping steps to keep up is the failure mode; making the steps faster is the fix.
Pick a time on the calendar that loads next — no email back-and-forth.
The honest bottom line
A pre-shipment compliance check is just the disciplined use of the last cheap moment before an export leaves. Classify, screen, vet the destination, verify the end use and end user, determine the license, get the documents right, and keep the record — in that order, every time. Do it before the goods move, because afterward the checklist becomes an enforcement file. And as export controls keep widening, the check stops being a formality and starts being the thing that keeps you out of trouble.
TariffWolf handles the heavy 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.