Mastering E‑Commerce Product Management: From SPU & SKU to Full Lifecycle
This comprehensive guide explains the core concepts of e‑commerce product systems—including SPU and SKU definitions, their relationships, and the complete product management workflow covering publishing, editing, inventory, payment, logistics, and status transitions—providing essential knowledge for building robust online retail platforms.
What Is a Product System
Product management systems are the most fundamental and core component of e‑commerce platforms, supporting the entire product lifecycle from procurement and warehousing to listing, ordering, delivery, receipt, and after‑sales service.
SPU and SKU
SPU (Standard Product Unit) is the smallest unit of standardized product information, representing a group of items with identical attributes; for example, "Apple iPhone X" defines an SPU. SKU (Stock Keeping Unit) is the inventory unit, each with a unique code, representing a specific product variant such as "Apple iPhone X 12G Black".
Typically an SPU contains multiple SKUs, and a product is the physical realization of a SKU. In some rare cases a SKU may map to multiple SPUs.
Product Management
Backend product systems consist of category management, attribute libraries, brand management, and product management functions such as publishing, editing, up/down, auditing, pricing, inventory, and freight template settings.
Publishing (Adding) Products
Before creating a product, select the appropriate category to inherit attribute templates, then use key and sales attributes to associate SPU and SKU. Platforms like JD.com manage products by SKU, while Taobao and Tmall use SPU.
Published products undergo an audit process to ensure compliance before they can be listed.
Product Information Components
Basic information (category, title, brand, code, attributes, slogans)
Attributes (key, sales, product, ordinary, and custom types)
Image and text description
Inventory settings (price and stock per SKU, sync with WMS)
Payment information (pricing models, payment methods, inventory deduction rules)
Logistics information (freight templates)
After‑sales service (return policies, guarantees)
Product Up/Down
Products can be in "on‑sale" or "off‑sale" states, with options for automatic or scheduled transitions. Reasons for down‑shelf include violations, brand expiration, store migration, or category changes.
Product Editing
Editing modifies existing product data and may trigger the same audit flow as publishing.
Product Deletion
Only products not currently on sale can be deleted; active listings must be taken off‑sale first.
Setting Freight Templates
Freight templates are configured in the logistics system and applied during product publishing; pricing can be based on quantity, weight, or volume.
Product Status Flow
Products move through eight states: New, Pending Review, Approved, Rejected, Listed, Delisted, Invalid, and Valid Pending Review. A flow diagram illustrates these transitions.
Conclusion
A well‑designed product management system forms the foundation of an e‑commerce platform; careful planning of each module’s extensibility and low coupling is essential to avoid costly re‑engineering as the business scales.
Dual-Track Product Journal
Day-time e-commerce product manager, night-time game-mechanics analyst. I offer practical e-commerce pitfall-avoidance guides and dissect how games drain your wallet. A cross-domain perspective that reveals the other side of product design.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.