HOME / BLOG / MIXED-CARTON RACK PROGRAMS

PROCUREMENT · SEP 26, 2026

Buying a Whole Rack's Power From One Factory

A rack's power chain is not one product. It is a busway tap, a pair of PDUs, a set of power shelves, battery modules, capacitor banks and the hardware that ties them together — each with its own form factor, its own dangerous-goods rules and its own lead time. Buying them on one contract is a logistics problem before it is a pricing one. This is how a mixed-carton rack program actually runs.

1 contract, five product lines15–60 days lead time by lineFOB / CIF / DDP termsUN38.3 documentation on lithium lines

WHY MANY CARTONS

One rack, five different delivery shapes.

Form factor dictates pack-out

A 0U vertical PDU leaves the line as a slim carton measured in centimetres of depth; a CRPS power shelf ships with modules in individual foam trays so they can be handled and hot-swapped without touching a board; busway straight sections are metres long and travel on cradles with joint hardware in separate cases. There is no single crate that suits all of them, and any vendor claiming a "one-box rack" is describing a marketing photograph rather than a shipping plan.

Lithium changes the packing rules

BBU modules and supercapacitor cells are lithium articles. They ship with a UN38.3 test summary and MSDS, packed to PI965/PI966 instructions, and they follow separate handling and documentation from the moment they leave the aging room. Mixing a battery carton into a general freight pallet because it is convenient at pack-out is how shipments get held at a border — so on a mixed-carton program the lithium lines get their own packing lane, their own paperwork and their own place on the packing list.

PACKING MATRIX

How each line leaves the floor.

The matrix below is what a program packing list has to reconcile. Every row is a different handling instruction, which is exactly why a mixed order needs one owner rather than five.

Product linePack formHandling constraintPairs with other lines
Rack PDU0U vertical or 1U horizontal, individual carton in master cartonKeep cord set coiled to its rated bend radius; no stacking load on the chassisYes — general freight
CRPS PSUModules in ESD foam trays, shelf in its own cartonMoisture and ESD control; trays must survive drop without module contactYes — general freight
BBU modulesLithium article packing, separate laneUN38.3 test summary and MSDS per shipment, PI965/PI966 packingOnly with the declared lithium documentation set
Supercapacitor modulesRackmount units, terminals capped and shroudedUN38.3 cell and module documentation; terminal protection in transitOnly with the declared lithium documentation set
BuswayStraight sections on cradles, joints and tap-offs cratedDimensional weight and handling length; joint surfaces protectedShipped as its own consignment

LEAD-TIME CLOCKS

One contract, five clocks to sequence.

The most common mistake in a bundled order is signing it as if every line had the same build time. They do not. Order the longest clock first, phase the shortest last, and the whole rack lands in one delivery window instead of three partial ones.

LineMOQLead timeWarranty
Data center buswayPer project, minimum one run45–60 days1 year including installation guidance
CRPS server PSU100 pcs30–45 days3 years
BBU battery modules50 sets30–45 days2–3 years, cell cycle dependent
Supercapacitor modules50 sets30–45 daysProgram-defined, roughly 15-year design life
Rack PDU10 pcs15–30 days3 years

Phase the release dates, not the PO

Busway carries the longest clock because it is built to a hall layout and type-tested as a run, so it releases first. The power shelves, BBU and supercapacitor lines follow, and the PDU — the fastest line at 15–30 days — releases last so it does not sit in a warehouse waiting for a crate from the other side of the schedule. One order, three release dates, one arrival.

Lead times run from confirmation and deposit

Every figure above starts when the order is confirmed and the deposit lands, which is why the commercial terms belong in the same conversation as the technical ones: T/T 30+70 or L/C, FOB Shenzhen or Ningbo, CIF or DDP on request, and a quote held for 30 days. A bundled program that takes six weeks to clear its own paperwork has spent the lead time it was trying to save.

THE DOCUMENT SET

Paperwork that must travel with the cartons.

Export documentation is where a mixed order either closes cleanly or stalls. This is the set we assemble per shipment, and the set worth naming in the purchase order so nothing is discovered at the port.

DocumentApplies toWhy the buyer needs it
Commercial invoice and packing listAll linesCarton-level reconciliation against the PO and the rack bill of materials
HS classificationAll linesConsistent declaration across shipments and lines so clearance does not re-rate the goods
UN38.3 test summary and MSDSBBU modules, supercapacitor cellsAir and sea acceptance of lithium articles; required before a forwarder will book
PI965 / PI966 packing declarationLithium linesConfirms the packing instruction the shipment was built to
CE declaration of conformity and RoHSShipped programs by lineMarket access and customer compliance files
UL evidence filesPDU and PSU (UL 62368-1 path), busway (UL 857 / IEC 61439-6)Shared with qualified buyers under NDA as compliance-ready evidence packages
QC dossierAll linesFAI per lot, AOI and X-Ray results, hi-pot and functional logs, burn-in exit records — keyed to serials
Busway pre-test recordsBusway runsMillivolt-drop verification joint by joint, plus 100% hi-pot and resistance checks on tap-off boxes
Third-party inspection certificateOn requestSGS, BV, TUV or your appointed agency at pack-out

ACCOUNTABILITY

The boundary is the product.

Where responsibility starts and stops

On an integrated program the scope starts at the busway tap-off and ends at the PDU outlet plus its telemetry API. Inside that span there is one warranty, one QA file and one escalation path covering busway, PDU, power shelf, BBU and supercapacitor. The facility side — service entrance, generators, upstream distribution — stays with your electrical contractor, which keeps licenses and liability where they belong.

What the alternative costs

Multi-vendor racks fail at the seams: PDU firmware the shelf manager cannot poll, BBU CAN frames the PSU telemetry ignores, tap ratings the PDU inlet never anticipated. Each of those is a support ticket that starts with two vendors pointing at each other and a rack that stays dark while they do. One factory turns those seams into internal hand-offs with a single test record behind them.

WRITING THE ORDER

Mixed-carton checklist for the purchase order.

  • One PO, line items by product line, each carrying its own MOQ and unit price — mixing lines should not hide which minimum each line is clearing.
  • Release dates per line, not one blanket date. Busway first, shelves and cells next, PDU last, converging on a single arrival window.
  • A packing list keyed to rack numbers. Cartons labelled so a receiving team can walk a rack's power chain from the crate to the elevation without opening anything.
  • Brand-neutral or branded packaging, stated up front. OEM options cover silk-screen logos, housing colour, cord lengths and outlet maps; manuals ship in your language.
  • One QC file per rack, not per product line. The point of a bundled order is a single acceptance document; on a delivered 42-rack row at 132 kW per rack, that replaced three vendor binders with one burn-in report per rack.
  • A named telemetry and firmware configuration. SNMPv3, Modbus TCP or Redfish on the PDU side; PMBus or CAN maps on the shelf and battery side — agreed during the pilot, not after delivery.
  • A spare parts kit and a warranty statement per line. Modules, tap-off boxes and PDU controllers fail at different rates, and the spares list should follow the failure data rather than a round number.
  • An inspection right, exercised. Name the third-party agency and the inspection point in the PO; pack-out inspection is where a mixed shipment is easiest to verify and hardest to argue about later.

RACK PROGRAMS

Send the rack count and the destination port — one quote covers the whole chain.

Request RFQ