What Is a SKU on Etsy?

Etsy does not require SKUs and plenty of shops run without them. Here is what they do, when they start mattering, and how to build a format that still makes sense at two hundred listings.

What is a SKU on Etsy

SKU stands for stock keeping unit. On Etsy it is a text field on each listing, and on each variation within that listing, where you can put your own code.

MUG-LRG-CRM tells you it is a mug, large, in cream. Nothing about that comes from Etsy. You decide the format, you decide what the letters mean, and Etsy simply stores whatever you type.

That is the whole feature. The value is not in the field, it is in having a consistent system behind it.

Where SKUs actually appear

Three places, and buyers are in none of them.

Your order details. When a sale comes in, the SKU appears alongside the item. On a listing with nine variations, that code tells you exactly which one to pack without cross referencing the buyer's selections.

Your CSV exports. Etsy lets you download your listings and orders as spreadsheets. SKUs come with them, which makes sorting, filtering and reconciling stock possible.

Any tool you connect. Accounting software, inventory apps, shipping platforms and print on demand integrations all match items by SKU. Without one, they match on title, which breaks the moment you edit a title.

Do you need one

Not at first. With ten listings and no variations, a SKU is a field you fill in for no benefit.

They start earning their place at one of three points.

When variations multiply. Three sizes and three colours is nine things to keep straight. At that point "the medium one in the green" stops being a reliable instruction to yourself.

When you hold physical stock. SKUs are what let a label on a shelf match a line on an order. If you make to order, this matters less.

When you connect anything. The moment an external tool touches your shop, it wants a stable identifier. Titles change, listing IDs are Etsy's, SKUs are yours.

What makes a good SKU format

Readable, consistent, and structured from general to specific.

MUG-LRG-CRM reads at a glance. A7X92B does not, even though a computer is equally happy with both. You are the one reading it at eleven at night with an order sheet in your hand.

Three rules cover almost everything.

General to specific, always in the same order. Product, then size, then colour. Once that sequence is fixed, every code in your shop reads the same way, and so does every code you add next year.

Never encode anything that changes. No prices, no years, no seasons, no supplier names. All of those move, and a SKU that contains one becomes wrong the moment it does. Then you are relabelling stock rather than selling it.

Three characters per segment, usually. Two is often too few. Cream and Charcoal both become CR, and now two different products share a code. Three gives you room, or use initials for two word values so Forest Green becomes FG rather than FOR.

Free toolSKU GeneratorEnter your product code and variation lists, get every combination coded consistently. Copy as a list or CSV.

Building a system that scales

The point of a SKU system is that it still works when you have four times as many products. Two decisions determine whether it does.

Pick your product codes deliberately. Every mug starts MUG, every candle CAN, every print PRT. Write the list down somewhere. Future you will not remember whether tote bags were TOT or BAG, and inconsistency is what makes a system stop being one.

Decide the segment order once. If some codes read product, size, colour and others read product, colour, size, the system is already broken. It only takes a few weeks of casual coding to end up there.

A worked example, for a shop selling mugs and candles:

Anyone could pick up that order sheet and find the right item.

Mistakes that cost you later

Starting with random numbers. Sequential codes like 0001 and 0002 are easy to generate and useless to read. You will still have to look them up, which is the exact problem SKUs are meant to solve.

Reusing a SKU for a different product. Once a code has been on an order, it is in your history. Reusing it for something else corrupts every record that came before.

Leaving them blank on variations. A listing level SKU with nothing on the individual variations gives you a code that identifies the product but not which one sold. That is half a system.

Changing the format halfway. Two hundred listings in two formats is worse than two hundred in a bad one. If you must change, change everything, in one sitting.

How to add SKUs to a listing

In the listing editor, the SKU field sits in the Inventory and pricing section.

If your listing has variations, you will find a SKU column in the variations table once you have set them up. Fill that in rather than the single listing level field, because that is where the useful detail lives.

For bulk edits, Shop Manager has a listings view that lets you edit fields across several listings at once, which is far quicker than opening each one.

Where to start

If you have never used SKUs, do not try to code your entire catalogue today.

Take your three best selling listings, decide your product codes, and code those. Live with the format for a fortnight and see whether it reads well when an order actually arrives. Then roll it out to everything else.

The format you can follow for two years beats the clever one you abandon in a month.