What should a private-label fiber optic RFQ include?

Provide an itemized BOM or product list, existing SKU, photo or drawing where available, connector and fiber details, cable length, quantity, label or artwork reference, packing instructions, destination country and the current document revision.

How should a buyer handle different label or packing requirements in one order?

Keep a separate BOM line or clearly identified instruction for every product, label version or packing configuration. Give each attached artwork, photo or drawing a file name and revision so it can be matched to the correct line.

Can an OEM BOM include fiber cable assemblies and passive products?

Yes. Patch cords, MTP/MPO assemblies, ODF hardware, pigtails, adapters, splitters and FTTH items may be listed together when relevant. Retain individual product fields and identify the connected application so the scope remains reviewable.

OEM & Private-Label Fiber Optic RFQ Checklist

Separate the Product Definition from the Branding Instruction

Start every line with what is being purchased, then add the instruction that makes that line distinct. A product reference can be an existing SKU, a category description, a photo or a drawing. Technical details such as connector, polish, fiber, cable, length and quantity should stay with that product line. Label and packing instructions should identify exactly which line they apply to.

This approach is useful for repeat distributor products as well as project-specific cable assemblies. It reduces the risk of applying one label file, color note or packing request to every item in a multi-product order.

Copyable OEM / ODM RFQ Fields

Line referenceYour line number plus existing SKU, photo, drawing or clear product description.

Technical specificationConnector, polish, fiber, cable type, length, color and quantity as relevant to that item.

Application contextDistributor replenishment, FTTH project, ODF installation, data center cabling or another stated use.

Label instructionNeutral, private-label or project label requirement with artwork or text reference and revision.

Packing instructionUnit, bag, carton, kit or project-packing reference assigned to the relevant line.

Document controlBOM revision, drawing or photo file name, quantity revision and destination country.

Use a Simple Revision Trail

Private-label RFQs often change after the first draft. Instead of replacing information informally, identify the BOM version and label each attachment with a clear file name or revision. When a single line changes, note what changed: for example, product length, label text, carton mark or quantity. This makes it easier for both buyer and supplier to compare the current scope with the earlier request.

Common RFQ Mistakes

Sending label artwork without identifying the product line or packing level it belongs to.
Using a single generic product name when connector, polish, fiber, length or color differs by line.
Mixing a repeat-stock item and a project-specific configuration without separate quantities and instructions.
Referencing a previous supplier model without a photo, drawing or a clear description of the required equivalent.
Changing a BOM attachment without a revision identifier, then assuming all related files will be interpreted as current.
Listing packaging as “OEM” or “custom” without stating whether the request concerns a product label, bag, carton mark, kit or another packing reference.

Group Connected Products, Keep Their Fields Distinct

A single sourcing request can include cable assemblies and passive fiber products when they serve the same buyer program or installation. Keep each product type on its own line, then use the application or project reference to show their relationship. For example, an ODF line can remain separate from pigtail, adapter and patch-cord lines; an FTTH order can retain independent drop-cable, splitter and fast-connector rows. The supplier can then review the connected scope without guessing which specification belongs where.