I have noticed that the database design is not efficient and update proof. All the columns that can be calculated during execution are hardcoded. Which seems like waste of space as well as cause issues with updated.

Let me give you an example.

In customer returns, you are storing totals. As per my previous bug report where taxes were not properly calculated for “inclusive” taxes, the update will not “fix” the old records. It will simply work on future records only.

In my opinion, all totals and tax calculation fields must be “CALCULATED” on the fly and should not be hardcoded.

PS: This also makes correcting wrong figures due to bugs, very hard.

I understand that at this point, it is very hard and practically impossible to make database changes. I am reporting this so that you can consider the same for upcoming major release.