A raw-yarn RFQ is a structured request that gives a supplier enough context to review feasibility and prepare the next technical questions. A good RFQ distinguishes fixed requirements from preferences and open fields instead of asking for a generic best yarn.

What application context should the RFQ include?

Application context is the downstream use and development stage, not a marketing slogan. MFE asks whether the project is for commercial fishing, lure fishing, match angling, deep-sea use, aquaculture or another programme, then records whether the request is exploration, sampling or pre-order confirmation.

  • Intended market and fishing application
  • Finished-line concept or strand context
  • Current development and approval stage

Which material and package fields are essential?

The material block is a list of known values with their source units. State denier or dtex exactly as received, then add colour and package requirements rather than assuming the supplier will choose a format compatible with the buyer’s equipment. MFE quotes raw yarn by the bobbin or cone, so state the package unit, net weight and core your winding equipment accepts.

  • Linear-density value plus source unit
  • Colour reference or open colour direction
  • Package form (bobbin or cone), net weight and core questions

How should supplied parameter data be used?

The public 2026 parameter set contains 8 PE braided-line series and 139 rows transcribed from the supplied workbook. Those pages help a buyer identify a discussion reference; they do not replace a raw-yarn TDS, COA, test method or order-specific acceptance record.

  • Name the candidate series and row
  • State which fields need confirmation
  • Request evidence relevant to the intended decision

What makes an RFQ ready to send?

An RFQ is ready when another reviewer can understand the request without guessing. Our review checks seven input groups, marks unknowns as open and identifies the next requested action—data review, sample proposal, packaging discussion or quotation.

  • Remove unsupported performance claims
  • Attach only current, named references
  • Ask for one clear next action and due date

Request technical data ↗