5 What Is an SKU? Understanding Product Management for Different Specification Combinations
Create a clear way to identify specific product versions, so inventory checks, order picking, and restocking are more organized
An SKU is a stock keeping unit used to distinguish and manage products. When the same product comes in different colors, sizes, or capacities, each combination that needs to be managed separately can correspond to one SKU. This article uses simple examples to explain the relationship between SKUs, product specifications, product numbers, and barcodes, helping merchants organize product information and reduce confusion during order processing.
When the same product comes in different colors, sizes, or capacities, how can merchants distinguish them accurately?
For example, a top is offered in:
๐ต Blue, size S.
๐ต Blue, size M.
๐ต Blue, size L.
โช White, size S.
โช White, size M.
โช White, size L.
When a customer buys "Blue, size M," the merchant needs to locate the correct product version, not just know that the customer bought a top.
If the warehouse also holds other colors, sizes, and items with similar appearances, relying on the product name alone may lead to picking errors.
A SKU (Stock Keeping Unit) helps merchants distinguish between product versions, so that product specifications, codes, prices, inventory, and orders are clearly linked.
For merchants who manage products using the WeiCity Shop, understanding the role of SKUs helps organize product information, reconcile orders, and plan inventory management.
This article introduces the basic concept of SKUs, numbering methods, specification combinations, inventory management, the difference from barcodes, and points to note in actual use.
SKU is an abbreviation of Stock Keeping Unit, commonly called "inventory unit" in Chinese.
It is used to identify product versions that need to be managed separately.
For example:
A top comes in two colors, and each color has three sizes.
If all combinations are in supply, they form six SKUs.
๐ต Blue + S: one SKU.
๐ต Blue + M: one SKU.
๐ต Blue + L: one SKU.
โช White + S: one SKU.
โช White + M: one SKU.
โช White + L: one SKU.
When all combinations are actually supplied and managed separately:
2 colors ร 3 sizes = 6 SKUs.
However, if one of the combinations is not supplied, you do not necessarily need to create a saleable inventory record for it.
It can also have one.
For example:
๐ฆ A storage box with a fixed specification.
โ A 500ml thermos bottle.
๐ ๏ธ A tool in one fixed model.
Even if a product has no multiple specifications, it can correspond to one SKU as long as it needs to be identified and managed separately.
๐ฆ Distinguishing different product versions.
๐จ Corresponding to colors, sizes and styles.
๐ฐ Checking the selling prices of different versions.
๐ Managing inventory for each version.
๐ Identifying products in orders.
๐ Supporting returns, exchanges and restocking.
๐ The key point of a SKU is to let merchants know exactly which product version they are managing.
SKUs and product specifications are closely related, but they serve different purposes.
Mainly helps customers choose the product version they need.
For example:
Product: Men's Casual Top
Color:
๐ต Blue.
โช White.
Size:
๐ S.
๐ M.
๐ L.
Represents the specific version the customer ultimately selects.
For example:
Blue + M
Merchants can assign an identification number to this specific version.
For example:
TEE01-BLU-M
Product specifications: What does the customer need to choose?
Variant combination: Which version does the customer ultimately choose?
SKU number: How does the merchant identify this version?
The customer purchases:
๐ Men's casual top.
๐จ Color: Blue.
๐ Size: M.
๐ข Quantity: 1.
Internally, the merchant can match:
๐ท๏ธ SKU: TEE01-BLU-M.
In this way, customers see easy-to-understand product options, while merchants can use the number to support management.
Customers may not know:
TEE01-BLU-M
what it represents.
Therefore, product pages should still clearly display:
๐จ Blue.
๐ Size M.
๐ Product specifications help customers choose; SKUs help merchants identify and manage.
There is no fixed format for SKU numbers that applies to all merchants.
Merchants can set their own rules based on product quantity, categories and internal management methods.
A common approach is to use a short product style code plus a specification code.
Product: Men's Casual Top
Product style code:
TEE01
Color code:
๐ต BLU: Blue.
โช WHT: White.
Size code:
๐ S: Small.
๐ M: Medium.
๐ L: Large.
Combined, they can form:
๐ท๏ธ TEE01-BLU-S.
๐ท๏ธ TEE01-BLU-M.
๐ท๏ธ TEE01-BLU-L.
๐ท๏ธ TEE01-WHT-S.
๐ท๏ธ TEE01-WHT-M.
๐ท๏ธ TEE01-WHT-L.
Taking:
TEE01-BLU-M
as an example:
๐ TEE01: A certain top.
๐ต BLU: Blue.
๐ M: Size M.
Product: Stainless Steel Insulated Cup
๐ท๏ธ CUP01-BLU-500.
๐ท๏ธ CUP01-WHT-500.
๐ท๏ธ CUP01-BLU-750.
๐ท๏ธ CUP01-WHT-750.
Including:
CUP01: Product style code.
BLU / WHT: Color codes.
500 / 750: Capacity codes.
The above are illustrative number examples only and are not a fixed SKU coding rule of WeiCity.
โ Use a fixed order of arrangement.
โ Keep the number length moderate.
โ Use different numbers for different versions.
โ Use consistent codes for the same color.
โ Use a consistent format for the same size.
โ Keep a record linking numbers to product information.
The purpose of a SKU is to identify products, not to replace complete product descriptions.
For example:
Material, usage instructions and care requirements can be kept in the product description.
๐ A good SKU number should be easy to recognize, follow consistent rules and be convenient to maintain over the long term.
Suppose a merchant sells a thermos bottle.
Product name:
"Stainless Steel Thermos Bottle"
Actually provided:
๐ต Blue + 500ml.
โช White + 500ml.
๐ต Blue + 750ml.
โช White + 750ml.
If the order only records:
"One thermos bottle"
the merchant cannot determine which version should be provided.
๐ฆ Product names.
๐จ Product color.
๐ Product capacity or size.
๐ข Purchase quantity.
๐ท๏ธ The necessary internal product number.
Product: Stainless Steel Insulated Cup
๐จ Color: Blue.
โ Capacity: 750ml.
๐ข Quantity: 2.
๐ท๏ธ Internal SKU: CUP01-BLU-750.
Based on this information, merchants can check inventory and then arrange picking and packaging.
For example, the warehouse stores the following at the same time:
๐ต Blue 500ml.
๐ต Blue 750ml.
โช White 500ml.
โช White 750ml.
Through the correspondence between SKUs and product specifications, staff can more easily identify the version to pick up.
It is still recommended to check:
๐ท๏ธ SKU.
๐ฆ Product names.
๐จ Color.
๐ Specifications.
๐ข Quantity.
Especially for products with similar numbers, extra care is needed to confirm.
๐ SKUs can support order processing, but accurate product names and specification information remain essential.
A product having total stock does not mean every specification is still available.
For example, a thermos bottle has four specification combinations.
The following is hypothetical data.
๐ต Blue + 500ml: 8 pieces.
โช White + 500ml: 5 pieces.
๐ต Blue + 750ml: 3 pieces.
โช White + 750ml: 0 pieces.
8 + 5 + 3 + 0 = 16 pieces.
Although this thermos bottle has 16 pieces in total, the white 750ml version has no saleable stock left.
The merchant may only see:
"Thermos bottle: 16 pieces"
but not know:
โ Which color has sold out.
โ Which capacity needs restocking.
โ Whether the combination chosen by the customer is still in stock.
You can separately view:
๐ฆ The saleable quantity of each version.
๐ Which specifications have low stock.
๐ Which versions need order processing.
๐ Which products need restocking.
For example:
CUP01-WHT-750: 0 pieces.
The merchant can clearly see that the supply of white 750ml needs to be checked.
Instead of vaguely restocking all thermos bottles.
Even after SKUs are set up, regularly check:
๐ฆ Actual Stock.
๐ Unprocessed orders.
โฉ๏ธ Returned products.
โ ๏ธ Damaged products.
๐ Inventory adjustment.
For specific methods of inventory deduction, reservation and replenishment, refer to WeiCity's current Shop features.
๐ Distinguishing inventory by SKU lets merchants see more clearly which product version is short.
A SKU is more than just a number.
It also needs to be linked to the correct product information.
For example:
SKU: CUP01-BLU-500.
Corresponds to:
๐ต Blue.
โ 500ml.
If the SKU represents a blue thermos bottle, the related images should accurately show the blue version.
For example:
CUP01-BLU-500: RM29.
CUP01-BLU-750: RM39.
The above prices are examples.
For example:
CUP01-BLU-500: 8 pieces.
CUP01-BLU-750: 3 pieces.
If the merchant has a warehouse, the following can be added to internal management records:
๐ Shelf number.
๐ฆ Storage area.
๐ท๏ธ Product labels.
For example:
SKU: CUP01-BLU-500.
Internal location: Zone A, Level 2.
Recommended items to confirm:
โ The number matches the product.
โ Colors are correct.
โ The size or capacity is correct.
โ The images match the actual version.
โ Prices are accurate.
โ The inventory quantity is correct.
For example:
A merchant enters the 750ml price for the 500ml version.
Even if the SKU number is correct, the product price may still be wrong.
Therefore, the number and product information must be checked separately.
๐ A SKU is a tool for identifying products; accurate images, prices and inventory information still need to be maintained by the merchant.
SKUs and barcodes often appear together, but they are not the same thing.
An SKU is a stock keeping unit that merchants use to identify a specific product version.
For example:
TEE01-BLU-M.
An SKU number is a code that merchants use to identify a specific product version.
For example:
CUP01-WHT-750.
A barcode is a way of representing encoded data so that devices can scan and read it.
For example, the barcodes commonly printed on retail product packaging.
SKU: Represents a product version that needs to be managed separately.
SKU number: The identification code a merchant uses for that version.
Barcode: A way of conveying encoded information that can be read by a scanning device.
With suitable systems and devices, an internal number can be encoded as a barcode to make scanning and identification easier.
However, retail barcodes on product packaging may also use product identification standards such as GTIN, EAN, or UPC.
Therefore:
A product having a barcode does not necessarily mean the number in the barcode matches the merchant's internal SKU.
Whether the following are supported:
โฅ Barcode labels.
๐ฑ Scan-based identification.
๐ท๏ธ Barcode fields.
๐ฆ Barcode-based inventory management.
Please refer to WeiCity's current actual features and to the external devices or systems you use.
๐ An SKU identifies a product version, while a barcode is one way of reading encoded information.
Merchants have different types of products, so they can use a numbering method that suits their own business.
Product:
Men's casual top.
SKU examples:
๐ท๏ธ TEE01-BLK-M.
๐ท๏ธ TEE01-BLK-L.
๐ท๏ธ TEE01-WHT-M.
Product:
Casual sports shoes.
SKU examples:
๐ท๏ธ SHOE01-BLK-40.
๐ท๏ธ SHOE01-BLK-41.
๐ท๏ธ SHOE01-WHT-40.
Product:
Stainless steel insulated cup.
SKU examples:
๐ท๏ธ CUP01-BLU-500.
๐ท๏ธ CUP01-BLU-750.
๐ท๏ธ CUP01-WHT-500.
Product:
Canvas tote bag.
SKU examples:
๐ท๏ธ BAG01-BLK-ZIP.
๐ท๏ธ BAG01-WHT-ZIP.
๐ท๏ธ BAG01-BLK-OPEN.
Product:
Desktop storage box.
SKU examples:
๐ท๏ธ BOX01-WHT-S.
๐ท๏ธ BOX01-WHT-L.
๐ท๏ธ BOX01-GRY-S.
Product:
Holiday gift boxes.
SKU examples:
๐ท๏ธ GIFT01-RED-SET2.
๐ท๏ธ GIFT01-BLU-SET2.
๐ท๏ธ GIFT01-RED-SET3.
Product:
Fixed-model tools.
SKU examples:
๐ท๏ธ TOOL01-10MM.
๐ท๏ธ TOOL01-12MM.
๐ท๏ธ TOOL01-15MM.
Not necessarily.
Merchants can set their own rules based on the characters their system supports and their internal management needs.
However, a short and consistent combination of letters and numbers is usually easier to record and recognize.
In practice, rules should be set based on product structure, team habits, and system field requirements.
๐ SKU numbers do not need to be complicated. The key is to stay consistent over time and accurately match each product version.
When preparing products, you can first create a clear record that matches specifications with SKUs.
Then fill in the fields provided on WeiCity's current product editing page.
For example:
โMen's casual topโ
For example:
Color:
๐ต Blue.
โช White.
Size:
๐ S.
๐ M.
๐ L.
For example:
๐ต Blue + S.
๐ต Blue + M.
๐ต Blue + L.
โช White + S.
โช White + M.
โช White + L.
For example:
TEE01-BLU-S.
TEE01-BLU-M.
TEE01-BLU-L.
TEE01-WHT-S.
TEE01-WHT-M.
TEE01-WHT-L.
Make sure each combination has the correct selling price.
Record them based on your actual supply.
Confirm that the images match the colors and styles.
If the current product supports specification selection, check it from the customer's perspective:
๐จ Color.
๐ Size.
๐ฐ Prices.
๐ฆ Supply availability.
If the current product supports the shopping cart and checkout, you can check whether orders correctly show the selected specifications.
You can first keep SKU records in your internal product management spreadsheet.
For example:
๐ฆ Product names.
๐จ Specification combinations.
๐ท๏ธ SKU number.
๐ฐ Prices.
๐ Inventory.
Whether a dedicated SKU field, automatic numbering, or other management methods are available depends on WeiCity's current product editing page.
๐ Establishing accurate SKU mappings first, and then using them according to the actual features available, can keep product information organized.
SKU numbers are not complicated in themselves, but without consistent rules, they can easily become confusing over time.
For example:
TEE01-BLU-M.
The same number represents:
Blue, size M.
Blue, size L.
This makes the number lose its ability to distinguish products.
Recommendations:
Assign different numbers to versions that need to be managed separately.
For example:
Blue is sometimes written as BLU.
Sometimes it is written as BLUE.
Sometimes it is written as B.
Without a consistent team rule, this can easily cause confusion.
Recommendations:
Create a fixed color code table.
For example:
Putting the product name, full description, supplier name, and every feature into the number.
This may increase the chance of data entry errors.
Recommendations:
Keep only the identifying information that is necessary.
For example:
An SKU originally matched an old tote bag.
After it was discontinued, the same number was used for a different new product.
This can make it harder to identify historical orders and inventory records.
Recommendations:
Keep the historical mapping of the old number, and create a new number for the new product.
For example:
The SKU corresponds to blue, size M.
But the image shows white, size L.
Recommendations:
Check the number, specifications, images, and prices together.
Customers may not understand internal numbers.
Recommendations:
Product pages should still use clear names for color, size, and style.
For example:
The system record shows 10 items remaining.
The actual warehouse has only 6 left.
Recommendations:
Regularly check physical stock against records.
๐ SKU management requires a consistent numbering system and ongoing maintenance of accurate product information.
SKUs are not only used when listing products. They can also support everyday product management.
The customer purchases:
๐ Men's casual top.
๐จ Blue.
๐ Size M.
๐ข 2 pieces.
Merchants can check the products they need to prepare based on the corresponding SKU.
If a warehouse has several similar versions, SKUs can help staff identify the correct product.
For example:
TEE01-BLU-M: 3 remaining.
TEE01-BLU-L: 10 remaining.
Merchants can clearly see which version has less stock.
For example:
Blue size M often sells out.
Merchants can assess whether to increase purchase quantities for that version based on actual sales and inventory records.
For example:
A customer receives the wrong size.
Merchants can check:
๐ฆ The original ordered product.
๐จ Color.
๐ Size.
๐ท๏ธ SKU.
Then handle it according to the actual after-sales policy.
When a version changes, it is easier to find the corresponding record.
For example:
๐ฐ Price adjustments.
๐ฆ Inventory updates.
๐จ Style changes.
๐ผ๏ธ Image updates.
Creating SKUs does not mean the system will automatically complete the following tasks:
๐ Inventory deduction.
๐ Restock alerts.
โฅ Barcode-based picking.
โฉ๏ธ Returned stock replenishment.
Whether these features are available depends on the system you are currently using.
๐ SKUs provide a clear basis for product identification, while actual automation depends on system features.
The main purpose of SKUs is product identification and inventory management, not search ranking optimization.
However, accurate product numbers and specification information can help merchants keep product information consistent.
For example:
โ500ml Stainless Steel Thermosโ
Rather than simply using:
โCUP01-BLU-500โ
Names that are easier for general customers to understand.
For example:
Color: blue.
Capacity: 500ml.
For example:
๐ Dimensions.
๐ ๏ธ Materials.
๐ฆ Package contents.
For example:
Use the matching blue product photo for blue items.
Adding SKUs does not automatically increase search visibility.
Whether search engines can crawl, index, or display different product versions also depends on platform technical settings, page structure, and other factors.
๐ SKUs mainly help merchants manage products, while Google SEO focuses more on whether pages provide accurate, useful, and accessible content.
SKU is an abbreviation of Stock Keeping Unit, commonly called "inventory unit" in Chinese.
It is used to identify product versions that need to be managed separately, making it easier to check specifications, prices, inventory, and orders.
Specifications help customers make their choice.
An SKU helps merchants identify and manage specific versions.
Yes.
For example, different colors and sizes of the same top can each correspond to their own SKU.
It can also have one.
A product with only one fixed version can correspond to one SKU.
You can use the product style number plus color, size, or capacity codes, and keep the rules consistent.
Not necessarily, but they must follow the character rules supported by the actual system.
For different product versions that need to be identified separately, it is not recommended to reuse the same code.
No.
An SKU identifies a product version, while a barcode is a way to scan and read encoded information.
Whether automatic numbering is available depends on the current product editing page.
Whether a separate SKU or merchant code field is provided depends on the features currently available.
SKUs help distinguish different versions; the specific way prices are set depends on the current product features.
They can serve as a basis for tracking inventory of different versions, but the actual inventory management capabilities depend on the system features.
They can help verify the original order against the actual product version.
No.
Codes that are clear, short, consistent, and non-duplicated are usually more convenient for daily management.
๐ The value of an SKU lies not in how complex the code is, but in whether it accurately corresponds to the product version.
โ Product name is correct.
โ Product styles are clear.
โ Actual supplied versions have been organized.
โ Colors are correct.
โ Dimensions are accurate.
โ Capacity information is complete.
โ Specification combinations are clear.
โ Code rules are consistent.
โ Different versions are easy to tell apart.
โ No codes have been reused.
โ Codes match product information.
โ The selling price of each version is correct.
โ Prices for different specifications are not confused.
โ Available quantities are accurate.
โ Inventory for each version is clear.
โ Actual supply has been checked.
โ Images match the colors.
โ Images match the styles.
โ Package contents are accurate.
โ The version chosen by the customer can be identified.
โ Product names and specifications are clear.
โ Quantities are correct.
โ New products have corresponding codes set up.
โ Discontinued products keep necessary records.
โ Inventory changes are updated promptly.
โ Code rules are kept consistent over time.
๐ After SKUs are set up, it is recommended to regularly check product information, inventory, and orders to ensure codes always correspond to the correct product versions.
The role of an SKU is not just to assign a code to a product.
It helps merchants organize different colors, sizes, capacities, and styles into clear product versions.
๐จ Product specifications: Help customers choose the version they need.
๐ฆ Specification combinations: Clarify the exact product the customer is buying.
๐ท๏ธ SKU code: Helps merchants identify specific versions.
๐ฐ Product price: Matches the correct specification combination.
๐ Inventory quantity: Tracks the supply status of different versions.
๐ผ๏ธ Product images: Show the correct colors and styles.
๐ Order checking: Helps merchants confirm the product the customer bought.
๐ Restocking and returns/exchanges: Makes it easy to find the corresponding version and historical records.
Product specifications and SKU management in the WeiCity Shop can be planned around the same set of product information, creating a clear link between customer choices and merchant management.
For customers, the clearer the product specifications, the easier it is to choose the right color, size, or style.
For merchants, the more accurate the SKU correspondence, the easier it is to identify products, check orders, and manage inventory.
๐ท๏ธ Clear codes make products easy to identify.
๐จ Accurate specifications make it easy for customers to choose.
๐ฆ Clear inventory shows merchants which version is running low.
๐ Clear order information makes picking and processing more organized.
From product name and specification combinations to SKU codes, then checking prices, images, and available quantities, every product version has a clear basis for management.
Specific SKU fields, automatic numbering, inventory management, barcodes, and order features depend on the current WeiCity Shop pages, product editing features, and the services you have activated.
๐ Open WeiCity: https://wei.city/