It’s Only Common Sense: Creativity Is Noisy, Messy, and So Worth It
Dan’s Biz Bookshelf: ‘The Soul of a New Machine’
The Chemical Connection: Back to Basic Cupric Chloride Etching
In my previous article, I discussed the importance of classifying products as defence, dual-use, or civil. Once a product has been classified as dual-use, the next challenge is to determine whether it requires an export license.
When a product is identified as dual-use, many companies become uncertain about how to proceed because they are unfamiliar with these regulations and lack the required routines and procedures to identify, handle, and structure internal procurement, sales, and marketing.
Unlike products classified as military, which are “designed for defence” and automatically subject to export controls, dual-use products tend to be somewhat complicated and confusing when you’re trying to understand the potential usage and alterations of a product, which can create quite significant potential liabilities in regard to risk.
First, let’s define what dual-use is. Dual-use items are goods, software, and technology that can be used for both civilian and military applications. Sounds simple, right? Many, however, don't know what this entails or how to establish appropriate documents to determine and control whether their products are dual-use, or how to handle these transactions.
Dual-use products are designed for legitimate commercial applications, yet many possess capabilities that can also support military programs, aerospace systems, cybersecurity, advanced telecommunications, critical infrastructure, or intelligence activities.
Therefore, the question is no longer simply, "What is the product?" The more important question becomes, "Is the product specifically designed, developed, or modified for military use?” If yes, it may fall under a military control list.
That distinction changes everything. Now you’re asking whether it meets any technical parameters in the dual-use control lists. If so, it may be classified as dual-use. If neither applies, is it a civil product? If so, it may not require an export licence, although catch-all controls can still apply in certain situations.
Whether an export license is required rarely depends on a single factor. It is normally the combination of the product, its technical characteristics, the destination country, the end-user, the intended end-use, the transfer of technology, applicable sanctions, and the governing regulations that determine whether authorization is required.
For many organizations, answering these questions has become one of the most challenging aspects of doing business internationally.
Throughout this article, I would like to explore four areas that deserve particular attention:
- What determines whether a dual-use product requires an export license?
- Do we truly understand our customer and the intended end-use?
- Are we controlling both products and technical information?
- Can we document and defend the premise of our export-control analysis and decision?
These questions are no longer reserved for compliance specialists. They are becoming management questions.
What Determines Whether a Dual-Use Product Requires an Export License?
One of the most common misconceptions is that once a product has been classified as dual- use, the licensing decision becomes straightforward. It does not. Classification defines the regulatory framework, but it does not determine how every transaction should be handled.
For defence products, the regulatory expectations are generally well understood. Military-listed items are subject to export controls and, in most jurisdictions, require export authorization before the data or product can be transferred internationally. This simply means the transfer of data or products from one legal national entity to another legal national entity.
Dual-use products are different. By definition, they have legitimate commercial applications while also possessing characteristics that may support military, aerospace, intelligence, cybersecurity, or other strategic purposes. That is exactly why governments regulate them differently.
A communication module developed for commercial infrastructure may also support secure military communications. A commercially available processor may ultimately become part of a defence system.
A PCB manufactured for industrial automation may later be integrated into a radar platform or an unmanned aircraft. Nothing about the product itself has changed. What has changed is the context.
This is where many organizations become caught between engineering and regulation. Engineers naturally evaluate performance, functionality, and technical capability. Regulators evaluate something much broader:
- Where is the product going?
- Who will receive it?
- Who ultimately controls the receiving organization?
- How will the technology be used?
- Will technical data accompany the shipment?
- Could the product contribute to military capability or strategic technology?
- Is the destination subject to sanctions or additional restrictions?
The export decision is therefore rarely based on the product alone. It is based on the transaction.
This distinction becomes particularly important for dual-use technologies because the same product may be exported without an individual license in one transaction while requiring export authorization or even being prohibited in another.
Many companies understandably focus on what they are exporting.
Authorities are equally interested in why it is being exported, where it is going, who ultimately receives it, and whether the transfer introduces national-security concerns. Understanding that difference is the foundation of modern export compliance.
It is also why export control should never become a box to be checked after engineering has finished its work. It should become part of product development, customer qualification, sales, procurement, and supply-chain management from the very beginning.
Do We Truly Understand Our Customer and the Intended End-Use?
In the first article of this series, I discussed the importance of understanding suppliers beyond the first tier. Export control requires the same level of curiosity about customers.
Many organizations know who they sell to. Far fewer know who ultimately uses the product. That distinction is becoming increasingly important.
Modern supply chains are rarely linear. Products move through distributors, contract manufacturers, system integrators, and subcontractors before reaching their final destination. Along the way, ownership may change, projects evolve, and technology originally intended for one application may ultimately support another.
This creates one of the greatest challenges in export compliance. The transaction that appears perfectly acceptable on paper may look entirely different once the broader context becomes visible:
- Who owns the receiving company?
- Who is the ultimate end-user?
- Could the product become part of a military programme, a surveillance platform, critical infrastructure, or another controlled application?
- Has the customer itself been screened against sanctions or restricted-party lists?
Increasingly, these are commercial questions, not simply compliance questions. A company that understands its customers, their ownership, and their intended use of technology is far better positioned to manage both regulatory obligations and business risk. At CONFIDEE, we often say that transparency should not stop with the supply chain. It should extend all the way to the end-user.
Because, from an export-control perspective, the end-user can sometimes present more risk than the product itself. A dual-use analysis and documentation will determine this.
Page 1 of 2
