Chinese Memory Chip Rules Stop Short of a Private Purchase Ban
Primary lensTrade policy
Sub-topicPolicy monitoring
Evidence base11 records used
Use casePolicy monitoring
The letter asks Commerce to cross the private-market line
The July 14 House letter to Commerce Secretary Howard Lutnick presents three numbered recommendations. The first combines tighter Entity List restrictions on Yangtze Memory Technologies Corporation with a faster review of ChangXin Memory Technologies for the same list. The second asks for an executive order or agency directive that would stop specified U.S. purchases of memory from listed Chinese companies. The third calls for coordination with key allied governments.
The private-purchase recommendation is the consequential one. It would reach U.S. persons and U.S.-incorporated entities procuring DRAM, high-bandwidth memory and other memory components for artificial intelligence systems, data centers, federal information technology and critical infrastructure. The lawmakers present the package as a response to a global memory shortage.
Congress has already enacted two procurement regimes that expressly reach YMTC and CXMT. One is a Department of Defense regime for contracts and, from June 2027, specified grants, loans and loan guarantees. One contracting prohibition is already in effect. The other reaches executive agencies and begins in December 2027. They do not cover the same buyer, the same product layer or the same evidence.
Neither law is a general ban on commercial purchases by private U.S. companies. That leaves the July 14 request with a legal design problem hidden by the word procurement. The government already has federal purchasing restrictions. The new step would be a rule for private buyers.
Those lists do different legal work. Section 1260H identifies companies under a defense statute. The designation becomes a contracting trigger when another law attaches a prohibition to it. It is not by itself a rule against every commercial transaction with the named company.
The Entity List is an export control instrument. It imposes license requirements on exports, reexports and transfers of items subject to the Export Administration Regulations when a listed party is involved. It does not operate as a blanket import or purchase ban. BIS says in its current Entity List guidance that listing does not create a prohibition on purchases from that entity. BIS still treats dealings as a red flag and warns buyers to examine whether U.S.-origin or other controlled items reached the seller lawfully.
Adding CXMT to the Entity List could restrict what the company receives. It would not, without another operative rule, prohibit a U.S. company from buying every CXMT memory product.
Section 805 now runs through a class deviation
The current Section 805 statutory note creates three Department of Defense restrictions tied to the Section 1260H list. The first bars the department from entering, renewing or extending a covered contract for goods, services or technology with a listed entity or an entity it controls. That restriction took effect on June 30, 2026. A savings clause excludes contracts entered before the applicable date, including when they are later modified, extended or renewed. A 2025 amendment added grants, loans and loan guarantees to the later phase.
A listed counterparty is only the first fact. Section 805 excludes components from all three restrictions. A Department contract with YMTC or CXMT can therefore require both a listed-entity screen and a finding about what the company is supplying. The effective date passed only two weeks before the House letter, which makes the product analysis a current contracting issue.
DoD implemented that first phase through Class Deviation 2026-O0025. Revision 2, signed July 16, tells contracting officers not to award, renew or extend a contract on or after June 30 with a current Section 1260H company operating in the United States or an entity it controls. It excludes contracts awarded before June 30, including when they are later modified, extended or renewed. The deviation provides an offeror representation and a contract clause, including for commercial products and services, while preserving a component exception.
Permanent rulemaking remains incomplete for the next phase. The July 10 open DFARS cases report removes the June 2026 direct-entity provision from Case 2024-D012 because the class deviation implements it. The case now centers on the June 2027 goods and services prohibition, with a team report due September 30, 2026.
The next phase begins on June 30, 2027. For contracts entered on or after that date, it reaches goods or services that include goods or services produced or developed by a listed entity. Contracts entered before the date remain excluded even when later modified, extended or renewed. The 2025 grant and loan restriction begins on the same date. Both restrictions remain subject to the component exclusion.
Title 41 defines a component as an item supplied to the Federal Government as part of an end item or another component. A memory chip embedded in a server can therefore present a different Section 805 issue from a purchase in which a memory device is itself the end item.
The word chip does not decide the result. The contracted item and the role of the memory device in that item control the analysis. Contractors need the bill of materials and contract object before deciding whether Section 805 applies or stops at the component line.
Section 5949 reaches the chip inside the product
Section 5949 of the FY2023 defense law is the second procurement regime. It names semiconductor products and services designed, produced or provided by SMIC, CXMT and YMTC, including products from their subsidiaries, affiliates and successors. Its prohibitions take effect on December 23, 2027 and apply across executive agencies.
The first limb bars an agency from procuring electronic parts, products or services that include a covered semiconductor product or service. This language is built to follow the chip into a larger electronic offering. The second limb addresses contracts for electronic products that use other electronic products containing covered semiconductors. Congress limited that second contract prohibition to critical systems.
The February 2026 FAR Case 2023-008 document proposes how agencies and contractors would carry those commands into procurement. It is not a final rule. The notice set April 20, 2026 as the comment deadline, and the proposed text still contains placeholder clause numbers.
If finalized as proposed, the rule would reach micro-purchases, commercial products and commercially available off-the-shelf items. An offeror would conduct a reasonable inquiry, certify its result and disclose a noncompliant offering. Suppliers at the next lower tier would conduct their own inquiry and certification. The proposal would permit good faith reliance on a lower-tier certificate unless a discrepancy or reason for doubt appears. It would not require an independent third-party audit.
Beginning in December 2027, Section 5949 is designed to reach much of the embedded chip space that Section 805 leaves open. It would cover a wider set of federal buyers under a different product test. The proposed evidence system is not yet final.
Both statutes put supply availability in the relief test
The House letter uses the memory shortage as a reason to prevent dependence on Chinese suppliers. The enacted procurement laws also require the government to test availability when it considers relief.
Section 805 permits the Secretary of Defense to grant a waiver when an applicant provides a compelling justification for more time and a phase-out plan. The waiver may remain until the Secretary determines that commercially viable providers outside China can and will supply the Department with quality goods and services in the quantity demanded.
Section 5949 permits an executive agency waiver when a compliant product or service is unavailable when needed at U.S. market prices, or is prohibitively expensive, and the agency also finds that relief would not reasonably compromise critical national security interests. The proposed FAR rule adds a separate temporary exception for commercial products and services with no alternative source through December 23, 2028.
These provisions do not settle whether a particular memory shortage justifies relief. They identify the evidence the government must examine. Quantity, timing, price, alternative sources, national security and a phase-out record are part of the statutory architecture. A private buyer rule would need to say how those facts affect its own exceptions or waivers.
The private buyer remains outside both regimes
Section 805 governs Department of Defense contracts. Section 5949 governs executive agency procurement and the contractors supplying covered electronic offerings. Neither provision turns a purely commercial memory purchase by a private U.S. company into a prohibited transaction merely because the supplier appears on the Section 1260H list.
The Entity List does not supply the missing rule. Its license requirements govern the movement of items subject to the EAR to a listed party. BIS expressly distinguishes that control from purchasing goods from the listed party. Other laws and end use rules can still apply, but the list alone is not the commercial market ban described in the letter.
Any executive order or agency directive would have to identify an authority that reaches the buyer and transaction at issue. It would also have to say whether the regulated purchase occurs only in the United States or includes procurement abroad by a covered U.S. entity.
Product scope cannot be left at Chinese memory either. DRAM, high-bandwidth memory, NAND flash, a packaged chip, a memory module and a server containing those items occupy different places in a supply chain. A workable rule must state whether it follows a named producer's chip into any finished product or only into specified systems and end uses.
Commerce has used a separate authority to regulate private supply chain transactions in another sector. The connected vehicles rule relies on Executive Order 13873 and the International Emergency Economic Powers Act to restrict specified vehicle connectivity hardware and software transactions. It does not cover memory chips as a product class. Extending that structure to memory would require a new sector record, product definitions and rulemaking.
The July letter does not choose an authority or provide those definitions. It asks Commerce to build that legal bridge.
Contractors need a product evidence file
Contractors should keep the two procurement regimes separate now. For Section 805, the record begins with the legal counterparty, current Section 1260H status, control relationships, contract date and the object of the Department contract. The file should show whether the company itself produced or developed the relevant good or service and whether the disputed item is supplied as an end item or as a component.
The first routing decision is the buyer, product layer and contract vintage. A direct DoD contract awarded on or after June 30, 2026 with a listed entity belongs in the Section 805 file, with the component exception tested against the contract object. A contract awarded before that date stays outside the first prohibition even if later modified, extended or renewed. A DoD contract entered on or after June 30, 2027 that includes listed-company output requires an end-item versus component determination. An executive-agency offering containing a covered chip belongs in the December 2027 Section 5949 file. A purely private purchase belongs in a separate policy watch file unless another operative restriction applies.
For Section 5949, preparation moves deeper into the product. The proposed FAR inquiry would require an offeror to identify the source of semiconductors in electronic products and services offered to the government. When public information is not enough, the proposal sends the inquiry to the next lower tier.
A useful evidence file should connect supplier name, manufacturer, model and part number to the chip source and the electronic product containing it. It should identify the government customer, the offered service, any critical system status, the contract date and the basis for an exception or waiver. Supplier certifications should be preserved with the discrepancies that were investigated rather than filed as untested assurances.
Private manufacturers need a separate watch file. It should distinguish a current legal restriction from a requested policy action, map which products use YMTC or CXMT memory and record where the purchase and end use occur. That file allows a company to respond if Commerce proposes a rule without pretending that the July letter is already law.
The next instrument must define the market boundary
A proposed rule, executive order or other legal instrument would need to identify the authority and the regulated act.
Any instrument must name the buyer and the regulated geography first. Product and end-use definitions would determine whether it follows a bare die into a finished system. Evidence rules would decide what a buyer may rely on, while exceptions and waivers would address the absence of a compliant alternative on the required date.
The same definitions would guide allied coordination. Allied governments would need to know whether Washington is asking them to restrict exports to a producer, imports from a producer, government procurement, private purchasing or the use of covered memory in named systems.
Treat Section 805 as a DoD counterparty and contract-object review. Treat Section 5949 as an embedded-chip sourcing program for December 2027. Keep any private-buyer restriction in a separate watch file until Commerce identifies an authority and publishes an operative instrument.
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.