Before knitwear sampling begins, the supplier needs enough information to understand what the garment should look like, how it should fit, what material direction is intended and which details are commercially important.
This checklist explains what is useful to send and what can still be developed later.
The short answer
If available, send:
- tech pack
- design sketch
- reference images
- reference garment
- measurements or size chart
- yarn composition or hand-feel direction
- color references
- stitch or construction references
- expected quantity
- size range
- labels and trims
- packaging requirements
- target delivery timing
- destination market
You do not need every item before the first conversation.
But the fewer details that are defined, the more questions need to be resolved before the sample can become an accurate production reference.
1. Tech pack
A good tech pack can organize:
- flat sketches
- measurements
- construction details
- stitch information
- trims
- labels
- colorways
- artwork
- packaging notes
If you already have one, send the latest version.
If you do not have a complete tech pack, do not delay the first discussion simply because the document is incomplete.
A sketch, reference image and measurement direction can still be enough to identify the next questions.
2. Reference images
Reference images are useful for communicating:
- silhouette
- texture
- neckline
- sleeve shape
- rib proportions
- stitch direction
- overall visual mood
However, photographs do not fully define a knitwear specification.
A supplier still needs to clarify details such as:
- yarn
- gauge
- measurement
- stitch structure
- finishing
- color
- quantity
If several reference images are used, explain which detail should be taken from each image. Otherwise, the supplier may not know whether the image is a reference for fit, stitch, color or styling.
3. Reference garment or physical sample
A physical sample can be especially useful when you want to communicate:
- fit
- weight
- touch
- measurements
- construction
- finishing
- neckline
- linking
- rib tension
A reference garment does not mean it should be copied blindly.
It can be used as a technical reference while the new product is developed around your own specification and brand direction.
4. Measurements and size range
Measurements turn subjective feedback into something measurable.
At minimum, identify the dimensions that matter most to the style.
For a sweater, that may include:
- body length
- chest
- shoulder
- sleeve length
- cuff
- hem
- neck opening
- collar height
Also state:
- base sample size
- intended size range
- whether you already have grading rules
If grading is not available, it should be discussed rather than assumed.
5. Yarn direction
A supplier should know whether the project has a defined composition or only a target hand feel.
For example:
Defined:
“100% merino wool.”
Open direction:
“Soft wool-rich yarn with a premium hand feel.”
Both can work, but they lead to different sourcing discussions.
Helpful yarn information includes:
- fibre composition
- target softness
- yarn thickness direction
- color
- required certification, if any
- reference yarn or swatch, if available
If certification is important, state it before yarn sourcing begins.
6. Gauge and stitch direction
If you know the intended gauge, include it.
If you do not, send the visual direction and let the development discussion consider the appropriate gauge together with yarn and construction.
Useful stitch references may include:
- jersey
- rib
- cable
- jacquard
- intarsia
- textured structures
A close-up image is often more useful than a full-body fashion photograph when discussing stitch construction.
7. Color references
Color names alone can be ambiguous.
“Beige”, “navy” or “olive” can mean many different shades.
Useful color references may include:
- Pantone reference
- yarn color card reference
- approved physical swatch
- previous approved sample
The exact color-development method depends on the yarn and project.
8. Estimated quantity
Estimated quantity matters before sampling because it can influence:
- yarn sourcing
- color feasibility
- production-resource selection
- costing
- commercial setup
If the final order is not confirmed, provide a realistic estimate.
For example:
- estimated quantity per style
- estimated quantity per color
- number of colors
Do not ask a supplier for a highly precise bulk quotation while intentionally withholding quantity. Knitwear costs can change significantly with material and production setup.
9. Branding and packaging
If the product is private label, send the requirements early.
These may include:
- main label
- size label
- care label
- hangtag
- buttons or trims
- polybag
- folding method
- carton marks
Some items may have their own minimum quantities or development requirements, so they should not be left until the final shipment stage.
10. Target delivery timing
A target date helps the supplier work backward through:
- development
- revisions
- approvals
- yarn preparation
- bulk production
- inspection
- shipment
Do not confuse a target delivery date with a guaranteed lead time before the project has been reviewed.
Sampling and production timelines depend on the actual requirements.
11. Destination market
The destination market can affect:
- labeling
- fiber-content wording
- care instructions
- packaging
- shipment documentation
- buyer-specific requirements
State where the goods are expected to be sold or delivered.
JXDORT does not make blanket compliance claims for every market. Project-specific requirements should be confirmed by the buyer and relevant suppliers.
A useful first-email structure
You can keep the first inquiry simple:
Product:
Women’s cardigan
Reference:
Attached sketch and images
Yarn:
Merino wool direction, open to suitable options
Colors:
2 colors
Quantity:
Estimated quantity per color
Sample size:
M
Target delivery:
Month / season
Branding:
Private label required
Attachments:
Tech pack / sketch / measurement chart / reference images
This is enough to start a productive discussion.
What if you do not have a tech pack?
You can still start.
Send the clearest information you have and state which details are still open.
The development process can then identify:
- what can be proposed
- what needs buyer confirmation
- what affects quotation
- what must be decided before sampling
The goal is not perfect documentation on day one.
The goal is fewer hidden assumptions.
