GPU Delivery Damage or a Product Fault? Choose the Right Follow-Up

Request the answer you actually need

After a new GPU equipment delivery, a request to inspect the server can conceal three different purchasing needs. The buyer may want the supplier to review a damaged delivery, the OEM to assess a reported product problem, or the installation provider to compare the physical build with its approved instructions. Each response produces different evidence and leaves a different decision outstanding.

An inspection provider can describe an accessible condition within its agreed scope. The supplier reviews the order and requested return response. The applicable OEM support team assesses the product problem through its support process. An installation reviewer compares identified physical work with the governing build records. Selecting the provider starts with the missing answer, rather than treating attendance at the site as a promise of repair or exchange.

Dell's order guidance separates damage from a functional problem

Dell's US order-support FAQ, checked on 19 October 2026, directs a damaged-box or physically damaged-product issue toward its order Return or Exchange route. It separately directs an item without physical damage that is reported as malfunctioning or unable to power on to Technical Support. Its missing-or-wrong-item guidance addresses order reconciliation and Customer Support.

These are named Dell routing distinctions. They do not establish another supplier's process or the remedy for a particular purchase. The useful buying question is which review the observation calls for; eligibility and disposition still need the responsible supplier or support provider's response.

References: [D1]

A receiving notification can coexist with unresolved damage

Equinix's inbound-shipment documentation says its IBX staff accept visibly damaged shipments, photograph them and have the Service Desk notify the shipping contact. That is one operator's published receiving process, checked on 19 October 2026. It illustrates why a receipt notification can coexist with a damage report.

The buyer should therefore read the actual observation behind a received status. Receipt alone establishes neither the contents' condition nor system operation or installation acceptance. A carton photograph and a report of visible product damage also describe different objects. Keep that distinction in the question sent to the supplier: a damaged carton with unobserved contents is not yet an observed damaged server.

References: [E1]

Case 1: carton damage, contents unobserved

Consider three fictional follow-up requests for newly delivered equipment. In the first, the receiving record for carton EX-A describes a crushed corner. Its contents have not been observed. The buyer has evidence about the carton and an unresolved question about the equipment inside it.

The appropriate request is supplier review of the delivery exception and the applicable order/return route. A useful request states: review the recorded carton condition and identify the supplier's next response, with internal product condition still unverified. It does not announce that a GPU has failed or ask an inspection contractor to guarantee a replacement.

If additional physical observation is needed, agree its scope and who will review the resulting evidence. The purchased output might be a limited condition report for the supplier's consideration. That report answers only the observation question assigned to it; the supplier still determines its response. This case provides no direction to open the carton, handle the equipment or accept or refuse a shipment.

Case 2: a functional problem is reported without visible damage

For item EX-B, the supplied record reports no visible physical damage, while the customer's authorized technical team separately reports that the item is nonfunctional. The functional statement is a reported symptom. It does not identify a failed accelerator, power supply or other component, and the exterior record does not resolve that uncertainty.

Request the applicable OEM technical-support assessment for the identified product. The useful answer is its assessment of the reported problem and the next support response, including any further evidence it requires. Pass existing permitted records through the agreed support channel, preserving who reported the symptom and the equipment and configuration to which it belongs. This is a case-routing decision, not a request for the buyer to power on or test the item.

An inspection-only visit could document an agreed accessible condition but would leave the functional question unanswered. If separate hardware QA evidence is requested, specify that purpose and confirm the actual equipment, plan, resources and review owner before buying it. A QA report supplies scoped evidence; it does not make the provider the OEM's repair or exchange authority.

Case 3: the installation identifier disagrees with the plan

For newly installed item EX-C, an authorized observation records asset identifier EX-S28 at a rack position assigned to EX-S82 in the supplied rack elevation. No functional problem or cause has been established. This is a conflict between an observed identifier and an installation reference. It does not, by itself, establish a wrong shipment or defective product.

Request a bounded installation-work review against the applicable approved configuration and placement records. Its useful output is a comparison identifying the observed value, governing reference and any unresolved source conflict, followed by the responsible owner's disposition. Confirming which revision applies is part of answering that question. The finding alone supplies no reason to move equipment or change a label.

This review can establish whether a physical discrepancy remains against the confirmed requirement. A correction is a subsequent, separately defined work decision. If the customer's order review later establishes a supplied-item mismatch, that evidence can support a supplier follow-up. The initial installation observation does not decide it in advance.

An inspection-only visit does not purchase an OEM remedy

For the named DGX B200 platform, NVIDIA's service manual separates support and return arrangements from component replacement instructions. Its introduction directs return-for-repair or replacement requests through NVIDIA Enterprise Support for a return material authorization (RMA) number and limits replacement components to those supplied by NVIDIA. Its Customer Support section directs reporting, troubleshooting and diagnosis to that support team. The page states a last update of 13 September 2026.

That platform-specific boundary explains a practical purchasing limit: paying another provider for observations does not establish a component diagnosis, an RMA, a supplied replacement or permission to perform a repair. Ask an inspection bidder to identify the question its report can answer and the evidence it will return. A report of exterior condition should not be priced or accepted as if it delivered OEM diagnosis and replacement.

The cases can overlap. If the same item has recorded carton damage and a separately reported functional problem, give the relevant supplier and technical-support owners both observations while keeping their sources distinct. Neither observation proves that one caused the other. The buyer may need more than one response rather than one universal fault label.

References: [N1]

Scope the physical follow-up around a defined question

Leviathan's Rack Assembly & Preparation service is the relevant starting point for delivery reconciliation, visible-condition records and comparison with the approved physical build. For an inspection-only request, confirm the included equipment and locations, accessible observations, applicable records, site permissions, personnel, availability and returned report. Ask explicitly whether the proposed work answers a receiving question or an installation discrepancy.

Hardware burn-in and QA are a separate scoped evidence request. Leviathan's published service requires an agreed configuration, test plan, resources and acceptance parameters, with observations and exceptions recorded. That scope needs confirmation for the engagement; it is not automatically added to a receiving or inspection visit and does not replace the supplier's return decision or the OEM support route.

Use the linked service and project inquiry with a nonconfidential outline of what was observed or separately reported, the question still open, the site and the requested deliverable. Identify the supplier, customer or OEM function that will receive the evidence. Detailed identifiers and restricted records can follow through an agreed project channel. A concrete request lets the physical service address the missing evidence without promising a diagnosis or a remedy it has not been engaged or authorized to deliver.

References: [L1][L2]