The system modules involved in commodity circulation have been introduced earlier, and the management of suppliers and contracts has been summarized, so this article continues to write about commodity management modules.
The summary and introduction of the commodity management system can be searched for a lot on the Internet. It is also combined with the systems that have been contacted, and some materials are used for reference. It is sorted out according to personal understanding. I hope to form a complete series of articles on the supply chain according to the plan. The purpose is to By sorting out and summarizing the content that I was originally ignorant of, I hope that people who have the chance to read this article will give suggestions and learn and progress together.
There is a bright moon in my heart, and there will be no shortage of reunion throughout the ages. The mountains, rivers and the earth are full of brilliance, so why not enjoy the Mid-Autumn Festival.
1. SPU and SKU
This is a cliché, but let's review these two concepts.
- SPU : Standard Product Unit, which is the smallest unit of commodity information aggregation, is a collection of reusable standardized information. In my understanding, it is mainly for the purpose of front-end display;
- SKU : The smallest stock keeping unit (StockKeeping Unit), which can be stored in units of pieces, boxes, boxes, kilograms, etc. The purchase, sales, price, and inventory of goods are ultimately based on SKU.
A SPU can contain multiple SKUs, and SKUs are generally combined according to the sales attributes of the SPU (Cartesian product);
For example, Huawei Mate30 mobile phone is a product, but it has three colors: white, gold, and black. According to the specifications and attributes, there are 64G, 128G, and 256G storage. At this time, a total of 9 SKUs (3 colors * 3 types) will be generated. memory specifications).
Some e-commerce systems do not have SPUs, but only SKUs. The purpose of this is to increase the exposure of products and allow users to see their products more directly. The disadvantage is that products such as clothing and shoes are also available in different sizes. Display, make the user look uncomfortable (it feels like the same product is all over the screen);
How to enable the SPU can be designed according to the actual scene. The following figure is a simple association of spu, sku, classification and attributes.
2. Composition of commodity management system
The commodity system generally contains the above-mentioned parts of information, and completes the turnover in the entire supply chain system through the change of commodity status; all operations in the e-commerce system are carried out around the commodity or serve the commodity. pass.
Commodity search and commodities are closely related, but are generally established and deployed separately through commodity information and commodity attribute setting keywords, and are more closely related to the front-end system, so I won't introduce them too much here.
1. Classification management
Commodity classification is a very important part of the system, it is divided into front-end classification and back-end classification.
Back-end classification is the foundation, and the invoicing business is closely related to classification. From commodity purchase to commodity inventory, to commodity sales, and finally to financial accounting, many of them are carried out in the dimension of back-end classification; at the same time, many attributes of commodities are carried out. Information is also based on commodity classifications.
Front-end classification is established for front-end sales. It is based on back-end classification. It is a set of classifications established to effectively display products on the front end, and users can quickly search and find products.
Some systems only have one set of classifications. Although the business can be carried out normally, it may be extremely inconvenient for the website operators. The current e-commerce websites are separated from the front-end and back-end classifications. The front-end classification is responsible for the user experience of product display. , the back-end classification is built for internal ERP systems.
The front-end classification and the back-end classification level are currently the most common to establish three levels, classification content: classification ID, classification name and classification code.
Front-end and back-end classification association constraints:
- A front-end category can be associated with multiple back-end primary, secondary and tertiary categories;
- Backstage categories can only be associated with front-end three-level categories;
- A backend category can only be associated with one frontend category.
For functions such as classification maintenance, a tree-like hierarchy can be used, or a three-level connection method can be used (the prototype is omitted and everyone understands).
This part of the work is to first build the back-end classification, then build the front-end classification, and then set the classification mapping relationship (specifically, the rules can be set according to the actual business)
2. Classification adjustment
Front-end classification involves the display and search of products, mainly to deal with frequent changes, so there will be frequent adjustments to achieve a better user experience, and also to reduce the impact of the front-end on the back-end system classification.
It is not recommended to adjust the back-end classification from the perspective of supply chain and finance. However, due to the company's organizational adjustment and the adjustment of relevant national tax laws, it is inevitable to adjust the classification. The adjustment content is divided into two parts:
(1) The attribution of classification is adjusted. The three-level classification "Luzhou-flavored" originally under "Wine -> Liquor" is adjusted to "Wine -> Yellow Wine".
This adjustment has no effect on SKU and SPU , but will have a display effect on related statistical reports (if no redundant classification information is recorded in historical data).
(2) Changes in important information in classification, such as changes in tax rates; the old classification system is not suitable for newly established classifications. At this time, all commodities must adopt a new classification structure, and the front-end classification should also be adjusted. This part has a very large impact on the system, involving historical data and the current system (front-end and back-end).
Countermeasures:
- Add necessary redundant fields during system design to cope with the impact of classification adjustments on historical data (business documents, statistical reports);
- Add snapshot information, that is, there are snapshot tables of classified data every month, and related business documents, reports, etc. are associated with their own snapshot tables, which makes the program logic more complicated and is not recommended.
3. Property management
Commodity attributes are also basic information, generally divided into basic attributes, key attributes and sales attributes.
Each product attribute corresponds to a different attribute value, such as the attribute "size", it has attribute values such as "S, M, L, XL, XXL".
For this part, I also found some information. Personally, in terms of system design, two tables can be established for attributes, namely " commodity attributes " and " attribute item " dictionary tables (if the ER diagram is drawn, their relationship is one-to-many) .
We also need to clarify whether the product attributes are based on SPU, SKU, or classification? In the relationship I listed in the figure above, categories, products and commodities have attributes, which are easy to mislead, and explain them here.
- "Commodity attributes" and "attribute items" are dictionary information, that is, basic information. This information is not isolated when it is created. It can only be created after selecting the "three-level classification" of the background classification;
- When the SPU is created, it is also necessary to select the product classification (backstage classification), so all the product attributes of the SPU are determined at this time; each product attribute has an attribute item, and its attribute item (value) needs to be selected;
- A SKU can also determine the product attributes it has through product classification, and each SKU has a corresponding attribute item.
Note: The above ER diagram does not add "SPU attribute item relationship" to the product
4. Brand management
Brand is a business name or logo used to identify a product or service and differentiate it from competitors' products or services; it is also a basic information in the system similar to attributes, but because attributes can be customized and compared with flexibility High, so the brand is distinguished from it and managed separately.
It mainly includes brand name, English name, brand logo, brand website, brand description and other information; SPU determines its brand when it is established, and at the same time establishes quotations and keywords in the search system to facilitate users to search.
5. Origin management
As an important attribute, the place of origin can be managed separately to better supplement and improve product information. With the development of e-commerce today, everyone pays more attention to the brand and place of origin (domestic, foreign and domestic provinces and cities) when purchasing products; for example, in autumn For the listed hairy crabs, we must first judge whether they are from Yangcheng Lake, Jiangsu.
At the same time, the place of origin is also a key field of search, and the place of origin channel or search portal can be used on the website, APP or applet of front-end sales. The main fields of origin, such as serial number, Chinese name, English name, country code, continent/country, whether to display, etc., are set when creating SPU.
6. Product Information
The classification and attribute basic information (key attributes, sales attributes) of the products have been determined, and the SPU and SKU can be established below.
The front-end has introduced the relevant definitions and relationships between SPU and SKU. The following mainly talks about other relevant information of the product except classification, attribute, brand and origin.
Since the SKU is generated according to the different sales attributes of the SPU, many information of the SKU is inherited from the SPU (except inventory, price, etc.);
SPU and SKU coding rules: Product SPU can use 8-digit code (6-digit classification code + 2-digit random code), and product SKU can use SPU code + 2-digit incremental code.
(1) The following figure is the basic information of SPU and SKU for reference:
(2) If the product is sold by weighing, the weighing code field should also be added
Coding rules: product barcode + weighing code + weight (specifically, it can be designed according to the docking electronic scale)
(3) The goods belong to the supplier
Whether there is a situation of one product with many merchants, that is, one product can be purchased from multiple suppliers (with the same country barcode, such as mineral water).
For products supplied by only one supplier, it is very easy to purchase, replenish or sell first, but in reality, there will definitely be multiple suppliers for a product. In the invoicing management of the supply chain, or in the financial settlement, it is necessary to determine the ownership of each inbound and outbound commodity to the supplier.
In the commodity management system, it is necessary to maintain the suppliers to which it belongs (generally, there will not be many merchants for one product). If there are multiple suppliers, you need to set the main supplier.
(4) Father and Son Commodities
The relationship between parent and child products is similar to that of parent and child accounts, framework contracts and child contracts in suppliers, that is, a parent product can derive multiple child products, and each child product includes two or more parent products.
For example, each can of Yanjing Beer is a parent product (330ml in size, national barcode 60033022), but in supermarkets, it can be bought by can, by mention (6 for one mention) or by box.
If someone buys, you might think, just enter the quantity, there's nothing difficult. Yes it's a solution, and that's what we buy most of the time.
But there is another scenario, that is, how should merchants deal with it for promotion (9.9 yuan / mention, 2.5 yuan / can for a single purchase)? It is still possible to set up promotions or create sub-products.
This is actually a commodity combination that generates a new commodity code (the warehouse needs to operate according to the bill of materials). I have always had some objections to father-son products, but considering the whole process of the system, it involves not only sales but also warehouse operations, so you can decide whether to adopt this method.
(5) Other auxiliary information
- Corner label setting: the label information of the product (applicable to the crowd, health care, etc.), which is used for search; this part can also be realized through attributes.
- Commodity inspection information: inspection method, inspection strictness, inspection rules, inspection plan, sampling quantity, sampling ratio
- Commodity import and export information: English name, English specification, import tariff rate, import consumption tax rate, import VAT rate
7. Product pictures
Pictures are an important part of the product management system. When browsing a product on the APP or website, we can most directly judge the quality of the product by identifying the product image.
Products are divided into list page (entering the store homepage or channel page or multiple products displayed through the product list displayed after searching) and detail page (clicking on a product to enter the detailed introduction page).
The product pictures on the list page generally display the main picture, and the pictures in the details page are divided into the main picture of the product and other pictures (can also be set as the main picture).
- For pictures, you need to limit the size, and at the same time require the quality of the uploaded pictures;
- The storage capacity of the image server should be monitored, and the images should be stored on the CDN to ensure the loading speed of the product images;
- After the basic information of the product has been maintained, it is necessary to maintain the product picture, and the product without the picture is not allowed to be put on the shelves;
- Image Status: A picture status field needs to be set for the product. If it is a new product, it will be "to be uploaded". If the image has been uploaded, the status will be "to be reviewed", and the status of the review will be "approved or not approved".
8. Commodity qualification management
Qualification management was introduced in the supplier management section. Similarly, for the sales of some products, the necessary qualification certificates must be provided before purchasing or selling.
- Commodity qualification generally includes: commodity label, trademark registration certificate, authorization letter, entry commodity inspection certificate, etc.; when creating basic commodity information, you can select the required qualification template;
- According to the qualifications required by the qualification template, the suppliers or colleagues in the operation editorial department upload the qualification documents, and then review them to take effect;
- If the qualification of the product has not been uploaded or the review has failed, there will be a system prompt when the product is changed from a new product to a normal saleable product.
9. Commodity inventory management
- After the classification, attribute, brand, product information, and qualification are created in the product system, the product can be purchased, and the next step can be sold if the product is in stock;
- Commodity inventory management pays attention to the quantity and amount of inventory not only in the commodity management system, but also in the entire supplier system and financial system;
- When creating product information, you need to set the safety stock of the product for timely product replenishment;
- The inventory of goods is generally divided into genuine inventory and defective product inventory, and genuine inventory can be divided into normal inventory and gift inventory;
- Authentic inventory can be sold on the shelves, defective inventory can be reported for damage, returned to the factory or sold domestically;
- Inventory is divided into total inventory and sub-warehouse inventory. If there is a store, there is also store inventory, so the management of commodity inventory is very important. It not only records the change in quantity but also records the change in cost;
- In the commodity management system, it is mainly the display of inventory reports. The changes depend on each business document in the system. The main functions of the inventory management module are as follows.
For the inventory cost part, you can take a look at "FMS Chapter 11: Financial Inventory Management Concerned Public Account: Stubborn Big Radish".
3. Commodity-related services
- Commodity information service interface: It is used to provide an interface for querying the basic information of commodities.
- Product picture service interface: the interface used to display product pictures and upload pictures in each front-end channel.
- Commodity inventory query interface: This is a very important interface in the commodity management system. It combines with the commodity sales area template to provide whether the commodity is available for sale. This part has extremely high requirements. If the response time is too long, it will affect the user experience.
- Commodity inventory update interface: update inventory possession when placing an order, reduce inventory and decrease inventory possession when leaving the warehouse, and increase inventory when entering the warehouse.
- Commodity cache service: Update the relevant information of the commodity to the cache server, so as to quickly respond to the query and browse.
Commodity-related services need unified management. Commodity inventory query service is the most critical. Stress testing is required to achieve high availability (caching, load, service downgrade if necessary, etc. I don’t understand and feel ashamed, I can only talk about it);
For the update of inventory data, it is necessary to record detailed key logs so that problems can be analyzed and tracked.
Fourth, the product creation process
The related information involved in the product is described above, and what operations are required to create a new product. The following figure is a simple process for reference only.
You can design system functions and operation interfaces one by one according to the description. The commodity management part involves the cooperation between the commodity department, the operation and the quality inspection department.
The approval process will also run through the entire process. Personally, I feel that the system operation function should be provided with detailed and clear information prompts as much as possible - "speaking people's words", so that users can operate more easily.
To add to the above picture:
- When creating a new product/importing a new product, it is only the basic information of the product, and does not involve pictures, qualifications, etc., so the product code (if there is an SPU) or product code has not been generated at this time;
- If there is an SPU, we need to create a new SPU and SKU. When setting the sales attribute of the SPU after the review, the SKU will be generated according to the sales attribute. Some shared attributes are inherited from the SPU. After the SKU is generated, the price of the SKU is maintained. , supplier and other information;
- For the actual design of the commodity system, it is necessary to comprehensively consider the distinction between SPU and SKU. The simple process can achieve the production effect. It is too complicated not only for us, but also for use.
Summarize
This article may overlap a lot with the introduction of commodity management on the Internet. After reading it, you may feel that it has listed a large frame again. I personally think that the business scenarios of each company are different. It needs to be designed in detail according to the main modules. With the help of the wisdom of everyone in business, product, operation, R&D, etc., after having the overall framework and concept, I believe that we can design a general commodity system and work together. Finally, thank you for reading!