A knitwear line sheet is the document that decides whether a retail buyer asks for a quote or moves on. It lists every style you sell with the facts a buyer needs to place an order. When style numbers are missing, MOQs are vague, or price terms are unclear, buyers lose confidence and turn to a supplier whose information is easier to read. This guide is for brands, distributors, sales agents, and private label teams that sell sweaters, cardigans, and other knits to wholesale accounts. It covers the field set, SKU logic, pricing and MOQ wording, category structure, layout, and the buyer-specific versions that prevent the most common ordering errors.
What a Knitwear Line Sheet Actually Is

A line sheet is a structured sales document, usually a PDF or a shared link. It lists every available style with the exact information a retail buyer needs to order. In other words, it is written for the person who places the purchase order, not for the end consumer. That single difference shapes every layout and wording decision on the sheet.
Knitwear Line Sheet vs. Lookbook vs. Catalog
A lookbook sells mood, with full-page photography and very little product data. A consumer catalog, by contrast, sells the brand story. The line sheet is built for fast scanning instead. Each row or tile shows a clear image, style number, fiber content, gauge, colors, size range, MOQ, reference price with its Incoterm, lead time, and packaging note. As a practical test, a buyer should be able to read it on a phone during an appointment. They should also be able to forward a shortlist to their merchandising team the same day.
Who Reads It and What Each Reader Checks
Retail buyers, department store merchandisers, boutique owners, distributor agents, and private label sourcing managers all use the same document. However, each of them reads it differently. Buyers scan for newness and price points. Merchandisers check assortment balance across categories. Meanwhile, sourcing managers compare MOQs and lead times against their delivery windows. Your structure has to serve all three roles in one pass.
Core Fields Every Style on a Knitwear Line Sheet Must Carry

Every product entry should carry the same set of fields, in the same order, on every page. This consistency lets a buyer compare a men’s wool cardigan with a women’s cashmere pullover without slowing down.
The Mandatory Field Set
For each style, include a flat or ghost-mannequin image, the style number, product name, and category tag. Then add fiber content with exact percentages, gauge (for example 7GG, 12GG, or 14GG), colors, and sizes. After that come the MOQ, a reference price with currency and Incoterm, sample and bulk lead times, the packaging method, and an ordering contact.
Fiber percentages are not optional in most export markets. For example, U.S. law requires most textile and wool products to carry a label showing fiber content, country of origin, and the manufacturer or dealer identity (FTC apparel and labeling overview). So the composition on your line sheet must match the garment label exactly. Our guide to fiber content and care label rules explains how those label details are set.
Why Gauge and Yarn Count Belong on the Page
Gauge (needles per inch on the knitting machine) and yarn count set fabric weight, drape, and price band. Together, they decide whether a style sits in a light transitional drop or a heavy winter range. A 3GG chunky wool cardigan and a 14GG fine merino cardigan are not substitutes, even when the silhouette looks similar. Because of this, list gauge next to fiber content. Otherwise buyers compare wool, cotton, and cashmere cardigans on price alone without seeing why costs differ.
Style Numbers and SKU Logic for a Knitwear Line Sheet
Style numbers and SKUs are the backbone of a working line sheet. Without a stable coding system, your sales team, the buyer’s purchasing team, and the factory end up with three names for one product. That mismatch is a frequent cause of wrong-color shipments and duplicate bulk orders.
One Style Number per Silhouette
Each silhouette gets one permanent style number, such as CN-MC-001 for a specific men’s shawl-collar cardigan. The number stays the same when color, size, yarn, or packaging changes. It identifies the pattern, construction, and finishing, so it stays attached to that development file for the life of the product.
Building the SKU Underneath
The SKU sits one layer below the style number and carries the variable attributes: color, size, yarn version, and packaging version. A practical pattern is STYLE-COLOR-SIZE, for example CN-MC-001-NVY-L for a navy large. If the same silhouette comes in two yarn qualities, such as 100% lambswool and a wool-cashmere blend, the yarn version also becomes part of the SKU. Keep codes short and use only letters, numbers, and dashes. Spaces, slashes, and special characters often break buyer ERP and EDI imports.
Avoiding the Renaming Trap
When a buyer asks for the “navy heavy cardigan,” your team should map that phrase to one style number and SKU in seconds. Trouble starts once a salesperson invents a new name for the same product to please one customer. From then on, the line sheet drifts away from the factory tech pack and the warehouse record, and reorders become guesswork.
Pricing, MOQ, and Lead Time Without Ambiguity
Price and MOQ wording is where most knitwear line sheets break down. Buyers rarely chase you for clarification. Instead, they assume the worst case and either cut the order or skip the style.
Pricing Rules to State Explicitly
Always state currency, Incoterm, quantity tier, sample fee, and validity date. Also say whether the price includes labels, hangtags, polybags, and master cartons. Incoterms are published by the International Chamber of Commerce and assign costs and risks between seller and buyer at each handover point (ICC Incoterms 2020). As a result, “FOB Shenzhen, Incoterms 2020” is not a formality. It decides who pays ocean freight. If you quote several terms, see how EXW, FOB, and door-delivery quotes compare before you set the default on your sheet.
Stating MOQ in a Way Buyers Can Act On
State whether the minimum applies per style, per color, per size, or per total order. Then say whether mixed colors and sizes are allowed inside one style. If your styles are produced to order, the factory minimum sits underneath your own. At our factory, for instance, MOQ starts from 50 pcs per color per size. A buyer who wants 600 pieces of one style across six colors gets 100 per color. Spread over five sizes, that is only 20 per size, below the floor. Spelling out the rule lets the buyer see this before ordering, not after. Our MOQ and lead time terms show how the minimum works in practice.
Lead Time, Sampling, and Reorders
Show sample lead time, bulk lead time after sample approval, and reorder lead time as three separate numbers. Yarn dyeing, color matching, and special packaging all affect timing, so state that on the sheet rather than in a later email. Lead time also depends on yarn availability. Recycled, mulesing-free, or certified fibers can add weeks, and buyers need to know that before they promise a delivery window to their own customers.
Knitwear Line Sheet Field Reference Table
The table below summarizes the minimum field set, with examples from typical programs across sweaters and cardigans. Use it as a column template when you build or audit your own sheet.
| Field | Example | Why It Matters |
|---|---|---|
| Style Number | CN-WC-014 | Permanent ID linked to the tech pack and factory file |
| Category | Women’s Cardigan | Lets buyers filter by department |
| Fiber Content | 80% Lambswool / 20% Nylon | Must match the garment label; sets the price band |
| Gauge | 12GG | Determines fabric weight and price tier |
| Colors | Ivory, Camel, Charcoal | Drives SKU count and color minimums |
| Sizes | XS–XL | Defines the size-run minimum |
| MOQ | 50 pcs per color per size | Tells the buyer whether a color and size split is feasible |
| FOB Price | USD 18.50, FOB Shenzhen, 600+ pcs (example) | Anchors the negotiation |
| Sample Lead Time | Usually 3–7 days once yarn is confirmed | Sets the development calendar |
| Bulk Lead Time | Usually 15–45 days after sample approval | Sets the delivery window |
| Packaging | Folded, polybag + hangtag, 20 pcs/carton | Affects price and labeling cost |
The fields are simple. Still, filling every cell for every style each season is what separates a usable line sheet from a half-finished PDF.
Structuring Categories in a Knitwear Line Sheet
A knitwear line sheet that mixes men’s, women’s, cashmere, wool, and cotton styles on the same page forces the buyer to do your filtering. Most buyers will not; they simply close the file.
Split by Department and Category First
Organize the document into clear top-level sections. Typical ones are Men’s Sweaters, Men’s Cardigans, Women’s Sweaters, Women’s Cardigans, Vests and Sleeveless, Knit Dresses, Zip-Up and Hooded Knitwear, and Custom Development. Link each section from a contents page or thumbnail grid in the PDF. That way, a menswear buyer can jump straight to cardigans without scrolling past 40 knit dresses.
Split by Fiber and Price Band Within Each Category
Inside each category, group styles by fiber and price band. Cashmere jumpers and lambswool sweaters belong in different conversations, even when they share a silhouette. For example, a men’s cardigan section might split into Cotton and Cotton Blends, Lambswool and Merino, and Cashmere and Cashmere Blends. Each group then carries its own MOQ and price tier.
Cashmere needs extra care because the name is legally defined. In the U.S., the Wool Products Labeling Act limits “cashmere” to fine undercoat fiber with an average diameter of 19 microns or less. The Cashmere and Camel Hair Manufacturers Institute, a trade association, also publishes labeling guidance (CCMI cashmere labeling guidance). Keeping cashmere on its own pages also makes blend percentages easy to check.
Mark Core, Seasonal, and New Styles
Tag each style as Core (carry-over), Seasonal, or New. Core cardigans, crewnecks, and basic knits usually carry most of the reorder volume, so buyers need to find them at a glance for stock planning. New styles drive sample requests, but they should not dominate the document.
Images, Layout, and Versioning
A knitwear line sheet gets read on laptops, printed in buying offices, attached to emails, and forwarded in chat threads. Therefore, the layout has to survive all of those uses.
Image Standards That Hold Up
Use consistent, color-accurate flat shots or ghost-mannequin photos on a neutral background. Every image should share the same lighting, crop ratio, and shadow style. Photograph color swatches under controlled light as well. A buyer who orders Camel from a yellowed phone photo may refuse the bulk shipment when the real shade arrives.
For wash and care notes, use the same symbols the garment label will carry. Europe and many other markets use the ISO 3758 system (ISO 3758 care labeling code), while the U.S. accepts the closely related ASTM symbols. Matching the label avoids a second round of questions from the buyer’s compliance team.
Layout Discipline for Print and Email
Each style tile should hold its image, style number, name, fiber, gauge, colors, sizes, MOQ, and price in a fixed grid. Keep marketing copy off the product pages. Instead, reserve the brand story for the cover and back page. Export the file as searchable PDF text, not a scanned image, so a buyer can search for a style number across a 60-page document.
Versioning the Knitwear Line Sheet Master File
Put a version code and date in the footer of every page, for example CN-LS-FW26-v3 (2026-06-19). When a price, MOQ, or color changes, issue a new version and withdraw the old one. Without versioning, sales staff end up quoting from a six-month-old PDF. The order confirmation then no longer matches the factory’s current cost sheet.
Tailoring Knitwear Line Sheets to Different Buyer Types
One master line sheet is rarely enough. Different buyers need different cuts of the same data, and a single 120-page file dilutes every conversation.
Buyer-Type Versions Worth Maintaining
Build a few working versions from the master file, then keep their prices and codes linked to it:
- Core range version — carry-over styles only, for distributors who need predictable reorder programs and stable pricing.
- Men’s-only and women’s-only versions — for specialty buyers, with deeper assortment within one department.
- Cashmere and premium version — cashmere cardigans, cashmere jumpers, and fine wool blends, with their own MOQ and packaging tiers.
- Lightweight version — cotton cardigans, fine-gauge cotton knits, and lighter wool blends for spring and summer windows.
- Custom and private label version — development capability rather than ready styles, often paired with OEM/ODM service capabilities and a clear sampling path.
Aligning Versions With Sales Channels
A boutique buyer browsing on a tablet at a trade show wants newness and storytelling first. A department store buying office, on the other hand, wants core styles, clear price tiers, and lead times on page two. Meanwhile, a private label client wants to skip ready styles and see development capability, yarn sourcing, and quality control procedures. One document cannot serve all of them, but tailored versions can.
Pre-Send Check for Your Knitwear Line Sheet
Before a knitwear line sheet goes to a buyer, run one last pass. First, check that every style has an image, style number, fiber content, gauge, colors, sizes, MOQ, price with Incoterm, both lead times, and packaging. Next, confirm that codes match the factory file and that the footer shows the current version and date. Finally, make sure the version fits the buyer type you are sending it to.
If you are building a range on factory-made styles, we can check the production side of the sheet. Send us your style list for a review with categories, yarn details, colors and sizes, target prices, MOQ, and packaging needs. We will then confirm which MOQs, lead times, and yarn versions our production can support.
Knitwear Line Sheet FAQ
How many styles should a knitwear line sheet contain?
There is no fixed number. Keep each version short enough that a buyer can compare every style in one sitting. If the range is wider, split it into capsule versions rather than packing everything into one file.
Should retail prices appear on a wholesale line sheet?
Usually not. A wholesale sheet shows wholesale or FOB pricing with currency, Incoterm, and quantity tier. Suggested retail can go on a separate sheet, because mixing both on one page confuses buyers and exposes margin.
How do MOQs work when a style comes in several colors and yarn versions?
State the rule at each level that applies: per color, per size, and per yarn version. For example, a style might need 50 pieces per color per size, with a separate minimum if the buyer switches from lambswool to a wool-cashmere blend. Clear layers prevent disputes when a buyer asks for a small color or a special fiber.
How often should the line sheet be updated?
Issue a new version every season at minimum. Also update it mid-season whenever yarn prices, lead times, or core MOQs shift. Each version needs a date and version code in the footer, and old versions should leave the shared drive so nobody quotes from outdated data.
Can the same document serve OEM/ODM private label clients?
Not directly. A ready-style sheet shows what is already developed. Private label clients, in contrast, need a development version that highlights yarn sourcing, gauge range, sample lead times, custom MOQ rules, and quality control capability.