How to Negotiate Partial-Shipment Acceptance Without Breaking Config Freeze

Consider a hypothetical procurement call: twelve reserved Supermicro HGX B300 nodes are due, but the supplier can ship eight now. The founder wants installation moving. Procurement agrees to “partial acceptance.” Then the packing list shows missing components, while the invoice treats the shipment as completion of the delivery milestone.

The problem is not accepting eight nodes. It is leaving “partial” undefined.

A workable agreement separates permission to split delivery from permission to change configuration, pass acceptance, or collect payment. Here is how to negotiate that separation.

1. Define a tranche as a complete subset, not an incomplete promise

Make the permitted shipment unit explicit: complete nodes, complete racks, or specified standalone SKU lines. These are different commitments.

For example, eight complete nodes from a twelve-node order can constitute a tranche. Eight chassis missing components required by their frozen node BOM cannot qualify as eight complete nodes. Separately ordered cables or spares may ship as their own tranche if the agreement expressly permits it.

Attach a tranche schedule identifying:

• Order and frozen BOM revision.
• Authorized unit type, quantity, and included SKU lines.
• Dependencies required for that tranche’s agreed acceptance.
• Remaining quantities and their contractual delivery dates.

If incomplete equipment must arrive for staging, classify it as received for custody only, not accepted as a complete tranche. Confirm that receipt does not start acceptance-dependent payment or warranty clocks unless expressly agreed.

2. Keep the same freeze attached to every tranche

A split shipment changes delivery sequencing—not the approved Supermicro HGX B300 configuration.

Require every tranche to conform to the same frozen attributes applicable to its units: manufacturer part numbers, quantities within each assembly, GPU configuration, CPU and memory specifications, storage, networking, power components, firmware baseline, and agreed rack integration requirements.

“Equivalent,” “temporary,” or “available now” components should not become acceptable merely because the buyer authorized an earlier shipment. Any permitted deviation still belongs under the existing change-order and config-freeze terms.

Proposed language for counsel to review:

Ask counsel to review all proposed contractual language against the purchase agreement, especially any provisions treating delivery, silence, installation, or use as acceptance.

For broader procurement context, see reserved GPU capacity planning at Pacific; keep the tranche schedule specific to your actual order.

3. Separate tranche acceptance from final order acceptance

Use three distinct records: receipt, tranche acceptance, and final acceptance. A carrier delivery record should not silently become all three.

Receipt records what arrived, visible condition, and exceptions.

Tranche acceptance establishes whether the authorized subset matches its frozen configuration and passes tests that can meaningfully run on that subset.

Final acceptance covers the completed order, including remaining quantities, consolidated documentation, and integration or performance tests that depend on equipment not yet delivered.

List deferred tests and their prerequisites in advance. If a network dependency prevents a valid test, mark it deferred—not passed. Decide whether that prevents tranche acceptance or permits a narrowly defined conditional acceptance.

Tie shipped serial numbers to the relevant order lines, tranche ID, and evidence package. Reconcile accepted, rejected, shorted, and outstanding quantities after every delivery. This is the transaction-level bridge to your named-SKU and serial traceability requirements, not a replacement for them.

Acceptance of tranche one should not waive shortages, unresolved defects, or final system-level obligations.

4. Limit payment release to the agreed tranche outcome

Do not let an authorized split trigger a payment milestone written for the entire order.

Allocate contract value to the tranche before shipment using agreed line-item values or another documented allocation. State what becomes payable on receipt, on tranche acceptance, and only after final acceptance. Preserve an agreed holdback where unresolved integration obligations justify it.

Avoid blanket withholding that ignores conforming accepted equipment, but equally avoid paying for missing lines because they appear on the original invoice. Negotiate how disputed amounts are separated from undisputed amounts.

Check whether the split creates extra freight, handling, storage, or installation costs. Assign those costs explicitly without casually rewriting the existing freight, title, or risk provisions.

If the remaining delivery gap threatens launch, compare bridge-capacity options for interim workloads separately. An interim solution should not automatically release the original supplier from its outstanding delivery obligations.

Before approving a split, schedule a procurement discussion with Pacific Intelligent Technologies, Inc.. Bring the frozen BOM, proposed tranche schedule, and milestone language.

5. Give shorted lines a dated remediation path

A shortage report needs more than “balance to follow.” Require the supplier to acknowledge each shorted line, confirm its frozen specification, and provide a binding cure date under the agreed terms.

Specify who pays corrective shipping and repeat testing, how affected acceptance and payment remain suspended, and which existing remedies apply if cure fails. Distinguish an authorized later tranche from an unauthorized shortage: the former follows its agreed schedule; the latter enters remediation.

Close the loop with a reconciled order register. No final-completion certificate should issue while quantities or required evidence remain unresolved.

FAQ

Can procurement accept complete nodes before the full rack arrives?

Yes, if node-level tranches are authorized and their tests are valid independently. Reserve rack-dependent obligations for final acceptance using the existing acceptance framework.

Does partial acceptance automatically release a proportional payment?

No. Negotiate the allocation and trigger explicitly in the payment-milestone schedule.

Where does this fit in the broader purchase?

Treat it as a narrow delivery-and-acceptance schedule within the existing agreement. Explore Pacific Intelligent Technologies, Inc.’s infrastructure offering, then have counsel confirm that the schedule preserves configuration, remedies, and final acceptance rights.