01 Product Background
1.1 Background overview
The aboss WMS Southeast Asia warehouse management system is based on the use of the BigSeller system, coupled with the solution of multiple warehouses, to solve the functions of warehousing business, outbound business, warehouse transfer, inventory transfer and virtual warehouse management, etc., for batch management, Comprehensive application of functions such as material correspondence, inventory counting, quality inspection management, virtual warehouse management and real-time inventory management, effectively control and track the entire process of logistics and cost management of warehouse business, and realize or improve enterprise warehouse information management.
1.2 Problems and opportunities
During the use of BigSeller, problems such as insufficient use and the use of multiple warehouses were discovered, which can be used as important key points for this research and development. Important questions to be addressed:
1) Multiple account issues.
2) Multi-warehouse problem.
3) Order distribution problem.
4) Multi-device linkage problem.
5) Third-party docking problems.
6) The problem of e-commerce platform binding.
7) Warehouse inventory issues.
1.3 Boundary definition
1.3.1 User defined
The overall application of aboss WMS includes four types of personnel:
1) WMS mid-stage managers
Middle-stage managers refer to managers who manage the entire application. It involves warehouse management, logistics management, freight management and so on.
2) Customer background management personnel
Customer background management personnel refer to store management personnel who use aboss to manage stores and products. It involves commodity management, store binding, and inventory viewing.
3) User
Users refer to consumers, people who purchase goods from various stores. Users are involved in order creation, return orders, etc.
4) Staff
Staff refers to the personnel who handle the goods, the personnel who handle the delivery of orders and inventory operations. It involves order delivery, return processing, inventory operations, etc.
1.3.2 Definition of authority
Permissions include two aspects:
1) Background function module permissions
The master account can control which function modules the sub-account can use.
2) Warehouse permissions
Warehouses can be assigned in the multi-warehouse mode, which includes the background management interface and operable data permissions in the pad.
Permissions shall be divided into three levels of permissions:
The first level of authority: general account
The master account can use all functions and control all secondary accounts, but cannot view and control tertiary accounts.
Second-level authority: Second-level account
The secondary account is a customer account or a manager account, and the permissions of the secondary account are set by the master account. The sub-account created by the second-level account is a third-level account, and the assigned permissions are the permissions contained in the second-level account.
Level 3 permission: level 3 account
The third-level account is the lowest-level account, and sub-accounts cannot be created.
1.3.3 Pad permission definition
Pad permissions are independent of account permissions, and pad permissions can only be created and processed by the master account or secondary accounts, and tertiary accounts have no permissions to process.
1) Warehouse permissions
Each account can distinguish warehouses, and can only receive orders and work orders from corresponding warehouses.
2) Operation authority
Assignable operation authority of pad: warehousing, picking, packaging, inventory, express interception and tracking
1.3.4 Settlement definition
1) Point recharge Recharge in advance and buy tickets.
2) Ticket recharge
*Agreed amount of money per vote, then the unit price * number of votes is the amount that needs to be paid
*Including packaging fee and material fee, multiple order combination fee
3) Precise recharge
For the length, width and height of a single package provided by the warehouse, the price matching each package is accurately calculated. For multiple skus, the basic price is calculated according to the largest sku in the package.
For each package exceeding 3 sku, ***money calculation will be added
4) Monthly account customers
Time-sku-order number-express number-total number-payment clear
1.3.5 Store definition
Stores on different e-commerce platforms can be connected to the WMS system.
1) Multiple e-commerce platforms
shopee/lazada/Qimenhufu, reserve the possibility of docking with other platforms.
2) Multiple stores on the same platform
Multiple stores can be bound under the same e-commerce platform.
1.3.6 Definition of Logistics
Multiple logistics platforms can be connected, and logistics templates can be set separately, and stores can be set to use specified logistics templates.
02 Product Overview
Users can use aboss WMS to complete functions such as inbound business, outbound business, warehouse allocation, inventory allocation, and virtual warehouse management, and comprehensively use functions such as batch management, material correspondence, inventory count, and real-time inventory management to effectively control and track warehouses The entire process of business logistics and cost management, to achieve or improve the enterprise's warehouse information management.
Users can complete store association, goods management, order management, etc. through the background management platform to solve after-sales problems of commodities.
Managers can manage warehouses, commodities, orders and permissions through the background management platform.
The staff can complete the workflow of picking, packing, shipping and inventorying of goods through the pad platform
03 Detailed requirements
3.1 List of business functions
3.2 Architecture Diagram
3.2.1 Requirements Architecture Diagram
3.2.2 Business Architecture Diagram
3.2.3 Technical Architecture Diagram
3.2.4 Data Architecture Diagram
3.3 Description of business function modules
Aboss WMS has many business modules with strong correlation, but it needs to be decoupled. Therefore, the functional modules should be relatively independent. The main functional modules include:
1) Third-party linkage: third-party payment agencies, shipping platforms, logistics platforms, SMS, email
2) Warehouse management: warehouse management, inventory management, scheduling management, work order processing
3) Authority management: store management, authority center, marketing module, equipment linkage
4) Order module: inbound order, outbound order, return order, automatic order splitting
5) Logistics module: logistics setting, picking, sorting, packing, write-off
6) Guarantee module: log collection, message queue, service governance, api management, system announcement, data analysis
04 Other problem descriptions
4.1 All modules must provide industry standard interfaces
Considering that this system will definitely have some functional modules and other functional services, it will be satisfied through a third-party system. In this case, all you need to do is to provide industry-standard interfaces and let them connect.
4.2 Module size division problem
When the complexity of the system reaches a certain level, the code needs to be split. Before that, it would be good to have a general range division. It is difficult to sort out the business completely at once. Secondly, the business is constantly changing, and new businesses are constantly emerging. Maybe the sub-modules will be dismantled under the big module