What Is a SKU? Meaning, Examples, and How to Build SKU Codes That Work With a 3PL
.webp)
A SKU (stock keeping unit) is an alphanumeric code a business creates to identify each distinct product it stocks, down to the variant: every size, color, and pack size gets its own SKU. SKUs are internal, so two retailers selling the same item will each use a different SKU, while the item's UPC or GTIN stays the same everywhere.
This guide covers what a SKU is and isn't, how it differs from a UPC, how to build a SKU format that holds up as your catalog grows, and what your 3PL needs from your SKUs to receive, pick, and count inventory accurately.
Updated October 8, 2026: added a GS1-sourced SKU vs. UPC/GTIN comparison, a SKU format template, and 3PL-specific requirements; removed repetitive keyword phrasing.
What does SKU mean?
SKU stands for stock keeping unit. GS1 US, the organization that issues UPC barcodes, describes a SKU as "a flexible code you create yourself to track your own inventory" (GS1 US). Because you define it, a SKU can encode whatever helps your team: product line, style, color, size, or pack count.
Example: TEE-CRW-BLK-M could mean a crew-neck tee, black, size medium. The medium and large versions of that shirt are different SKUs because they are counted, stored, and sold separately.
What is the difference between a SKU and a UPC?
| SKU | UPC / GTIN | |
|---|---|---|
| Who creates it | Your business | Issued through GS1 using your company prefix |
| Scope | Internal to one business; another retailer uses its own SKU for the same item | Global; the same item carries the same number everywhere |
| Format | Any letters and numbers you choose | Fixed length; UPC-A encodes a 12-digit GTIN-12 |
| Variants | One SKU per variant you stock | Each distinct size, flavor, or package needs its own GTIN |
| Main use | Inventory, purchasing, reporting, warehouse picking | Point-of-sale scanning, retail and marketplace listings |
Sources: GS1 US UPC guide; GS1 US GTIN overview. For a deeper comparison and setup steps, see UPC vs. SKU and what a UPC is and how to get one.
How do you create a SKU code?
Pick a structure once and apply it to every product. A common pattern moves from general to specific:
| Segment | Example | Notes |
|---|---|---|
| Category or product line | TEE | 2-4 letters |
| Style or model | CRW | Distinguishes products within the line |
| Attribute 1 (color, flavor, scent) | BLK | Use a fixed code list so BLK always means black |
| Attribute 2 (size, pack count) | M | Put size last so variants sort together |
Rules that prevent problems later:
- One SKU per stocked variant. If it's counted separately, it needs its own SKU.
- Don't start with zero. Spreadsheets drop leading zeros, which silently breaks imports.
- Use letters and numbers only. Spaces and symbols such as / # & can break integrations; hyphens are usually safe, but confirm with your systems.
- Avoid look-alike characters such as O and 0 or I and 1 in positions where both could appear.
- Keep SKUs short enough to read on a pick screen; most teams stay under about 12-15 characters.
- Never reuse a retired SKU for a different product. Historical sales and inventory records will merge.
- Give bundles and kits their own SKU and map them to their component SKUs, so your systems can deduct the right inventory.
Why do SKUs matter when you work with a 3PL?
A 3PL counts, stores, and picks by SKU, so your SKU list becomes the backbone of every inventory report you get. Problems that start as SKU mistakes show up as fulfillment errors:
- Receiving: the SKUs on your advance shipping notice must match what's in the cartons. Mismatches cause receiving discrepancies and delay stock going live; see how 3PL receiving works.
- Scannable barcodes: each SKU needs a barcode the warehouse can scan, usually its UPC. Cases are often identified with a GTIN-14, which GS1 notes is meant for groupings like cases rather than point-of-sale scanning; see case packs and master cartons.
- Look-alike variants: scan verification at pack-out catches a size M shipped as size L, but only if each variant has its own SKU and barcode.
- Lot and expiry tracking: for supplements, beauty, and food, lots are tracked under the SKU; see lot tracking.
- Reporting: clean SKUs make ABC analysis and cycle counts trustworthy.
Atomix connects to your store and marketplaces through 100+ integrations, so SKUs sync from your sales channels instead of being re-keyed. If your catalog has grown messy, this SKU management guide covers cleanup.
Frequently Asked Questions
What does SKU stand for?
SKU stands for stock keeping unit. It is an alphanumeric code a business creates to identify each distinct product it stocks, including each size, color, or pack variant, so inventory can be counted, stored, and reported accurately.
Is a SKU the same as a UPC?
No. A SKU is an internal code each business creates, so two retailers selling the same item use different SKUs. A UPC encodes a GTIN issued through GS1 and identifies the same product globally. Most brands assign both to every sellable variant.
How many characters should a SKU have?
There is no required length. Most teams keep SKUs short enough to read on a pick screen, roughly under 12-15 characters, use only letters and numbers (plus hyphens if their systems allow), and avoid starting with a zero.
Do product variants need separate SKUs?
Yes. Any variant you stock and count separately, such as each size, color, flavor, or pack count, needs its own SKU. GS1 also requires a separate GTIN for each distinct option such as a different size or flavor.
What SKU information does a 3PL need?
A 3PL needs a complete SKU list with product names, a scannable barcode for each SKU, case-pack quantities, dimensions and weights, and any lot or expiry requirements. The SKUs on each advance shipping notice must match the cartons sent.
.svg)
.svg)
.svg)
