SKU (Stock Keeping Unit)
A SKU is a unique identifier assigned to a specific product or variant within an inventory management system. Each SKU represents one distinct combination of attributes (color, size, model) and is used for inventory tracking, orders, and reporting. In StoreChart, SKUs are automatically synced across every connected store.
A SKU (Stock Keeping Unit) is a unique alphanumeric code assigned to a specific product or variant within an inventory management system.
A SKU acts as a shared language between different systems — the storefront, the warehouse, accounting, and the BI layer. A well-designed SKU encodes information such as category, color, size, and storage location.
In StoreChart, the SKU is part of the SSOT (Single Source of Truth) architecture, which ensures every inventory change is automatically reflected across all connected stores — WooCommerce, Shopify, and dedicated sales channels.
Good SKU design pays off most when a catalog grows past a few hundred products: a code like "TSH-BLU-M" (t-shirt, blue, medium) lets a warehouse worker or a report reader understand what an item is without opening the system, while a purely sequential number like "10482" requires a lookup every time. A common mistake is reusing a SKU for a redesigned or replacement product instead of issuing a new one — this corrupts historical sales and inventory reports because the system can no longer tell the old and new versions apart. When a product is sold under more than one connected store (WooCommerce, Shopify, a marketplace), keeping one shared SKU per physical variant, rather than a different code per channel, is what makes cross-channel inventory sync and reporting possible in the first place.
Inside StoreChart specifically, the SKU is the join key that ties a catalog item to its inventory count, its purchase-order history in the imports/procurement module, and its appearance across every connected sales channel — WooCommerce, a marketplace listing, or a WhatsApp catalog reply. Because that same code has to stay stable across every one of those surfaces, changing a SKU after a product has already sold is far riskier than it looks: any report, reorder point, or automation rule keyed to the old code silently stops matching, which is why the platform treats SKU edits on live products as a deliberate action rather than a casual rename.
A useful discipline is deciding a SKU naming convention before the catalog grows past a few dozen items, then documenting it somewhere the whole team can reference — retrofitting a convention onto hundreds of existing, inconsistently-named SKUs is far more painful than starting with one, even a simple one, from day one.
Related terms
Inventory management is the process of tracking, controlling, and optimizing every product held in a warehouse. It covers stock counts, purchase orders, minimum-stock thresholds, and low-stock alerts. A good inventory management system prevents both stockouts and overstock, and directly improves customer satisfaction.
Landed cost is the total cost of getting an imported product to your warehouse — including the product price, international freight, customs duties, insurance, storage, and local delivery. Calculating landed cost accurately is essential for knowing your true profitability.
Multi-tenant architecture lets a single SaaS system serve multiple separate organizations (tenants) on the same underlying infrastructure, while keeping their data completely isolated from one another. In StoreChart, tenant isolation is enforced at the database level using Row-Level Security (RLS).
Frequently asked questions
No — a SKU must be unique per distinct sellable variant. Two products sharing a SKU will corrupt inventory counts and reporting, since the system can no longer tell which physical item actually sold or shipped.
No. A barcode is a standardized, often supplier- or industry-assigned code meant for scanning at checkout, while a SKU is an internal code a business defines itself for its own inventory and reporting needs — the same product can carry both at once.
The SKU should stay assigned to that exact historical variant rather than being reused for a new product, so past orders and inventory reports remain accurate. A replacement product should get its own new SKU even if it looks similar.