The design from the actual needs of agricultural staff, the development of agricultural products distribution management system.From the point of view of combining theory with practice, the process of demand analysis, detailed design and concrete realization of agricultural product management is given concretely, and many problems existing in similar systems are improved.This system includes agricultural product information management module, sales management module, customer information management module, order management module and online service module, each module also contains a number of sub-function modules, to achieve the goal of data security, advanced performance, unified platform information management system.Through the test of the system, the system has been further improved and modified, and the system can basically carry out information management on agricultural products.The main work of this design is as follows:1. The user has a good system experience and simple operationDue to the operator's educational background, ability and other aspects of the difference, so the system in the development of attention to the operation of the reasonable simplification.The page has a strong sense of hierarchy, and the functions of each module and corresponding sub-module can be clearly seen through the structure expansion diagram on the left.Click on the submodule on the left, and the detailed information will appear on the right. This page has both the overall structure and detailed data records.For data add, delete, change and check, there are also very clear instructions on the interface, for the operator at a glance.For data increase, delete, modify, operation success or failure, there will be a return prompt, more reasonable.2. The system has good expansibilityWith the continuous deepening of agricultural products management, there will be more demands, so the function expansion should be considered in the system development.The system uses SSM framework, combined with MVC design pattern, makes the hierarchy relationship clear, if the need to add pages, then in the view layer for expansion;If the database needs to be changed, only the data logic layer needs to be changed and no changes to the other two layers are involved.There is a clear division of labor between the various levels, and there are interrelated interfaces, thus greatly improving the flexibility of the project.