Sourcing cable from Türkiye: technical review

A data sheet, a test certificate, and a declaration of performance are not interchangeable, even though buyers sometimes request “the certificate” without specifying which one the project actually needs. Each document type answers a different question — a data sheet describes typical construction and ratings, a certificate records a specific test result, and a declaration of performance addresses regulatory conformity — and a project file that mixes them up can raise questions in an audit later even if the cable itself is correct.

Before filing any document, check that the product code printed on it matches the product actually being purchased, and read the scope stated on the document itself rather than relying on its title or file name alone. A file labelled “certificate” may cover a different size, construction, or version of the family than the one on order, and confirming the scope in writing at RFQ stage removes ambiguity long before the goods or the paperwork reach the project site.

Once the family and document type are settled, the RFQ should state the cross-section or size range required, the conductor material, and the number of cores or conductors needed for the installation, since a single family can normally be supplied across a range of constructions. Leaving any of these open invites a quotation for the supplier's default configuration, which may not be the one the buyer's engineering drawings actually call for.

It is also worth asking the supplier directly about packaging and delivery-unit options — drum length, reel type, or coil weight, for example — rather than assuming a standard unit will match the project's handling equipment or storage space. These are ordinary questions in export cable procurement, and asking them at quotation stage avoids a late discovery that the delivery unit does not fit the site's cable-pulling or storage arrangements.

Incoterm, destination port, and lead time are commercial details, but treating them as a separate conversation that happens only after the technical scope is agreed tends to slow projects down rather than simplify them. Industry practice is to raise the intended incoterm and the destination together with the first technical enquiry, since the answer affects who arranges insurance, inland transport, and customs clearance, and it can also affect which packaging option is realistic for the route.

Lead time should be confirmed against the actual order quantity and construction, not against a general estimate quoted for a different size or family, because production and dispatch schedules can vary meaningfully between configurations. Buyers who confirm incoterm, destination, and lead time at the same stage as the technical specification generally avoid the late-stage surprises that arise when logistics questions are only raised once a quotation has already been accepted.

Industry practice allows a buyer to ask a supplier what quality records are available for a given order, such as mill or test records tied to the production batch, before the goods are shipped, and to ask how sampling or witness inspection could be arranged if the project requires it. These are reasonable questions for any export order and are best raised while the technical scope is still being defined, not after production has already started.

What a buyer should not do is assume that a general reputation for quality removes the need to specify inspection requirements in writing, since unspecified expectations are difficult to enforce once goods are already in transit. Agreeing in advance on which records will accompany the shipment, and how any sampling or inspection will be organised, gives both sides a shared reference point if a question about the order arises later.

A well-formed RFQ ties the product family and code, the correct document type, the technical parameters, the logistics terms, and the quality-control expectations together in one enquiry rather than spreading them across several follow-up emails. Buyers who confirm these points before sending the request typically receive a quotation that matches the project on the first pass, which saves time for both sides of the transaction.