Allocation vs Stock vs Executable Supply — What the Terms Actually Mean
Stock, a supplier offer, an allocation, executable supply and a purchase order are five different states of GPU supply, and the market often calls all five "available". Stock is hardware that physically exists and can be inspected. A supplier offer is a price and a date from someone in the chain: a statement, not evidence. An allocation is a share of constrained future production committed by the manufacturer or OEM channel to a specific order and deployment. Executable supply is an offer that the named supplier has confirmed it can fulfil on stated terms. A purchase order is the buyer's binding commitment against that confirmation. Each state is confirmed by a different party and proved by a different document. Knowing which one is on the table tells a buyer what can be checked, by whom, and what is still missing.
What are the five states of GPU supply?
The five terms describe how far a unit of supply has moved from "someone says it exists" to "both sides are committed". They are not synonyms and they are not grades of confidence in the same thing. Each answers a different question, and the gap between them is where most failed GPU purchases are lost.
| State | What it is | Who can confirm it | What proves it | What it does not prove |
|---|---|---|---|---|
| Stock | Finished hardware that exists now, at a known location | The party that holds it | Serial numbers that match the configuration and check out with the OEM; inspection | That it is reserved for this buyer, that the seller controls it, or that it can ship to this end user and destination |
| Supplier offer | A price, configuration, quantity and claimed date from any party in the chain | Only the party making it | Nothing beyond the seller's willingness to sell on those terms | That the units exist, that the seller can obtain them, or that the date is more than an estimate |
| Allocation | A committed share of constrained future production, assigned to a particular order for a particular deployment | The party that assigned it: the manufacturer or OEM channel | Written confirmation traceable to that party, referring to this order | The final price or date, or that it survives a change of end user, site or configuration |
| Executable supply | An offer the named supplier has confirmed it can fulfil on stated terms | The supplier that will actually fulfil the order | A written confirmation stating configuration, quantity, terms, validity and remaining conditions | Delivery; the listed conditions still have to be met |
| Purchase order | The buyer's formal commitment to buy on the terms of executable supply | The buyer issues it; the supplier accepts it | The purchase order and the supplier's order acknowledgement | Shipment, export clearance or acceptance on site |
What counts as stock?
Stock is finished hardware that exists now, at a known location, under the control of a named holder. For data-center GPUs that means a built system or a boxed card with serial numbers, not a line on a price list and not units "coming in next month".
Who can confirm it. Only the party that physically holds or controls the hardware.
What proves it. Serial numbers that match the offered configuration and can be checked against the manufacturer's warranty or entitlement records; the location of the hardware; and, for a large purchase, inspection or a written reservation. The practical checks are covered in how to verify in-stock offers.
What it does not prove. Stock that exists is not necessarily stock that is free. The same units can be offered by several resellers at once, and only one of them controls them. Stock is also not exempt from review: hardware sold from a warehouse passes through the same end-user and destination screening as hardware built to order.
What it means for the buyer. When verified stock exists for the configuration needed, it is usually the most direct route to hardware. It is also the state most often claimed for current-generation systems that are in fact built against specific orders. For rack-scale systems in particular, a stock claim deserves the ordinary checks plus one more: whose order the hardware was built for. The difference between stock and a factory build-to-order is covered in stock vs BTO/CTO orders.
What is a supplier offer, and what does it not prove?
A supplier offer is a quotation: a price, a configuration, a quantity, a claimed delivery date and usually a validity period, issued by any party in the supply chain. From the vendor of record or from a reseller several links away, it looks the same on paper.
Who can confirm it. Only the party that makes it. That is its limitation.
What proves it. Nothing beyond the seller's stated willingness to sell on those terms if it can source the hardware. An offer is a statement of intent, not evidence of supply.
What it does not prove. That the units exist, that the seller controls them or can obtain them, that anyone upstream has agreed to the order, or that the date is more than an estimate. A lead time in an offer is the seller's number until the named supplier confirms it; how dates are built and why they move is covered in NVIDIA GPU lead times.
What it means for the buyer. Most offers are made in good faith, but ten matching offers can be one source, or a claim of one, seen through ten windows; the mechanism is explained in how NVIDIA GPU allocation works. The useful questions about an offer are not about its price. They are the seller's own role, the seller's source, how many links separate the seller from the vendor of record, and whether that source has confirmed anything.
What is a GPU allocation?
An allocation is a committed share of constrained production, assigned by the manufacturer or OEM channel to a particular order for a particular deployment. It is future supply, not a physical unit. Allocation exists only when demand for a product runs ahead of what can be built; when supply is plentiful, buyers purchase from stock or order to build, and nothing is allocated.
Who can confirm it. The party that assigned it. That is normally the OEM or manufacturer channel. NVIDIA may take part in a technical, ecosystem or end-user review, depending on the product, the volume, the destination and the supply route, but it doesn't take part in every order. A reseller can pass a request upstream and report the decision. It can't create an allocation.
What proves it. Written confirmation traceable to the party that assigned it, referring to the specific order. There is no public registry of allocations and no document a buyer can look up independently, which is why a verbal "we have allocation" carries no weight on its own.
What it does not prove. The final price or delivery date, which are set in the terms that follow. Nor does it survive changes to what it was based on. An allocation is granted against a disclosed end user, intended use, site and volume; changing any of them changes the request, and the decision has to be made again.
What it means for the buyer. Allocation is attached to a deployment, not held in general and passed to whoever pays first. A claim of "open allocation" available to any buyer describes something different from how allocation is assigned. The questions that separate a real allocation from a claim are: assigned by which party, for whose order, for which deployment, and confirmed in what document. The factors the channel weighs before it commits supply are set out in what decides whether an allocation request is approved.
What is executable supply?
Executable supply is an offer that the named supplier, the party that will actually fulfil the order, has confirmed it can fulfil on stated terms, and that can become a purchase order.
In the allocation route, allocation is what makes executable supply possible for a current-generation product. In the stock route, a written reservation of verified hardware on stated terms does the same job.
Who can confirm it. The named supplier, in writing. A confirmation relayed by an intermediary is only as strong as the buyer's ability to trace it to that supplier.
What proves it. A written confirmation that states the exact configuration and quantity, the commercial and delivery basis, the validity period, and the conditions that remain open. Typical open conditions are completion of end-user and export review, the payment terms, and readiness of the site to receive the hardware. A confirmation that lists its conditions is more informative than one that lists none, because every real order has some.
What it does not prove. Delivery. Executable supply can still fail if a condition isn't met: a document is missing, the review isn't passed, the site isn't ready, or the validity period lapses before the buyer commits. Any date it contains is subject to supplier confirmation for the specific order.
What it means for the buyer. This is the first state against which a budget, a board decision or a site plan can reasonably be committed. Everything before it is a claim to be tested. It is also the right moment to compare suppliers: two confirmed offers can be compared line by line, two unconfirmed ones only on what each seller says about itself.
What does a purchase order add?
A purchase order is the buyer's formal commitment to buy on the terms of executable supply. In ordinary commercial practice it becomes binding when the supplier accepts it, and the supplier's order acknowledgement is the document that shows the order is booked.
Who can confirm it. The buyer issues it; the supplier confirms it by accepting it.
What proves it. The purchase order itself and the supplier's acknowledgement, both stating the same configuration, quantity, end user, destination and terms that were confirmed.
What it does not prove. Shipment, export clearance where it is required, or acceptance on site.
What it means for the buyer. The order in which things happen matters more than the documents themselves. A purchase order or a deposit issued against a supplier offer, before executable supply exists, commits the buyer without committing supply. And a purchase order that differs from what was reviewed, with a different end user, destination or configuration, is a new request rather than the execution of the old one.
What do common phrases in GPU offers actually mean?
The same words are used for different states. A phrase in an offer doesn't settle which state is on the table; the question after it does.
| Phrase in an offer | State it usually describes | Question that settles it |
|---|---|---|
| "In stock" | Stock, or an offer on someone else's stock | Held by whom, where, and with which serial numbers? |
| "Available" | Any of the five | Existing units, an offer, or a supplier confirmation? |
| "We have allocation" | A claim of allocation | Assigned by which party, for whose order and which deployment, confirmed in what document? |
| "Confirmed" | A supplier offer or executable supply | Confirmed by the seller, or by the named supplier that will fulfil the order? |
| "Ready to ship" | Stock | To which destination and end user, after which screening? |
| "Lead time N weeks" | A supplier offer | From which event to which, and confirmed by whom? |
| "Send the PO and we'll secure the units" | A supplier offer | What will be secured, from whom, and what happens to the payment if it isn't? |
None of these phrases is a warning sign by itself. What matters is whether the answer moves the offer to a state that can be checked. How to test those answers before money moves is covered in how to verify a GPU supplier, and the risks of hardware sold outside authorised channels in gray-market channel risks.
Frequently asked questions
What is the difference between allocation and stock?
Stock is finished hardware that exists now at a known location and can be verified by serial number. Allocation is a committed share of constrained future production, assigned by the manufacturer or OEM channel to a particular order for a particular deployment. Stock is confirmed by the party that holds it; allocation only by the party that assigned it.
What is executable supply?
Executable supply is an offer that the named supplier, the party that will actually fulfil the order, has confirmed in writing it can fulfil on stated terms: configuration, quantity, commercial and delivery basis, validity and the conditions still open. It is the first state that can become a purchase order.
Is an allocation the same as a confirmed order?
No. An allocation commits supply to a project; it doesn't fix the price or the final date. Those come with executable supply, and the order is booked only when the buyer issues a purchase order and the supplier accepts it.
Can a reseller sell me an allocation?
A reseller can pass a request to the party that assigns allocation and report its decision. It can't create an allocation, and an allocation assigned to one order and deployment doesn't move to another buyer unchanged. The useful questions are which party assigned it, for whose order, and in what document it is confirmed.
When is it reasonable to pay a deposit?
Payment terms vary by supplier and order, but the principle is the same: money committed before executable supply exists buys an offer, not supply. A deposit is easier to justify once the named supplier has confirmed the order on stated terms and the purchase order matches that confirmation.
Does hardware from stock need end-user screening?
Yes. End-user and destination screening applies to hardware sold from stock as well as to hardware built to order. Being screened is not a sign of an allocation route, and not being screened is not a shortcut.
How Haink takes a request from a first enquiry to executable supply and a purchase order: GPU procurement process →
Final allocation and hardware availability remain subject to manufacturer/OEM/supplier approval, applicable compliance requirements and supply availability.
This page describes general market practice. It does not state availability, lead times or prices for any product or order.