The announcement on standardizing export declarations for UAVs and related items states that, from June 30, 2026, exporters of unmanned aircraft, unmanned airships, related equipment and components, and civil counter-UAV systems must provide complete and truthful declaration information. For EO/IR imaging module suppliers, this is not merely a customs-form update. It moves product parameters, end use, end user information, and technical documentation into the early stages of quotation, order review, and shipment preparation.
Key points of the announcement
The announcement focuses on export declaration discipline for UAVs and related items. Exporters should pay attention to these requirements:
- If an item is subject to export control, the declaration remarks should state that it is an export-controlled item and list the dual-use item code.
- If an item is not controlled but is close to controlled items in characteristics or use, the declaration should state that it is not an export-controlled item.
- Declarations must follow the required control-related declaration elements. Cross-border e-commerce export lists may not use simplified declaration and must use complete tariff codes.
- The overseas consignee must be identified by full Chinese or English name. The actual manufacturer or seller must be declared rather than an e-commerce platform or agent name.
- Customs declarations should be accompanied by contracts, invoices, and technical documents.
- If Customs questions the authenticity of the declaration, the shipment will not be released during the review period.
For infrared imaging products, this means the export file should be consistent across the quotation, datasheet, contract, invoice, packing list, and customs declaration.
Why EO/IR modules are affected
IRmodules supplies uncooled LWIR cores, cooled MWIR modules, SWIR imaging modules, dual-band fusion modules, and AI imaging systems. These products can be used in industrial inspection, power-line inspection, firefighting, robotics, and search and rescue. They can also be integrated into UAV payloads, airborne observation systems, border security systems, or counter-UAV monitoring systems.
The compliance question is therefore not only whether the exported item is a complete UAV. It is also whether the item is a related component, whether it supports UAV or counter-UAV use, and whether it provides long-range detection, target recognition, tracking, or image fusion capability.
For example, SPECTRA L06 640×512 LWIR 12μm may follow a relatively clear compliance path when used for industrial inspection. If the same module is exported as the core of a UAV payload, the exporter should document the platform, end user, and integration form. A cooled MWIR module such as SPECTRA M06 640×512 Cooled MWIR 15μm requires closer review when used for airborne, maritime, or border-monitoring applications. A dual-band module such as FUSION LV0625A 640+2560×1440 MIPI can improve day-night recognition and should be reviewed carefully when supplied together with UAV platforms, target-detection algorithms, or stabilized gimbals.
Documentation impact for export declarations
Technical documents should not be limited to marketing brochures. For EO/IR products, a practical shipment file should include:
| Document type | Suggested content | Compliance purpose |
|---|---|---|
| Datasheet | Spectral band, resolution, pixel pitch, frame rate, NETD, FOV, interface, size, weight, operating temperature | Supports tariff, item classification, and technical parameter review |
| Function description | Target detection, tracking, AI recognition, image fusion, stabilization, rangefinder linkage | Clarifies whether the item is close to sensitive or controlled use |
| Integration description | UAV, airship, gimbal, counter-UAV system, fixed surveillance system, or industrial device | Explains export form and end application |
| End-use statement | Industrial inspection, power inspection, firefighting, research, security, low-altitude monitoring | Reduces uncertainty caused by unclear use |
| End-user information | Full consignee name, actual user, project background, re-export status | Supports consignee and end-user review |
| Contract and invoice | Model, quantity, price, delivery terms, and matching technical description | Prevents inconsistencies across commercial and customs documents |
Even samples should be handled carefully. If a sample is intended for UAV payload validation, counter-UAV testing, or sensitive scenario demonstration, it should not be described only as “camera module” or “electronic parts.”
Orders that need enhanced review
Exporters should apply enhanced review before quotation or shipment when an order involves:
- UAV payloads, UAV gimbals, unmanned airships, or low-altitude inspection platforms;
- Counter-UAV detection, tracking, warning, or multi-sensor systems;
- Cooled MWIR modules, high-resolution LWIR modules, long-range surveillance, maritime monitoring, airport perimeter, or border observation;
- Dual-band imaging or AI recognition functions supplied with imaging hardware;
- Incomplete end-user information, unclear use, resale, or re-export arrangements;
- Inconsistent product names, model numbers, invoices, logistics descriptions, or datasheet parameters.
Enhanced review does not mean the item cannot be exported. It means the company should determine whether the item is controlled, how it should be declared, whether a license is required, and whether the documentation is complete before the shipment reaches the port.
Recommended workflow for EO/IR suppliers
A professional EO/IR export workflow should connect sales, engineering, compliance, and logistics:
- Ask about the application early. If an inquiry includes UAV, drone, payload, gimbal, counter-UAV, border, surveillance, or tracking, request end use, end user, platform, and destination country information.
- Lock the technical version. Resolution, frame rate, NETD, spectral band, lens focal length, and interface may affect classification and review. The quotation, datasheet, and contract should use the same version.
- Check declaration consistency before shipment. Product name, HS code, model number, invoice, packing list, technical documents, and consignee name should match.
- Manage samples like real projects. Samples for UAV payload validation or counter-UAV testing should use complete tariff codes and accurate product descriptions.
- Keep traceable records. Preserve end-use statements, customer correspondence, datasheet versions, classification notes, licenses, or non-controlled-item analysis for later audit.
Conclusion
The new UAV-related export declaration rules push EO/IR imaging module export management from the shipping stage to the order stage. For infrared camera cores, dual-band modules, AI imaging systems, and UAV payload suppliers, the key question is not simply whether a product can be exported. The practical question is whether a specific model, parameter set, end use, end user, destination country, and declaration package have been reviewed together.
IRmodules recommends that overseas buyers and system integrators provide complete application background at the beginning of a project. Suppliers should manage datasheets, end-use statements, contracts, invoices, and customs information as one consistent compliance file. This reduces customs uncertainty and improves delivery efficiency for legitimate civil projects.
This article is a technical and business compliance analysis, not legal advice. Export licensing, dual-use item codes, and final declaration conclusions should be determined according to applicable regulations, competent authorities, and professional compliance advice.
