3 ms·
> #3, maintaining old pricing I copy the entire product into the order. The thing one buys should be the thing on the screen when the decision is made. Poor pi
by 6510 3y ago
> #3, maintaining old pricing
I copy the entire product into the order. The thing one buys should be the thing on the screen when the decision is made. Poor pictures, description with typos, wrong categories, old/wrong pricing etc
- vidarh 3y agoYeah, that can be a good approach. Including all the data defining the old product in an unchanging way was one of the sticking points that led to the creation of my team at Yahoo. The US team didn't think twice about changing invoice templates for examples, while the European finance teams broke out in hives at the thought of anything changing on already issued orders, much less invoices. I spent three years holding the fort to ensure the US team didn't take over invoice processing on our behalf until they could guarantee at least the invoices were unchanging...
- swader999 3y agoEverything has to be historically available. Think about returns and redoing the entire period and so on. Sometimes even the old code if you want to be perfect.
- wredue 3y agoThis approach is generally okay. It at least keep your mandatory data for audit around. One issue with it is that it often ends up forcing you to build out a lot of backward compatibility into your audit system as things change.