Custom MTP/MPO Cable Assemblies: RFQ Checklist for Accurate Quotes

A custom MTP/MPO quote becomes inaccurate when the RFQ describes only the connector name and not the actual build logic. Technical buyers usually do not need more generic checklists. They need an RFQ structure that tells the supplier which product family is being built and which part of the route carries the highest risk.

Step 1: state the cable family before the option details

Cable family	Use this when	What the RFQ must lock early
MTP/MPO Trunk Cable	The cable is a planned backbone route between cabinets, rows, or distribution points.	Total count, fiber mode, A-end/B-end option structure, route length, label plan.
MTP/MPO Fiber Patch Cable	The cable connects nearby same-connector MTP/MPO interfaces.	Count, fiber mode, Connector A and B polish/gender, length, polarity review.
MTP/MPO Harness Cable	The cable uses an MTP/MPO A-end and breaks into LC branches or matching multiple MPO/MTP branch ends.	Connector B logic, branch structure, labels, and route map.

If the cable family is vague, all later RFQ fields become harder to trust because the option structure changes by family.

Step 2: define the optical and mechanical core clearly

• Connector system: MTP or MPO
• Fiber count inside the correct product family
• Fiber mode: OS2 G.657.A1, OS2 G.657.A2, OM4, or OM5 as applicable
• Polish type and gender where the selected family requires it
• Polarity or drawing-based channel map
• Length and any tolerance or route constraint

Step 3: do not under-specify harness assemblies

Harness RFQs fail most often because the buyer states the A-end but not the branch logic. In the current Huawellux structure, the key question is whether Connector B is:

• LC branches
• or matching multiple MPO/MTP branch ends

That single decision changes how the branch side is reviewed, labeled, and quoted. A strong RFQ should also state branch grouping, label sequence, and whether the branch side needs its own polish or gender review.

Step 4: state the order context so the quote can be reviewed correctly

Context field	Why it matters
Sample or production order	Changes how repeatability, packing, and record-keeping should be handled.
One-time or repeat supply	Determines whether the quote needs a stable future re-order reference.
OEM/ODM requirement	Affects labels, packaging, and recurring file control before release.
Documents required	Determines what must be reviewed before shipment instead of after.

Common RFQ failures

1. Saying only “MPO cable” and forcing the supplier to infer the family.
2. Using one count list for patch, trunk, and harness without separating the live family logic.
3. Leaving branch logic until after the quote for a harness build.
4. Adding document or packing requirements too late.

Copy-ready RFQ format

• Product family:
• Application / route role:
• Fiber count and fiber mode:
• Connector A details:
• Connector B details:
• Polarity or route map:
• Length and branch details:
• Labels and packing:
• Documents required:
• Destination and shipping preference:

Send the completed fields through the Huawellux RFQ path so the assembly can be reviewed as a real build with the right family logic, not as a loose keyword.