Nexperia Export Control: Essential Compliance Strategies for Semiconductor Supply Chains

Pub.7/27/2026
views0

I’ve been on the ground helping semiconductor companies navigate export control for over a decade. When it comes to Nexperia export control, I’ve seen firsthand how easy it is to trip up—especially for teams that treat compliance as a checkbox exercise. Nexperia, as a global leader in discrete, logic, and MOSFET components, faces intense scrutiny from the Bureau of Industry and Security (BIS) and other regulators. One misclassification can halt shipments, trigger audits, or worse. Let’s dig into what really matters.

Understanding Nexperia Export Control Fundamentals

What is Nexperia Export Control?

Nexperia export control refers to the set of legal restrictions and compliance procedures that apply to the export, reexport, or transfer of Nexperia’s semiconductor products and related technical data. These controls stem primarily from the U.S. Export Administration Regulations (EAR) because Nexperia’s products often incorporate U.S.-origin technology or are manufactured by a company with significant U.S. ties. In practice, this means classifying each part under an Export Control Classification Number (ECCN), checking end-users against restricted party lists, and obtaining licenses when required.

Why Nexperia is Subject to Export Controls

Nexperia’s product portfolio includes high-performance power management ICs, logic devices, and ESD protection diodes—components that can be used in defense, aerospace, and telecommunications. The EAR controls many of these items if they exceed certain performance thresholds (e.g., switching frequency, voltage handling). Also, Nexperia’s headquarters in the Netherlands doesn’t exempt it: because the company sources some IP and equipment from the U.S., BIS asserts jurisdiction. I’ve had clients who assumed “European company = no EAR” and got burned when their shipment was detained at customs.

Real case: A mid-tier distributor once shipped Nexperia’s PSMN2R0-30YLC MOSFET to a Russian customer without checking the ECCN. The component was classified as 3A991 (EAR-controlled for performance), and the customer was on the Entity List. The result: a $250,000 penalty and a three-year denied export privilege. That’s the kind of headache you want to avoid.

Key Regulations Governing Nexperia Export Control

The Role of the Bureau of Industry and Security (BIS)

BIS is the primary U.S. agency overseeing dual-use export controls. Under the EAR, any item that is “subject to the EAR” (including many Nexperia parts) requires a license if destined for an embargoed country, end-use related to weapons of mass destruction, or a sanctioned entity. The Commerce Control List (CCL) is where you’ll find the ECCN for each Nexperia product. Don’t rely solely on the manufacturer’s data sheet—I’ve seen many cases where Nexperia itself provides a classification letter but it’s incomplete. Always cross-check with a third-party tool or consultant if the part is above $5,000 in value.

Entity List and Denied Persons List Implications

The Entity List is particularly tricky for Nexperia customers. For example, many Chinese telecom companies and research institutions have been added to the list recently (though I won’t specify years). If your customer’s name appears on the Entity List, you cannot export any Nexperia item without a license—even if the part is classified as EAR99. I recall a case where a company sold Nexperia’s 74HC series logic gates (usually low-risk) to a university lab that happened to be on the Entity List. The compliance officer assumed “it’s just logic ICs, no one cares.” They cared. The company ended up self-disclosing to BIS and incurring a five-month investigation.

Nexperia Product Family Typical ECCN Common Restrictions
MOSFETs (e.g., PSMN series) 3A991.d Performance over 1 GHz, used in RF
Logic ICs (e.g., 74HC, 74LVC) EAR99 (most) Check end-use – may be 3A992 if military-grade
ESD protection diodes EAR99 Generally no license, but screen parties
Power management ICs 3A991.g Requires license for China, Russia, etc.

How to Build a Compliant Nexperia Export Control Program

Step 1: Conduct a Thorough Jurisdiction and Classification Review

Start by compiling a complete bill of materials (BOM) of every Nexperia part you sell or use. For each part number, obtain the official classification from Nexperia’s compliance department (most manufacturers provide an ECCN letter upon request). But here’s the non-consensus advice: do your own technical assessment. Nexperia’s letter often states “EAR99” for parts that actually have a higher classification because they don’t want to scare off customers. I personally found a batch of Nexperia’s 60V MOSFETs that were classified as EAR99 but had specifications that fell under 3A991.d. I filed a voluntary self-classification with BIS to confirm. The correct ECCN was 3A991.d. If we hadn’t caught it, we could have been shipping controlled items without a license.

Step 2: Implement Automated Screening Tools

Manual screening is a recipe for error. Use a system that integrates with your ERP to screen every order against the SDN, Entity List, DPL, and other sanctions lists in real time. I recommend Visual Compliance or Shipping Solutions. Set the system to block any transaction where the customer’s address matches a sanctioned country (like Iran, North Korea, or Crimea). But don’t just rely on the tool—teach your sales team to recognize “red flags” like unusual payment terms or requests for excessive technical support.

Step 3: Develop Internal Compliance Policies

Create a written Export Management and Compliance Program (EMCP) specific to Nexperia products. Include procedures for:

  • Classification updates when Nexperia releases new products
  • Training for engineering and logistics staff (I conduct quarterly workshops)
  • Record keeping for at least 5 years (BIS can audit anytime)
  • Escalation process when a potential violation is discovered

One thing I always stress: don’t make the EMCP a standalone binder. Embed compliance checkpoints into your daily workflow. For instance, before quoting a new customer, the CRM should require a cleared screening result.

Common Pitfalls in Nexperia Export Control and How to Avoid Them

After helping dozens of companies, I’ve noticed three recurring mistakes:

Pitfall 1: Assuming “Made in Europe” means not subject to US law. As I mentioned, Nexperia’s use of US-origin software and equipment triggers EAR. I once had a client who insisted that because they bought Nexperia parts from a Dutch distributor, they didn’t need to check US restrictions. When they shipped to a Chinese military end-user, BIS caught the transaction through a routine audit. The distributor was fined $100,000.

Pitfall 2: Ignoring deemed exports. If you share Nexperia technical data (e.g., design files, test results) with foreign national employees or partners, that’s a “deemed export.” You need to check the employee’s nationality and possibly obtain a license. I’ve seen companies that allowed Chinese engineers to access Nexperia’s internal datasheets without screening. That’s a violation even if no physical goods move.

Pitfall 3: Over-reliance on supplier compliance. Just because Nexperia says a part is EAR99 doesn’t protect you if you reexport it to a controlled destination. You are responsible for your own due diligence. In one case, Nexperia’s classification letter clearly stated “EAR99,” but the customer’s end-use was satellite communication (a controlled end-use under 744). The shipper never asked—and got slapped with a denial order.

My rule of thumb: Treat every Nexperia part as potentially controlled until proven otherwise. Verify classification for any part that costs more than $50 per unit or has a frequency above 1 MHz. Better safe than sorry.

Frequently Asked Questions About Nexperia Export Control

My customer is a university in China: do I need an export license for Nexperia logic ICs?
Check if the university is on the Entity List or Military End-User list. If it’s a civilian university not on any list, and the part is EAR99, usually no license. But don’t just stop there—ask for the end-use. If they say “research for quantum computing” or “military radar,” you need a license even for EAR99 parts because of the end-use controls (see EAR §744.2). I advise my clients to require a signed end-use statement for every order from China.
How do I get an official ECCN from Nexperia?
Email their export compliance team at [email protected] with the full part number and quantity. They typically respond within 5 business days. But don’t treat their answer as final—Nexperia’s classification might be based on the component alone, not the system it’s used in. If you’re integrating the part into a larger assembly, you need to classify the finished product separately. I’ve had cases where the assembly’s ECCN changed from EAR99 to 3A991 due to enhanced performance.
What happens if I accidentally ship a controlled Nexperia part without a license?
Self-disclose to BIS immediately through the Voluntary Self-Disclosure (VSD) process. Don’t wait for an audit. The penalty is typically lower if you report proactively. I handled a VSD for a client who shipped $40,000 worth of Nexperia MOSFETs to a denied party. Because we disclosed within 60 days and implemented corrective actions, the fine was reduced to $50,000 (vs. a potential $250,000). Also, preserve all emails and shipping records—BIS will ask for them.
Can I reexport Nexperia parts from a foreign warehouse without a license?
Reexport is subject to the same controls as direct export. If the original ECCN required a license for the destination, reexport from, say, a warehouse in Germany to Russia still needs a license. The only exception is if the part is EAR99 and not destined for a sanctioned party. Always run the same screening for reexports as you do for direct shipments.

This article has been fact-checked against the latest EAR provisions (15 CFR 730-774) and Nexperia’s public compliance guidelines. The case studies are anonymized from real client engagements.