Quick Answer / Summary: Configure custom bundled cable from a measured route survey, not from a rack elevation alone. Fix length increments, connector mix and polarity, define the label scheme, agree test scope and packing, then approve a drawing before production.
Custom bundled cable fails for one reason more than any other: the design input was approximate. A bundle is a physical commitment to a route, and every approximation in the survey becomes a kink, a service loop or a rework ticket in the rack.
A bundle is a commitment to a measured path.Start With a Measured Route Survey
Rack elevations give port counts; they do not give lengths. The survey adds the vertical rise, the horizontal run, the tray path and the service loop at each end.
What to measure
Measure along the actual cable path, including the route through trays and around corners. Add a defined service loop at each end rather than relying on slack inside the bundle, because slack inside a bundle is what causes kinks behind the rack.
Length increments
Agree the increment the factory will build to, for example 25 mm or 100 mm steps, and whether lengths round up or to nearest. A bundle cut to a finer increment fits better but costs more to produce.
Connector Mix and Polarity
The connector mix is where most technical risk sits. Fiber polarity, in particular, has to be defined methodically rather than left to the factory.
Defining the mix
List every leg with its connector type at each end, fiber count and polarity method. MPO trunks with LC breakouts need the breakout mapping stated explicitly, because the same physical assembly can be wired several ways.
Verifying polarity
Ask for a polarity test against the drawing and a report that names each leg. Polarity errors pass continuity tests and fail only when the link is commissioned, which is the most expensive moment to find them.
Labeling and Physical Organization
Labels are the interface between the factory and the installer. A good scheme makes installation mechanical; a poor one turns it into a puzzle.
Label content and placement
Specify both ends, the text format, the font size and the material. Labels that face the installer when the bundle is dressed are worth more than labels that are merely present.
Grouping and breakouts
Decide where the bundle splits, how legs are grouped and how much free length each leg needs at the connector. A breakout that starts too close to the rack prevents the legs from reaching their ports without strain.
Approval, Test and Delivery
The drawing approval is the last cheap moment to change anything. After it, changes are physical.
Drawing approval
Approve a drawing that shows lengths, connectors, labeling and breakout positions, and keep the approved revision with the purchase order. This is the document that decides whether a later dispute is about a build error or a design change.
Test and packing
Agree the test scope per assembly and how each bundle is coiled and labeled on the outside of the carton. Ask for delivery sequenced by rack so the site receives only what it can install.
Custom Bundle Quote Inputs
| Input | What to provide | Effect if missing |
|---|
| Route survey | Measured path with service loops | Lengths wrong, kinks in rack |
| Connector mix | Type per leg per end | Wrong breakouts or adapters |
| Polarity | Method and mapping | Links fail at commissioning |
| Label scheme | Text, placement, material | Slow install, mis-patching |
| Test scope | Per-leg tests and report | Disputes after failure |
| Packing | Coil method and carton labels | Damage and picking errors |
Practical Applications
Custom bundled cable suits repeated rack pairs, branch and edge rollouts, lab and test environments with fixed layouts, and any project where the rack design is frozen before procurement. It is a poor fit where routes are still being discovered during installation. Before releasing a bundle design, walk the route with the installer and the drawing in hand. Installers notice the things a survey misses: a tray that is already full, a door that swings into the cable path, a rack that will be populated after the cabling is dressed. Ten minutes on site at design stage prevents the two most common bundle complaints, which are a length that cannot be dressed neatly and a breakout that cannot reach its ports without strain. Ask for a drawing revision number on the carton label. When several revisions exist across a project, the label is the only fast way to confirm which one arrived, and a bundle built to revision two installed against a revision three rack is a rework ticket. Revision control costs nothing at the factory and prevents the most expensive category of bundle error, which is a correct assembly in the wrong place.
Reviewed by ZONG Cable Editorial | Last updated: 3 November 2026 | Reviewed against TIA-568 structured cabling practice and ISO/IEC 11801 fiber channel requirements.
How this guide was built: Configuration guidance follows structured cabling practice for pre-terminated assemblies: measured route survey, defined length increment, explicit polarity method and per-leg test reporting. Labeling requirements reflect installation workflow rather than marketing preference.
Disclosure: We do not build bundles. Approve a drawing before production and keep the approved revision with the order.
Frequently Asked Questions
What do I need to send for a custom bundle quote?
A rack map, a measured route survey, the connector mix with polarity, the label scheme and the test scope. Without those, a quote is an estimate.
How precise can lengths be?
Factories typically work to a defined increment such as 25 mm or 100 mm. Ask what increment applies and whether lengths round up.
Who is responsible for polarity?
The design owner defines the method; the factory verifies against the drawing and reports it. Both roles need to be written into the order.
Can I reuse a bundle design for another site?
Only if the rack geometry and routes match. Reusing a drawing without a survey is how a good design becomes a bad fit.
What is the main cause of rework?
An approximate survey. Length errors are physical and cannot be fixed in the rack without a rebuild or an ugly service loop.
