How to build a SKU system for custom apparel
By UniformsOS Team. Updated .
What a SKU is, and what it is not
SKU stands for stock keeping unit. It is an internal code that you invent and control. It identifies one variant that you sell, stock or make.
Three other numbers get confused with it.
| Code | Who assigns it | What it identifies |
|---|---|---|
| Style number | You | A design, across all its colors and sizes |
| SKU | You | One style in one color and one size |
| GTIN, the number under a UPC barcode | You, from numbers licensed from GS1 | One variant, in a form other companies' systems can read |
| Supplier item number | Your supplier | Their code for the blank or the fabric |
A style number with nothing after it is not a SKU. BJ201 is a jersey design. BJ201-NVY-AL is something you can count.
The format
Go from general to specific: style, then color, then size.
BJ201-NVY-AL
- BJ201 is the style. Two letters for the category and three digits for the design.
- NVY is the color. Always three letters.
- AL is the size. Always two characters.
Rules that keep it working for years:
- Fixed length for every segment. Codes then sort and scan cleanly, and a missing character is obvious.
- Hyphens between segments. Staff can read a code aloud and spot the part that is wrong.
- Capital letters and digits only. No spaces, slashes or symbols. They break spreadsheets, URLs and barcodes.
- In any segment that contains digits, leave out the letters O and I. They get read as zero and one.
- Twelve to sixteen characters in total. Long enough to carry meaning. Short enough to say on the phone.
- Nothing that changes. No price, no season, no supplier, no customer. When those change, the code would have to change with them.
- Never reuse a code. A retired SKU stays retired, or old orders and reports start pointing at the wrong product.
Segment tables
Write the codes down once and make everyone use the same list.
| Category code | Category |
|---|---|
| BJ | Basketball jersey |
| BS | Basketball short |
| FJ | Football jersey |
| SJ | Soccer jersey |
| BB | Baseball jersey |
| HD | Hoodie |
| TS | T-shirt |
| Color code | Color |
|---|---|
| BLK | Black |
| WHT | White |
| NVY | Navy |
| ROY | Royal |
| RED | Red |
| KLY | Kelly green |
| GLD | Gold |
| Size code | Size |
|---|---|
| YS, YM, YL | Youth small, medium, large |
| AS, AM, AL | Adult small, medium, large |
| XL, 2X, 3X | Adult XL, 2XL, 3XL |
A women's cut is a different pattern, so give it its own style number. Do not hide it in the size code.
Decoration and custom products
This is where apparel SKUs go wrong. The test is simple. Does the difference change what you stock, or what the factory makes as a standard product?
A stock decorated item is its own SKU. A navy hoodie with the school crest, printed 200 at a time and sold all season, is a product. Give the decorated version its own style number.
A made-to-order sublimated jersey is different. Every team gets its own artwork, and every player gets a name and a number. If each of those were a SKU, you would create thousands of codes that are each used once.
So split it three ways:
- The SKU identifies the base product: the cut, the fabric and the size. On a sublimated style the color segment can be a fixed code such as SUB, because the color is printed.
- The design gets a design ID that belongs to the customer or the order.
- Names and numbers live on the order's roster.
An order line then reads: SKU BJ201-SUB-AL, design D-4471, name RIVERA, number 12. The catalog stays small and every order is still fully specified.
Blanks that you decorate follow the same idea. Keep the supplier's item number on the product record as a reference. Do not use it as your SKU. You will change suppliers, and the product will stay the same.
When you need GTINs
A GTIN is a Global Trade Item Number, the number encoded in a UPC or EAN barcode. GS1 is the organization behind the system. You license numbers from GS1 and assign them to your products.
You need them when you sell through someone else's system. Retailers, distributors and most large marketplaces ask for a GTIN on each listing. Under GS1's GTIN Management Standard, every variation gets its own number. One style in 5 colors and 8 sizes needs 40.
You do not need them for made-to-order team uniforms sold direct, or for products that only move inside your own business. Your SKU does that job.
If you use both, store the GTIN on the variant next to the SKU. They are two labels for the same thing, and neither replaces the other.
A worked example
One basketball jersey style in stock colors.
| Item | Value |
|---|---|
| Style | BJ201 |
| Colors | 4: BLK, WHT, NVY, ROY |
| Sizes | 9: YS through 3X |
| SKUs | 36 |
The first is BJ201-BLK-YS and the last is BJ201-ROY-3X.
Add the matching short, BS201, and the uniform has 72 SKUs. Pairing styles by number, 201 with 201, tells anyone that the jersey and the short go together.
Mistakes that cost money later
Letting every salesperson create codes. Two people will code the same product two ways. One person or one written rule owns the list.
Using the supplier's number as your SKU. It ties your catalog to a vendor.
Putting the customer in the SKU. A team's name belongs on the order.
Skipping the size. "Size is on the PO" works until someone has to count stock.
Changing codes that are already in use. If a code is wrong, retire it and create a new one. Do not edit history.
One SKU for a set. A jersey and short sold together is a bundle of two SKUs. Otherwise you cannot replace one piece.
SKUs in UniformsOS
In UniformsOS a product has a style number and one variant for each color and size, and each variant has its own SKU. Variants are typed in or generated from your colors and the product's size ranges, and the style number prints on quotes, orders and factory purchase orders. See Products and SKUs.
FAQ
- What does SKU stand for?
- Stock keeping unit. It is your own code for one variant of a product.
- Is a SKU the same as a UPC?
- No. A SKU is internal and you invent it. A UPC is a barcode that carries a GTIN, which comes from GS1 and is recognized by other companies.
- How long should a SKU be?
- Twelve to sixteen characters works for apparel. That is enough for style, color and size, and short enough to read aloud.
- Does every size need its own SKU?
- Yes. If you count it, pick it or make it separately, it needs its own code.
- Do custom team jerseys need a SKU for every team?
- No. Use one SKU for the base product and size, and keep the team's design on the order.
Sources
Related articles
- Tech pack checklist: the ten parts a factory needsA checklist of the ten parts of an apparel tech pack, what each must contain, the gaps factories complain about most and how to test yours before sending it.
- Apparel ERP software: what it does and how to choose oneWhat apparel ERP software covers, how it differs from accounting, PLM and shop management tools, and which type fits which apparel business.
- How to price custom apparelPrice custom apparel from landed cost and a target gross margin. The formula, a worked jersey example, quantity breaks and what to charge separately.
Try UniformsOS free for 30 days
30-day free trial, every module on, no card needed.
