A European prime sends an RFQ for 40 reaction wheel assemblies. The sales team is ready to quote. Then compliance flags the line item: ITAR-controlled, DSP-5 required. The prime’s procurement lead replies with one sentence: we will go with an ITAR-free supplier.

Nobody on that deal checked whether the part was ever ITAR-controlled in the first place. It was classified that way three years ago by an engineer who was told “when in doubt, call it ITAR.” That habit feels conservative. In practice it is a pricing decision your sales team never got to make.

The gap between ITAR and EAR treatment of space parts has widened since 2024. Teams that have not revisited their classifications are paying for that gap in lost allied deals.

Why “ITAR to be safe” is a revenue decision

Since October 2024, many spacecraft parts and components under ECCN 9A515.x ship license-free to a large group of allied countries. BIS’s interim final rule removed license requirements on certain 9A515.x items for more than 30 US allies, which also ended the need to use License Exception STA for those exports. A companion final rule went further for Australia, Canada and the UK on certain remote sensing and servicing spacecraft items.

That relief only applies to parts that are actually classified under the EAR. A part your records call USML Category XV gets none of it. Every foreign sale needs a DSP-5. Every technical exchange with the customer’s engineers needs a license or a TAA. Our post on the ITAR deemed export trap explains how quickly those technical exchanges add up.

Over-classification is not a safe default under the law either. Labelling an EAR item as ITAR does not make you more compliant. It means your records are wrong, your licenses cover the wrong regime, and an auditor will ask why.

How the leak shows up in the pipeline

The revenue loss rarely shows up as a lost deal labelled “export controls.” It shows up as slow quotes, shortlists you never make, and renewals that quietly move to a European or Japanese competitor.

Three patterns are common:

1. Qualification friction. Allied primes and space agencies run supplier qualification with export status as an early filter. An ITAR flag can remove you before your price or performance is ever compared.
2. Quote-cycle delay. A DSP-5 adds weeks to months before the first unit ships. For a customer on a launch schedule, that delay is often the deciding factor.
3. Engineering lockout. Integration support, anomaly reviews and design changes all need technical data to flow. Under ITAR, every one of those conversations needs authorization. Under 9A515.x, many of them do not.

Investors and acquirers notice too. In mission assurance data room audits, we covered how buyers discount companies whose compliance records do not hold up. A BOM full of unjustified ITAR flags reads as both a revenue ceiling and a records problem.

What a defensible reclassification looks like

Reclassification is not relabelling. You cannot move a part to the EAR because it would be commercially convenient. You need a documented analysis that would survive a DDTC or BIS review.

A defensible review usually runs in this order:

1. Start from the USML entry, not the part. Check whether the item is enumerated in Category XV or caught by a “specially designed” catch-all. Most over-classified parts are catch-all calls, not enumerated items.
2. Run the “specially designed” releases. Test each release in 22 CFR 120.41(b) and record the result. DDTC’s October 2026 proposed rule would add two more, including one for basic parts like brackets, hinges, switches and fuses.
3. Classify under the EAR. If the item is released from the USML, assign the ECCN, usually in the 9×515 family for spacecraft parts, and confirm whether the .x relief applies to your target countries.
4. Request a commodity jurisdiction ruling where it is unclear. A CJ determination from DDTC settles the question for that item and gives you a record you can show customers.
5. Fix the supplier data. Many over-classified parts come from a supplier’s own ITAR flag passed through without review. Our post on COTS component export controls covers how to challenge supplier classifications.

Do this with export counsel, and document every step. The goal is a classification record that holds up, not a shorter ITAR list.

Where to start this quarter

Pull the parts that appear in allied deals first. Take the last 12 months of RFQs from Europe, Japan, Australia, Canada and the UK. List every line item that triggered a license request or a lost deal. That list is your reclassification priority, ranked by revenue at stake.

Then ask one question in your next pipeline review: for every ITAR-flagged part in an allied deal, can your team show the analysis that put it on the USML?

If the answer is no, you are carrying unnecessary regulatory risk. We built Astrolytics specifically to eliminate this blind spot, giving you dual-regime ITAR and EAR classification with overlap detection on every BOM line so you can open allied markets with parts that never needed a DSP-5. See how we secure your mission architecture at Astrolytics.