A Simple SKU System for Resellers: Tie Every Listing to a Physical Spot

Published 2026-11-10

If you cannot find an item when it sells, the problem is not your memory, it is your labelling. A SKU system gives every physical item one code that never changes, and a location system tells you where that code is sitting right now. Set both up before your stock grows and finding things stops being a daily search. Below is a simple method you can start today, the trade-offs between the options, and the places it can still go wrong.

What a SKU is for, and what it is not

A SKU is your own internal item code. Its job is to link one physical item to one record, so that when a sale comes in you can find the thing in seconds. It is not the manufacturer's barcode, and it is not the marketplace listing number. Confusing these is the most common reason resellers end up with a box of items they cannot match to a sale.

Keep the SKU short, unique and never reused. Sequential codes such as SL-1001, SL-1002 and so on work well because they carry no meaning that could go out of date. A code like BLK-M-NIKE-HOODIE looks helpful but breaks the moment the item's colour, size or brand is edited or misentered, and then the label no longer matches the record.

Step-by-step: set up the system in an afternoon

Work through these steps in order. Doing them out of order is how duplicates appear.

• Pick one SKU format and write it down. Use a fixed prefix and a counter, and never change the format halfway through.
• Assign the SKU at the moment the item enters your stock, not when it is photographed for listing. Items that are only ever photographed end up with no code at all.
• Print the SKU onto a label and attach it to the item, not to the packaging. Packaging gets separated from items; the item rarely does.
• Give every storage spot its own location code, such as a shelf, bin or rail reference. Write the location against the SKU in your records the moment you put the item down.
• Each time you move an item, update its location in the same session. A location that is wrong by one move is still wrong.
• Do a short spot check each week: pick five random SKUs, find them, and fix any that are not where the record says.

Choosing between printed labels and handwritten codes

There are two realistic ways to mark items. Handwritten codes on a tag or sticky label cost almost nothing and need no equipment, but they are hard to read once tags curl, fade or get damp, and handwriting errors (a 1 that looks like a 7) cause mismatches that are hard to spot. A thermal or label printer costs more to set up but produces clean, consistent codes that can be scanned rather than typed.

A scanner removes typing errors entirely. If you use a USB barcode scanner or a webcam in Chrome, scanning a label can open the matching item directly, which is far quicker than searching by hand when a sale arrives. The trade-off is that scanning only helps if the label is on the item and stays readable, so the physical attachment still matters as much as the code.

Whichever you choose, keep the SKU itself in one place and do not create a second code for the same item. Two codes for one item means two records that will drift apart.

Worked example: finding a sold item

Suppose you sell a navy wool jumper. It has the label SL-1047 stuck inside the collar and sits on the shelf marked B3 in your storage box. The sale notification comes through with the item name. You search your records for the name, find SL-1047, check its location field reads B3, and go straight to the shelf. You pack it, and the SKU on the packing slip matches the label you can see.

Now imagine the same jumper with no SKU and a location written only in your head. You search through three boxes, find a similar navy jumper, pack the wrong one, and only realise when the buyer messages you. The system did not fail because the tools were bad. It failed because the identifier was never attached to the physical item.

Where this goes wrong, and how to lower the risk

A SKU system breaks in predictable ways, and it is better to know them now. Labels fall off, especially on soft or textured items, so check adhesion when you attach them. Items get moved without the record being updated, so the spot check matters more than the setup. Two items get the same code because a counter was reset or two people labelled stock on different days; keep one person responsible for issuing codes, or use software that assigns them and blocks duplicates.

Automation adds its own risk. If you use a crosslisting tool, the SKU only protects you if the item it links to is the one on your shelf. A tool that matches on the wrong record will send a sale notice for the wrong item, and automated delisting can then take down a listing you still have. The safeguard is to check that the item name, photos and SKU in the record match the physical object before you rely on any automatic sale or delist. Swiftlisted assigns a SKU to each item the first time it is saved, and can print labels and scan a SKU to open the matching item, but it cannot confirm that the label is physically on the right object. That check is yours.

Marketplace policies on item identifiers, labelling and automated activity differ by marketplace and change over time. Check each marketplace's current policy before you rely on a particular method, rather than assuming a rule that held last year still applies.

Start today: a minimal checklist

You do not need a perfect system to get value from one. Start small, and tighten it as your stock grows. The first week is about consistency, not completeness.

• Choose your SKU format and never change it.
• Label every new item the day it arrives.
• Write the storage location against the SKU the moment you store it.
• Scan or search the SKU when a sale comes in, and check it against the physical item before packing.
• Run a five-item spot check every week.

Common questions

Should my SKU include the brand or size?

Generally no. Brand and size can be edited or mistyped, and a code that changes meaning no longer matches the label on the item. A simple sequential code that never changes is safer. Keep descriptive details in the record, not in the code.

Is a SKU the same as a barcode?

No. A SKU is your own internal code for a physical item. A barcode is usually a retail EAN or UPC printed on a product by its manufacturer. Some sellers record both: the SKU to find the item in their own stock, and the barcode to identify the product.

What if a label falls off an item?

Re-label it straight away using the same SKU, not a new one, and check your record still points to that code. Use labels suited to the material of the item and test adhesion when you attach them, since soft or textured items are the most likely to lose labels.

Do I need label-printing software to do this?

No. Handwritten codes work if you write them clearly and keep one person responsible for issuing them. Printed labels reduce reading and typing errors, and a scanner removes most of the remaining ones, but neither is required to start.