Seller sorting cardigan variants for inventory

SKU System Setup: A Step-by-Step Guide for Small Sellers

An SKU system is a set of rules you write once, so every product and variant you sell gets a short, unique, readable code. To set one up, decide which attributes matter (category, product, color, size), give each a short abbreviation, join them with dashes, write the rules down, test them on a few products, and then use them every time. You make up the codes yourself. No agency issues them and no universal format exists.

We are a marketplace built around Black-owned businesses, so we talk with a lot of founders who are launching their first catalog. Most of them ask this question at the same moment: a wholesale buyer, a marketplace, or a spreadsheet that has gotten out of hand suddenly needs codes. This guide walks you through it.

Davillagenetwork
Put Your Values Into Every Purchase
Explore an online marketplace connecting shoppers with Black-owned businesses across fashion, beauty, home, tech, fitness and self-care.

TL;DR

  • An SKU is an internal code you create to track inventory and sales. Every product and every variant gets its own unique one.
  • Keep codes short, uppercase, and consistent, with dashes between attributes. Skip spaces and special characters, and avoid look-alikes such as 0 and O.
  • A 3-size, 4-color shirt needs 12 SKUs. Plan the structure before you create them.
  • An SKU is not a barcode. Your SKU is private to your business, while a barcode carries a GTIN that trading partners can scan.
  • Write the rules down in a one-page master list so everyone on your team codes products the same way.

Table of Contents

What an SKU system actually does

SKU stands for stock keeping unit. According to the ecommerce platform help documentation on SKUs, SKUs are internal codes used to track inventory and report sales. They can also help with storage, fulfillment, exchanges, returns, and integrations.

In plain terms, the SKU is how you and your software refer to one exact sellable item. “Black cardigan” is not specific enough. “Black cardigan, size M” is. The SKU is the code for that second description.

Because you create them, the same product can carry different SKUs at different companies, as this inventory management explainer points out. A selling platform’s help center confirms the same thing from another angle: SKUs identify products and variants for internal tracking, and there is no standardized format.

That freedom is the good news. It also means nobody will fix a messy system for you.

What an SKU system actually does — overview diagram

Why a system beats ad hoc codes

When codes are invented one at a time, three things tend to happen:

  • Two products end up with similar codes, and the wrong one gets picked and shipped.
  • New hires cannot decode anything, so they guess.
  • When you add a second sales channel, you have to re-code everything.

A system prevents all three. It takes an afternoon to design and saves you from hours of cleanup later.

Step 1: List what makes each item different

Start with your products, not with the codes. Write down every attribute that makes one item different from another. Shopify’s SKU guide names the common components: category, brand or supplier, product attributes such as size, color, and material, and location.

For most small sellers, the useful list is short:

  1. Category or product line
  2. Specific product or style
  3. Color or scent
  4. Size or quantity
  5. Optional: supplier or vendor, if you source from several

If an attribute never changes what the customer receives, leave it out. A code that tries to say everything becomes unreadable.

Step 2: Choose abbreviations and a separator

Each attribute gets a short abbreviation. The selling platform guidance suggests 1 to 3 characters per attribute, alphanumeric codes, uppercase letters for legibility, no spaces, and few or no special characters. It also recommends going over six characters in total where practical.

The ecommerce platform’s help page adds two rules worth tattooing on your wall:

  • Avoid characters that look alike, especially the number 0 and the letter O, and the number 1 and the letter I.
  • Use dashes or underscores to separate attributes, not spaces or special characters.

A practical example from that same guidance is WAL_BLK_25: a wallet, in black, with a number at the end. You can read it at a glance.

A sample abbreviation key

Here is an illustrative key for a small apparel and self-care shop. It is an example of structure, not a required standard:

Attribute Code Meaning
Category TEE T-shirt
Category CAR Cardigan
Category SOP Soap
Color BLK Black
Color OLV Olive
Color CRM Cream
Size S, M, L Small, medium, large
Scent LAV Lavender

Notice that no code uses a zero or a lowercase letter. We avoid “OAT” for oatmeal soap only if the same list also contains a zero-heavy numeric field; otherwise it is fine. The point is to check your own list for look-alikes before you commit.

Step 3: Build the template

Now string the pieces together in a fixed order. Put the broadest attribute first and the most specific last. That way, when you sort codes alphabetically, similar items group together.

A template might look like this:

CATEGORY-STYLE-COLOR-SIZE

Then a few real-looking codes:

  • TEE-CLS-BLK-M: classic tee, black, medium
  • TEE-CLS-BLK-L: classic tee, black, large
  • CAR-LIN-OLV-S: linen cardigan, olive, small
  • SOP-OAT-NAT-4Z: oatmeal soap, natural, 4 oz bar

Nobody has to open a spreadsheet to know what TEE-CLS-BLK-M is. That is the test of a good SKU.

Keep codes meaningful, not clever

Resist the urge to encode your cost, your supplier’s internal number, or the date you bought the item. Those details change, and a code should not. If you need that information, store it in a separate field in your inventory tool.

Step 4: Code every variant separately

This is where beginners lose the most time. The help guidance says to assign a unique SKU to each product and each variant, and gives the math: 3 sizes in 4 colors require 12 SKUs.

So the classic tee above is not one SKU. It is 12 if you sell it in three sizes and four colors. Each one has its own stock count, because you may have eight black mediums and zero olive smalls.

Here is how a small run looks for a single tee in two colors and three sizes:

SKU Color Size Units on hand
TEE-CLS-BLK-S Black Small 8
TEE-CLS-BLK-M Black Medium 12
TEE-CLS-BLK-L Black Large 6
TEE-CLS-CRM-S Cream Small 0
TEE-CLS-CRM-M Cream Medium 9
TEE-CLS-CRM-L Cream Large 5

The quantities are made up to show the idea. What matters is that each row can be counted, reordered, and reported on alone.

How to enter them

You do not have to type every one by hand. The platform guidance notes you can add or edit variant SKUs individually, use a bulk editor, or import a CSV file. A point-of-sale system’s support article on SKUs also says you can enter custom SKUs for standard products, products with variants, and composite products. It adds that editing a product does not automatically change its SKU. So if you rename a product later, update the code on purpose, or leave it alone and keep it stable.

If you are comparing the software that will hold these codes, our inventory management tools comparison lays out what to look for.

Step 5: Plan for growth, then test

A system that works for 20 products can break at 200. The help page recommends planning your structure so it can handle expansion without running out of combinations. Some questions to ask now:

  • If I add a new category, does my format still fit?
  • If a style comes in 15 colors instead of 4, are my color codes still unique?
  • If I open a second location or storage spot, can I use the same SKU and track stock separately?

That last one is useful. For multiple locations, the guidance says to use the same SKU for each variant and track inventory by location rather than creating new codes.

Then test before you commit. Shopify’s framework recommends defining the structure, choosing identifiers, setting character limits, creating a template, and testing before implementation. Take ten products of different types and code them on paper. If any code is ambiguous, too long, or collides with another, fix the rules now, while it costs nothing.

Step 6: Write the rules down

A system lives in a document, not in your head. The same framework recommends a master list of approved abbreviations, used consistently across products. In practice, that is a one-page sheet with:

  1. The template (for example, CATEGORY-STYLE-COLOR-SIZE)
  2. Every approved abbreviation and what it means
  3. The rules (uppercase, dashes only, no 0/O or 1/I confusion)
  4. Who is allowed to add a new code

Documenting and testing the scheme, per that guidance, reduces inconsistent abbreviations and exposes workflow problems early. When you bring on a helper or a fulfillment partner, hand them this sheet on day one.

SKU vs. barcode: not the same thing

This is the most common mix-up, and it matters the moment you sell through a larger channel.

  • An SKU is yours. You create it, it can differ from business to business, and it is mainly used inside your operation.
  • A barcode is a physical carrier. GS1 US explains that the barcode is the thing a scanner reads, and the GTIN is the data encoded in it. A GTIN is a globally unique product identifier used across trading partners.
  • In North American retail, a UPC-A barcode commonly encodes a 12-digit GTIN-12, per the same GS1 US page.

You can, and often should, use both for the same item. Your SKU says TEE-CLS-BLK-M in your system. The barcode on the package carries the GTIN that a retailer’s scanner understands.

When you need real barcodes

If you only sell from your own storefront and ship yourself, an SKU may be all you need day to day. Barcodes become necessary when a channel or buyer requires them. GS1 US says each Amazon product variation needs a unique barcode, and recommends getting UPCs directly from GS1 or the original manufacturer. For beauty sellers, each color or container size needs its own GTIN. Variants again: the more options you offer, the more codes you manage.

Mistakes that cause the most cleanup

  • Reusing a code. Never assign a retired SKU to a new product. Old orders and reports will mix the two.
  • Using spaces or symbols. They break imports and look different across tools.
  • Letting codes drift. One person writes BLK, another writes BK, a third writes BLACK. Your master list prevents this.
  • Coding for today only. A format with room for two colors fails when you add a third.
  • Encoding things that change, like price or supplier.
  • Skipping variants. One code for a product that comes in five sizes makes stock counts meaningless.

Our perspective: codes are how a small brand becomes a big one

We see the same pattern again and again with the founders in our community. The product is beautiful, the story is strong, and the back office is a notebook. Then a bigger opportunity shows up: a marketplace listing, a wholesale buyer, a holiday rush. The brands that can say yes quickly are the ones that did the unglamorous work early.

An SKU system is that work. It is free, it is yours, and nobody can take it away. It lets you count what you have, reorder what is selling, and hand a clean spreadsheet to anyone who helps you grow. If you are planning to list with us, a tidy catalog also makes your product pages easier to build, and it pairs well with the habits in our first 30 days of listing SEO and our launch checklist for Black entrepreneurs.

Our advice is simple. Do not wait until you have 500 products. Set the rules at 5. Keep them boring. Your future self, and your future team, will thank you.

— Ronnie

Where to go next

Once your codes are in place, the same catalog feeds everything else: photos named by SKU, listings, bundles, and fulfillment. These guides pick up from here:

Sell with us or shop with purpose

Da Village Network is an online marketplace where every vendor is Black-owned. If you make products, you can apply to sell with us, and our vendor onboarding has no monthly fees. If you are a shopper, DVN Premium is $2.99 per month and gives you sitewide member discounts of 15%. Either way, your dollars stay circulating in the community. Browse the marketplace or learn about DVN Premium.

FAQ

What is the standard SKU format?

There isn’t one. Ecommerce platform documentation says you can use any format you like, and one help center states plainly that SKUs have no standardized format. What works is a consistent one: short, uppercase, dash-separated, and readable by a person who did not create it.

Can I just make up a SKU?

Yes, as long as it is unique and follows rules you apply every time. Random codes work for a week and then become a problem. Build each code from attributes like category, style, color, and size so you can decode it without a lookup.

How many SKUs do I need for one product?

One for every variant a customer can choose. Three sizes in four colors means 12 SKUs. A product with no options needs just one.

Is an SKU the same as a UPC or barcode?

No. The SKU is your internal code. A barcode is the scannable symbol, and a UPC-A barcode typically carries a 12-digit GTIN that is recognized across retailers. You can keep both on the same item without conflict.

Should I change an SKU if I rename the product?

Usually not. Editing a product name does not change its code in at least some systems, and a stable code keeps your sales history connected. Retire a code only when the item itself is discontinued, and never reuse it.

Sources