Supply chain and resilience
What Export Controls Change for Electronics Teams
Who needs a licence, for what, and the engineering consequences nobody budgets for.
Export controls are a compliance topic, which is why most engineers never read anything about them until a supplier asks for an end-use statement and the schedule stops.
This note is about what they change for the engineering and procurement side of a hardware team: who needs an authorisation, for what, and which parts of the work get longer.
As of November 2026, the facts below reflect the European Commission's published guidance. Export control regimes are updated frequently, including by delegated acts that change the control list without changing the regulation itself. Treat any specific list entry as something to verify rather than to remember.
The position. Export controls do not usually stop a product. They add an approval step, an information requirement and a destination dependency to work that previously had none. Those three additions are schedule items, and they are the ones nobody budgets for.
What the EU regime actually requires
Under Regulation (EU) 2021/821, dual-use items are goods, software and technology usable for both civilian and military applications. The published guidance sets out the structure:
- The control list is Annex I of the Regulation, updated by delegated
regulation. The Commission notes that the Excel version of the list is for information only and has no force in law, which is a useful reminder that the authoritative text is the legal one.
- Authorisations come in four kinds: EU general authorisations for
specified destinations and conditions, national general authorisations, global licences covering one exporter across multiple items or destinations, and individual licences for one exporter and one end user.
- Controls can reach unlisted items through end-use provisions, and
Member States may add national controls.
- The regime covers more than shipping goods, including brokering,
technical assistance and transit.
Other jurisdictions differ in detail and agree in shape.
What changes for an engineering team
| Area | Before | After |
|---|---|---|
| Part selection | Availability and price | Availability, price and jurisdictional exposure |
| Supplier onboarding | Commercial terms | End-use statements, destination declarations |
| Documentation | Manufacturing package | Plus classification records, kept per released version |
| Lead time | Manufacturing and logistics | Plus authorisation time, which is outside your control |
| Variants | Technical reasons | Possibly a market-specific configuration to maintain |
The last row is the expensive one. A product that needs a different configuration per destination has doubled its configuration management burden permanently, and that burden is paid by engineering long after the compliance question is settled.
The engineering consequences nobody budgets for
- Classification is per item and per version. A design change can alter a
product's classification, which means the question returns at every major revision.
- Technical assistance counts. Sending detailed design support across a
border can itself be controlled, which affects how distributed teams work.
- Documentation becomes evidence. When a compliance question arrives, it
is about what was released, in what configuration, on what date.
- Approvals are serial, not parallel. An authorisation cannot start until
the information is complete, and the information is usually engineering's to produce.
What a good hardware team should know
- Do not guess at classification. It is a formal determination made by
the people responsible for it, in writing.
- Know your jurisdictional single points. A function available only from
one regime is a risk with a different trigger from a single-source part.
- Keep release records that can answer a question years later. This is
ordinary configuration management, used for an unusual purpose.
- Expect the rules to move. Anything specific you memorise today may be
superseded by a delegated act.
Where structured engineering data helps
A compliance question is an impact-analysis question with a different motivation: which products, at which released versions, contain what, and what was shipped where. XKEMA records products, versions, BOMs and components as related objects with release state, which is the data such a question needs.
XKEMA does not classify items, does not track regulatory changes and does not give compliance advice. It holds the record that a classification decision is made against.
Sources
- European Commission, Exporting dual-use items — Regulation (EU) 2021/821, the Annex I control list, the four authorisation types, end-use controls and the coverage of brokering, technical assistance and transit. Consulted November 2026.
- NASA Systems Engineering Handbook Rev 2, section 6.5 — configuration status accounting, which is what lets a team answer a question about a configuration released years earlier.