What is a Stock Keeping Unit (SKU)?

A Stock Keeping Unit, commonly referred to as a SKU, is a unique set of characters assigned to a specific product or service to track inventory and manage sales. In the context of a startup or a growing business, the SKU acts as the primary identifier for everything you sell. While consumers often see them as barcodes on a retail shelf, for a founder, the SKU is the fundamental building block of an operational data system.

Unlike other identifiers, a SKU is strictly internal. This means your business decides how to format it, what information to include, and how to organize the hierarchy. Every variation of a product requires its own unique SKU. If you sell a t-shirt in three sizes and three colors, you do not have one product; you have nine distinct SKUs. This granularity allows you to see exactly which items are moving and which are sitting in storage.

The SKU serves as a shorthand for product attributes. In a digital environment, it links your physical inventory to your point of sale system and your accounting software. When an item is scanned or sold, the SKU tells the system which item has left the building. This automation is necessary for maintaining accurate stock levels and preventing overselling in e-commerce.

For many founders, the first encounter with SKUs happens when they move beyond their first few sales. At the start, you might know your inventory by heart. However, as soon as you add complexity, such as different materials or packaging sizes, memory fails. The SKU provides a systematic way to categorize these differences without relying on human memory or descriptive names that might be interpreted differently by different employees.

It is important to note that a SKU is not the same as a serial number. A serial number tracks a specific, individual unit (like the specific iPhone in your hand). A SKU tracks a group of identical units (like all iPhone 15 Pro Max 256GB models in Titanium). This distinction is vital for quality control and warranty management.

Designing a SKU system requires a balance between information density and readability. Most entrepreneurs use an alphanumeric format that reflects the attributes of the product. A common mistake is to create a random string of numbers. Random numbers do not provide any context to the warehouse picker or the person managing the spreadsheets. Instead, a logical structure might follow a pattern like Category, Sub-category, Color, and Size.

Consider a small company selling coffee beans. A SKU like COF-BOL-MED-12 might represent Coffee, Bolivia origin, Medium roast, 12-ounce bag. This format allows anyone looking at the code to understand exactly what the product is without looking up a master list. It also helps in sorting data. If you sort your sales data by the first three letters, you can instantly see how the entire coffee category is performing compared to equipment or merchandise.

There are several technical pitfalls to avoid when creating these codes. You should avoid using the letters O and I because they can be easily confused with the numbers 0 and 1. You should also avoid using special characters or symbols that might break a CSV file or cause errors in database software. Keep the codes as short as possible while still remaining descriptive. Long SKUs are prone to data entry errors and can be difficult to print on small product labels.

One of the most frequent points of confusion for new founders is the difference between a SKU and a UPC. A Universal Product Code (UPC) is a standardized barcode used across the entire retail world. If you want to sell your products in a major retail chain, you will likely need to purchase UPCs from an organization called GS1. A UPC remains the same no matter who is selling the product.

In contrast, the SKU is yours alone. You can change your SKU architecture whenever you want without asking for permission from an outside body. Two different companies selling the exact same brand of shoes will have the same UPC for those shoes, but they will almost certainly have different internal SKUs to match their own warehouse management systems.

Why use both? The UPC allows you to play in the global marketplace and ensures compatibility with external vendors. The SKU allows you to run your internal operations with a logic that makes sense for your specific team. If you are a direct to consumer startup that never intends to sell in third party retail, you might never need a UPC, but you will always need a SKU to keep your warehouse organized.

When should you start building your SKU library? The answer is usually sooner than you think. Retroactively changing your inventory system once you have hundreds of products is a logistical nightmare. It involves relabeling physical stock and updating digital records across multiple platforms. Starting with a clean, scalable SKU architecture on day one saves significant time and money later.

In a manufacturing scenario, SKUs are also used for raw materials. This is often called a Bill of Materials. If you build furniture, you might have SKUs for the finished table, but you also have SKUs for the specific screws, the wood planks, and the finish used. This allows you to track the cost of goods sold with extreme precision. You can see how a price increase from a screw supplier affects the overall margin of your finished product.

In a service based startup, SKUs are used to track different service tiers or billable units. For example, a consulting firm might have different SKUs for a junior associate’s hourly rate versus a partner’s hourly rate. This allows the business to analyze which services are the most profitable and how many hours are being allocated to specific tasks. Even without physical goods, the SKU provides the framework for data analysis.

As we look toward the future of logistics, the role of the SKU is evolving. We are seeing the rise of RFID tags and computer vision systems that can identify products without a traditional barcode scan. If a camera can identify a product just by looking at its shape and color, do we still need an alphanumeric code? This is a question many logistics researchers are currently exploring.

There is also the question of how much data a SKU should actually hold. Some argue that with modern databases, the SKU should be a simple, short identifier, and all product attributes should live in the database metadata. Others argue that human readable SKUs are essential for frontline workers who may not always have a screen in front of them. Finding the balance between human centered design and machine efficiency is a challenge every founder faces.

Ultimately, the SKU is a tool for clarity. It removes ambiguity from your operations. Whether you are managing five items or five thousand, the way you structure your identifiers will determine how easily you can scale. It is a quiet, often overlooked part of the business, but it is the foundation upon which your inventory management and financial reporting are built. Think through your architecture now so you do not have to fix it when you are too busy to stop.