Why Magento Custom Products Have SKUs

Question

I am going to create about 300 products (not many, but enough). Most of them are customizable, so I will enter a ton of information and then collect it together. Each simple product that makes up a configuration product has its own sku, so why does a configurable product need sku?

Answer 1

SKU is a primary key that does not rely on automatically generated db indices, although when working with packages you can generate SKUs dynamically.

The main reason for this is to get the database dissatisfied and provide easy import and export of the database contents (since the elements are not identified by the automatic identifier and such that it will cause problems when importing and exporting and increasing the identifier or duplicates) / p>

So, for configurable products, you still need an SKU to identify a group of products or a series of products that can be configured as a single product. Let's say you have 3 different configurable PC servers, and you get 3 orders to determine them for the program where you need the group ID, and determine them to complete the order, it's nice to know what type of configuration client you bought.

Answer 2

, "" , SKU. entity_id ( PK), .

Answer 3

, , . , , - , - . SKU - , . . , , , . skus, , . , ?