SKUs, barcodes, and variants: build a catalog that stays understandable
Learn the difference between SKUs, barcodes, categories, and variants. Build a clear TinyPOS catalog with stable identifiers and a practical clothing example.
A product name tells a person what an item is. A stable identifier helps you distinguish it from every similar item. When names, codes, and variants are mixed together, checkout and stock counts become harder to trust. A simple catalog convention prevents much of that confusion.
Give each field one job
Use the product name for a readable description, the category for grouping, and a SKU for your internal identity. A barcode is a scannable identifier; it may come from packaging rather than your own naming system. These fields can support one another without being interchangeable.
| Field | Example | Purpose |
|---|---|---|
| Product name | Everyday T-shirt | Recognizable family name |
| Variant | Blue / Medium | Exact sellable choice |
| SKU | TEE-BLU-M | Stable internal reference |
| Barcode | The code on the actual package | Scanning the intended item |
Create only the choices you actually sell
A product with colors and sizes can generate many combinations. Review which combinations exist before creating them all. Keep each available choice's code and price unambiguous, especially when one size costs more.
TinyPOS Cloud's product editor supports simple and variable products within its current limits. Check the editor's rules when planning option groups. Do not design a catalog around unlimited combinations or assume every product type can be edited in the same way.
Keep identifiers stable as the shop changes
Do not encode information that will change next week, such as the current shelf or promotional price, into the only identifier you use. Renaming a display should not require re-identifying every item.
Before assigning a new code, search for an existing product. Duplicates often come from minor spelling differences or a barcode that lost leading zeros in a spreadsheet. Keep a short written rule so everyone adds new products consistently.
Audit a sample before expanding
Select several similar items and follow them from the physical label to the catalog, checkout, receipt, and stock count. If you cannot identify the exact choice at each step, simplify the naming or variant structure before importing more data.
Archive discontinued choices with care rather than casually reusing their codes for a new item. Historical records need to remain interpretable. A smaller clean catalog is easier to maintain than a large one filled with ambiguous duplicates.
- Use a readable product-family name.
- Identify the precise size, color, or package.
- Keep one stable code per intended identity.
- Test the physical label against the checkout result.
Frequently asked questions
- Is a SKU the same as a barcode?
- No. A SKU is an internal reference, while a barcode is a scannable identifier. They may be related, but should not be treated as the same field by default.
- Should every color be a separate product?
- Choose the structure that keeps the exact sellable choice clear. Variants are useful when choices belong to the same family and fit the current editor's supported model.