Stock Keeping Unit (SKU)

Definition: A Stock Keeping Unit (SKU) is an internal alphanumeric identifier assigned to a specific inventory item to distinguish it from all other items in a storeroom or warehouse. Each SKU captures the attributes that make an item unique within a given organization, including category, specification, unit of measure, and storage location.

What Is a Stock Keeping Unit (SKU)?

A Stock Keeping Unit is the smallest discrete unit of inventory tracked within a storage system. Unlike a manufacturer part number, which is set externally, a SKU is created and controlled by the organization managing the stock. This means two facilities in the same company can assign different SKUs to the same bearing, gasket, or filter based on how each location classifies and stores it.

In maintenance and operations contexts, SKUs are most valuable when they encode enough information to make an item identifiable at a glance. A technician searching for a replacement seal should be able to read the SKU and know immediately whether that item is the right type, the right size, and stocked in the right location, without needing to cross-reference a separate catalog.

How SKUs Are Structured

A SKU is typically an alphanumeric string of 8 to 14 characters divided into segments. Each segment encodes a specific attribute. The exact structure varies by organization, but a common pattern for maintenance inventory looks like this:

Segment Example What It Encodes
Category prefix BRG Item category (e.g., Bearing)
Supplier code SKF Preferred supplier or manufacturer
Specification code 6205 Part specification or model number
Unit of measure EA Each, box, liter, meter, etc.
Location code A04 Bin, shelf, or storeroom aisle

A full SKU built from these segments might be BRG-SKF-6205-EA-A04. A technician reading this knows immediately: it is a bearing from SKF, model 6205, stocked by the unit, located in bin A04.

Some organizations shorten SKUs by dropping the supplier or location segment and managing those attributes separately in a CMMS. The key principle is consistency: every SKU must follow the same structure and every attribute must mean the same thing across all records.

SKU vs UPC vs Part Number

These three identifiers are often confused in maintenance and procurement conversations. They serve different purposes and originate from different sources.

Identifier Who Assigns It Scope Primary Use
SKU Internal (your organization) Unique within your system only Internal inventory tracking, reorder, and auditing
UPC Manufacturer (via GS1 standard) Globally unique across all retailers Point-of-sale scanning and supply chain traceability
Part Number Manufacturer Unique within a manufacturer's catalog Ordering from supplier, cross-referencing spec sheets

In practice, a well-configured inventory management system stores all three identifiers for each item. The SKU drives internal workflows. The part number links to procurement. The UPC supports barcode scanning during receiving and cycle counts.

SKUs in MRO and Maintenance Inventory

In MRO (maintenance, repair, and operations) environments, the SKU system carries more operational weight than in retail or distribution. Maintenance teams do not re-order based on sales velocity; they re-order based on equipment criticality, failure rates, and lead time. A broken SKU system introduces delays precisely when they hurt most: during a corrective repair on a critical asset.

Common problems caused by poor SKU discipline in maintenance storerooms include:

  • Duplicate records for the same part under slightly different descriptions, leading to phantom stock counts.
  • Parts ordered from multiple suppliers without a consistent identifier, making spend analysis unreliable.
  • Technicians unable to locate spare parts by description alone, wasting time during a repair window.
  • No link between the SKU and the equipment it supports, making it impossible to build an accurate bill of materials per asset.

A structured SKU system eliminates these failure points. When every item in maintenance inventory carries a consistent, descriptive SKU, technicians find parts faster, planners reorder with confidence, and managers produce accurate inventory reports without manual reconciliation.

Benefits of a Good SKU System

A well-designed SKU system produces measurable improvements across several maintenance and procurement functions.

Faster Part Retrieval

When SKUs encode category and location, a technician can identify the correct bin from a work order without walking the entire storeroom. This reduces repair time and increases wrench time on planned jobs.

Accurate Reorder Triggers

SKUs enable reliable reorder point calculations. If every unit of a given bearing is tracked under a single SKU, the system produces an accurate on-hand count and fires a reorder alert before the last unit is consumed.

Prevention of Stockouts

A stockout on a critical spare forces unplanned downtime or emergency procurement at a premium. A clean SKU system surfaces low-stock conditions in advance, allowing planners to replenish before a failure event occurs.

Improved Stock Turnover

SKU-level reporting shows which items move frequently and which sit idle. This data drives decisions on safety stock levels, supplier rationalization, and disposal of obsolete inventory, all of which improve stock turnover ratio.

Barcode and CMMS Integration

SKUs printed as barcodes allow receiving, issuing, and cycle counting to happen by scan rather than by manual entry. When paired with barcoding workflows in a CMMS, this eliminates transcription errors and creates an auditable transaction history for every inventory movement.

Common SKU Management Mistakes

Even organizations with formal SKU policies encounter recurring problems. These are the most common mistakes maintenance teams make when managing SKUs.

Allowing Free-Text Item Descriptions

When technicians or planners can create new inventory records without following a defined SKU structure, duplicates multiply. The same bearing gets added as "SKF 6205," "Bearing 6205 SKF," and "6205 Deep Groove Ball Bearing." Each becomes a separate SKU with its own stock count, breaking every downstream report.

Not Linking SKUs to Equipment

A SKU without an equipment association has no context. Maintenance planners cannot build accurate parts kits, and reliability teams cannot model failure-driven demand. Every SKU for a critical spare should link to the assets it supports.

Ignoring Unit of Measure Consistency

If lubricant is received in liters but issued in milliliters, and the SKU does not specify the unit of measure, the on-hand quantity is meaningless. Unit of measure must be standardized at SKU creation and never changed without a formal adjustment process.

Skipping Periodic Audits

SKU databases accumulate errors over time: items discontinued by suppliers, parts superseded by newer versions, and locations that changed during a storeroom reorganization. A formal cycle counting process tied to SKU classification keeps the database accurate without requiring a full annual inventory count.

Using SKUs from External Sources Without Normalization

When multiple facilities merge systems or when a new CMMS is implemented, item records are often imported from spreadsheets or legacy systems with inconsistent formatting. Importing raw data without normalizing to a standard SKU structure re-creates the duplicate problem at scale.

The Bottom Line

A Stock Keeping Unit is more than a label. It is the foundation of every reliable inventory process in a maintenance operation. When SKUs are structured consistently, linked to equipment, and maintained through regular audits, maintenance teams locate parts faster, avoid unplanned stockouts, and make better decisions about what to stock and how much to carry.

The investment in a well-designed SKU system pays off across the entire maintenance workflow, from daily parts retrieval to annual budget planning. Organizations that treat SKU design as a one-time setup task and ignore ongoing governance consistently face the same problems: phantom stock, emergency procurement, and inventory costs that are impossible to justify or reduce.

Take Control of Your Maintenance Inventory

Tractian's inventory management software connects SKUs, equipment records, and work orders in a single system, so your team always knows what is in stock, what needs to be reordered, and where every part is stored.

See How Tractian Works

Frequently Asked Questions

What is a Stock Keeping Unit (SKU)?

A Stock Keeping Unit (SKU) is an alphanumeric code assigned internally by an organization to uniquely identify a specific inventory item within their storeroom or warehouse. SKUs encode attributes such as item category, supplier, specification, and storage location, enabling accurate tracking, reordering, and auditing of stock.

How is a SKU different from a UPC or part number?

A UPC is a globally standardized barcode assigned by the manufacturer and recognized across all retailers. A part number is the manufacturer's catalog identifier for a component. A SKU is created and managed internally by your organization. Two facilities can assign different SKUs to the same physical part based on how they classify and store it. In a CMMS, all three identifiers are typically stored together for cross-reference purposes.

Why do maintenance teams need SKUs?

Maintenance teams rely on SKUs to locate parts quickly during repairs, trigger automated reorder alerts before stock runs out, and prevent duplicate purchasing of the same component under different descriptions. A structured SKU system reduces stockouts on critical spares, lowers emergency procurement costs, and provides the data foundation for accurate MRO spend analysis.

What makes a good SKU naming convention?

A good SKU convention is short (typically 8 to 14 characters), human-readable, and logically segmented so that each character group encodes a meaningful attribute such as item category, supplier code, or specification. Avoid spaces and special characters that can cause errors in CMMS or ERP systems. Once defined, the convention must be applied consistently and maintained through periodic audits to prevent duplicate records from accumulating.

Related terms