In June 2026, the Ministry of Commerce website republished the General Administration of Customs notice on standardizing export declarations for unmanned aircraft and related items. The notice takes effect on 30 June 2026 and focuses on the export declaration of unmanned aircraft, unmanned airships, related equipment and components, civil counter-unmanned aircraft systems, and similar goods.
For companies supplying low-altitude surveillance radar, counter-UAS radar, and multi-sensor low-altitude security systems, this notice is more than a minor change to customs paperwork. It makes consistency between product classification, technical documentation, contract information, consignee information, end-use statements, and customs declaration data a practical delivery requirement.
This article provides a technical and project-compliance interpretation for the low-altitude security sector. It is not legal advice. Whether a specific item is controlled, which dual-use export control code applies, and whether a licence is required should be determined according to current official rules, competent-authority requirements, and professional compliance review.
What the notice requires
According to the notice, exporters must declare relevant goods truthfully to Customs in accordance with law. If the goods are controlled items, the exporter must state “属于出口管制物项” (“belongs to export-controlled items”) in the remarks field of the customs declaration and list the corresponding dual-use item export control code.
The notice also addresses items whose characteristics are close to controlled thresholds, or whose stated use does not fall within a controlled use while the technical characteristics still meet relevant indicators. In such cases, the declaration must provide a clear statement. For example, if the goods are not controlled items, the remarks field should state “不属于出口管制物项” (“does not belong to export-controlled items”) in accordance with the notice.
For enterprises, the immediate message is clear: export declarations cannot rely only on a product name, customs commodity code, or sales-purpose description. The review must return to the product’s technical parameters, configuration boundary, and actual transaction background.
Why this matters to low-altitude surveillance and counter-UAS radar
The notice explicitly refers to civil counter-unmanned aircraft systems. In industry practice, a counter-UAS system is rarely a single device. It may include several subsystems, such as:
- low-altitude surveillance radar or counter-drone detection radar;
- electro-optical tracking equipment;
- RF detection or geolocation equipment;
- command-and-control platforms;
- alarm, linkage, recording, and situational-awareness software;
- on-site integration, commissioning, and training services.
Radar often provides the core sensing capability: small-target detection, continuous tracking, track output, and cueing for other sensors. Even when a product is positioned for civil airports, energy facilities, industrial parks, or event security, export declaration still requires a review of whether the item relates to a controlled category, dual-use code, or specific technical indicator.
In other words, “civil use” is not a substitute for compliance classification. The real assessment concerns the specific item, technical capability, end user, end use, destination, and consistency of transaction documents.
Impact on product documents and model control
Radar companies commonly use brochures, datasheets, quotations, interface descriptions, configuration lists, and acceptance documents. After this notice takes effect, consistency between these materials and export declaration documents becomes more important.
Companies should review the following points:
| Item | What to check |
|---|---|
| Model name | Whether quotations, contracts, invoices, packing lists, and technical documents use the same model name |
| Technical parameters | Whether detection range, frequency band, coverage, velocity/altitude capability, and target-processing functions are described consistently |
| Configuration scope | Whether software, control platform, antenna, turntable, brackets, spare parts, commissioning tools, or technical documents are included |
| Use description | Whether the civil use is specific, such as low-altitude security, perimeter protection, airport operations support, or another defined scenario |
| Delivery parties | Whether the overseas consignee, end user, integrator, and sales channel are clear |
If sales materials describe a “counter-UAS system,” the contract refers to “low-altitude surveillance equipment,” and the customs declaration uses another generic name, the exporter may face avoidable explanation work. For controlled items or products close to controlled indicators, such inconsistencies may directly affect customs clearance efficiency.
Impact on customs declaration and licensing work
The notice requires controlled items to be declared with the corresponding dual-use export control code. That means item identification and compliance review must be completed before shipment, not improvised after the goods have already reached the port.
A more reliable project workflow should include:
- Initial technical classification: assess whether product parameters, software scope, and technical documents may involve dual-use export controls.
- Transaction background review: confirm the overseas consignee, end user, end use, destination, and any re-export arrangement.
- Licensing path assessment: if the item is controlled, evaluate licence application needs, document preparation, and approval timeline.
- Pre-review of declaration materials: check consistency among contract, invoice, packing list, technical documents, and declaration elements.
- Record retention: keep classification rationale, customer information, end-use documents, licences, or internal basis for non-controlled determination.
For delivery management, the most important change is that compliance timing moves earlier. Classification and licence assumptions should not be left until the final week before shipment. If supplementary materials, licence applications, or technical explanations become necessary, the project schedule will be affected.
What “doubt about authenticity” means for project risk
The notice states that if Customs has doubts about the authenticity of declared information, Customs may raise inquiries in accordance with law, and the export goods will not be released during the inquiry period.
For radar projects, this risk often arises from situations such as:
- product names that are too generic to match the actual configuration;
- inconsistencies between technical documents and declaration elements;
- unclear relationships among overseas consignee, end user, and contract buyer;
- end-use descriptions limited to vague terms such as “security” or “monitoring”;
- software, technical documents, or accessories included in the shipment but not reflected in the declared scope;
- lack of a clear explanation as to whether the item belongs to export-controlled items.
Once a shipment enters an inquiry process, the impact is not limited to customs release. It can affect site installation windows, acceptance milestones, customer payment schedules, and the supplier’s delivery reputation. Export declaration consistency should therefore be treated as a project-management issue, not only as a customs-broker task.
Practical impact on this site’s product business
This site focuses on low-altitude surveillance radar, counter-UAS radar, and related low-altitude security applications. Based on the notice, the business impact is concentrated in four areas.
1. Product pages and specifications should avoid vague wording
Product materials should accurately describe civil application scenarios, performance parameters, and system boundaries. For models with longer detection ranges, stronger tracking capabilities, or integration into wider security platforms, public materials, quotation documents, and formal technical files should use a consistent vocabulary.
2. End-use information should be collected earlier in the enquiry stage
For overseas enquiries, it is not enough to ask only “how many kilometres of detection range are required.” The supplier should also understand the deployment site, end-user type, application scenario, whether an integrator will resell the system, whether a government or critical-infrastructure project is involved, and whether any re-export arrangement exists.
3. Contracts and delivery schedules should include compliance time
If a project may involve a dual-use export control code or licence requirement, the delivery schedule should reserve time for compliance review and licensing. Before the compliance path is clear, suppliers should avoid promising immediate shipment.
4. Technical support and software delivery also require review
The value of a low-altitude security system is not only in the hardware. It also includes software configuration, interface protocols, commissioning support, remote maintenance, and training. Export projects should define which technical materials can be shared, which require internal approval, and which must wait until licensing or compliance conclusions are clear.
Internal checklist for exporters
Before exporting low-altitude surveillance radar or a counter-UAS system, companies should complete at least the following internal checks:
- identify the exact model, configuration, and software version;
- review the dual-use export control list and relevant temporary control measures;
- determine whether a licence or other official procedure is required;
- obtain the full Chinese and English name of the overseas consignee;
- confirm the domestic manufacturer or selling entity rather than substituting a platform or agent name;
- prepare contracts, invoices, technical documents, and other supporting materials;
- verify the declaration remarks field, restricted/control identification code, and declaration elements;
- avoid simplified declaration in cross-border e-commerce scenarios and declare the complete tax code where applicable;
- retain end-user and end-use documents;
- establish a pre-shipment gate confirmed jointly by engineering, sales, logistics, and compliance teams.
This checklist is not a legal conclusion, but it helps project teams reduce customs delays caused by inconsistent documents.
Recommendations for buyers and integrators
Overseas buyers and system integrators should also understand that counter-UAS radar and low-altitude surveillance systems are high-value sensing systems. When a supplier asks about end user, end use, and project scenario, it is a normal compliance step rather than an unnecessary delay.
Buyers can prepare in advance:
- company and end-user information;
- project location and application scenario;
- whether the system will be used at an airport, energy facility, industrial park, border, port, or other critical site;
- whether resale, re-export, or third-party integration is involved;
- import, spectrum, equipment certification, and counter-UAS operation requirements in the destination country.
The more complete the information, the easier it is for the supplier to assess compliance path and delivery schedule.
Conclusion
The General Administration of Customs notice strengthens standardized export declaration for UAVs and related items. For low-altitude surveillance radar and counter-UAS radar companies, the key question is not simply “can this be exported?” It is whether the exporter has a consistent process covering product classification, technical documentation, customer use case, licence assessment, and customs declaration.
In real projects, compliance capability directly affects delivery capability. Companies that identify items early, prepare complete documentation, explain end use clearly, and keep declaration documents consistent are better positioned to control schedule risk in international low-altitude security projects.