How to Require Anti-Counterfeit Chain-of-Custody for Reserved B300 Parts

Consider a procurement team receiving a reserved Supermicro HGX B300 system and a separate carton of spare optics. The system documentation looks complete. The optics carton, however, has been resealed, and its packing list names a warehouse the buyer has never approved. The supplier says a logistics partner consolidated the shipment.

That explanation may be legitimate. But without a recorded handoff and resealing event, procurement cannot distinguish routine handling from an undocumented substitution. The right response is neither automatic rejection nor “install now, investigate later.” It is a documented hold on the affected parts.

1. Define custody as a continuous evidence trail

Anti-counterfeit chain-of-custody records where parts originated, who controlled them, and what happened between release and receipt. For reserved Supermicro HGX B300 procurement, apply it to GPUs, boards, optics, and contracted spares—including parts introduced during integration or replacement.

Require a custody register that connects:

• The manufacturer or approved authorized-distribution source.
• Each supplier, integrator, warehouse, carrier, and receiving party.
• Transfer dates, locations, shipment references, and accountable custodians.
• Part identifiers, serials where available, and lot or carton references where appropriate.
• Seal identifiers, seal condition, and any opening, inspection, repacking, or resealing event.

A seal number without a shipment mapping is weak evidence. So is a receiving signature that says nothing about carton condition. The register should make gaps visible before the buyer accepts affected material.

2. Specify the evidence package before the purchase order

Attach an evidence schedule to the purchase order or supply agreement. Do not leave “standard shipping documents” undefined.

Require a certificate of conformity or conformance (COC), with its meaning expressly defined, identifying the issuer, covered parts or lots, purchase-order reference, and claimed conformity. A supplier-issued COC is an assertion, not independent proof of authenticity.

Pair it with source invoices or appropriately redacted purchase records, relevant authorized-distributor documentation, custody-transfer records, and packing photos showing labels and seals. Redactions must not obscure the source, covered material, or shipment mapping procurement needs to verify.

Require authorization evidence relevant to the product and transaction, rather than accepting a generic distributor logo. For assembled systems, define what upstream evidence the integrator must retain and what the buyer may inspect; do not demand destructive access to installed components.

The supplier should deliver the package before dispatch, then add transit and receipt records as those events occur. Establish a repository, retention period, and owner for missing evidence.

3. Put checks at custody transitions

Inspection should follow the route, not happen only at the loading dock.

At source release, check the approved supplier, material references, and initial seals. At integration, record incoming component identity and any packaging opened during assembly. At warehouse transfers or consolidation, record custody changes and explain seal replacement.

At final dispatch, reconcile the released shipment against the evidence package. At receipt, compare seal identifiers, labels, carton condition, and receiving records before affected parts enter usable inventory.

Use trained receiving or quality personnel for defined visual checks. Suspicious markings or packaging justify escalation; visual inspection alone cannot establish authenticity. Any deeper authentication should use manufacturer guidance or a qualified specialist.

For the broader delivery commitment, review reserved GPU capacity requirements. Keep custody requirements attached to the actual procurement route, not just the promised delivery date.

4. Contract for quarantine and controlled release

Define suspect-part triggers: an unexplained custody gap, mismatched labels, missing source records, an unrecorded seal break, or inconsistent documentation. A broken seal is not automatically counterfeit; an unexplained break requires resolution.

Quarantine should mean physical segregation, an inventory-system hold, preserved packaging and evidence, and no installation or redistribution while the hold remains open. Specify notification deadlines, investigation ownership, and release authority.

Proposed language for counsel to review:

Supplier shall maintain documented custody for covered parts from the approved source through delivery. Unexplained custody gaps or evidence discrepancies shall place affected material on hold pending investigation. Release requires Buyer’s designated approval based on documented resolution. Unresolved material shall follow the agreed replacement, rejection, or other remedy process.

Ask counsel to review this language alongside acceptance, payment, investigation costs, delay remedies, and evidence-preservation obligations. Set response and resolution deadlines rather than accepting an indefinite investigation.

If a hold threatens deployment, assess a bridge-capacity option separately. Schedule pressure should not silently waive the custody gate.

5. Keep adjacent controls distinct

Serial traceability answers which item. Chain-of-custody answers who controlled it and how it moved. Pack-out photos document condition at a moment; they do not establish the entire route. Firmware hashes concern software state, while warranty and RMA terms govern support and remedies.

Use those controls together without treating any one as proof of authenticity. Assign a procurement owner to collect the package and a receiving or quality owner to authorize release.

Pacific Intelligent Technologies, Inc. can be part of your procurement conversation through its GPU infrastructure overview. Bring your proposed custody schedule and exception workflow to a 30-minute procurement discussion.

FAQ

Does serial matching establish chain-of-custody?

No. A matching serial identifies an item but does not explain intervening possession. Pair this requirement with named-SKU and serial traceability.

Are packing photos sufficient?

No. Use pack-out photo evidence to corroborate seals and condition, alongside source and handoff records.

Can firmware verification clear a suspect part?

Not by itself. A firmware baseline and hash lock addresses software state, not physical provenance.

Should replacement spares meet the same requirements?

Yes. Apply the custody schedule to replacement material and connect it to warranty, RMA, and spares terms, including who approves release from quarantine.