Clothing Brand SKU System Template: How to Name Sizes, Colors & Variants

Small clothing brands often name inventory casually at first: “black tee medium,” “cream hoodie large,” “sample 2.” That works until orders, restocks, printers, fulfillment files and wholesale conversations begin overlapping.

A SKU system gives every sellable variant a consistent internal name. Unlike a GTIN, a SKU is yours to design. The goal is not to make it complicated. The goal is to make it readable, scalable and difficult to misinterpret.

The ii syndicate four-part apparel SKU template

Use this structure:

BRAND-STYLE-COLOR-SIZE

Example:

II-KWTEE-BLK-M

• II = brand code
• KWTEE = Keep Watching tee/style code
• BLK = black
• M = medium

The exact codes matter less than consistency. A system should let someone unfamiliar with the product locate the right variant without guessing.

Copyable color-code glossary

These are examples, not an industry mandate. If your supplier already uses stable color codes, you can preserve those in a separate supplier-code field rather than forcing them into your customer-facing product names.

Copyable size-code glossary

Spreadsheet-ready SKU template

Create these columns in your inventory sheet:

Product Name | Style Code | Color | Color Code | Size | Size Code | SKU | Supplier Style | GTIN/UPC | Cost | Retail Price | Quantity

Example rows

SKU vs. UPC/GTIN: do not combine the jobs

GS1 US distinguishes the two concepts clearly: GTINs identify products across commerce systems, while retailers can use their own SKUs to track products internally. That means your SKU can remain human-readable even when the same variant also has a standardized GTIN.

If retail barcodes are part of your roadmap, use our companion UPC barcodes and GTIN guide for clothing brands.

8 rules for a SKU system that survives growth

1. Make every sellable variant unique. Different size or color means a different SKU.
2. Keep the order consistent. Do not use STYLE-COLOR-SIZE on one product and COLOR-STYLE-SIZE on another.
3. Avoid spaces. Hyphens make codes easier to scan visually and move between systems.
4. Avoid ambiguous characters. Codes such as O/0 or I/1 can be misread.
5. Do not encode changing information. Price, stock count and warehouse location can change; keep them in separate fields.
6. Document your abbreviations. Maintain one master color and style-code glossary.
7. Do not recycle retired SKUs casually. Historical orders and reports may still reference them.
8. Test the system before launch. Generate every planned variant and check for duplicates.

SKU audit checklist before a drop

• Every product style has a unique style code.
• Every color uses one approved abbreviation.
• Every size uses one approved abbreviation.
• No two active variants share a SKU.
• Shopify variant SKUs match the master inventory sheet.
• Supplier style numbers are stored separately.
• GTIN/UPC fields are stored separately when used.
• Costs and retail prices are not embedded in the SKU.
• Sample-only items are clearly separated from sellable inventory.
• The final variant matrix has been checked against the production order.

Connect SKU planning to production

Inventory naming works best when it is connected to the rest of your product-development system. Use the tech pack checklist to document production specifications, the sample QC checklist before approving bulk production, and the streetwear launch KPI tracker after release.

For a broader planning framework, use The Entrepreneur Resource Vault™. Brands that need direct help organizing apparel direction, product decisions and launch execution can book an Apparel Brand Direction Session.

Source

• GS1 US — Guide to UPCs, GTINs and SKUs
• GS1 US — Apparel & General Merchandise

Build a brand that can operate, not only launch

A clean SKU system is invisible to most customers, but it makes fulfillment, restocks, reporting and growth easier to manage. Get The Entrepreneur Resource Vault™ for the broader business framework, or book an Apparel Brand Direction Session with ii syndicate LLC.