[Lilishop Mall] No3-9. Module detailed design, order module-3 (after-sales) detailed design

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

A1. After-sale reasons (including types: refund, cancellation, return, complaint)

B1.M terminal (belongs to explicit operation)

B2.B side (belongs to explicit operation)

A2. After sales

B1.B end (belongs to explicit operation)

B2.S terminal (belongs to explicit operation)

B3.M terminal (belongs to explicit operation) 


After the order is shipped, the buyer B can choose to confirm receipt or apply for after-sales, which means return/refund.

4030b8db3367438ea1008806cabfa021.png (893×944)

[Lilishop Mall] No1-1. Business understanding + division of each module logic_ order module sorting diagram

A1. After-sale reasons (including types: refund, cancellation, return, complaint)

When applying for after-sales service, you need to select the reason for after-sales service, and the reason for after-sales service is managed by the operation M terminal. After-sales reason and after-sales information are weakly related, so there are not many complicated businesses.

B1.M terminal (belongs to explicit operation)

  • Get after-sales reasons by page, get after-sales reasons by id, add after-sales reasons, modify after-sales reasons, delete after-sales reasons

 

B2.B side (belongs to explicit operation)

When the buyer B applies for after-sales, it will obtain the after-sales reasons. Here, the interface for obtaining after-sales reasons is placed in the after-sales module interface.

A2. After sales

B1.B end (belongs to explicit operation)

Here is a small bug. After the buyer’s B-end applies for a return and is approved by the store’s S-end, the product can be mailed, but the after-sales module does not display the store’s delivery address, but the back-end has this interface, but the front-end does not. show~

  • Obtain information on the after-sales application page, obtain a list of after-sales reasons, apply for after-sales, and cancel after-sales
  • Obtain after-sales service by page, view after-sales service details according to the after-sales order number, obtain after-sales log, submit return logistics information by the buyer, and obtain the after-sales receiving address of the merchant

 

  

B2.S terminal (belongs to explicit operation)

If logistics information is displayed, display the business address.

  • Get after-sales service by page, view after-sales service details, review after-sales application, seller confirms receipt, obtain merchant's after-sales delivery address, and view buyer's return logistics trace

 ​​​​​​

B3.M terminal (belongs to explicit operation) 

The refund will use the payment plug-in Payment here, and it will also involve the journal business

  • Obtain after-sales service by page, view after-sales service details, review after-sales application, refund offline after sales, obtain merchant's after-sales receiving address, and view buyer's return logistics trace

Guess you like

Origin blog.csdn.net/vaevaevae233/article/details/128306162