Designing an E‑Commerce Product Center: Key Concepts, Architecture & Features

This article explains the essential concepts, functional architecture, and detailed design of an e‑commerce product center, covering SPU/SKU definitions, front‑ and back‑end categories, attribute types, CRUD operations, and specific features such as product publishing, review, unpublishing, editing, and category management.

ITFLY8 Architecture Home
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Designing an E‑Commerce Product Center: Key Concepts, Architecture & Features

In e‑commerce companies, the product center is the backend hub for managing product data, orders, and marketing activities, while on the frontend it displays product information to users. It supports the entire product lifecycle from upload to delivery and returns, making it indispensable.

1. Basic Concepts

Before designing a product center, it is important to understand common e‑commerce terminology.

(1) SPU : Standard Product Unit, a collection of standardized information; for example, "iPhone 8" is an SPU.

SPU illustration
SPU illustration

(2) SKU : Stock Keeping Unit, the smallest unit for inventory control; for example, "iPhone 8 Plus 256G Gold" is a SKU.

SKU illustration
SKU illustration

(3) Front‑end Category (Classification) : Created to help users filter and find products; operators can adjust these categories flexibly, and the front‑end categories map to back‑end categories for product retrieval.

Front‑end category illustration
Front‑end category illustration

(4) Back‑end Category : Used by operators to manage inventory, SKUs, and product specifications; it maps to front‑end categories and is rarely changed.

Back‑end category illustration
Back‑end category illustration

(5) Attributes : A set of values describing a product. They are divided into key attributes (uniquely identify a product, e.g., screen size, model), sales attributes (used to form SKUs, e.g., color, memory), and non‑key attributes (optional, e.g., interface type).

2. Functional Architecture

After understanding the basic terminology, the product center’s core backend functions can be grouped into four CRUD operations: create, read, update, delete. Use‑case diagrams illustrate the needs of operators, and an information‑architecture diagram shows the overall structure.

Use‑case diagram
Use‑case diagram
Information architecture diagram
Information architecture diagram

3. Functional Design

Based on collected business requirements, each function is designed as follows:

3.1 Publish Product

Publishing allows operators to enter product data into the platform. After approval, the product becomes visible on the front‑end. Some platforms require a separate “list” step after approval before the product appears to users.

Publish product flow
Publish product flow

3.2 Product Review

The review function ensures product quality and compliance. It includes pre‑submission review and post‑listing review, though the latter is less common. Review results are either "approved" or "rejected"; rejected items must provide reasons for correction.

Product review interface
Product review interface

3.3 Product Unpublish (Down)

Unpublishing removes a product from the sale list. If the platform takes down a merchant’s product, a reason must be recorded, and appropriate permissions are required for such actions.

3.4 Product Edit

Edit functionality provides quick access to frequently used changes such as price or sort order, improving operational efficiency.

3.5 Category Management

Operators can add, modify, move, delete, and view categories. The example below shows front‑end category management; note that categories cannot be deleted or moved while they contain products, to avoid affecting front‑end display.

Category management UI
Category management UI
Category prototype example
Category prototype example
e-commercebackend designSPUskucategory managementproduct center
ITFLY8 Architecture Home
Written by

ITFLY8 Architecture Home

ITFLY8 Architecture Home - focused on architecture knowledge sharing and exchange, covering project management and product design. Includes large-scale distributed website architecture (high performance, high availability, caching, message queues...), design patterns, architecture patterns, big data, project management (SCRUM, PMP, Prince2), product design, and more.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.