Comment from tanya-soroka, posted on GitHub Feb 18, 2014
Hello @chrom, thank you for your question! Could you please provide a use-case of using history of the product price changes?
Comment from protechdeveloper, posted on GitHub Feb 18, 2014
Hi, I'm also interested in this feature, but maybe more about tracking several changes as well. E.g by having a version history. A version history would make it easy for us to modify a product description / price / image and other details, and see what perform best. It's easy to revert back if needed. In addition I would love to keep track on which user who does what. I think this should be considered for managing orders as well: tracking which user/person who complete the order.
Comment from philwinkle, posted on GitHub Feb 19, 2014
I can't see this being a core feature as there are many ways to track this yourself outside of your ecom platform. Keep a ledger, inspect the admin actions log; there are numerous ways of handling this. It would be trivial to code a module that kept track of when a price change occurred.
Comment from chrom, posted on GitHub Feb 23, 2014
Sometimes for the purpose of marketing is important to monitor the changes in the data item (description specified harakteritiki images) affect changes in the number of views and purchases of goods. Example:
Comment from davidalger, posted on GitHub Feb 16, 2016
@LoneRegister Please do not post self-promoting links. This is a channel for reporting technical issues and tracking feature requests, not for advertising!