Skip to main content Scroll Top

Product Variants, SKUs and Options: Structuring an Online Catalog

A small online catalog can be managed almost any way. As it grows, structure starts to matter. How products, variations and options are set up affects whether inventory counts stay accurate, whether shipping calculates correctly, whether shoppers can find what they want and whether you can update the catalog without dread. A little planning keeps the catalog manageable for years.

Products versus variants

Most store platforms distinguish between a product and its variants. The product is the overall item, such as a particular sweater. Variants are the specific versions a customer can buy, such as that sweater in medium and navy. Each variant can have its own price, stock count, weight, photo and SKU.

The rule of thumb is simple. If two versions differ only in a choice the customer makes, like size or color, they are usually variants of one product. If they differ substantially in purpose, description or audience, they may deserve separate product pages.

Advertisement

SKUs that make sense

A SKU, or stock-keeping unit, is your own internal code for a specific item you stock. Every variant you track should have a unique one. A clear SKU system helps with picking orders, counting inventory and connecting your store to other systems.

  • Keep SKUs short and consistent in format.
  • Build them from meaningful parts, such as a product code, then color, then size.
  • Avoid characters that cause problems in spreadsheets or other software, like spaces or slashes.
  • Never reuse a SKU for a different item, even after the old one is discontinued.

Options that do not need variants

Not every choice should become a variant. Platforms often limit how many variants a product can have, and combinations multiply quickly. A product in several sizes, colors and materials can produce dozens of variants. Some choices are better handled as add-on options or custom fields:

  • Personalization, such as engraving or monograms.
  • Gift wrapping or gift messages.
  • Choices that do not affect inventory, such as a note to the maker.

The test is whether the choice affects stock you need to count. If it does, a variant usually makes sense. If it does not, an option is often simpler.

Categories, collections and filters

Shoppers need ways to narrow a catalog. Categories or collections group related products, and filters let people sort by attributes like size, color, material or price. Plan these with customers in mind, using the words they would use. Keep the number of top-level categories modest, and make sure each product’s attributes are filled in consistently, since filters only work when the data behind them is complete.

Keep the source data clean

Many store owners find it easiest to manage the catalog in a spreadsheet and import changes in bulk. Whatever method you use, consistency is the goal: the same units for weight, the same capitalization for colors and the same format for SKUs. Clean catalog data pays off every time you add products, run a sale or connect a new sales channel.

Advertisement

A Worked Example: Setting Up One Product

Imagine a shop that sells a canvas tote bag in three colors and two sizes. The customer can also add a monogram for an extra charge.

  • Product: Canvas tote bag, one product page with one description.
  • Variants: three colors times two sizes, which makes six variants. Each has its own stock count, weight and SKU, and the larger size can carry a different price.
  • Option: the monogram is an add-on with a text field, because it does not change which physical bag is pulled from the shelf.
  • Photos: at least one photo per color, linked to the matching variants so the image changes when the shopper picks a color.

A SKU pattern might combine a short product code, a color code and a size code, such as a few letters for the tote, then a color abbreviation, then S or L. Every bag on the shelf can be labeled with its SKU, so picking and counting match the website exactly.

Now imagine the shop later adds a leather version. It looks similar, but it has a different description, price range and care instructions. That is a good candidate for its own product page rather than a fourth material variant on the canvas tote.

Planning a Catalog Spreadsheet

Whether or not you import products in bulk, a spreadsheet is a useful way to plan. Common columns include:

  • Product name and a short handle or identifier for the product page.
  • Variant attributes, such as size and color, each in its own column.
  • SKU, price and, if you use them, compare-at or sale prices.
  • Weight and dimensions for shipping, all in the same units.
  • Stock quantity.
  • Category or collection, and filter attributes like material.
  • Image file names.
  • Tax category, if your accountant has advised you to use different ones.

Before importing, download your platform’s sample import file and match its column names exactly. Then import a small batch first and check it carefully before loading the whole catalog.

Common Catalog Mistakes

  • Inconsistent attribute values. If some products say Navy, some say navy blue and some say Dark Blue, filters will show three separate choices. Pick one value and use it everywhere.
  • Missing weights. Products without weights can produce wrong shipping charges, sometimes in your favor and sometimes not.
  • Duplicate products. Creating a new product for every color makes inventory harder and splits reviews across pages.
  • Variants for everything. Turning every customization into a variant multiplies the catalog and can hit platform limits.
  • Changing SKUs casually. If your SKUs connect to a register, marketplace or inventory system, changing them can break the link. Plan any change carefully.

Questions to Ask When Choosing or Changing Platforms

  • How many variants and options can each product have?
  • Can each variant have its own photo, weight and price?
  • How are add-on options priced and shown in orders and packing slips?
  • Can filters be built from our own attributes?
  • How does bulk import and export work, and can we export the entire catalog if we leave?

Questions Store Owners Ask

Do we need SKUs if we only have a few products?

They are still helpful. SKUs make orders easier to pick, help when you connect another sales channel and save renaming work later as the catalog grows.

Should discontinued products be deleted?

Often it is better to mark them unavailable or redirect the page to a similar item, especially if the page gets visits from search or old links. Keep the SKU retired rather than reusing it.

Latest stories

View all
Our clients