Managing product variations: sizes, grades and colors without a SKU mess
A lumber yard sells Black Walnut in 4/4, 6/4 and 8/4, in FAS and Select grades. A print shop sells one T-shirt in five colors and six sizes. A hardware store stocks the same screw in a dozen lengths. In every case it is “one product” to the customer and several very different things on the shelf. How you list those variations decides whether your counts mean anything.
Two common approaches, and why they break
One item for the whole range
“Black Walnut”, stock 180, with a note saying “mixed thicknesses”. It is quick to set up and useless the first time a customer asks for 40 board feet of 8/4. The total hides the one number you need, and a low-stock alert on the total fires far too late for the thickness that actually runs out.
Everything crammed into the name
“Black Walnut 4/4 FAS”, “Blk Walnut 8/4 Sel”, “Walnut, black, 6/4 (FAS)”. Each variation has its own count, which is right, but the details live in free text. Spelling drifts, search misses half of them, and there is no way to filter or report by grade because grade is not a field, just part of a sentence.
A better pattern: one item per variation, details in fields
Give each variation you count separately its own item, keep the shared product name, and put what differs in a custom field:
- Name: Black Walnut (the same for every variation)
- Thickness/Grade: 4/4 FAS, 6/4 FAS, 8/4 Select
- Barcode or SKU: one per variation, if you label them
- Unit, cost and sale price: per variation, because they really do differ
The name stays clean and searchable, the counts are per variation, and the field can be shown as a column, filtered and exported. In Simple Inventory, items that share a name are automatically labelled with what tells them apart, so lists, orders, quotes and printed purchase orders all read “Black Walnut (8/4 Select)” and nobody picks the wrong board.
What counts as a variation?
Not every difference needs its own item. A simple test:
- Do you count it separately? If you need to know how many 8/4 boards you have, 8/4 is a variation.
- Do you price or reorder it separately? Different cost, sale price or supplier usually means a separate item.
- Does it have its own barcode? If the manufacturer gives it one, treat it as its own item.
If the answer to all three is no, for example a batch number or a shelf location, it is a detail of the item, not a variation. Keep it in a field, or on a lot if you track lots.
Keep the values consistent
The pattern only works if the values match. Decide on one way of writing each attribute and stick to it: “4/4”, not sometimes “four quarter”; “Navy”, not “navy blue” on half the shirts. A short list of allowed values on a sticky note beats a clever naming scheme nobody remembers. For codes, our guide to SKUs and barcodes covers how to build them so they stay readable.
Import a whole range at once
Setting up dozens of variations by hand is tedious. A spreadsheet with one row per variation and a column per attribute is faster:
A CSV import brings in each row as its own item when the attribute column (or the barcode) tells them apart. If the attribute is not a custom field yet, the importer can create it for you. The preview lists the variations it found before anything is saved, and a row that matches an item you already have is skipped, or updated if you choose to update existing items. That makes the same spreadsheet useful later for refreshing prices or stock counts.
A short checklist
- Make a variation its own item when you count, price or reorder it separately.
- Keep one shared product name and put the differences in custom fields.
- Agree on how each attribute is written, and stick to it.
- Give each variation its own barcode if you label stock.
- Set warning levels per variation, so the size that runs out is the one that alerts you.