A stock‑keeping unit (SKU) is a retailer’s internal identifier for a specific product, printed (or encoded) as a unique series of characters and a scannable barcode. SKUs let a business track inventory, sales, pricing, location, and other product attributes at a granular level. SKUs are created by the seller; they are not universal identifiers.
Key takeaways
– An SKU is a retailer‑specific code and barcode used to track inventory and sales. (Not the same as a universal UPC.)
– SKUs typically encode product attributes important to the seller (brand, type, size, color, location, etc.).
– SKUs enable automated inventory updates at point of sale (POS) and power analytics like sell‑through, stockouts, and reorder triggers.
– Vendors use SKUs to manage ordering, fulfillment, and to compute reorder points such as Economic Order Quantity (EOQ).
– UPCs (universal product codes) are the same across sellers; SKUs vary by seller and help internal operations.
How SKUs track inventory (the mechanics)
– Assign: Each distinct inventory item (e.g., Red T‑shirt, size M, style #123) receives an SKU.
– Label/encode: SKUs are printed on labels or encoded into barcodes/QR codes and attached to product packaging.
– Scan at POS/warehouse: When sold or moved, the SKU barcode is scanned—POS, ERP, or inventory software decrements (or moves) the SKU’s on‑hand quantity.
– Record data: Sale price, sale time, location, customer (if tracked), and stock level changes are logged against the SKU.
– Trigger actions: Low‑stock alerts, reorder recommendations, and fulfillment picks use SKU‑level data.
Why SKUs matter (important benefits)
– Accurate inventory counts and fewer stockouts: SKU‑level tracking tells you what’s selling and what’s running low.
– Faster fulfillment and reduced picking errors: Warehouse staff use SKU labels/barcodes to find and pick items reliably.
– Better pricing, promotion and assortment decisions: SKU sales history reveals best sellers, slow movers, and seasonal demand.
– Simplifies returns and warranty handling: Returns processed by SKU let you match to purchase history and warranty terms.
– Works for tangible and intangible offerings: SKUs can represent services, labor hours, warranties, or bundled offerings.
SKUs vs. UPCs — how they differ
– Purpose:
• SKU = internal, seller‑defined code for tracking inventory and operations.
• UPC = universal product identifier (12‑digit number + barcode) that identifies the product across all sellers.
– Scope:
• SKUs vary by retailer—same product can have different SKUs at different stores.
• UPCs are standardized and identical regardless of seller, so they’re used for cross‑retailer comparison and manufacturer identification.
– Format:
• UPC: usually 12 numeric digits.
• SKU: alphanumeric, length and structure up to the seller.
How to distinguish an SKU from a UPC
– Check the digits and format: UPCs are strictly numeric and 12 digits (often displayed under a barcode). SKUs commonly include letters, vary in length, and reflect merchant conventions.
– Ask the seller or check packaging: UPCs are often printed on manufacturer packaging; SKUs may be stickers added by the retailer or printed as part of a merchant’s label.
– Use barcode scanners/apps: A UPC scan will often return manufacturer and universal product data; an SKU scan will only be meaningful to the retailer’s system.
How SKUs are used in e‑commerce
– Catalog management: Sellers assign SKUs to every product variation (size, color, bundle) so listings, inventory counts, and pricing align.
– Marketplace listings: Marketplaces like Amazon allow (or require) sellers to submit their own SKUs to link inventory to listings and fulfillment services.
– Multichannel sync: SKUs let you synchronize inventory across web store, marketplaces, and brick‑and‑mortar POS so sales on one channel decrement stock for all channels.
– Fulfillment & returns: Fulfillment centers use SKUs to pick, pack, and manage returns, enabling accurate restocking and reconciliation.
– Analytics: SKU‑level sales and traffic metrics help optimize product assortment, pricing tests, and promotional planning.
Practical steps to create and manage SKUs (implementation checklist)
1. Define what constitutes a unique SKU:
• Decide product differentiators (e.g., style, color, size, pack count, bundle).
• Treat each sellable variant as its own SKU.
2. Establish a SKU naming format (consistent and parsable). Example structure:
• [Category][Brand][Style][Color][Size][Location]
• Example SKU: APP‑NIKE‑RUN001‑RED‑M‑NYC
• Shorter example: SH‑AD‑LTA‑BLK‑10 (shoe, Adidas, model LTA, black, size 10)
3. Keep rules simple and consistent:
• Use fixed‑length segments where practical; choose separators (dash or no separator).
• Avoid ambiguous characters (I, O) and special characters that some systems reject.
• Limit SKU length to what your systems and labels/scanners handle comfortably.
4. Use alphanumeric codes to increase information density without long strings.
5. Avoid embedding dynamic data (price, date) in SKUs—those change and would force reassigning SKUs.
6. Document SKU conventions in a short style guide for staff.
7. Generate barcodes from SKUs:
• Use a barcode standard compatible with your scanners (Code 128 is common for alphanumeric SKUs).
• Print labels that include both barcode and human‑readable SKU.
8. Load SKUs into your inventory/ERP/POS and test scanning in all environments.
9. Train staff on SKU use: receiving, putaway, picking, returns.
SKU naming best practices (do’s and don’ts)
Do:
– Keep SKUs readable to humans (use meaningful codes).
– Reserve specific segments for fixed attributes (e.g., first 3 chars = category).
– Use leading zeros consistently if you rely on fixed widths.
– Centralize SKU creation to avoid duplicates.
Don’t:
– Don’t use product price, supplier invoice number, or dates inside SKU.
– Don’t change SKUs arbitrarily—if you must change, map old → new for historical data.
– Don’t make SKUs longer than necessary—long strings increase label errors.
Practical examples of SKU patterns
– Apparel: APP‑TSH‑NIKE‑BLK‑L
– Electronics: ELC‑LAP‑DL‑XPS13‑8GB
– Grocery: FOD‑DRK‑COKE‑12PK
– Service/warranty: SRV‑OILCHG‑LAB‑1HR
Implementing SKUs in POS & e‑commerce platforms (step‑by‑step)
1. Decide on SKU format and document rules.
2. Bulk‑generate SKUs for existing catalog (use spreadsheet formulas or inventory tool).
3. Import SKUs into POS/ecommerce platform (Shopify, Magento, Amazon Seller Central, etc.).
4. Print and affix barcode labels for existing stock or use manufacturer labels mapped to SKUs.
5. Test scanning at POS and in the warehouse; verify inventory decrements correctly.
6. Integrate inventory across channels with middleware or unified inventory management software.
7. Monitor for mismatches and reconcile weekly until reliable.
How SKUs relate to Economic Order Quantity (EOQ)
– EOQ is the inventory model that calculates the optimal order size to minimize total inventory cost (ordering + holding).
– Retailers often compute EOQ at the SKU level so each item’s reorder policy matches its demand profile.
– EOQ formula (classical): EOQ = sqrt((2 * D * S) / H)
• D = annual demand (units)
• S = ordering cost per order (setup/transaction cost)
• H = holding cost per unit per year (storage, capital cost)
– Practical steps to use EOQ with SKUs:
1. Pull SKU historical demand (annualized).
2. Estimate ordering cost and per‑unit holding cost for that SKU.
3. Compute EOQ and round to practical order multiples (case packs).
4. Set reorder point = lead time demand + safety stock (based on variability).
5. Monitor and adjust EOQ as demand, cost, or lead times change.
– Example: If D=2,400 units/year, S=$50/order, H=$4/unit/year:
• EOQ = sqrt((2 * 2400 * 50) / 4) = sqrt(240,000 / 4) = sqrt(60,000) ≈ 245 units.
Inventory analytics and KPIs to monitor per SKU
– On‑hand quantity and days of inventory (DOI)
– Sell‑through rate (units sold / units received)
– Gross margin per SKU and margin % (helps rationalize assortment)
– Stockouts and backorder frequency
– Turnover rate (cost of goods sold / average inventory)
– Days‑to‑replenish (lead time + processing)
– Shrinkage / returns rate
Practical tips for scaling SKU systems
– Automate SKU creation using SKU‑generation logic in your catalog management tool to avoid duplicates.
– Use barcoded bin locations and include location code in SKU or inventory records for quick picking.
– Archive but don’t delete old SKUs—keep them for historical sales and accounting reconciliation.
– Use SKU analytics to identify slow movers for markdowns, bundling, or delisting.
– Consider inventory management software or WMS if you have hundreds to thousands of SKUs.
The bottom line
SKUs are a simple but powerful tool for tracking and managing inventory at the unit level. They are seller‑specific, flexible, and essential for accurate POS operations, e‑commerce sync, and inventory optimization (including EOQ calculations). A consistent, well‑documented SKU strategy—combined with barcode labeling and an integrated system—reduces stockouts, speeds fulfillment, and provides the data you need to improve purchasing and merchandising decisions.
Sources
– “Stock‑Keeping Unit (SKU)” — Investopedia (Theresa Chiechi).
– Industry best practices for SKU formatting, barcode use, and EOQ (standard inventory management references)
Editor’s note: The following topics are reserved for upcoming updates and will be expanded with detailed examples and datasets.