Aside from the great difficulties in re-coding many elements, this does not make commercial sense in the world of e-business.
Once an order is placed and paid for, the process to "update" it will be virtually identical to the process to simply place a second order.
The difficulties you will have (in writing programming) are extensive, and probably not worth the effort.
Consider for example, just one small issue:
Once the original order is submitted and paid for, how is the programming going to deal with what has already been paid for (and charged to the customer), compared to what alterations the customer makes to his order? If he orders 5 t-shirts, then pays for them - then wants to update it to 4 t-shirts, you are going to need some system to not only refund the customer the difference, but put in place programming to re-stock the item (reverse the order process).
I wouldn't even try to attempt what you are suggesting. It can create enormous practical difficulties, as the example above seems to suggest.