Garment Barcode Generator (Style, Color, Size SKUs)

Why Code 128 is the right garment barcode format

A garment barcode has to carry more than a plain SKU number. Style, color, size, and often a batch or lot number all need to fit in one scan, and the code still has to look clean on a hang-tag the size of a thumbnail. Code 128 does this because it's fully alphanumeric: letters, numbers, and symbols like hyphens all encode cleanly, and the format is dense enough that a string like TSHIRT-BLK-M-2601 prints small without turning into a blur of bars. UPC-A and EAN-13, by contrast, are digits-only and fixed-length, built for a checkout scanner reading a single retail product number, not a style-color-size-batch string. This tool generates Code 128 barcodes in your browser using JsBarcode, defaulted to a garment SKU pattern, with nothing uploaded and no account needed.

Internal tracking vs. a retail-chain barcode

This is the distinction that trips up most small clothing brands. If you're tagging your own inventory for your own point-of-sale system, in your own boutique, thrift store, consignment shop, or small production run, you don't need to register anything. Any SKU pattern that makes sense to you and your staff is a valid barcode. Scan it at your own register, and it works.

That changes the moment the garment is going to sit on a shelf at a different retailer and get scanned at their chain point-of-sale: that's where a homemade Code 128 stops being enough. Most multi-store and big-box retailers require a real GS1-assigned GTIN, printed as a UPC-A or EAN-13, tied to your company's registered prefix. That's a separate process through GS1 with its own cost structure, and it's not something this tool, or any free generator, can substitute for. So the question to ask before printing 500 hang-tags is simple: is this garment leaving my own checkout, or someone else's? If it's just yours, barcodes for clothing built on an internal Code 128 system are standard practice and perfectly legitimate.

A SKU pattern that actually scales

The pattern most small brands and shops land on is: style code, color, size, and an optional batch or lot number, separated by hyphens. It reads left to right the way a person would describe the item out loud.

Example: TSHIRT-BLK-M-2601 decodes as t-shirt style, black, medium, batch 2601. A hoodie in the same system might be HOODIE-GRY-L-2602. Keep style codes short and consistent (3-8 characters), use a fixed short color abbreviation list so BLK always means black and never blue, and use standard size letters (XS-XXL) or numeric sizes as your line expects. The batch or lot segment is optional but worth keeping if you run multiple production batches of the same style, color, and size across the year: it separates a spring restock from a fall one without inventing a whole new style code.

Where to put the barcode on a garment

Print the code onto a hang-tag, not into the fabric. A barcode sewn or printed directly onto cloth stretches, wrinkles, and curves with the garment, and a curved or distorted barcode is exactly what scanners struggle to read. A flat paper or cardstock hang-tag, attached with a tag pin or plastic loop, keeps the code rigid and scannable. Leave a clean margin (the quiet zone) around the barcode, and don't let a folded tag edge cross through the bars: a scanner reading through a fold is the single most common reason a "correct" barcode won't scan at the register.

For material, durable cardstock covers most cases, since these are hang-tags customers or staff remove at purchase, not permanent labels. If the tag needs to survive laundering, such as private-label care labels or rental uniforms, use the woven or synthetic tag stock made for that purpose through a label vendor, rather than an ordinary paper tag.

Why garment barcoding isn't general retail barcoding

A single grocery product has one barcode. A single garment style rarely does. One t-shirt design in 4 colors and 5 sizes is already 20 unique SKUs before you've made a second style. Multiply that across a real collection and a small brand can be managing hundreds of individual codes. Paying for that many GS1 GTINs adds up fast for a business selling only through its own boutique or website, which is exactly why an internal Code 128 system, built on a clear style-color-size-batch pattern, is the more practical route for small operations. Save GTIN registration for garments actually going into someone else's retail chain.

Worked example

A small clothing brand is prepping its first production run: 8 styles, 4 colors, 5 sizes, sold only through their own boutique and online store. That's 160 unique SKUs (8 × 4 × 5). No big-box retailer is involved, so no GTIN registration is needed. They build codes like JKT02-NVY-L-2601 for jacket style 2, navy, large, first 2026 batch, generate all 160 as Code 128 barcodes with this tool, print them on cardstock hang-tags, and attach one per garment before the run ships to the shop floor. If a wholesale account later wants to stock the line in their own stores, that's the point to look into GS1 registration, not before.

Related tools

Need a barcode in a different symbology, or for something other than a garment? The multi-format barcode generator covers Code 128, Code 39, and other formats in one place. If a garment is headed for a retail chain and needs a real registered code, generate the visual with the UPC-A barcode generator once you have your GS1-assigned number.