An Unlisted Chinese Fab Can Still Require an Export License
For specified China chipmaking exports, an unknown production node can trigger a license requirement even when the customer is absent from the Entity List.
Primary lensExport controls
Sub-topicLicensing regime
Evidence base7 records used
Use caseExport-control exposure
An exporter can clear a Chinese chipmaker's name against the Entity List and still need a license to supply its factory. For specified items, the existing semiconductor rules expressly cover a known chipmaking destination whose technology level remains unknown.
That distinction gives practical weight to Representative John Moolenaar's September 18 letter to President Trump, pages 1 and 3. Writing ahead of the Trump-Xi summit, he questioned the lack of routine Entity List designations and urged stronger controls on semiconductor manufacturing technology. His concern about new designations does not establish that all list activity stopped. BIS removed two Arrow Electronics addresses in August.
For an export compliance lead, the immediate issue is an order awaiting release. A designation can make a restriction easier to identify. Its absence leaves the exporter to apply rules that already turn on the factory, intended use and information available inside the business. Some of that information may sit with the people quoting, installing or servicing the equipment.
Unknown technology is an express licensing case
Section 744.23(a)(2)(ii), the semiconductor facility rule, addresses a specific combination of facts. The item must be subject to the Export Administration Regulations and classified in a Category 3 ECCN in Product Group B, C, D or E. These groups cover equipment, materials, software and technology.
The exporter must know that the item will be used in integrated-circuit development or production and is destined to a facility in China where integrated-circuit production occurs. China is one of the destinations covered by the rule. If the exporter does not know whether advanced-node IC production occurs at that facility, the provision requires a license.
An unanswered questionnaire alone does not establish those predicates. Conversely, once they are present, leaving the technology field blank does not remove the requirement. The rule deliberately assigns a consequence to that uncertainty.
The following comparison concerns those two facility provisions. The exclusions discussed below apply throughout.
What is established about the Chinese facility
Item scope
Result under the facility provisions
Advanced-node IC production occurs, and the specified IC development or production use is known
Any item subject to the EAR
Section 744.23(a)(2)(i) requires a license
IC production occurs and the specified use is known, but advanced-node production status is unknown
Items subject to the EAR in Category 3, Product Groups B through E
Section 744.23(a)(2)(ii) requires a license
The evidence establishes that advanced-node production does not occur
The proposed item still requires its own classification and jurisdiction review
These two facility provisions do not establish a license requirement. Other EAR controls still require review
The factory needs a technical answer
A customer's description of its business as a mature-node producer may help, but it must answer the regulatory question about the destination facility. The file should identify the production activity and the basis for the technology assessment. A corporate label or the specifications of the one chip associated with the order may leave other production at that facility unresolved.
This is where a commercial record can change the legal conclusion. An installation plan identifies where a tool will operate. A configuration request can reveal what process it is meant to support. Information already received by the supplier may support the customer's account or create a reason to question it.
BIS made that connection explicit in its December 2024 semiconductor rule, 89 FR 96790. The agency said it would continue identifying entities while exporters continued examining transactions for red flags. Its accompanying guidance treats a non-advanced fab's order for equipment inconsistent with its stated technology as a concern requiring resolution.
The inquiry is different from the classification presumption examined in Traverse's foundry due-diligence analysis. Here the exporter is reviewing supplies for the production facility. The decisive uncertainty concerns what that facility makes.
A distributor's name can leave the end user unresolved
BIS Red Flag 21 describes an equipment order through a distributor without a manufacturing operation when the item would ordinarily be customized for, or installed at, the actual user. The distributor's clean name does not answer who will use it.
That concern precedes the unknown-node test. If the actual facility is unresolved, the exporter cannot simply assume the transaction falls within, or outside, that particular provision. It needs to resolve the facts that determine the applicable rule.
A new account can also carry an old customer's operational history. Red Flags 24 and 25 address overlapping senior or technical leadership with a listed entity and requests for items or services customized for a customer now listed. These are inquiry triggers. They do not establish that every successor business is restricted.
Routing relevant sales and engineering information into the release decision is therefore more useful than adding another copy of the same name-screen result.
The exclusions change the result
Section 744.23(a)(5) excludes back-end assembly, testing and packaging from production for these purposes when those activities do not alter the IC technology level. Calling a site a packaging facility is insufficient if the relevant work changes that level. BIS provides an advisory-opinion route for uncertainty over the manufacturing stage or its effect.
Footnote 5 entities receive a different treatment. Paragraph (a)(2)(iv) removes items destined to those entities from the two facility licensing provisions. Applicable Entity List and foreign direct product requirements remain separate checks. That exclusion cannot support a general no-license conclusion.
Nor does the Affiliates Rule suspension suspend this facility inquiry. The November 2025 stay concerns specified automatic ownership-based extensions and the associated Red Flag 29. The stay runs through November 9, 2026 under the current rule. Red Flags 21, 24 and 25 and section 744.23's semiconductor facility provisions remain in place.
Release the order on the resolved facts
The release record should connect the item's classification and EAR jurisdiction to the actual destination, known use, technology assessment and any suspicious circumstances resolved before shipment. This is a practical way to document the decision, not a new government-prescribed form.
BIS's KYC guidance permits reliance on customer representations absent red flags or an express EAR requirement. It also tells firms not to block relevant information and warns that employee knowledge can be attributed to the company. A blanket demand to investigate every customer would overstate that guidance. Discarding an engineer's contrary information would miss its point.
Where the unknown-node provision applies, the exporter needs a license before the covered transaction. Section 744.23(c) supplies no license-exception route for these facility provisions. Approval is a separate question under the applicable review policy.
A later technical explanation can change which provision applies. A different installation site, changed end user or new evidence of advanced production can reopen the conclusion. Those are reasons to revisit an order before release, even if the Entity List looks exactly as it did when the customer was onboarded.
From reading to review
Run the numbers on your lane.
The duty calculator runs the current stack for any HTS code and origin. A free account opens full tool output, AD/CVD detail, Chapter 98 processing, and available exports.