Only the backend is involved, see the top column for all directories, codes, documents, and interface paths are:
[Lilishop Mall] Record the study notes of the B2B2C mall system~
The whole article will combine the business introduction to focus on the design logic, including the interface class and business class. The specific combination of source code analysis is not complicated to read~
Caution: Some comments in the source code are wrong, some comments have completely opposite meanings, and some comments are not correct. I updated them during the reading process and added new comments where I did not know. So be careful when reading the source code!
Table of contents
B1.B end (belongs to explicit operation)
B2.S terminal (belongs to explicit operation)
B3.M terminal (belongs to explicit operation)
The order has been generated at the time of settlement, and the status is unpaid at this time, and then the status is changed to paid after the user pays. For the order flow chart, you can look at the previous logic diagram~
A1. Order
We will only talk about the logic of the order here, and distinguish the return/refund process from the order.
Explain that the order mentioned here is not a transaction order, not a sub-order, but an order generated according to the store. The three terminals operate orders in the order module, which are orders generated by the store, and when settlement and payment are made at the cash register, the payment is for the transaction order~
B1.B end (belongs to explicit operation)
C1. Interface
- Query member order list, query order details according to order number
- Confirm receipt, cancel order, delete order according to order number
- Query the logistics trace and invoice according to the order number
Remark:
There will be business logic of billing flow in the order section, such as canceling the order operation, if it is an unpaid order, the status will be directly modified, if it is a paid order, the status will be modified, and a refund flow will be generated~
To delete an order, only the B-side can delete it, and it can only be deleted when the order is completed, and the deletion is also a soft deletion, just set the deletion status to deleted.
Querying logistics traces requires the business logic of logistics electronic bills.
B2.S terminal (belongs to explicit operation)
On the S side of the store, you can view all your orders, and then operate and ship them.
- Query the order list, order details according to the order number
- Modify consignee information, modify order price, order delivery, query logistics trace
- Obtain order information and order verification according to the verification code
- Download the list of orders to be shipped, upload files for batch shipment of orders, and export orders to be shipped
B3.M terminal (belongs to explicit operation)
There are more order operations on the operation M side than on the S side and B side. For example, the operation M side can cancel orders and collect money offline.
- Query order list pagination, order details according to order number
- Confirmation of payment - the administrator collects payment offline, modifies consignee information, modifies order price, cancels order, and inquires about logistics traces
- Query the order export list
