How to design the order review process more reasonably? ? ?

Foreword: Please give me some advice on how to design the order review process to be more efficient and reasonable. I would be very grateful if you could design it in detail.

System role

Store sales, store manager, order reviewer, financial specialist, order placer.

Process

Pass the process

Store sales entry order information > Submit > Store manager review > Order reviewer review > Financial review > The orderer decides whether the order can be placed, otherwise it will be returned.

Return Process
The store manager, order reviewer, finance, and order placing can all return the orders that have been submitted for review; only the roles that have reached a certain step in the review can return it.

The design model of the current system (it feels stupid as hell)
The current system gives the order a status field, 1 means unapproved, 2 means approved by the store manager, and so on.
Then make logic based on this. For example, only orders with status=3 can be seen in the financial review order list.

Asking for advice

1. How to design this kind of process review better.

2. Consider possible factors, such as the leader saying that there will be no need for store manager review in the future; an review link can be removed efficiently and safely.

Reply content:

Foreword: Please give me some advice on how to design the order review process to be more efficient and reasonable. I would be very grateful if you could design it in detail.

System role

Store sales, store manager, order reviewer, financial specialist, order placer.

Process

Pass the process

Store sales entry order information > Submit > Store manager review > Order reviewer review > Financial review > The orderer decides whether the order can be placed, otherwise it will be returned.

Return Process
The store manager, order reviewer, finance, and order placing can all return the orders that have been submitted for review; only the roles that have reached a certain step in the review can return it.

The design model of the current system (it feels stupid as hell)
The current system gives the order a status field, 1 means unapproved, 2 means approved by the store manager, and so on.
Then make logic based on this. For example, only orders with status=3 can be seen in the financial review order list.

Asking for advice

1. How to design this kind of process review better.

2. Consider possible factors, such as the leader saying that there will be no need for store manager review in the future; an review link can be removed efficiently and safely.

Just write a document and indicate the ID corresponding to each review. Set struts to 3 directly after submission without review by the store manager, and set the review status of the store manager in the previous database to the next review status.

It’s better to make permission control, just like the permission menu.
Make a check option for each status of the order, and check the corresponding check when setting the role. When displaying data, the corresponding SQL conditions are easy to write.