A stock keeping unit (SKU) is a unique alphanumeric code that a retailer assigns to each distinct product or product variation in their catalog. Unlike a Universal Product Code (UPC), which is assigned by the manufacturer and shared across retailers, a SKU is created internally, meaning two stores can sell the same item with completely different SKU codes. The code itself typically encodes key product attributes like category, brand, size, or color, making it human-readable at a glance. In a multi-location retail or [[quick-service restaurant]] environment, SKUs serve as the unique identifier between physical inventory, pricing databases, [[Point-of-Sale systems]], and any connected device that displays or processes product information, including [[digital signage]], self-checkout [[kiosks]], and electronic shelf labels.

Goal of Stock Keeping Units

The primary goal of a SKU system is to give operators precise, granular visibility into what they have in stock, where it is, and how it's moving. By assigning a unique identifier to every product variation, retailers can track sales patterns, manage reorder timing, prevent stockouts, and keep pricing consistent across channels, doing this without relying on manual counts or generalized product categories.

Key Functions

• Inventory tracking: Identify exactly how many units of each product variation are on hand, on order, or sold across locations
• Pricing and promotion management: Tie specific price points, discounts, or promotional rules to individual SKUs so changes push accurately to checkout and shelf displays
• Sales analysis: Break down performance by product attribute (e.g. size, color, flavor, format) to inform purchasing and merchandising decisions
• Order fulfillment: Route the correct item variation through pick, pack, and ship workflows by referencing SKU codes rather than product names
• Omnichannel synchronization: Keep in-store, online, and app inventory counts aligned so customers and staff see accurate availability regardless of channel

Challenges

• SKU proliferation: As product assortments expand, the number of active SKUs can grow unwieldy, making it harder to identify slow-moving inventory or rationalize the catalog
• Inconsistent naming conventions: Without standardized SKU structures across systems or locations, duplicate or conflicting codes create inventory discrepancies
• Device dependency: SKU data is only as accurate as the devices that read, display, and process it. A [[Point-of-Sale system]] outage or a misconfigured electronic shelf label can surface incorrect prices or stock levels tied to the wrong SKU
• Multi-location complexity: Keeping SKU data synchronized across dozens or hundreds of locations requires reliable connectivity and consistent system configuration at every site

Canopy's Role

SKU accuracy is affects remote device reliability. In a retail or c-store environment, the devices responsible for displaying, scanning, and processing SKU data ([[Point-of-Sale systems]], [[kiosks]], electronic shelf labels, and self-checkout terminals) need to be online, correctly configured, and running current software for SKU data to flow correctly. Canopy's [[remote monitoring and management]] platform gives multi-location operators visibility into the health and [[uptime]] of every device in their fleet, so that a downed terminal or misconfigured display doesn't quietly create SKU-level pricing errors across a store.