Most custom PDU RFQs fail at the first revision because the buyer leaves out three or more of the twelve standard specification fields. Filling those twelve fields in advance collapses a 14-21 day quotation cycle into 5-7 days and tightens the unit-price spread from ±25 percent to ±5 percent.

If you have ever sent a custom PDU manufacturer a one-line “quote please” email with only a voltage and an outlet count, you have already felt the cost of an incomplete RFQ. The supplier has to come back with three to five clarification rounds, your engineering team has to context-switch each time, and the unit price you finally receive is the one the supplier hedged against the unknown fields. That is not a procurement workflow — it is a guess-and-correct loop, and it is the most common reason PDU sourcing runs late.

This guide walks through the twelve specification fields every custom PDU RFQ should include, flags the six mistakes that show up most often in incomplete RFQs, and ships a free template you can copy into your procurement system. The framework is field-tested across thousands of Newsunn RFQs for basic, intelligent, and fully custom rack PDUs serving data centers, server rooms, and mission-critical facilities.

1. Why Most PDU RFQs Fail at the First Revision

A typical custom PDU RFQ that lands in our inbox has between seven and nine of the twelve fields populated, which sounds respectable until you realize that every missing field forces a back-and-forth email. The most common omissions, in our experience handling custom PDU socket factory work for global clients, fall into four categories. For a deeper treatment of how data center procurement teams structure RFQs for power equipment, the Data Center Knowledge procurement guide and the Data Center Dynamics opinion column on RFQ failures cover complementary ground.

1. Missing electrical parameters — the RFQ lists voltage but not phase, or current but not voltage. Without all five electrical parameters, the supplier cannot pick an input plug or a bus bar rating.
2. Missing outlet configuration — the RFQ lists “C13″ but not the count, or the count but not the C13/C19 ratio. Without the ratio, the supplier cannot quote the right outlet mix.
3. Missing certification list — the RFQ lists “CE” but not the destination market. CE is European; the same PDU shipped to North America usually needs UL 62368-1, and shipped to China usually needs CCC.
4. Missing commercial terms — the RFQ lists a quantity but not the lead time expectation, or the lead time but not the MOQ. These two fields have to land together, because a 200-unit MOQ has a different production schedule than a 5,000-unit MOQ.

2. The 12 Fields — Field-by-Field Walkthrough

The twelve fields below are organized in the order a custom PDU manufacturer reads them. Fields 1 through 5 drive the physical hardware. Fields 6 through 9 drive the electronics. Fields 10 through 12 drive the certification paperwork, the environmental qualification, and the commercial terms. Filling them in this order keeps the RFQ internally consistent and lets the supplier return a clean quote on the first pass. For reference definitions of the underlying standards (IEC 60320 inlet and outlet families, IEC 60309 industrial plugs, IEC 62053-21/22 energy metering), the IEC standards catalog and the Schneider Electric rack PDU reference cover the same families in manufacturer terminology.

Field 1 — Electrical Spec

The five values that anchor every other field on the spec sheet. State all five, even if some seem obvious from context.

• Voltage rating — 100-240V single-phase, 200-240V single-phase, 380-415V three-phase, or a custom range
• Current rating — 16A, 32A, or 63A are the three values that drive the bus bar and the plug
• Phase — single-phase (1P) or three-phase (3P)
• Frequency — 50Hz, 60Hz, or 50-60Hz dual-rated
• Power factor / harmonic profile — for loads with active power factor correction, specify the expected range so the monitoring firmware can be calibrated

Field 2 — Input Plug Type

The plug type is fully determined by Field 1, but it belongs on the RFQ as its own line because different suppliers source different plug families.

• IEC 60320 C14 or C20 inlet — for single-phase 10A or 16A loads up to 250V
• IEC 60309 16A / 32A / 63A industrial plug — for three-phase or high-amperage single-phase loads
• National plug — NEMA 5-15P, NEMA 5-20P, NEMA L6-30P, BS 1363, CEE 7/7, AS/NZS 3112, and so on for regional markets
• Hardwire terminal block — for permanent install where no plug is acceptable

Field 3 — Output Outlet Configuration

This field is where the most unit-price variation lives. The C13/C19 ratio matters more than the raw count, because C19 outlets cost more and have a higher assembly labor content.

• Outlet type and count — IEC 60320 C13, IEC 60320 C19, national socket (NEMA 5-15R, NEMA 5-20R, BS 1363, CEE 7/4, AS/NZS 3112), or universal
• C13/C19 ratio — typical data center PDUs use 24 C13 plus 4 C19, but the ratio depends on the rack’s blade server density
• Outlet spacing — 1U and 1.5U spacing for standard plugs; 2U spacing to accommodate large transformer plugs without blocking the adjacent outlet
• Outlet color or labeling — for PDUs with grouped outlet banks (for example A/B feed on each side)

Field 4 — Form Factor & Mounting

Three form factors cover almost every data center rack PDU use case. Specifying the mounting hardware up front avoids a second round of clarification when the supplier asks “button mount or L-bracket?”

• 1U horizontal — for 19-inch rack mount with limited outlet count, typically up to 12 outlets
• 2U horizontal — for higher outlet count where 1U does not provide enough chassis depth
• 0U vertical — for tall, dense rack configurations; outlet count up to 48 or higher
• Mounting hardware — L-bracket, button mount, or clip mount; specify whether brackets ship pre-installed or separately

Field 5 — Circuit Protection

Four protection layers can be specified independently. Most data center PDUs ship with at least MCB and surge protection; the choice to add RCD and a specific trip curve depends on the local electrical code.

• MCB count and rating — one MCB per outlet bank; 1P, 2P, or 3P depending on the circuit topology
• Residual current device — RCD (IEC term), RCCB (UK term), or GFCI (North American term); Class A or Class AC
• Surge protection — SPD Type 1, Type 2, or Type 3 per IEC 61643-11
• Overload trip curve — B curve (resistive), C curve (standard inductive), or D curve (high inrush)

Field 6 — Monitoring & Metering

The jump from a basic PDU to an intelligent PDU happens here. Basic PDUs have a single total-current ammeter at most. Intelligent PDUs report voltage, current, power factor, kilowatt-hours, and — at the per-outlet tier — current and energy per individual outlet. The IEC 62053-21 and IEC 62053-22 standards define accuracy classes for active energy meters used in this role.

• Metering scope — total current only, per-bank, or per-outlet
• Measured parameters — current, voltage, frequency, power factor, kilowatt-hours, apparent power, reactive power
• Data refresh rate — 1 second, 5 seconds, 30 seconds, or 1 minute; faster refresh usually costs more
• Log retention — onboard flash retention period before roll-over; usually 90 days at 1-minute resolution

Field 7 — Remote Management & Communication

What an intelligent PDU can do over the network is governed by this field. Three layers should be specified: physical interface, protocol stack, and feature set.

• Network interface — Ethernet RJ45 (10/100/1000 Mbps), WiFi (802.11 a/b/g/n), 4G LTE, or RS-485 serial
• Protocol stack — HTTP / HTTPS web GUI, SNMP v1, SNMP v2c, SNMP v3 with authentication and encryption, Modbus TCP for BMS integration, SSH for command-line access
• Remote switching — none, per-bank, or per-outlet; specify the dwell time between switching events to avoid inrush trips
• User authentication — local user database, LDAP, RADIUS, or TACACS+; usually relevant for enterprise data centers

Field 8 — Display & User Interface

The display is a small but operationally important field. A field technician can recover from an unreadable web GUI; they cannot recover from an unreadable local display during a power event.

• Display technology — monochrome LCD, color TFT, OLED, or LED indicator strip
• Hotkey functions — total current, per-bank current, sequential outlet cycle, alarm acknowledge
• Menu language — English, Chinese, Spanish, or multilingual; bundle languages if the destination market is mixed
• Web GUI customization — default Newsunn GUI, OEM-branded GUI, or fully custom GUI with customer logo and color scheme

Field 9 — Environmental Sensors

Environmental sensors are usually optional but are worth specifying on the RFQ because they change the chassis cutouts and the connector plate. The data center hardware ecosystem usually uses RJ12 or RJ45 sensor ports with daisy-chain capability.

• Temperature sensors — count and cable length; typical 3-meter, 5-meter, or 10-meter
• Humidity sensor — usually bundled with temperature on the same probe
• Door, smoke, and water-leak sensors — usually third-party supplied but should be specified for connector compatibility
• Sensor input connector — RJ12 (most common), RJ45, or proprietary

Field 10 — Certifications & Compliance

This is where incomplete RFQs lose the most time. The certification mark, the regional scope, and the issuing test house have to be specified together — “CE” by itself is ambiguous because CE-LVD, CE-EMC, CE-RED, and CE-ErP are four different test certificates issued for different compliance directives.

• Safety certification — UL 62368-1 (North America), EN 62368-1 (EU), GB 4943.1 (China), KC (Korea), BSMI (Taiwan), RCM (Australia)
• EMC certification — FCC Part 15 (North America), CE-EMC (EU), VCCI (Japan), CCC (China)
• Energy efficiency — Energy Star, 80 PLUS, DOE Level VI where applicable
• Substance compliance — RoHS, REACH, Proposition 65, TSCA; list all four if the PDU ships to multiple regions

Field 11 — Mechanical & Environmental Spec

Data center PDUs are not usually deployed in hostile environments, but the operating limits still matter because some edge deployments (telecom shelters, factory floors, outdoor enclosures) push the spec sheet.

• Operating temperature — typical commercial grade is -10 to 45 °C; industrial grade is -25 to 65 °C; data center grade usually sits at 0 to 45 °C
• Operating humidity — 5 to 95 percent non-condensing is the usual range
• Altitude — ≤ 2000 m standard; 2000 to 3000 m may require derating; above 3000 m requires a special housing and bus bar design
• IP rating — IP20 for indoor rack; IP54 for dust and water resistance where required

Field 12 — Commercial Terms

The last field, but often the first one a procurement team looks at. Specifying all five values avoids a back-and-forth on what is and is not included in the unit price.

• Quantity — trial order MOQ, steady-state annual volume, and forecast
• Lead time — sample lead time (typically 7-15 days), production lead time (typically 30-45 days for a custom SKU), and acceptable variation
• Packaging — individual retail box, bulk pack, OEM-branded retail box, or palletized for data center drop-ship
• Warranty — 2 years standard, 3 years extended, or 5 years extended; specify whether the warranty covers advance replacement or return-to-depot
• Customization depth — logo silk-print only, firmware customization, or full ODM with new housing and new electronics

3. The Free RFQ Template — How to Use It

The free RFQ template below is the same twelve-field structure Newsunn’s procurement team sends to OEM clients who want a complete first-pass quote. Copy it into your RFQ email or procurement system, fill in the value next to each field, and attach any drawings or reference photos. The download the RFQ template link on our contact page returns a clean PDF version of the same form, with default values and unit notes for each line.

4. Common Mistakes When Filling the 12 Fields

Six mistakes account for most of the back-and-forth email on a custom PDU RFQ. Each is easy to avoid once it is named, and each costs the procurement cycle about a week when it slips through.

Mistake 1 — Voltage without current

A spec line that says “230V” without a current rating forces the supplier to assume 16A as the default. If your actual load needs 32A or 63A, that assumption will be wrong, and the input plug, the bus bar, and the MCB will all need to be re-quoted. Always pair voltage with current on Field 1.

Mistake 2 — C13 without C13/C19 ratio

A spec line that says “24 outlets, C13″ sounds complete but does not tell the supplier whether the unit should be 24 C13 only, 20 C13 + 4 C19, or some other ratio. The supplier has to come back to ask. State the count and the ratio together.

Mistake 3 — Certification without destination market

“UL listed” by itself is meaningless if the destination is the EU; “CE marked” by itself is meaningless if the destination is North America. List the certification mark together with the destination market on Field 10.

Mistake 4 — Lead time without MOQ

“Lead time 30 days” without a quantity is not a lead time — it is an order-less target. A 100-unit trial order usually has a longer production lead time than a 5,000-unit annual run, and the price per unit is also different. Specify both.

Mistake 5 — Form factor without mounting hardware

“1U horizontal” leaves the supplier to choose between L-bracket, button mount, and clip mount. Most data center PDUs ship with two of the three pre-installed; specifying which one avoids a second round.

Mistake 6 — “Custom” without customization depth

“Custom logo” can mean a single-color silk-print on the housing (tooling-free at typical MOQ) or a custom-anodized color matched to a brand palette (which requires a one-time color setup). “Custom firmware” can mean a logo on the LCD or a full GUI redesign. The price gap between these is significant; always state the depth.

5. How Suppliers Read Your RFQ — Behind the Scenes

Walking through the supplier’s review process is the fastest way to understand why a complete spec sheet matters. Most custom PDU manufacturers — including the Newsunn engineering team — read an RFQ in five steps.

1. Step 1 — Technical screening. Five fields get checked first: voltage, current, phase, plug type, and certification. If any of these is missing, the supplier sends back a clarification before any engineering work begins.
2. Step 2 — Mechanical evaluation. Three fields drive the mechanical review: form factor, mounting, and outlet count. These determine whether the existing chassis fits or whether a new housing is needed.
3. Step 3 — Electronics evaluation. Four fields drive the electronics review: monitoring scope, remote management protocol, display, and environmental sensor count. These determine whether the standard intelligent PDU board covers the requirements or whether a firmware or PCB customization is needed.
4. Step 4 — Compliance and certification. Field 10 is checked against the destination market and the issuing test house. If the certification scope is incomplete, the supplier has to come back for clarification.
5. Step 5 — Commercial review. Field 12 is checked last, after the supplier has confirmed the unit can be built. MOQ, lead time, packaging, warranty, and customization depth all feed into the final unit price.

6. Quick-Reference Checklist for Procurement

The checklist below is the compact version of the twelve-field structure. Print it, attach it to your RFQ template, and tick each line before sending the inquiry. The custom PDU product range page carries the same twelve-field structure in its product filter, so you can cross-reference what Newsunn considers the standard scope.

Two cross-cutting reminders, both of which sit outside the twelve fields but matter for the RFQ outcome:

• Reference photos help. A photo of the existing rack, the existing PDU (if any), and the proposed mounting location lets the supplier flag physical-fit issues that the spec sheet would otherwise miss. Two minutes of photography saves a week of mechanical clarification.
• Single point of contact. A custom PDU RFQ typically crosses engineering, certification, and commercial review. Naming a single point of contact on the buyer side lets the supplier consolidate clarifications into one round of emails instead of three.

7. Industry Context — What RFQ Quality Means Across the Supply Chain

The twelve-field framework above is not unique to Newsunn. The same field structure appears in ABB low-voltage power distribution reference documentation for European utility buyers, in Eaton rack PDU specification guides for North American data centers, and in the ENISA data centre infrastructure reports that shape European procurement standards. A complete twelve-field RFQ is the lingua franca that lets a buyer in Frankfurt, a supplier in Ningbo, and a test house in Shenzhen all agree on the same deliverable in a single review cycle.

The flip side is what happens when a buyer’s RFQ is incomplete. In our own data, an incomplete RFQ does not just delay the quote — it shifts which suppliers are willing to engage. Tier-one suppliers will return a clarification email. Tier-two and tier-three suppliers may either decline the inquiry or quote the widest band of their price range to hedge. In both cases, the buyer pays for the missing fields in either time or in unit price. The free template above eliminates that cost.

8. Closing — One Complete Spec Sheet Beats Three Rounds of Revision

The custom PDU manufacturer you want to work with is not the one with the lowest first-pass quote — it is the one who returns a complete, accurate quote against a complete spec sheet. The twelve-field framework above is the difference between a 14-day quotation cycle and a 35-day quotation cycle, and between a unit price spread of ±5 percent and a spread of ±25 percent.

For buyers evaluating Newsunn as a custom PDU manufacturer, the three links below cover the typical entry points: the full custom PDU product range, the custom PDU socket factory product page with form factor and outlet details, and the download the RFQ template link that returns the same twelve-field PDF used internally by our procurement team.