Knitted Bag Product Naming: SKU Code Rules, Colourway Codes and Variant Logic for a Retail-Ready Knit Range
A knit range usually breaks at the naming layer long before it breaks at the knitting stage: the buying team orders the grey tote, the production team reads it as an E12 body in heather grey, and the wrong 400 pieces get booked. The fix is to name nothing until the code exists. A 12-character SKU in five blocks — family, style, colourway, size and trim — with the colourway tied to a measured shade reference rather than a word, removes that failure at a cost of about one working day of set-up per range. This article sets out the code structure, the display-name rules behind a 28-character listing window, and what a naming convention costs to change once bulk has started.

What a Knitted Bag SKU Has to Carry
A knitted bag SKU has to carry five decisions — family, style, colourway, size and trim — because each one changes the knitting file, the yarn booking or the trimming operation, and a code that omits any of them forces a re-book at 100 pcs minimum per style and colourway.
The reason a display name cannot do this job is that names optimise for the shopper while codes optimise for the order. A shopper needs Ridge Tote in Slate. A purchase order needs to know that the body is knitted at gauge E12 from a 300D recycled polyester, that the handle is a 25 mm webbing tape rather than a knitted strap, and that the shade is the second colourway of the season rather than the first. Those are four separate decisions and they belong in four separate blocks of one code. When a brand folds them into prose, the first person to suffer is the merchandiser building the assortment plan, because two products that look distinct on a line sheet turn out to share a knitting file and cannot be scheduled or costed separately.
- Family block: the product type and its knitting route, which is what a production planner schedules against.
- Style block: the shape itself, tied one-to-one to a knitting file and a tech pack revision.
- Colourway block: a measured shade reference, not a descriptive word, so a reorder cannot drift.
- Size block: the finished dimension, because a knit body is programmed to size rather than cut to size.
- Trim block: handle, closure, lining and hardware, which are assembled after the bed and booked separately.
The Five-Block Code Structure and Why Twelve Characters Is the Limit
Twelve characters is the practical ceiling for a knitted bag SKU: five blocks plus two separators fit inside a barcode field, a warehouse label and a purchase-order line without truncation, while codes above 14 characters are cut by most retail item masters.
The limit is an interoperability constraint rather than a preference. Item masters, warehouse labels and marketplace feeds each impose their own width, and the narrowest of them usually decides. A code of 12 characters survives all three; a code of 18 characters survives the warehouse system and then gets silently truncated in the retail feed, which is worse than failing loudly because two products end up sharing a key. The structure below distributes the twelve characters as two, three, three, two and two, which is wide enough for a four-season range and narrow enough to be read aloud on a phone call without error.
- Family (2)
- TB for tote and shopper bodies, BP for backpack bodies, PC for pouches and cases
- Style (3)
- Sequential per family, tied to one knitting file and one tech pack revision number
- Colourway (3)
- Brand-side token, cross-referenced to a measured shade reference such as TCX 19-4007
- Size (2)
- S, M or L against a stated finished dimension in centimetres, never a nominal label
- Trim (2)
- Handle and closure code, for example KT for knitted strap and tape, WV for webbing
- Separators
- Two hyphens: family-style-colourway and size-trim, giving a twelve-character string
Colourway Codes: Naming a Shade Without Naming a Colour
A colourway code should be a three-character brand-side token cross-referenced to a measured shade reference, never a descriptive word: grey drifts between seasons, buyers and dye lots, and that drift is what produces a re-dip costing about 10 working days.
Words fail on a knit surface for a specific reason. A loop structure reads darker than the flat chip a brand reference is usually printed on, so the same dye recipe on two constructions reads as two shades, and a colourway named after the chip becomes ambiguous the moment the construction changes. A code tied to a number does not have this problem, because the number describes the target rather than the appearance. The practical rule is that the colourway token is what appears in the SKU and on the hangtag, while the shade reference and the Delta E acceptance figure live in the tech pack, and the two are linked by a cross-reference table that is versioned alongside the style.
Colourway naming rules that survive a reorder
- Never reuse a colourway token: retire it with the shade rather than recycling it onto a new one.
- Hold one shade reference per yarn count, because the same recipe reads differently on 300D and 600D.
- State the Delta E acceptance figure next to the reference, not in an email thread.
- Keep the token to three characters so the colourway block cannot push the SKU past twelve.
- Record the dye-lot number against the colourway on every bulk run.
- Version the cross-reference table; a token whose meaning changed silently is worse than no token.
Size and Gauge Codes: Where Naming Meets the Technical Pack
Gauge belongs in the code rather than in the marketing copy, because two bodies with identical finished dimensions knitted at gauge E7 and gauge E12 differ by about 28% in fabric mass and are not substitutes on a planogram or in a capacity claim.
Size is the other place where knit naming departs from cut-and-sew naming. A knitted body is programmed to size, so a dimension change is a file change rather than a pattern grade, and a size code that means only small, medium or large carries no information at all about which file to load. The workable convention is to state the finished dimension in the tech pack and let the size block point at it: M means 34 by 38 cm on this style and a different figure on the next. That is tolerable as long as the mapping is documented, but it stops being tolerable the moment a size block is reused across families, because the same letter then loads two different files in two different ranges.
Naming for Search: The Twenty-Eight Character Display Window
A knitted bag display name should be built inside 28 characters, because most marketplace and retail listing templates truncate a title between 28 and 40 characters on a mobile screen and the first two words carry almost all of the search weight.

The order of the words is therefore a commercial decision rather than a stylistic one. Putting the family first and the material second — Knit Tote, Slate — puts two searchable terms inside the window; putting the brand or a poetic style name first puts one term and a word nobody searches for. The discipline that follows is unglamorous: write the name against a character count, check it in the truncated state rather than the full state, and refuse names that only work when the whole string is visible. A range of twelve styles named this way typically shares a three-word pattern, which also makes the range read as a family on a shelf.
| Name component | Characters allowed | What happens if it overruns |
|---|---|---|
| Family word (Knit Tote) | 10 to 12 | The product type disappears from search on mobile listings |
| Material or structure word | 6 to 8 | The seamless or 3D knit term is lost, which is the differentiating term |
| Colourway descriptor | 6 to 8 | Truncated first, so shade is the least risky component to place last |
| Size or capacity | 4 to 6 | Usually dropped; acceptable, since it is repeated in the spec block |
| Full display name | 28 maximum | Above 28 the template cuts it, and above 40 the cut lands inside the family word |
Carry-Over, Season and Revision Codes
A carry-over style keeps its style block and takes a new season block, which is the only way to compare sell-through across seasons without re-keying history or losing the knitting file it was built from.
The mistake most ranges make here is to treat the season as part of the style. When the season moves into the style block, every carry-over becomes a new product, the sales history resets, and a merchandiser comparing two seasons has to match products by hand. Keeping season as a separate attribute — SS26 or AW26 stored as a field rather than baked into the SKU — leaves the style block stable across years and lets the carry-over be identified by comparing the same key. Revisions need the opposite treatment: a revision belongs inside the style block, because a revised knitting file is genuinely a different physical product, and shipping it under the old key is how a warehouse ends up holding two versions under one location.
Renaming an Existing Range Without Breaking the Supply Chain
Renaming a live knitted bag range is a mapping exercise, not a writing exercise: the new code set has to be published as a cross-reference against every open order, warehouse location and listing before the old codes are switched off.
The sequencing matters because three systems hold the code and they do not update together. Open purchase orders reference the old code and will be received against it; warehouse locations are labelled and picked against it; listings are indexed against it. A rename that switches listings first produces orders that cannot be picked. A rename that switches the warehouse first produces listings that resolve to no stock. The safe order is listings last, with the old code kept as an alias for a defined period rather than deleted, because deletion is irreversible while an alias can be retired on a date.
- Freeze new naming at the start of a season, never mid-season, so the two code sets do not overlap in trade.
- Publish the cross-reference table before any system is switched, and version it.
- Keep the old code as an alias for at least one full replenishment cycle.
- Remap warehouse locations in one operation, not store by store.
- Switch listings last and re-check the truncated display name after the switch.
What a Naming Convention Costs to Change Later
Changing a naming convention after the first bulk run costs about three weeks of reconciliation per 100 active SKUs, which is more than the one working day the convention costs to design properly at the start of the range.

The three weeks are not mostly writing time. They are reconciliation: matching open orders, relabelling locations, re-indexing listings and re-issuing hangtags and care labels that were printed against the old code. Printed material is the slow item, because a care label carries the code and cannot be overstickered, so a rename mid-season either scrubs printed stock or ships two code sets in parallel. Against that, the cost of getting the convention right before the first bulk run is roughly a day of work and it removes an entire class of error from every subsequent season, which is why the naming decision belongs in week one of the range rather than after sampling.
Code first, name second
The SKU carries the five production decisions; the display name carries search and tone. Deciding them in this order prevents a re-book at 100 pcs per style and colourway.
Twelve characters, five blocks
Two, three, three, two and two characters, separated by two hyphens. Fits a barcode field, a warehouse label and a purchase-order line without truncation.
Shade by reference, not by word
A three-character token cross-referenced to a measured shade reference and a Delta E figure. Removes about 10 working days of re-dipping per drift.
Season as a field, revision in the key
A carry-over keeps its style block and takes a new season field; a revised knitting file takes a new style block, because it is a different physical product.
Set up a code system for your knit range
Send the style count, the colourway split and the trim options you intend to run. Our knit team will return a SKU structure, a colourway token table mapped to measured shade references, and a range plan against MOQ 100 pcs per style and colourway, 7 working days of sampling and 30 days of bulk. Start on the contact page.
Frequently Asked Questions
Why does a knitted bag need a different SKU structure than a cut-and-sew bag?
Because a knit body is programmed to size rather than cut to size, so size, gauge and structure are file decisions rather than cutting decisions. A code that omits any of them cannot tell a planner which knitting file to load, and the gap is discovered at booking rather than at design.
How long should a knitted bag SKU be?
Twelve characters is the practical ceiling. Five blocks of two, three, three, two and two characters plus two separators fit a barcode field, a warehouse label and a purchase-order line. Above 14 characters most retail item masters truncate, and two products then share a key.
Should gauge appear in the SKU or only in the tech pack?
In the code, because gauge changes the physical product. Two bodies with identical dimensions knitted at gauge E7 and gauge E12 differ by about 28% in fabric mass and are not substitutes on a shelf or in a capacity claim, so they should not share a key.
Why should a colourway never be named with a descriptive word?
Because knit surfaces read darker than the flat chip a brand reference is printed on, so a word like grey becomes ambiguous when the construction or yarn count changes. A token tied to a measured shade reference and a Delta E figure survives a reorder; a word does not.
How many characters should a knitted bag display name use?
Build it inside 28 characters. Most marketplace and retail templates truncate a title between 28 and 40 characters on mobile, so the family word and the structure word have to sit first, and the shade descriptor belongs last because it is the first thing to be cut.
Does MOQ apply per code or per style?
Per style and per colourway, at 100 pcs. A four-colourway programme therefore commits 400 pieces at minimum, which is why the colourway block is the most expensive block in the code to expand and the one an assortment plan should cut first.
How should season be handled in a knit range code?
As a separate field rather than inside the style block. If the season moves into the style key, every carry-over becomes a new product and the sales history resets, which forces a merchandiser to match products by hand when comparing seasons.
Where does a revision belong in the code?
Inside the style block, because a revised knitting file produces a different physical product. Shipping a revision under the old key is how a warehouse ends up holding two versions in one location, and the discrepancy only surfaces at pick time.
What does it cost to rename a range after bulk has started?
About three weeks of reconciliation per 100 active SKUs, mostly matching open orders, relabelling warehouse locations, re-indexing listings and reprinting hangtags and care labels that carry the old code on the printed surface.
In what order should systems be switched during a rename?
Listings last. Open purchase orders are received against the old code and warehouse locations are picked against it, so switching listings first produces orders that cannot be picked. Keep the old code as an alias rather than deleting it.
Should the trim and hardware be a separate block?
Yes. Handles, closures, linings and hardware are assembled after the knitting bed and are booked separately, so folding them into the style block hides a purchase decision. A two-character trim block keeps the SKU inside twelve characters.
How many styles can a five-block code support?
Three style characters give 1,000 sequential references per family, which is far more than a four-season range needs, and three colourway characters give the same headroom. The binding constraint is not capacity but the twelve-character display limit.
What is the single most common naming failure on a knit programme?
Reusing a colourway token. A retired token recycled onto a new shade carries orders against the old dye lot, and the mismatch is found when bulk arrives rather than when the code is issued. Retire tokens with the shade and issue a new one.
Can the same display name be used across two markets?
Only if the truncated form still carries the family word. A name that works in English at 24 characters may reach 34 characters once localised, so the character allowance should be set in the longest market language rather than in English.
People Also Ask
What is a good SKU format for a knitted bag range?
Twelve characters in five blocks: family, style, colourway, size and trim. Each block maps to one production decision, and the code fits a barcode field, a warehouse label and a purchase-order line without truncation.
Why do knitted bag colourways need codes instead of names?
A knit surface reads darker than a flat reference chip, so a descriptive word drifts when the yarn or gauge changes. A token tied to a measured shade reference and a Delta E figure survives the change and prevents a re-dip.
How long should an e-commerce product title be for a bag?
Build it inside 28 characters. Retail and marketplace templates cut titles between 28 and 40 characters on mobile, and the family and structure words must come first because the shade descriptor is cut first.
When should a naming convention be decided?
In week one of the range, before sampling. Designing it costs about one working day; changing it after bulk costs about three weeks of reconciliation per 100 active SKUs, mostly in relabelling and reprinting.
Should a carry-over style get a new SKU each season?
No. Keep the style block stable and carry the season as a separate field, so sell-through can be compared across seasons. Only a revised knitting file earns a new style block, because it is a different physical product.
Sources and further reading
Every figure on this page is either our own programme data or attributed below. Open the originals before you write them into a specification.
- Industrial designsWIPO The intellectual-property frame behind protecting a registered product name and a distinctive shape alongside the SKU.
- HS nomenclatureWorld Customs Organization The classification system a product code has to survive when a knitted bag range crosses a border.
- ISO 2859-1 — Sampling procedures for inspection by attributes, Part 1: AQL-indexed sampling schemesISO Defines the AQL 2.5 release that a bulk run is inspected against once the code on the order matches the code on the box.
- ISO 3801 — Textiles, determination of mass per unit length and mass per unit areaISO The method behind the fabric mass figure that separates an E7 body from an E12 body in a size and gauge code.
- WHOLEGARMENT knitting machinesShima Seiki The machine class whose gauge range sets the E7 to E14 ladder referenced in the style block.
- Global Recycled Standard (GRS)Textile Exchange The claim standard a material word in a product name has to be able to substantiate.
Name Nothing Until the Code Exists
A naming convention is the lowest-cost piece of infrastructure on a knit programme and the most expensive thing to change. One working day spent fixing five blocks, a colourway token table and a 28-character display rule removes re-books, re-dips and relabelling from every season that follows, and it makes the sales history comparable across years, which is the only way a carry-over decision can be made on evidence rather than recollection.
For the imagery that sits behind the display name, see knitted bag photography. For the wording that carries the code on a listing, see knitted bag product page copy, and for the palette the colourway tokens point at, see knitted bag colour strategy. Programme structure and volume commitments are set out under custom knit bags.