Mastering Fresh E‑Commerce Product Management: From Category Trees to SKU Strategies

Explanation: In a Java fresh e‑commerce platform, the product architecture largely determines scalability and extensibility. Based on years of fresh‑food e‑commerce experience, a mind map of the product center is presented.

For newcomers to fresh e‑commerce, the concept of a basic category is similar to classifying a product as a phone, tablet, or laptop; it defines what the product is. Different basic categories describe different feature sets.

For example, a phone category includes front‑camera megapixels, rear‑camera megapixels, screen size, network type, etc.; a pants category includes waist size, length, material, thickness, etc. In e‑commerce, these features are called attributes. When maintaining a category, you select its attributes, and when adding a product you first choose its basic category, which then displays the relevant attributes for the operator to fill.

A platform has a single basic category tree; each product belongs to exactly one node on that tree. Category management includes adding/editing/deleting nodes, sorting nodes, and maintaining node attributes.

Each platform provides a default basic category tree. Selecting a node (e.g., "Casual Snacks") opens a detail tab with name, description, and a flag indicating whether it is a minimal category. A minimal category means the classification has reached the smallest granularity needed for operations and should not be further subdivided.

Non‑minimal nodes have additional tabs for adding sub‑categories and sorting sub‑categories.

The "Category Attributes" tab defines which attributes belong to the current category. Concepts such as attribute library, attribute groups, and default attribute groups are introduced.

Adding an attribute requires selecting it from a pre‑maintained attribute library. Deleting an attribute is only allowed if the category has no products; otherwise the attribute is moved to a default attribute group.

Brand management maintains a shared brand library to avoid duplicate brand names and to enable brand‑based operations. It includes brand search, addition/editing, and deletion.

Product management covers product query, addition/editing, deletion, and status control. Product status flows through stages: New, Pending Review, Pending Publish, Review Failed, and Unpublished.

When adding a product, the entry point is the product query page or product detail page. The first step defines product type (regular or virtual), warehouse type (domestic, direct‑mail, bonded), and the basic category, which determines the subsequent information and order processing flow.

All six tabs must be completed: basic info, images, description, category attributes, inventory & shipping, and pricing.

Pricing tab sets prices for different platforms and user groups (e.g., lower price on app to attract mobile users, member‑specific pricing).

Series products (e.g., same clothing item in S/M/L or different colors) are managed as separate SKUs with shared attributes, allowing aggregation on the front end.

Combo products (bundling two SKUs) can be implemented as a real SKU (complex inventory handling) or a virtual SKU (simple price rule). The virtual approach is recommended for ease of inventory and order processing.

Front‑end categories differ from basic categories: they are consumer‑facing groupings (e.g., "Dual‑camera Phones" or "Best‑selling Flagships") and a product can belong to multiple front‑end categories. Management of front‑end category trees follows similar CRUD principles, and products are linked to front‑end categories via selection based on basic category, brand, and SKU.

Why restrict series product categories and brands? To maintain consistency and simplify aggregation.

Combo products can be real or virtual; virtual is usually preferred for simplicity.

Front‑end categories align with consumer perception and can exist in multiple trees (PC, H5, APP).

Linking products to front‑end categories is essentially a selection operation based on basic category, brand, and SKU.

In summary, the product management module of a B2C fresh e‑commerce platform involves building a well‑structured basic category tree, maintaining attribute and brand libraries, controlling product lifecycle, handling SKUs, series and combo products, and aligning front‑end classifications with consumer expectations.

Source: https://www.cnblogs.com/jurendage/p/12550404.html