How to Structure Liquidated Damages for Late Reserved B300 Delivery

A procurement team reserved Supermicro HGX B300 capacity against a twelve-week delivery commitment. The supplier shipped on day 84. By ship date they were compliant. Installation, networking, firmware alignment, and acceptance then consumed several more weeks. The training window had already slipped, and the liquidated-damages clause never started because “delivery” meant a loading-dock event.

That is the failure mode this playbook is written to prevent. For reserved B300 purchase orders, delay remedies should attach to commercially usable capacity, not to shipment, warehouse receipt, or a packing list.

Define delay against usable capacity

Start by naming the event that actually matters to the workload. Ship date, arrival date, installation date, acceptance date, and usable-capacity date are different commercial facts. Only one of them should start delay.

Usable capacity is the date the reserved Supermicro HGX B300 environment can run the contracted class of work. Hardware in a crate is not that date. Hardware on the floor with incomplete networking is not that date. A cluster that enumerates GPUs but cannot pass the agreed acceptance suite is not that date.

Write the delay definition so both parties can answer a single question: as of the committed date, can the buyer commercially use the reserved quantity? If the answer is no, delay has begun for the unavailable portion. Carrier bills of lading prove shipment. Acceptance records, access credentials, and passing validation results prove usable capacity.

This is the same commercial boundary used when sourcing reserved GPU capacity from Pacific. Procurement is buying compute that can be scheduled, not a logistics milestone.

Make the LD formula proportional and measurable

A liquidated-damages clause that cannot be calculated from objective facts will not be administered. The formula should scale with how late the capacity is and how much of the reserved quantity remains unusable.

A workable structure is delay days multiplied by delayed quantity multiplied by an agreed daily or weekly rate. Quantity should be the same unit used in the order: reserved systems, usable GPUs, or contracted capacity blocks. Delay days should run from the usable-capacity date, after any agreed grace that is itself defined against that same date.

The rate itself is a negotiated commercial number. The drafting job is to make it measurable: which calendar starts the count, which quantity is delayed, which records control if the parties disagree, and whether buyer-caused holds are excluded. If the order form counts usable B300 GPUs and the damages exhibit counts shipped chassis, the clause will fail at the first dispute.

Partial delay should be calculated against the late portion only. If eight reserved systems are committed and two remain unusable, damages should run on two unless the contract expressly treats the block as indivisible.

Use cure periods without creating a free delay window

A cure period is a defined opportunity to restore usable capacity after notice. It is not a second delivery date that silently replaces the first.

The mistake is drafting cure so that delay does not begin until a long notice-and-cure sequence has expired. That converts liquidated damages into a delayed option the supplier can exercise for free.

A tighter structure is: the usable-capacity date arrives; delay begins for any shortfall; the buyer gives notice through a simple named path; the supplier has a short, defined cure window to restore the missing quantity; damages continue to accrue during cure unless the parties expressly freeze them for a bounded number of days; and failure to cure does not restart the original commitment. Restoring shipment status is not a cure. Restoring commercially usable reserved B300 capacity is a cure.

Choose cash, credits, or substitute capacity deliberately

Liquidated damages are not a single product. Cash, service credits, and substitute capacity solve different problems, and treating them as interchangeable is how buyers lose the operational remedy they actually needed.

Cash is the right primary remedy when the delay has already imposed unrecoverable cost: a slipped training window, idle staff, missed customer commitments, or a need to buy cover elsewhere. Credits are useful only if the commercial relationship continues and the credit can actually be consumed against remaining charges. A credit against a deployment that never becomes usable is not a remedy.

Substitute capacity is an operational remedy. If the reserved Supermicro HGX B300 environment is late, the buyer may need compute immediately. That substitute should be defined: architecture class, quantity, location, duration, and whether it is temporary cover or a permanent replacement. Pacific's bridge capacity is designed for the interval before longer-term capacity becomes usable. It should have its own commercial terms rather than silently rewriting the reserved-order delay definition.

State expressly whether tendering substitute capacity suspends liquidated damages, reduces them, or runs in parallel. If the contract is silent, the supplier will argue that any GPU is a cure. The buyer will argue that only the reserved configuration is a cure. Write the rule before that argument starts.

Align the cap with termination and cover rights

A cap is necessary. An unbounded daily charge is rarely a contract either party can sign. The cap must not, however, become the buyer’s only remaining right after a severe miss.

Read the exclusive-remedy language with the cap. If liquidated damages are the sole remedy, and the cap is exhausted after a modest delay, the buyer can be left with late capacity, no further compensation, and no exit. That is not a balanced delay regime.

A cleaner package is: liquidated damages accrue against delay in usable capacity up to a defined cap; once delay exceeds an agreed duration or the cap is reached, the buyer may terminate the undelivered portion; and termination preserves a cover right to obtain replacement capacity without waiving damages already accrued, including release of undelivered quantity and associated deposits.

Pacific Intelligent Technologies, Inc. structures reserved capacity around the date compute becomes usable. If your team is aligning a B300 purchase-order delay regime with that same event, book 30 minutes with Harper.

FAQ

Should liquidated damages run from the ship date?

No. Shipment can be a progress milestone, but delay for reserved B300 capacity should be measured from the date that capacity is commercially usable. A Supermicro HGX B300 system that left a loading dock on time is not the same as accepted, schedulable compute. Review Pacific's reserved GPU capacity offering when that distinction is the commercial issue.

Do force majeure shortages automatically excuse liquidated damages?

Only if the clause actually covers the event and the supplier has met its notice and mitigation duties. Ordinary allocation pressure, competing customer demand, or a general GPU shortage should not become force majeure by implication. If the parties intend specific supply-chain events to pause delay, name those events, the evidence required, and whether the usable-capacity date moves or merely the damages clock pauses.

Does substitute capacity stop liquidated damages?

Only when the contract says so and the substitute is actually usable for the intended work. Temporary cover can protect the workload without erasing delay on the reserved configuration. If bridge capacity is used while the reserved environment is late, treat that cover as a separate service unless both parties agree that it suspends damages.

What if only part of the reserved order is late?

Apply damages to the delayed quantity unless the reserved block is expressly indivisible. Partial usability should reduce the damages base, not reset the entire commitment. The buyer should still retain termination and cover rights for the undelivered remainder once the agreed delay threshold is crossed.

Where can procurement learn more about structuring this commercial sequence?

Start with how Pacific Intelligent Technologies, Inc. presents capacity, then review the reserved-capacity and bridge-capacity pages linked above. For a working purchase order, schedule 30 minutes with Harper and bring the delivery definition, cure language, cap, and termination draft in the same package.

The core rule is simple: define delay against usable reserved B300 capacity, make the damages formula proportional to late quantity and late days, keep cure from becoming a free extension, choose cash, credits, and substitute compute as distinct remedies, and leave termination plus cover intact after the cap. That is how a twelve-week ship date stops masquerading as on-time delivery.