Product attribute management in e-commerce system_PHP tutorial

Commodity is the same as content in CMS. It is something with uncertain specific attributes. Different types of commodities have different attributes and specifications, and the rules can also affect the price. From this point of view, it is better than CMS The content is a bit more complicated.

For program developers, a relatively good model system needs to be designed to meet this demand.

Comparing ECShop, iWebShop, YunCart, PrestaShop, zencart and other systems, we found that each has its own advantages and disadvantages, which need to be combined and weighed accordingly.

The product model system is mainly divided into two parts:

Attribute system

Corresponds to the model function in CMS

Allow users to fully customize various attributes of various products according to their needs, and set whether they can be retrieved on the front end

Specification system

Specifications belong to a certain product model. After being defined in the model, when the operator adds and edits products, based on the selected model, the system automatically generates a price, inventory, etc. setting interface that is arranged and combined by various rules

The entire system is relatively well designed and may involve more than 10 tables.

How to construct a filterable interface for front-end products also requires a relationship; at the same time, how to construct and pass filtering parameters is also a problem.

Relatively speaking, the latter one is more in line with technical logic, and has stronger retrieval performance, security, and flexibility.