Designing a Basic Product Model for E‑commerce Systems

In e‑commerce systems the product model is a core component; this article walks through a simple analysis and design of a foundational product model.

Initially, many sites inherited a CMS‑style category‑article structure, treating categories as product classifications and articles as products, which later proved insufficient when brand information needed to be added.

To meet user expectations for browsing by brand or category and for refined filtering, a UI with multiple filter criteria was introduced, prompting a shift to an attribute‑based design where each category can have its own set of attributes and options.

The relationship is illustrated as: a category maps to several attributes, each attribute maps to multiple attribute options, and a concrete product maps to specific attribute options (e.g., a pair of jeans with a 7‑point length and straight cut). Price is also treated as an attribute rather than a simple field.

Further analysis distinguishes between “product” and “SKU” (stock‑keeping unit): different specifications such as color, size, or storage capacity represent separate SKUs under a single product, with specifications handled as attribute options.

With this model, basic product search, display, and indexing requirements are satisfied, and the product module can be isolated as a “product center” service that handles queries, updates, and publishing while collaborating with user, order, and payment systems.