Warehouse management system and method
By constructing a modular architecture of information reception, business processing, and result feedback, the problems of low data processing efficiency and slow response in the warehouse management system were solved, the accuracy and consistency of data were achieved, the system's execution efficiency and scalability were improved, and material flow and inventory management were optimized.
Patent Information
- Application Number
- CN202511690050.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-18
- Publication Date
- 2026-02-10
AI Technical Summary
Existing warehouse management systems suffer from data entry delays, error-proneness, and untimely inventory updates, leading to inaccurate inventory data, difficulties in inventory counting, and challenges in material traceability. Furthermore, excessive manual intervention results in slow system response and low efficiency.
A collaborative processing architecture consisting of three major modules—information reception, business processing, and result feedback—is constructed. User interaction, core business logic, and data storage are clearly defined. A modular design is adopted, including software management, data management, and inventory management modules. The system resource scheduling and task allocation are optimized through the principle of high cohesion and low coupling, so as to achieve standardization, automation, and closed-loop data processing.
It improves the execution efficiency and scalability of the warehouse management system, reduces the complexity of system iteration and development costs, ensures the accuracy and consistency of data, realizes real-time feedback and efficient material flow tracking, and optimizes inventory management and logistics control.
Smart Images
Figure CN121504331A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of warehouse management, and more particularly to warehouse management systems and methods. Background Technology
[0002] In warehouse management within the manufacturing and logistics sectors, the efficiency and accuracy of inventory management directly impact a company's operating costs and response speed. Early warehouse management systems (WMS) relied heavily on manual recording and paper documents, which suffered from inherent flaws such as delayed data entry, susceptibility to errors, and untimely updates to inventory information. This resulted in inaccurate inventory data, difficulties in inventory counting, and challenges in achieving precise material traceability.
[0003] With the development of information technology, Warehouse Management Systems (WMS) based on computer databases have emerged, enabling the electronic recording of information. However, a significant gap still exists between these systems and the physical warehouse inventory and the database records. Operations such as material entry, exit, and transfer still require manual identification of goods and manual input of information into the computer. This is not only inefficient but also highly susceptible to human error, leading to discrepancies between system records and physical inventory. The problem of "discrepancy between accounts and physical inventory" has not been fundamentally solved.
[0004] Therefore, warehouse management methods have become an urgent problem to be solved.
[0005] Based on this, this application provides a warehouse management system and method to improve the prior art. Summary of the Invention
[0006] The purpose of this application is to provide a warehouse management system and method that provides enterprises with data management, process management and business management, while also enabling more convenient tracking of material flow and providing accurate data support for quality traceability.
[0007] The objective of this application is achieved through the following technical solution: In a first aspect, this application provides a warehouse management system, including an information receiving module, a business processing module, and a result feedback module. The information receiving module receives user input information and transmits it to the business processing module. The business processing module processes the user input information and transmits the processing result to the result feedback module. The result feedback module stores and provides feedback on the processing result. The system is characterized by... The business processing module includes a software management module, a data management module, and an inventory management module. The software management module is used to control the operation of the warehouse management system, the data management module is used to process the data within the warehouse management system, and the inventory management module is used to generate business processes to manage storage operations.
[0008] In some optional implementations, the software management module includes a personnel unit, a component unit, a permission unit, a functional unit, and an operation unit; the data management module includes an internal data unit and an external data unit; and the inventory and sales business management module includes an inbound management unit, an outbound management unit, and an in-warehouse management unit.
[0009] In some optional implementations, the internal data unit includes a department data unit, a warehouse data unit, a material data unit, a metering data unit, and a barcode data unit, and the external data unit includes a customer data unit and a supplier data unit.
[0010] Secondly, this application provides a warehouse management method that combines user-inputted data to monitor, process, and maintain warehouse information, the method comprising: The information receiving module acquires user input and inputs it into the business processing module. The business processing module performs business processing on the information input by the user, including software management, data management, and inventory management. The results feedback module is used to store and provide feedback on business processing results.
[0011] The beneficial effects of this technical solution are as follows: By constructing a collaborative processing architecture consisting of three major functional modules—information reception, business processing, and result feedback—it achieves standardization, automation, and closed-loop processing of data processing workflows in the specific technical field of warehouse management. This fundamentally solves the technical problems of low data processing efficiency, high error rates, and slow system response caused by excessive manual intervention and low coupling between system modules in traditional warehouse management. Specifically, this architecture technically decouples user interaction, core business logic, and data storage / output, and clearly defines their functions. This is itself an efficient computer system resource scheduling and task allocation scheme. The information reception module, as a unified technical interface, ensures the standardization and consistency of data input, laying the foundation for subsequent automated processing. The business processing module, as the core technology, centralizes all computing and logical judgment resources, avoiding resource conflicts and performance bottlenecks caused by functional dispersion. The result feedback module ensures that data processing results can be reliably persisted by the system and instantly fed back to the user interface or other related systems, forming a complete technical closed loop. This modular system design not only improves the execution efficiency of individual business processes, but also gives the entire warehouse management system good scalability and maintainability. When new business functions need to be added, incremental development can be carried out within the business processing module without changing the overall architecture, which greatly reduces the technical complexity and development cost of system iteration and reflects significant technological progress.
[0012] In some optional implementations, the process of using the business processing module to process the user-input information includes: The software management module is used to control and regulate the operation of the warehouse management system; The data management module is used to process data within the warehouse management system; The inventory management module is used to generate business processes for managing storage operations.
[0013] The beneficial effects of this technical solution are as follows: This claim further decomposes the functional limitation of "business processing" into three technical sub-modules: "software management," "data management," and "inventory and sales management." By precisely subdividing and specializing the core business areas that consume the most computing resources in the warehouse management system, it effectively solves the technical problems that may arise in general business processing modules when facing complex and diverse warehouse operations, such as internal logic confusion, conflicting processing priorities, and uneven resource allocation. The software management module focuses on regulating the system's own operating status, which involves the governance of the system's underlying resources and operating environment; the data management module focuses on the lifecycle management of data within the system, ensuring data accuracy and consistency; and the inventory and sales management module focuses on the generation and execution of upper-level business logic. These three modules form a clear technical hierarchy within the business processing module, from underlying support to the data hub and then to top-level applications. This division is not a simple listing of functions, but a technical architecture optimization based on the principle of "high cohesion and low coupling" in computer software engineering. This allows each submodule to independently optimize algorithms and improve performance. For example, a more efficient data indexing and transaction processing mechanism can be deployed for the data management module, while the business process engine of the inventory management module can be optimized. This specialized design avoids interference between tasks of different natures, thereby significantly improving the throughput, stability, and specialization of the business processing modules as a whole, forming a collaborative and efficient technical processing core.
[0014] In some optional implementations, the process of using the business processing module to process the user-input information includes: The software management module is used to control and regulate the operation of the warehouse management system; The data management module is used to process data within the warehouse management system; The inventory management module is used to generate business processes for managing storage operations.
[0015] The beneficial effects of this technical solution are as follows: This claim explicitly defines the "business processing module" as a collaborative system composed of three technical sub-modules: "software management," "data management," and "inventory management." The software management module acts as the "cornerstone and guardian" of the system, ensuring the basic stability, security, and maintainability of the entire platform by regulating the system's operating environment, personnel permissions, and functional components. This is a prerequisite for the reliable operation of all business functions. The data management module acts as the system's "data hub," uniformly responsible for the lifecycle operations of adding, deleting, modifying, and querying internal and external data, ensuring data consistency, integrity, and authority, and providing clean and reliable data fuel for upper-level applications. The inventory management module, as the "scheduling engine" oriented towards core business, focuses on transforming static data into dynamic, executable business process instructions. These three modules each perform their respective functions, following the software design principle of "high cohesion and low coupling," allowing them to independently undergo technical evolution and performance optimization. For example, a more efficient data caching strategy can be introduced to the data management module, while the business process engine of the inventory management module can be optimized, with minimal impact on each other. This architecture not only significantly improves the system's processing efficiency and stability, but also endows the system with excellent scalability. When a new warehousing business model needs to be introduced, incremental development can be carried out mainly in the inventory management module without shaking the underlying data and software management architecture. This greatly reduces the technical complexity of system iteration and long-term maintenance costs, demonstrating its significant technological progress at the level of computer system design.
[0016] In some optional implementations, the use of a software management module to regulate the operation of the warehouse management system includes: Use personnel units to record and verify personnel identity information; Component units are used to install, upgrade, and uninstall corresponding business components; The system uses permission units to assign system function access permissions, record permission change logs, and monitor the usage of permissions in real time. The system functions are operated and managed using functional units and operational units.
[0017] The beneficial effects of this technical solution are as follows: This claim provides a deep refinement of the "software management module," revealing its internal technical mechanism of collaborative work through the "personnel unit," "component unit," "permission unit," "functional unit," and "operation unit." It constructs a comprehensive, multi-layered system operation guarantee system with security audit capabilities, specifically addressing the technical shortcomings of existing warehouse management systems in terms of security, maintainability, and dynamic adaptability. Specifically: The personnel unit establishes the first security barrier for system access through authentication technology, ensuring the legitimacy of the operating entity; the component unit implements modular deployment and dynamic loading of business functions, an advanced software architecture technology that enables the system to perform hot updates and expansions without interrupting core services, greatly improving system maintainability and flexibility; the permission unit, through refined permission allocation and full lifecycle log monitoring, elevates system security from static configuration to a dynamic, traceable, and proactive defense level, effectively preventing unauthorized operations and data leaks. The technical implementation of this unit involves complex access control lists and real-time log analysis algorithms; the functional unit and operation unit ensure that various system functions can be reliably scheduled and executed. These five units work together to concretize software management from a vague concept into a series of executable, monitorable, and controllable technical operations, significantly enhancing the robustness, security, and manageability of the warehouse management system as a complex software—a fundamental technological advantage that cannot be achieved through purely business-oriented approaches.
[0018] In some optional implementations, the data management module is used to process data within the warehouse management system, including: Use internal data units to add, modify, and delete corresponding data in department data units, warehouse data units, material data units, metering data units, and barcode data units; Use external data units to add, modify, and delete corresponding data in customer data units and supplier data units.
[0019] The beneficial effects of this technical solution are as follows: This claim focuses on the internal structure of the "data management module," clearly dividing it into "internal data units" and "external data units," and enumerating the data entities managed by each. It achieves categorized, refined, and integrated lifecycle management of heterogeneous data sources in the warehouse management system, effectively overcoming the technical challenges of integration difficulties, maintenance chaos, and inconsistency caused by diverse data sources and varying structures. From a technical architecture perspective, this division conforms to the design philosophy of the data domain model, physically or logically isolating the stable core data within the system (such as departments, warehouses, and materials) from the relatively variable external subject data (customers, suppliers). The internal data units are responsible for maintaining the foundational data for system operation. Adding, modifying, and deleting this data typically triggers a series of internal consistency checks and related update algorithms to ensure the stability of the system's basic logic. The external data units focus on managing data interacting with external entities; their change frequency and business rules may differ from those of the internal data. This classification management mechanism allows the system to design optimal storage strategies, indexing methods, and transaction processing logic for different types of data, thereby significantly improving the accuracy, completeness, and execution efficiency of data operations. Through this structured data management scheme, this claim provides high-quality, highly reliable data support for the entire warehouse management system, which is the foundation for realizing intelligent warehouse decision-making.
[0020] In some optional implementations, the use of the inventory management module to generate business processes for managing storage operations includes: Obtain barcode information, allocate warehouse storage locations using the inbound management unit, and update inventory data to generate an inbound notification. Adjust the serial number storage location and generate inventory layout records using the warehouse management unit; The outbound management unit is used to allocate materials for outbound distribution and generate outbound notification forms.
[0021] The beneficial effects of this technical solution are as follows: This claim provides a crucial and specific technical elaboration on the "inventory and sales management module," revealing that it constructs an automated, real-time warehousing and logistics control loop driven by barcode information as the core data and aimed at dynamic physical space management through the sequential connection of the "inbound management unit," "in-warehouse management unit," and "outbound management unit." It concretizes the abstract "business process generation" into a series of executable, traceable computer control instructions that are precisely mapped to the physical world, effectively solving the technical bottlenecks in traditional warehousing caused by the disconnect between information flow and physical flow, such as difficulty in finding goods, inaccurate inventory, and slow response speed. Specifically: By acquiring barcode information, the system assigns a digital identity to each item, which is the data foundation for achieving end-to-end tracking. The core technological contribution of the inbound management unit lies in its proactive allocation of warehouse storage locations, in addition to recording information. This involves the application of intelligent location allocation algorithms, which comprehensively consider various technical factors such as material attributes, warehouse layout, and storage strategies to optimize storage space utilization and subsequent picking efficiency, and automatically update inventory data, ensuring real-time consistency between system data and physical inventory. The in-warehouse management unit effectively controls the dynamic process of in-warehouse movement by adjusting "serial number storage locations" and generating layout records, providing accurate data support for inventory counting and layout optimization, and enhancing the system's ability to manage internal logistics in a refined manner. The outbound management unit's "outbound allocation" also involves intelligent algorithms, such as allocating specific batches according to a first-in, first-out (FIFO) strategy to ensure process fairness and material quality. These three units are interconnected, forming a complete closed-loop management chain from material arrival, storage, movement, and departure. This transforms the warehouse management system from a passive recording tool into an intelligent decision-making and control center capable of proactive optimization, real-time response, and precise control, greatly improving the overall efficiency, accuracy, and automation level of warehousing operations.
[0022] Thirdly, this application provides an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of any of the above methods.
[0023] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the above methods. Attached Figure Description
[0024] The present application will be further described below with reference to the accompanying drawings and embodiments.
[0025] Figure 1 A schematic diagram of the structure of a warehouse management method system provided in an embodiment of this application is shown.
[0026] Figure 2 A schematic flowchart of a warehouse management method provided in an embodiment of this application is shown.
[0027] Figure 3 A structural framework diagram of an electronic device provided in an embodiment of this application is shown. Figure 4 A schematic diagram of the structure of a program product provided in an embodiment of this application is shown. Detailed Implementation
[0028] The embodiments of this application will be further described below with reference to the accompanying drawings and specific implementation methods. It should be noted that, without conflict, the various embodiments or technical features described below can be arbitrarily combined to form new implementation methods.
[0029] In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, a and b and c, where a, b, and c can be single or multiple. It is worth noting that "at least one" can also be interpreted as "one or more".
[0030] It should also be noted that, in the embodiments of this application, the words "exemplary" or "for example" are used to indicate that they are examples, illustrations, or descriptions. Any implementation or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other implementations or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0031] System Implementation Examples See Figure 1 , Figure 1 A schematic diagram of the structure of a warehouse management method system provided in an embodiment of this application is shown.
[0032] This application provides a warehouse management system, including an information receiving module, a business processing module, and a result feedback module. The information receiving module receives user input information and transmits it to the business processing module. The business processing module processes the user input information and transmits the processing result to the result feedback module. The result feedback module stores and feeds back the processing result. The system is characterized by... The business processing module includes a software management module, a data management module, and an inventory management module. The software management module is used to control the operation of the warehouse management system, the data management module is used to process the data within the warehouse management system, and the inventory management module is used to generate business processes to manage storage operations.
[0033] In some optional implementations, the software management module includes a personnel unit, a component unit, a permission unit, a functional unit, and an operation unit; the data management module includes an internal data unit and an external data unit; and the inventory and sales business management module includes an inbound management unit, an outbound management unit, and an in-warehouse management unit.
[0034] In some optional implementations, the internal data unit includes a department data unit, a warehouse data unit, a material data unit, a metering data unit, and a barcode data unit, and the external data unit includes a customer data unit and a supplier data unit.
[0035] Method Implementation Examples See Figure 2 , Figure 2 A schematic flowchart of a warehouse management method provided in an embodiment of this application is shown.
[0036] This application provides a warehouse management method that combines user-input data to monitor, process, and maintain warehouse information. The method includes: The information receiving module acquires user input and inputs it into the business processing module. The business processing module performs business processing on the information input by the user, including software management, data management, and inventory management. The results feedback module is used to store and provide feedback on business processing results.
[0037] Therefore, by constructing a collaborative processing architecture consisting of three major functional modules—information reception, business processing, and result feedback—standardization, automation, and closed-loop processing of data processing workflows have been achieved in the specific technical field of warehouse management. This fundamentally solves the technical problems of low data processing efficiency, high error rates, and slow system response caused by excessive manual intervention and low coupling between system modules in traditional warehouse management. Specifically, this architecture technically decouples user interaction, core business logic, and data storage / output, and clearly defines their functions, which is itself an efficient computer system resource scheduling and task allocation scheme. The information reception module, as a unified technical interface, ensures the standardization and consistency of data input, laying the foundation for subsequent automated processing; the business processing module, as the core technology, centralizes all computing and logical judgment resources, avoiding resource conflicts and performance bottlenecks caused by functional dispersion; and the result feedback module ensures that the data processing results can be reliably persisted by the system and fed back to the user interface or other related systems in a timely manner, forming a complete technical closed loop. This modular system design not only improves the execution efficiency of individual business processes, but also gives the entire warehouse management system good scalability and maintainability. When new business functions need to be added, incremental development can be carried out within the business processing module without changing the overall architecture, which greatly reduces the technical complexity and development cost of system iteration and reflects significant technological progress.
[0038] In some optional implementations, the process of using the business processing module to process the user-input information includes: The software management module is used to control and regulate the operation of the warehouse management system; The data management module is used to process data within the warehouse management system; The inventory management module is used to generate business processes for managing storage operations.
[0039] Therefore, this claim further decomposes the functional limitation of "business processing" into three technical sub-modules: "software management," "data management," and "inventory and sales management." By precisely segmenting and specializing the core and most computationally resource-intensive business areas within the warehouse management system, it effectively solves the technical problems that may arise in general business processing modules when facing complex and diverse warehouse operations, such as internal logic confusion, conflicting processing priorities, and uneven resource allocation. The software management module focuses on regulating the system's own operational status, governing the system's underlying resources and operating environment; the data management module focuses on the lifecycle management of data within the system, ensuring data accuracy and consistency; and the inventory and sales management module focuses on the generation and execution of upper-level business logic. These three modules form a clear technical hierarchy within the business processing module, from underlying support to the data hub and then to top-level applications. This division is not a simple listing of functions, but a technical architecture optimization based on the principle of "high cohesion and low coupling" in computer software engineering. It allows each sub-module to independently optimize algorithms and improve performance; for example, a more efficient data indexing and transaction processing mechanism can be deployed for the data management module, while the business process engine of the inventory and sales management module can be optimized. This specialized design avoids interference between tasks of different natures, thereby significantly improving the throughput, stability, and specialization of the business processing module as a whole, forming a collaborative and efficient technical processing core.
[0040] In some optional implementations, the process of using the business processing module to process the user-input information includes: The software management module is used to control and regulate the operation of the warehouse management system; The data management module is used to process data within the warehouse management system; The inventory management module is used to generate business processes for managing storage operations.
[0041] Therefore, this claim explicitly defines the overarching concept of "business processing module" as a collaborative system composed of three technical sub-modules: "software management," "data management," and "inventory management." The software management module acts as the "cornerstone and guardian" of the system, ensuring the basic stability, security, and maintainability of the entire platform by regulating the system's operating environment, personnel permissions, and functional components. This is a prerequisite for the reliable operation of all business functions. The data management module acts as the system's "data hub," uniformly responsible for the lifecycle operations of adding, deleting, modifying, and querying internal and external data, ensuring data consistency, integrity, and authority, and providing clean and reliable data fuel for upper-level applications. The inventory management module, as the "scheduling engine" oriented towards core business, focuses on transforming static data into dynamic, executable business process instructions. These three modules each perform their respective functions, adhering to the software design principle of "high cohesion and low coupling," allowing them to independently undergo technological evolution and performance optimization. For example, a more efficient data caching strategy can be introduced into the data management module, while the business process engine of the inventory management module can be optimized, with minimal impact on each other. This architecture not only significantly improves the system's processing efficiency and stability, but also endows the system with excellent scalability. When a new warehousing business model needs to be introduced, incremental development can be carried out mainly in the inventory management module without shaking the underlying data and software management architecture. This greatly reduces the technical complexity of system iteration and long-term maintenance costs, demonstrating its significant technological progress at the level of computer system design.
[0042] In some optional implementations, the use of a software management module to regulate the operation of the warehouse management system includes: Use personnel units to record and verify personnel identity information; Component units are used to install, upgrade, and uninstall corresponding business components; The system uses permission units to assign system function access permissions, record permission change logs, and monitor the usage of permissions in real time. The system functions are operated and managed using functional units and operational units.
[0043] Therefore, this claim provides a detailed description of the "software management module," revealing its internal technical mechanism through the collaborative work of the "personnel unit," "component unit," "permission unit," "functional unit," and "operation unit." It constructs a comprehensive, multi-layered system operation assurance system with security audit capabilities, specifically addressing the technical shortcomings of existing warehouse management systems in terms of security, maintainability, and dynamic adaptability. Specifically: the personnel unit establishes the first line of security for system access through authentication technology, ensuring the legitimacy of the operating entity; the component unit implements modular deployment and dynamic loading of business functions, an advanced software architecture technology that enables the system to perform hot updates and expansions without interrupting core services, greatly improving system maintainability and flexibility; the permission unit, through refined permission allocation and full lifecycle log monitoring, elevates system security from static configuration to a dynamic, traceable, and proactive defense level, effectively preventing unauthorized operations and data leaks. The technical implementation of this unit involves complex access control lists and real-time log analysis algorithms; the functional unit and operation unit ensure that various system functions can be reliably scheduled and executed. These five units work together to concretize software management from a vague concept into a series of executable, monitorable, and controllable technical operations, significantly enhancing the robustness, security, and manageability of the warehouse management system as a complex software—a fundamental technological advantage that cannot be achieved through purely business-oriented approaches.
[0044] In one specific embodiment, the software management module is the control core of the warehouse management system, responsible for ensuring the system's safe, stable, and compliant operation. It manages and controls the "personnel" and the "software" itself through two key components—the personnel unit and the component unit. Its specific implementation includes: 1. Implementation of personnel units The personnel unit acts as the "access control" and "position management" of the entire system, and its core task is to ensure the clear legal identity and authority of the operators.
[0045] Personnel Information Recording and Organization: During system initialization, the system administrator enters the information of all employees who need to use the warehouse management system into the system through a dedicated management interface. This information includes at least the employee's name, employee ID, department, and preset login account and initial password. The system will create a unique digital identity file for each employee.
[0046] Authentication Process: When any user attempts to log in to the system, the HR unit initiates an authentication process. After the user enters their username and password on the login screen, the HR unit compares this information with a pre-recorded digital identity profile in the system. Only if the username and password match exactly will the system allow the user to log in. Otherwise, the system will refuse login and display an error message. This process ensures that only authorized internal personnel can access the system, forming the first line of defense for information security.
[0047] Job Role and Permission Association: Based on the recorded basic information, the administrator will assign one or more preset job roles to each employee (such as "Warehouse Manager," "Inventory Checker," "System Administrator," etc.). Each job role is associated with a specific set of operation permissions in the system (for example, an inventory checker may only have the permission to query and check inventory, but not the permission to modify the basic information of the goods). When a user successfully logs in, the HR unit will pass their job information to other parts of the system, thereby controlling which menus they can see and which operations they can perform in that session.
[0048] 2. Implementation of Component Units The component unit acts as the system's "functional repository" and "license manager," and its core task is to centrally manage the legality and availability of various functional components within the system.
[0049] Modular software management: This warehouse management system is not a single, rigid software, but rather consists of multiple relatively independent functional components (or "modules"), such as the "Inbound Management Component," "Outbound Management Component," and "Inventory Counting Component." Each component unit is responsible for the unified management of the installation, activation, and deactivation of these components.
[0050] License and User Number Control: The system has strict commercial license controls for software use. In the component unit management interface, administrators can clearly see the current license status, including but not limited to: Total number of licensed users: The maximum number of users that the system allows to be online at the same time.
[0051] Lite User Limit: Under the total license, there may be a limit on the number of "Lite" users with limited functionality.
[0052] Valid until: The final effective date of this software license.
[0053] Registration and Activation Mechanism: When an enterprise needs to update its registration due to changes in the number of users, functional modules, or license expiration, the administrator can perform the "Adjust Registration" operation within the component unit. The specific process is as follows: Administrators enter change information (such as the new number of users, the new validity period, etc.) in the unit interface.
[0054] The component unit will generate a brand new, unique serial number based on this new information and the specific hardware information of the machine through an internal algorithm.
[0055] The administrator needs to formally submit this new serial number and related application documents to the software provider.
[0056] After receiving the official registration file from the provider that matches the new serial number, the administrator imports the file into the system.
[0057] Once the component unit verifies the validity of the registration file, the system updates its authorization status, and the new license (such as an increase in the number of users or an extended validity period) takes effect. In some optional implementations, the data management module is used to process data within the warehouse management system, including: Use internal data units to add, modify, and delete corresponding data in department data units, warehouse data units, material data units, metering data units, and barcode data units; Use external data units to add, modify, and delete corresponding data in customer data units and supplier data units.
[0058] Therefore, this claim focuses on the internal structure of the "data management module," clearly dividing it into "internal data units" and "external data units," and enumerating the data entities managed by each. This achieves categorized, refined, and integrated lifecycle management of heterogeneous data sources in the warehouse management system, effectively overcoming the technical challenges of integration difficulties, maintenance chaos, and inconsistency caused by diverse data sources and varying structures. From a technical architecture perspective, this division aligns with the design philosophy of the data domain model, physically or logically isolating stable core data within the system (such as departments, warehouses, and materials) from relatively variable external subject data (customers, suppliers). Internal data units are responsible for maintaining the foundational data for system operation. Adding, modifying, and deleting this data typically triggers a series of internal consistency checks and related update algorithms to ensure the stability of the system's basic logic. External data units focus on managing data interacting with external entities; their change frequency and business rules may differ from internal data. This categorized management mechanism allows the system to design optimal storage strategies, indexing methods, and transaction processing logic for different types of data, thereby significantly improving the accuracy, completeness, and execution efficiency of data operations. Through this structured data management solution, this claim provides high-quality and highly reliable data support for the entire warehouse management system, which is the foundation for realizing intelligent warehouse decision-making.
[0059] In one specific embodiment, this module manages the entire lifecycle of internal operational elements and external business partner information through internal data units and external data units, respectively. A specific implementation method may be: I. Implementation of Internal Data Units The internal data unit is responsible for building the internal environment and rules for the enterprise's warehouse operations; the data it manages is the foundation for warehouse operations. The specific implementation process is as follows: Departmental Data Maintenance: The system administrator first establishes the company's organizational structure through the "Basic Data" menu. For example, adding departments such as "Warehouse," "Purchasing," and "Sales" and assigning them unique codes. This step ensures that all subsequent business processes (such as inbound and outbound operations) have clearly defined responsible departments.
[0060] Warehouse and storage location data maintenance: The administrator then needs to digitize the company's physical storage space. Through the corresponding menu, specific warehouses can be added (such as "Raw Materials Warehouse" or "Finished Goods Warehouse No. 1"), and each warehouse can be further refined by adding storage areas, shelves, and even specific storage location codes (such as "A-01-001"). This digitized warehouse map is a prerequisite for achieving accurate inventory location and efficient shelving operations.
[0061] Material Data Maintenance: This is the core of internal data construction. Administrators first establish a material classification system (such as "Electronic Components" or "Packaging Materials") using the "Material Categories" function under the "Material" menu. Then, a unique file is created for each commodity or raw material in "Basic Material Information." When adding a new material entry, its unique material code, name, and specifications must be entered, and related items must be selected from the maintained material category and unit of measurement data. For example, adding a "Mobile Phone" with the code "PH-001," belonging to the "Electronic Products" category, and the unit of measurement is "unit." When material information changes (such as specification updates), the administrator updates its file using the modification function; when a material is obsolete, a deletion operation is performed (the system usually performs logical deletion, i.e., marking it as disabled, rather than physically deleting it, to retain historical records).
[0062] Measurement Data Maintenance: To ensure the consistency of quantity information in the system, administrators can add all necessary units of measurement, such as "piece," "box," "kilogram," and "meter," through the "Units of Measurement" function under the "Measurement" menu. Simultaneously, the "Substitute Units of Measurement" function allows the establishment of conversion relationships between different units (e.g., 1 box = 12 pieces). This function enables the system to flexibly handle complex business scenarios where procurement is done by "box" and delivery by "piece."
[0063] Barcode Data Maintenance: To achieve efficient product identification, administrators can bind materials to barcode rules using functions such as "Subcontracting Rule Maintenance" under the "Barcode Management" menu. For example, a new subcontracting rule can be added for the aforementioned "Mobile Phones" (material code PH-001), defining the quantity per box as "20" units. This way, when the system generates or recognizes barcodes, it can automatically associate the box code with the internal material information and quantity.
[0064] II. Implementation of External Data Units The external data unit is responsible for managing information about external entities that do business with the company and is the foundation for supply chain collaboration.
[0065] Customer Data Maintenance: Sales or customer service personnel add customer profiles through the "Customer Basic Information Maintenance" function under the "Basic Data / Customers" menu. Key steps include: assigning a unique customer code, entering the complete customer name, abbreviation, and generating a mnemonic code for easy searching (usually composed of the first letters of the customer's name in Pinyin). Simultaneously, a customer category must be assigned (e.g., "VIP Customer," "Regular Customer"), and their address and contact person must be recorded. When customer information changes or cooperation terminates, authorized personnel can modify or delete (logical deletion) the information accordingly.
[0066] Supplier data maintenance: Purchasing personnel can add, modify, or delete supplier profiles through the "Basic Data / Suppliers" menu's "Supplier Basic Information" function, following a process similar to customer management. This also requires maintaining key information such as supplier code, name, category, and address. Suppliers should be categorized (e.g., "Raw Material Suppliers," "Logistics Service Providers") to facilitate subsequent performance evaluation and procurement statistics.
[0067] Business process integration example: When a procurement transaction occurs, the system behaves as follows: In purchase orders created by purchasing agents, the supplier field is selected from a list of suppliers maintained by an external data unit.
[0068] The material details in the order are selected from the material list maintained by the internal data unit.
[0069] The unit of measurement for materials is automatically populated and can be converted between "purchasing units" (such as "boxes") and "inventory units" (such as "pieces") according to the conversion rules defined by the internal data units.
[0070] After the goods are delivered, warehouse staff scan the barcode on the packaging. This barcode is defined by the barcode rules of the internal data unit. The system automatically identifies the corresponding material, batch and quantity, and completes the warehousing operation.
[0071] In some optional implementations, the use of the inventory management module to generate business processes for managing storage operations includes: Obtain barcode information, allocate warehouse storage locations using the inbound management unit, and update inventory data to generate an inbound notification. Adjust the serial number storage location and generate inventory layout records using the warehouse management unit; The outbound management unit is used to allocate materials for outbound distribution and generate outbound notification forms.
[0072] Therefore, this claim provides a crucial and specific technical elaboration on the "inventory and sales management module," revealing that it constructs an automated, real-time warehousing and logistics control loop driven by barcode information and aimed at dynamic physical space management through the sequential connection of the "inbound management unit," "in-warehouse management unit," and "outbound management unit." It concretizes the abstract "business process generation" into a series of executable, traceable, and precisely mapped computer control instructions, effectively solving the technical bottlenecks in traditional warehousing caused by the disconnect between information flow and physical flow, such as difficulty in finding goods, inaccurate inventory, and slow response speed. Specifically: by acquiring barcode information, the system assigns a digital identity to each material, which is the data foundation for achieving end-to-end tracking; the core technological contribution of the inbound management unit lies in its proactive "allocation of warehouse storage locations," involving the application of intelligent location allocation algorithms. This algorithm comprehensively considers various technical factors such as material attributes, warehouse layout, and storage strategies to optimize storage space utilization and subsequent picking efficiency, and automatically updates inventory data, ensuring real-time consistency between system data and physical inventory. The in-warehouse management unit effectively controls the dynamic process of in-warehouse movement by adjusting "serial number storage locations" and generating layout records. This provides precise data support for inventory counting and layout optimization, enhancing the system's ability to manage internal logistics with precision. The outbound management unit's "outbound allocation" also involves intelligent algorithms, such as allocating specific batches according to a first-in, first-out (FIFO) strategy to ensure process fairness and material quality. These three units are interconnected, forming a complete closed-loop management chain from material arrival, storage, movement, and departure. This transforms the warehouse management system from a passive recording tool into an intelligent decision-making and control center capable of proactive optimization, real-time response, and precise control, significantly improving the overall efficiency, accuracy, and automation level of warehousing operations.
[0073] In one optional implementation, the process covers the entire lifecycle management from material receipt and in-warehouse management to material issuance, as detailed below: Step 1: Inbound Business Process – Generating Inbound Notification Form This step corresponds to the claim "obtaining barcode information, allocating warehouse storage locations using the inbound management unit, and updating inventory data to generate an inbound notification form," and its specific implementation process is as follows: Barcode Information Acquisition and Business Creation: Users can access the "WMS Inbound Notification Maintenance" or similar function interface through the system client (such as a computer).
[0074] Users click the "New" button to create a new inbound transaction. In the new transaction interface, users enter basic transaction information, including the transaction date, target warehouse, transaction type (such as purchase inbound, transfer inbound, production return, etc.), material code, and planned inbound quantity.
[0075] Generate and confirm the inbound notification form: After the information is entered, the user clicks the "Save" button, and the system generates a formal inbound notification. This notification specifies "what materials are present," "how many are to be received," and "which warehouse they will be received in," providing instructions for subsequent physical inbound operations.
[0076] Users can select the notification and click the "Confirm" button to put it into a pending state.
[0077] Physical barcode scanning for warehousing and storage location allocation: Warehouse operators can log in and access the
WMS Inbound Scan
[0078] The operator first scans the target storage location code (i.e., the barcode of a specific shelf in the warehouse). The system's app interface then displays the information for that storage location.
[0079] Next, the operator scans the barcode or packaging code of the material to be put into storage. After obtaining the barcode information, the system automatically binds the material to the currently scanned storage location, completing the allocation of the warehouse storage location.
[0080] The operator clicks the "Confirm" button. After receiving the confirmation instruction, the system updates the inventory data in real time, recording information such as the inventory quantity and storage location of the material in the database, marking the final completion of this warehousing operation.
[0081] Step 2: Warehouse Management Business Process – Generating Inventory Layout Records This step corresponds to the claim "adjusting the serial number storage location using the warehouse management unit and generating inventory layout records", and its core implementation process is storage location adjustment: Initiate warehouse location adjustment: When it is necessary to optimize the warehouse layout, conduct inventory checks, or move materials for other reasons, operators can use the mobile app to access the
WMS Warehouse Location Adjustment
[0082] Scan adjustment information: The operator first scans the new target storage location code.
[0083] Next, scan the serial number barcode of the material to be moved. For each serial number scanned, the system interface will dynamically display information about the material's relocation from its original location to the new location.
[0084] Confirm adjustments and generate records: After verifying that the information is correct, the operator clicks the "Confirm" button.
[0085] The system performs an adjustment operation, updating the storage location information of the material with that serial number in the database. Simultaneously, this adjustment operation is recorded by the system, generating an inventory layout record. This record details information such as the material serial number, original storage location, new storage location, adjustment time, and the operator, enabling traceable management of dynamic inventory layout.
[0086] Step 3: Outbound Business Process – Generating Outbound Notification Form This step corresponds to "using the materials in the outbound management unit to allocate them for outbound distribution and generate an outbound notification slip" in the claim, and its specific implementation process is as follows: Create outbound instruction – Generate outbound notification: Users can access the "WMS Outbound Notification Maintenance" interface via computer.
[0087] Click the "New" button to enter the outbound demand information, including the business date, shipping warehouse, transaction type (such as sales outbound, workshop material requisition, transfer outbound, etc.), material code, and quantity to be issued.
[0088] Clicking the "Save" button will generate an outbound notification. This document specifies "what materials are to be shipped", "how many are to be shipped", and "from which warehouse".
[0089] Execute outbound allocation: Users access the
WMS Outbound Allocation
[0090] Selecting a created and confirmed WMS outbound notification will display the details of that notification.
[0091] Users click the "Outbound Allocation" button to enter the allocation interface. Clicking the "Automatic Allocation" function under the "Run" menu will automatically allocate specific serial numbers or batches of materials from the inventory for the outbound task according to preset strategies (such as FIFO, proximity principle, etc.).
[0092] After allocation is complete, the system generates allocation results, clearly indicating which specific serial number (in which storage location) should satisfy each material in the notification. Clicking "Confirm" will make the allocation results effective.
[0093] Physical goods are shipped out via barcode scanning: Warehouse operators use a mobile app to access the "WMS Outbound Scan" function.
[0094] First, scan the picking order number (usually associated with the outbound notification or allocation result).
[0095] Then, following the system instructions, locate and scan the assigned material serial number barcode or packaging code.
[0096] After the scan is successful, click the "Confirm" button. The system will then verify the inventory, update the inventory data, and complete the outbound operation.
[0097] Equipment Implementation Examples This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps of any of the above methods. The specific implementation method and the technical effects achieved are the same as those described in the above method embodiments, and some contents will not be repeated.
[0098] See Figure 3 , Figure 3 A structural framework diagram of an electronic device provided in an embodiment of this application is shown.
[0099] The electronic device includes at least one memory 210, at least one processor 220, and a bus 230 connecting different platform systems.
[0100] The memory 210 may include a readable medium in the form of volatile memory, such as random access memory (RAM) 211 and / or cache memory 212, and may further include read-only memory (ROM) 213.
[0101] The memory 210 also stores a computer program, which can be executed by the processor 220 to enable the processor 220 to implement the steps of any of the above methods.
[0102] The memory 210 may also include a utility 214 having at least one program module 215, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.
[0103] Accordingly, processor 220 can execute the aforementioned computer program, and can also execute utility 214.
[0104] The processor 220 may employ one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.
[0105] Bus 230 can be one or more of several types of bus structures, including a memory bus or memory controller, peripheral bus, graphics acceleration port, processor, or a local bus using any bus structure with multiple bus structures.
[0106] The electronic device can also communicate with one or more external devices 240, such as a keyboard, pointing device, Bluetooth device, etc., and with one or more devices capable of interacting with the electronic device, and / or with any device that enables the electronic device to communicate with one or more other computing devices (e.g., a router, modem, etc.). This communication can be performed through input / output interface 250. Furthermore, the electronic device can communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 260. Network adapter 260 can communicate with other modules of the electronic device via bus 230. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage platforms.
[0107] Medium Examples This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the steps of any of the above methods. The specific implementation method and the technical effects achieved are the same as those described in the above method embodiments, and some contents will not be repeated.
[0108] See Figure 4 , Figure 4 A schematic diagram of the structure of a program product provided in an embodiment of this application is shown.
[0109] The program product is used to implement any of the methods described above. The program product may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In embodiments of this application, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device. The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.
[0110] Computer-readable storage media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The readable storage medium may also be any readable medium capable of sending, propagating, or transmitting a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, or any suitable combination thereof. Program code for performing operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java and C++, as well as conventional procedural programming languages such as C, Python, or similar programming languages. The program code may be executed entirely on a user computing device, partially on a user device, as a standalone software package, partially on a user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to a user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider). This application, from the perspectives of purpose, performance, progress, and novelty, meets the functional enhancement and use requirements emphasized by patent law. The above description and accompanying drawings are merely preferred embodiments of this application and are not intended to limit this application. Therefore, all structures, devices, and features similar to those of this application, i.e., all equivalent substitutions or modifications made within the scope of this patent application, should fall within the scope of protection of this patent application.
Claims
1. A warehouse management system, comprising an information receiving module, a business processing module, and a result feedback module, wherein the information receiving module receives user input information and transmits it to the business processing module; the business processing module processes the user input information and transmits the processing result to the result feedback module; and the result feedback module stores and feeds back the processing result, characterized in that... The business processing module includes a software management module, a data management module, and an inventory management module. The software management module is used to control the operation of the warehouse management system, the data management module is used to process the data within the warehouse management system, and the inventory management module is used to generate business processes to manage storage operations.
2. The warehouse management system according to claim 1, characterized in that, The software management module includes a personnel unit, a component unit, a permission unit, a functional unit, and an operation unit. The data management module includes an internal data unit and an external data unit. The inventory and sales business management module includes an inbound management unit, an outbound management unit, and an in-warehouse management unit.
3. The warehouse management system according to claim 2, characterized in that, The internal data units include department data units, warehouse data units, material data units, metering data units, and barcode data units, while the external data units include customer data units and supplier data units.
4. A warehouse management method, characterized in that, The method for monitoring, processing, and maintaining warehouse information by combining user-entered data includes: The information receiving module acquires user input and inputs it into the business processing module. The business processing module performs business processing on the information input by the user, including software management, data management, and inventory management. The results feedback module is used to store and provide feedback on business processing results.
5. The warehouse management method according to claim 4, characterized in that, The process of processing user input information using the business processing module includes: The software management module is used to control and regulate the operation of the warehouse management system; The data management module is used to process data within the warehouse management system; The inventory management module is used to generate business processes for managing storage operations.
6. The warehouse management method according to claim 5, characterized in that, The software management module is used to control the operation of the warehouse management system, including: Use personnel units to record and verify personnel identity information; Component units are used to install, upgrade, and uninstall corresponding business components; The system uses permission units to assign system function access permissions, record permission change logs, and monitor the usage of permissions in real time. The system functions are operated and managed using functional units and operational units.
7. The warehouse management method according to claim 5, characterized in that, The data management module is used to process data within the warehouse management system, including: Use internal data units to add, modify, and delete corresponding data in department data units, warehouse data units, material data units, metering data units, and barcode data units; Use external data units to add, modify, and delete corresponding data in customer data units and supplier data units.
8. The warehouse management method according to claim 5, characterized in that, The use of the inventory management module to generate business processes for managing storage operations includes: Obtain barcode information, allocate warehouse storage locations using the inbound management unit, and update inventory data to generate an inbound notification. Adjust the serial number storage location and generate inventory layout records using the warehouse management unit; The outbound management unit is used to allocate materials for outbound distribution and generate outbound notification forms.
9. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory storing a computer program and the processor being configured to perform the steps of the method according to any one of claims 4-8.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 4-8.