A clothing SKU is an internal stock-keeping code used to distinguish inventory items. For a simple apparel range, give each saleable style, colour and size combination its own unique SKU. Keep the code stable so sales, returns and stock counts continue to refer to the same item.

Decide what deserves a separate code

If customers can choose a different colour or size, those variants need to be distinguishable in your records. The same applies when two products look similar but cannot be substituted for each other. Write down that rule before creating codes, so one employee does not group items that another separates.

A SKU is not automatically a standardized retail barcode identifier. Keep any externally assigned identifiers in their own fields and follow the requirements of the systems where you use them.

Choose a readable pattern

One possible internal format is style-colour-size. A hypothetical navy T-shirt in medium could be TS104-NV-M, while the large version could be TS104-NV-L. These examples show the logic; they are not codes for actual Attirings products.

Use a small, documented colour dictionary so navy is not NV in one sheet and NAVY in another. Avoid ambiguous characters where possible and check the character and length limits of your inventory software before committing to the pattern.

Keep changeable information outside the SKU

Price, stock quantity and storage location can change without changing the product itself. Store them in separate columns. Including a shelf position in a permanent SKU can make a simple stock move appear to create a new item.

Likewise, do not create a fresh SKU merely because you reorder the same product. Record the purchase batch separately unless the product specification changes enough that the stock must be treated as a different item.

Create a master register

• SKU and product title.
• Style reference, colour and size.
• Supplier reference where applicable.
• Active or discontinued status.
• Date created and person responsible.
• Any external identifier kept in a separate field.

Before adding a new code, search the register for both the proposed SKU and the variant it describes. A unique code is not enough if two different codes accidentally refer to the same item.

Test the system with real tasks

Ask someone to find a product, record a sale and process a return using a small trial set. If they repeatedly confuse codes, adjust the naming rule before rolling it out. Print or display the SKU clearly wherever staff need to reconcile physical stock with the system.

When preparing a wholesale clothing order, keep your internal SKUs alongside the supplier’s product references. This makes later stock receipt easier without expecting the supplier to know your coding system.