An H200 Export License Does Not Prove Market Access in China
Nvidia held U.S. H200 export licenses for Chinese customers but shipped only a fraction of the approved volume. Five stages determine market access.
Primary lensExport controls
Sub-topicLicensing regime
Evidence base7 records used
Use caseExport-control exposure
The public record now supports two facts about H200 sales to China that sound contradictory until the transaction is broken into stages.
The company received U.S. licenses for small amounts of H200 products for specified Chinese customers. Yet its August 26 Form 10-Q says it shipped only a fraction of the quantity allowed. Those shipments produced less than 1% of its latest quarterly Data Center revenue. Nvidia also says Chinese government restrictions prevented it from selling all the products covered by its licenses.
The better measure is conversion: how much authorized volume became usable customer capacity. U.S. authorization and customer access diverged.
The distinction matters beyond Nvidia. For an export compliance manager, an H200 license is one event in a chain that continues through inspection, shipment, import clearance or other Chinese regulatory acceptance, installation and remote use. Treating the license as the finish line leaves the most commercially important part of the transaction unmeasured.
Why this is new: the license opened a route, not a market
BIS changed its review policy in January for certain advanced computing chips shipped from the United States to China or Macau. Applications that meet the rule's conditions, including H200 products and comparable AMD chips, may receive case-by-case review. Reexports, exports from abroad and in-country transfers did not receive the same general change.
The route is narrow. At application, the exporter must show that aggregate TPP exported to China and Macau is no more than 50% of aggregate TPP shipped to U.S. customers for U.S. end use, measured from commercial launch through the application date. Before export, a qualified U.S.-based third-party lab must certify every shipment; the rule permits representative sampling of a batch. Nvidia says that inspection step brings the chips into the United States and exposes them to a 25% tariff that it has not been able to pass to customers.
The rule therefore creates permission to attempt a sale. It does not settle whether Chinese government restrictions allow the customer to take delivery, whether the shipment clears the required steps, where the chips are installed or who eventually uses their computing capacity.
This is the piece missing from a simple debate over whether Washington has tightened or relaxed semiconductor controls. Traverse previously mapped the Trade Expansion Act Section 232 semiconductor policy stack. The latest filing shows why a downstream test is needed: it identifies licenses, shipments of only an unspecified fraction of the permitted volume and limited revenue, but does not disclose how much capacity was installed or became usable.
BIS already separates the buyer from the user
The H200 application conditions make remote use part of the export file. The applicant must obtain the ultimate consignee's Know Your Customer procedures for preventing unauthorized remote access. It must also provide BIS with a list of intended Infrastructure-as-a-Service remote end users located in China, Macau or six other named destinations, as well as entities headquartered or ultimately parented in any of those eight destinations.
If the ultimate consignee or end user provides Infrastructure-as-a-Service, the applicant must verify that the ultimate consignee and any IaaS end user comply with the restricted-party conditions, do not transfer model weights to an undisclosed user without BIS authorization and do not give a covered prohibited party remote access to an algorithm trained on the licensed hardware.
Those conditions identify intended users in a way that a purchase order cannot. They do not prove who actually received the compute after the chip reached the approved facility.
They do not mean that every overseas cloud route is already covered by an H200 license. The conditions attach to this specific U.S. export pathway. H.R. 2683 addresses a different boundary: a foreign person's network or cloud access to an item subject to U.S. jurisdiction from a location other than where the item is physically located. Traverse examined that proposed authority in its H.R. 2683 hosted model access analysis. The two files should not be collapsed. One governs a licensed shipment and its conditions; the other concerns a proposed power to regulate remote access itself.
Five states replace the sold-or-blocked binary
Taken together, the Nvidia filing and the BIS license conditions support a five-state internal-control model for market access.
First, BIS authorizes a quantity for a named transaction. Second, the product completes the required U.S. inspection. Third, the exporter ships some or all of the authorized quantity. Fourth, the importing jurisdiction admits the hardware and the customer installs it at the disclosed site. Fifth, where the IaaS provisions apply, the operator allocates capacity while the applicant discloses the categories of intended remote users specified by the rule and verifies the applicable access conditions.
A transaction can stop at any of those points. In Nvidia's case, the public record confirms licenses, a fraction of allowed shipments and revenue below 1% of quarterly Data Center sales. It does not support the claim that no H200 changed hands. Nor does it show that the full licensed quantity became installed, approved computing capacity.
The same distinction should govern policy claims. A license approval measures U.S. willingness to permit a transaction. A shipment measures physical movement. Revenue measures a commercial sale. A required remote-user disclosure identifies intended users in the categories covered by the rule, while system logs show actual access. None is a substitute for the others.
What export compliance managers should do
Keep one H200 authorization-to-use workbook across all licensed customers. In an authorization tab, use one row per license-customer-site combination: license number, product, approved quantity, ultimate parent, test date, quantity shipped, import disposition, installation site and operator.
As an internal control extending beyond the rule's minimum disclosure fields, a linked remote-user tab should use one row per disclosed or risk-relevant user. Carry the authorization key, legal name, headquarters, ultimate parent, account administrator, approved geography, resource allocation, KYC reference and any model-weight or algorithm-access assurance. An evidence tab can point to access logs and retention locations without copying session data into the workbook. Date every tenant, subtenant and administrator change and record whether the license still covers it.
Three checks follow from the file. Authorized quantity must reconcile with tested and shipped quantity. Shipped quantity must reconcile with admitted and installed quantity. Installed capacity should reconcile with the operator's current access-control roster. Operator logs, rather than the intended-user list alone, must provide the evidence of actual access. A gap in any reconciliation is a different problem, with a different owner.
Caveats and what would change the calculus
The House passed H.R. 2683 in January, but the bill has not become law. The House text would add to the Export Control Reform Act a defined power to regulate a foreign person's remote access, through a network or cloud service, to an item subject to U.S. jurisdiction when Commerce finds a serious national-security or foreign-policy risk. CBO describes the current boundary plainly: BIS can regulate exports, reexports and in-country transfers, but lacks comparable authority when foreign entities remotely access covered items.
That pending authority should not be written into today's H200 file as if it were already operative. The current license conditions are real and detailed. The broader remote-access regime remains a legislative watch item.
For now, the useful conclusion is narrower. An H200 license does not prove that China received the approved quantity, and a shipment does not prove that only the disclosed users received the compute. The authorization-to-use ledger is what connects those events. It turns a noisy argument about whether China accepted an offer into an auditable account of where U.S. permission ended and actual access began.
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.