Reuters reported on August 22, 2026, citing Bloomberg and people familiar with the process, that some large Nvidia customers had been told prices for servers containing its AI chips would rise by more than 15% in many cases for systems shipped in early 2027. The reported effect includes Vera Rubin and Grace Blackwell systems and varies by chip generation and memory configuration.
Reuters could not independently verify the report, and Nvidia did not immediately respond to its request for comment. Procurement should therefore treat the figure as a reported pricing signal, not a confirmed rate card or a universal budget uplift. The immediate decision is which configured system, supplier quote, shipment window and contract term may be exposed before an early-2027 purchase is approved.
What changed and what it means
A blanket 15% uplift could misstate capex because exposure may vary by configuration, supplier pass-through, shipment timing and contractual protection.
- Decision affected
- Decide whether early-2027 AI-server purchases need refreshed configuration-level quotes, contract-term review and revised budget scenarios before commitment.
- Evidence in brief
- Reuters recorded Bloomberg’s report that some large customers were told server prices would rise by more than 15% in many cases for early-2027 shipments, with variation by chip generation and memory configuration.
- What remains unresolved
- Nvidia has not confirmed the report, and affected SKUs, base prices, currencies, geographies, suppliers, existing-order treatment and escalation terms are not disclosed.
- Next verification
- Obtain comparable line-item quotes and written contract positions, then check Nvidia’s August 26 results and any later supplier or company notice.
Key takeaways
- The reported increase is more than 15% in many cases, not 15% for every Nvidia AI server.
- Exposure reportedly varies by chip generation and memory configuration, so procurement needs comparable line-item quotes.
- A supplier notice does not by itself amend a firm price, an accepted purchase order or an approved budget.
- Nvidia’s August 26 results are a verification point, but supplier documents still control each buying decision.
What the reported Nvidia price signal establishes
The report establishes a forward-looking customer notification, not a completed transaction. It says contract server builders serving large data-centre operators had informed customers of upcoming increases. It does not disclose affected stock-keeping units, named customer quotes, previous prices, currencies, geographies, supplier margins or the treatment of existing orders.
That boundary matters because procurement can verify a supplier quotation and contract position even while Nvidia’s own response remains absent. The task is not to prove a market-wide percentage. It is to establish the organisation’s own comparable before-and-after cost for the configuration it may buy.
Why 15% is not a universal budget assumption
Nvidia’s published platform specifications show why generation and configuration cannot be treated as interchangeable. The company describes Vera Rubin NVL72 as a 72-GPU, 36-CPU rack-scale system using HBM4, while GB300 NVL72 uses 72 Blackwell Ultra GPUs, 36 Grace CPUs and HBM3E-based memory. Those are company-stated specifications, not price evidence, but they demonstrate that generation, memory technology and system composition differ.
A procurement estimate also depends on what the supplier includes. Hardware, networking, cooling integration, software, support, installation, freight, tax and financing may sit on different lines or in one bundled figure. Applying 15% to the full project can overstate exposure if the signal affects only part of the bill. Applying it only to accelerators can understate exposure if the quoted server builder passes through wider configuration costs.
Run a configuration-level cost test
| Test line | Evidence to collect | Decision question | Budget treatment |
|---|---|---|---|
| Configuration baseline | Supplier model, accelerator generation and count, memory, networking, cooling, software and support | Are the old and new quotes technically comparable? | Exclude unmatched scope from the percentage calculation |
| Quote basis | Supplier, currency, quote date, validity period, shipment date and included services | Is the change a true price movement or a changed commercial package? | Measure the delta only on comparable lines |
| Contract position | Firm-price language, escalation formula, change rights, cancellation terms and accepted order status | Can the supplier pass the increase through to this purchase? | Keep protected commitments separate from open exposure |
| Supplier attribution | Written notice showing which component, platform or supplier charge changed | Is the uplift evidenced or only described as a market condition? | Hold unsupported amounts outside the approved baseline |
| Approval record | Scenario, owner, finance sign-off and effective purchase decision | Which assumption entered the capex plan and why? | Retain one auditable approved case |
Test the quote and contract before changing the purchase order
Ask each shortlisted supplier for a refreshed line-item quotation against the same configuration identifier and shipment window. The response should state whether the change applies to new quotes, unaccepted orders, accepted orders or all shipments after a stated date. Procurement should also request the clause or commercial mechanism that permits any pass-through.
A reported market signal belongs in monitoring until supplier evidence changes the organisation’s commercial position. Any accepted variance should move through the PO change-control workflow, with the earlier version preserved, the new amount reapproved where policy requires and the supplier response attached. A salesperson’s email or a revised total without a comparable configuration is not enough to overwrite the effective order.
Build three budget scenarios, not one blanket uplift
- Protected baseline: use the current committed price where the supplier confirms that a firm quote or accepted order remains valid.
- Supplier-indicated case: use the measured difference between comparable line-item quotes for the exact configuration and delivery period.
- Downside exposure: model the at-risk amount where price protection is absent, but keep the reported percentage separate from any supplier-confirmed figure.
The scenario delta should be the revised comparable quote minus the current comparable quote, not 15% multiplied by the whole programme budget. This separation follows the same control logic as a component-cost and price-recovery bridge: committed demand, component pressure, product mix and realised commercial terms belong on different lines.
What procurement should retain for approval
- the previous and refreshed quotations with dates, currencies and validity periods;
- the exact configuration and included service scope for both quotes;
- the supplier’s written explanation and treatment of existing commitments;
- the contract owner’s assessment of price-adjustment and change-control rights; and
- the approved budget scenario, financial delta, approver and next verification date.
Unknowns should remain visible rather than being converted into one percentage. The public report does not establish affected suppliers, countries, base prices or customer-specific contract rights. Those items can only be resolved through the buying organisation’s documents.
What Nvidia’s August 26 results could change
Nvidia has scheduled its second-quarter fiscal 2027 results for August 26 at 2 p.m. Pacific time. The event may confirm, qualify, deny or leave the pricing report unaddressed; the schedule is not a promise that management will discuss it.
Even a company comment would not replace the supplier evidence needed for a purchase. Until a direct notice or comparable quote establishes the organisation’s own exposure, the defensible position is narrow: a configuration-dependent increase above 15% has been reported for many early-2027 systems, while the actual cost and contract effect remain unverified.
