I showed the last article to a friend, and the feedback I got was a little white, who may not understand it, and wrote a bit similar to the requirements document. In fact, this is the idea of my writing the article, teaching you how to design WMS products, so the article will involve a lot of product logic descriptions, if you want to know other aspects, you can leave a message under the article, okay, continue today's content introduce. 1. Product information There are two design modes for designing the commodity module in WMS according to the company's business.
One is that if the company only has warehouse receipt and delivery business, then a complete commodity file needs to be established in WMS, that is to say, the addition and maintenance of commodity information is in the warehouse. The other is that in addition to b2b data receiving and delivering goods, the company also has sales-side business. In this case, the maintenance of commodity information is generally maintained in the commodity system by the people in the commodity group, and the warehouse is only used to supplement the commodity information. 1. Product information is maintained on the WMS side The maintenance of product information is as follows (for reference only):
The above picture is an example of a single product. Some students must find that if you add a multi-attribute product, you need to add attributes and attribute values. The specific part will be explained when it comes to the design of the commodity module of the ERP system. Some field descriptions in the product information: 1) Basic units and auxiliary units The conversion of multiple units is relatively common in the retail industry, such as: 1 box of water = 12 bottles of water, so 1 box = 12 bottles, the inventory management and delivery of this multi-unit product is a bit more complicated here, and the multi-unit product is recorded. inventory, as follows: