PROCUREMENT GUIDE · 800G
800G Optical Module RFQ Checklist for AI Data Centers
A useful 800G RFQ starts with the actual link, not only the word “800G”. Send the inputs below so form factor, optical architecture, cabling, compatibility and supply can be reviewed against the real project.
Platform & PortSwitch / NIC / DPU and host cage
Link ArchitectureNative / breakout, DR8 / 2×FR4 / project path
Fiber & ReachConnector, media and loss path
Commercial InputsQuantity, phase and target delivery
Exact PN available?Send the manufacturer PN and required quantity.
PN not fixed?Send platform, port, link and reach information.
New AI cluster?Include native / breakout topology and fiber plan.
Urgent requirement?Include target delivery date and acceptable validation path.
RFQ Checklist
Twelve inputs that turn “need 800G” into an executable RFQ
Not every field must be known on day one. Separate confirmed facts from open items so the technical recommendation and commercial quotation remain auditable.
01 / PLATFORMExact host platformSwitch, NIC / DPU, server or appliance model.
02 / PORTForm factor / host cageOSFP, QSFP-DD or another exact port implementation.
03 / PROTOCOLNetwork protocol and rateEthernet, InfiniBand and exact operating mode.
04 / TOPOLOGYNative or breakoutNative 800G or the required documented breakout mapping.
05 / OPTICALOptical architectureDR8, 2×FR4 or another documented project path if known.
06 / REACHRequired link distanceUse the installed cable route and optical loss path, not only rack spacing.
07 / FIBERFiber and connectorSMF / MMF, MPO / LC, polarity, panels and existing fiber plant.
08 / SOFTWAREFirmware / FEC / port configRecord current host software and any platform-required settings.
09 / MANAGEMENTCMIS / diagnostics requirementIdentify telemetry, EEPROM / management and validation evidence required by operations.
10 / THERMALPower and cooling contextConfirm module shell / cooling requirement and per-port thermal constraints where applicable.
11 / QUANTITYSample → pilot → volumeState initial quantity, pilot quantity and expected follow-on volume.
12 / COMMERCIALPN, substitution and required dateExact manufacturer PN if known, alternative policy, delivery location and target date.
Copy / Paste Template
A compact RFQ format your team can send
Technical inputs
- Platform / device model:
- Port form factor:
- Protocol / rate:
- Native or breakout:
- Optical architecture if known:
- Fiber / connector / reach:
- Firmware / FEC notes if specified:
Commercial inputs
- Manufacturer PN / target model if known:
- Sample quantity:
- Volume quantity:
- Target delivery date:
- Country / delivery location:
- Alternative solution acceptable: yes / no / discuss
Important: final PN, platform compatibility, availability, quantity allocation and lead time are confirmed against the actual RFQ. A generic “800G” request is not treated as a universal product match.
Minimum Viable RFQ
If you only know five things, send these first
A complete BOM is ideal, but a buyer can start with a smaller evidence set and close the remaining gaps during technical review.
1. PlatformExact switch / NIC / DPU model.
2. PortOSFP / QSFP-DD and port mode if known.
3. LinkNative / breakout + approximate route distance.
4. QuantitySample, pilot or volume requirement.
5. DateRequired delivery or deployment date.
Decision Path
What happens after QIANWU receives the RFQ
01Normalize requirementSeparate confirmed facts from missing inputs.
02Match technical pathForm factor, architecture, reach and cabling.
03Check validation needCompatibility, FEC, firmware and sample path.
04Confirm commercial positionExact model, quantity, availability and delivery.
Have an 800G requirement now?
Send the exact PN/BOM, or use the checklist above to describe the actual link.