One-line definition: A SKU (Stock Keeping Unit) is a unique code assigned to a specific product variant in your inventory - used to track, identify, and manage stock accurately across your store, warehouse, and shipping operation.
What it means
SKU stands for Stock Keeping Unit. It is a unique identifier — typically a short alphanumeric code — that you assign to each distinct product or product variant in your inventory. Every time a product differs in a way that requires it to be tracked separately — different size, different colour, different bundle configuration — it gets its own SKU.
A blue t-shirt in size small and a blue t-shirt in size medium are two different SKUs. The same t-shirt in blue and in green are two different SKUs. A product sold individually and the same product sold in a pack of three are two different SKUs. The rule is simple: if it is stored, picked, or shipped differently, it needs its own SKU.
SKUs are assigned by the merchant — they are internal codes, not universal identifiers. Unlike barcodes or GTINs (Global Trade Item Numbers), which follow international standards and are shared across the supply chain, a SKU is specific to your business. Your SKU for a product will not match your supplier's code for the same product or a retailer's code for the same item.
Why it matters for e-commerce merchants
SKUs are the operational backbone of inventory management. Without unique SKUs for every variant, tracking what you have, where it is, and how fast it is moving becomes unreliable — which leads to overselling, stock discrepancies, picking errors, and fulfillment delays.
The practical impact shows up in three areas:
Inventory accuracy. If two variants share a SKU — or if no SKU system exists at all — your inventory counts will be wrong. You will not know whether you have twelve blue small t-shirts or twelve blue t-shirts of mixed sizes. Fulfillment operatives will pick the wrong variant. Reorder decisions will be based on inaccurate data.
Picking speed and accuracy. In a warehouse, the SKU on the pick list and the SKU on the product's storage location are what guide an operative to the right item. A clear, consistent SKU system reduces the cognitive load on picking — the operative matches a code, not a product description — and makes barcode scanning verification possible.
Reporting and analysis. SKUs are the grain at which you can analyse sales velocity, return rates, and profitability by variant. Knowing that your blue medium t-shirt sells three times faster than your green large, or that one variant generates disproportionate returns, requires SKU-level data. Without it, product decisions are based on aggregate patterns that obscure variant-level performance.
How to structure a good SKU
There is no single correct SKU format, but some approaches are significantly more practical than others.
Keep it short. SKUs that are 6 to 12 characters are easier to read, type, and scan accurately than 20-character codes. Shorter codes also fit more comfortably in label fields and system interfaces.
Make it human-readable. A SKU like TS-BLU-M (t-shirt, blue, medium) is immediately interpretable by a warehouse operative without looking it up. A SKU like 00423819 contains the same uniqueness but requires a lookup to understand what it refers to. Human-readable SKUs reduce errors in manual processes.
Use a consistent structure. Decide on your format — product category, then colour, then size, for example — and apply it consistently across all products. Inconsistent structures create confusion as your product range grows.
Avoid special characters. Hyphens are generally fine. Spaces, slashes, and other special characters can cause problems in some warehouse management systems, CSV imports, and carrier integrations. Stick to letters, numbers, and hyphens.
Don't reuse SKUs. When a product is discontinued, retire its SKU rather than reassigning it to a new product. Historical order data is linked to SKUs — reusing codes corrupts that history.
A simple structure example for a clothing store:
| Product | Variant | SKU |
|---|---|---|
| Classic Tee | Blue / Small | CT-BLU-S |
| Classic Tee | Blue / Medium | CT-BLU-M |
| Classic Tee | Green / Small | CT-GRN-S |
| Hoodie | Navy / Large | HD-NVY-L |
SKU vs barcode vs GTIN — what's the difference
These three identifiers are often confused because they all relate to product identification — but they serve different purposes.
SKU — your internal code, assigned by you, used within your own systems. Not shared externally.
Barcode — a visual representation of a number, scannable by a barcode reader. The barcode encodes a number — which may be your SKU, a GTIN, or both. The barcode itself is a display format, not an identifier system.
GTIN (Global Trade Item Number) — a standardized, internationally recognized product identifier used in supply chains, retail, and marketplaces. Includes EAN-13 (the standard European barcode number) and UPC-A (the US equivalent). GTINs are required by some marketplaces (Amazon, Google Shopping) and are used in B2B supply chain transactions. Unlike SKUs, GTINs are globally unique — the same product has the same GTIN wherever it is sold.
For most Shopify merchants, SKUs are sufficient for internal operations. GTINs become relevant when selling on marketplaces that require them, or when supplying goods to retailers who use them in their purchase order systems.
Common misconceptions and mistakes
"SKUs are only necessary for large product ranges." Even a ten-product store benefits from SKUs — they make inventory counts faster, picking more accurate, and reporting cleaner. The overhead of assigning SKUs is minimal; the benefit starts from the first product.
"My Shopify product ID is my SKU." Shopify assigns its own internal product and variant IDs automatically. These are system identifiers used by Shopify internally — they are not the same as SKUs, which you define and which carry meaning about the product. Always set explicit SKUs in Shopify for each variant rather than relying on system-generated IDs.
"I can add SKUs later when my store grows." Retrofitting SKUs onto an existing product range — especially one with many variants — is time-consuming and error-prone. Building a SKU system from the start is significantly easier than applying one to an established inventory with historical order data already attached to unnamed variants.
"The SKU on my product label and in my Shopify store can be different." They should not be. When the SKU on the physical item, the SKU in Shopify, and the SKU on the pick list all match, scanning verification works reliably and errors are caught. When they diverge, the scan-verify step breaks down and manual matching is required.
How this connects to your Shopify store
In Shopify, SKUs are set per variant in the product editor — each size, color, or configuration of a product can have its own unique SKU. These SKUs flow through to Shopify orders, pick lists, and packing slips, and are the identifier used in Packrooster's scan-to-fulfill workflow.
When an operative scans a product barcode during packing to verify the correct item is being shipped, Packrooster matches the scan against the SKU on the order. If the scanned SKU matches what Shopify says should be in the parcel, the item is confirmed. If it does not match — the wrong size, the wrong product — the scan fails and the operative is alerted before the wrong item is sealed in the box.
This scan-to-verify step is only as reliable as the SKU data underlying it. A store with accurate, consistently structured SKUs gets the full error-prevention benefit of barcode verification. A store with missing, duplicated, or inconsistent SKUs will encounter scan mismatches that reduce confidence in the verification step and may lead operatives to bypass it.
For merchants managing multiple products, variants, and storage locations, SKU accuracy is foundational — it is the data layer on which picking accuracy, inventory visibility, and fulfillment automation all depend.
Learn more about Packrooster →
Frequently asked questions
How many SKUs can Shopify handle? Shopify supports up to 100 variants per product and has no published hard limit on total SKUs across a store. For stores with very large product ranges — thousands of SKUs — performance and management complexity are practical considerations, but the platform itself handles large SKU counts well. Shopify's inventory management, reporting, and order management all operate at the SKU level regardless of range size.
What is a parent SKU and a child SKU? Some inventory systems use a parent-child SKU structure where a parent SKU represents the base product (the Classic Tee) and child SKUs represent the individual variants (CT-BLU-S, CT-BLU-M, CT-GRN-S). Shopify uses a similar concept natively — a product (parent) with variants (children), each with their own SKU. This structure is useful for reporting at the product level while tracking inventory at the variant level.
Should my SKU match my supplier's product code? Not necessarily. Your supplier's product code and your internal SKU can differ — they serve different purposes in different systems. What matters is that you have a consistent mapping between the two. When a purchase order references your supplier's code and your goods receipt uses your SKU, the mapping between them needs to be reliable. Many merchants include the supplier code as a separate field in their inventory system rather than making it the SKU itself.
How do I handle SKUs for bundled products? A bundle — two or more products sold together as a single unit — should have its own SKU distinct from the individual component SKUs. When a bundle order is picked, the pick list should reference the component SKUs so the operative knows which individual items to include, while the order and the shipping label reference the bundle SKU. Shopify handles simple bundles natively; more complex bundle configurations may require a dedicated bundle app.
What should I do if I have duplicate SKUs in my store? Identify and resolve them as soon as possible. Duplicate SKUs cause inventory inaccuracies, picking errors, and reporting problems. In Shopify, a SKU uniqueness check can be run through the product export — download your product CSV and check for SKU duplicates. Once identified, assign new unique SKUs to the affected variants and update your physical labels and warehouse location references to match.
