Alexander, You can say that the system implemented in that way. But, if list price of a product exists then system know about the pricing structure that list price (price to display) is may be different from the actual sale price. So system go for the calculation otherwise not.
List Price setup is essential to run the current price rule engine. If you required to change it then you will need to do customization for that. It is just my personal thought that, if price rule engine active on certain condition and if that condition is setting the list price then I think it is fine. Because always go for the calculation is also not a good idea. All the other price types are there for some specific purpose, so I would say to not overlap their purpose, should be used for which they are defined. Anyways, you can override the price calculation service and change the implementation as per your needs. -- Rishi Solanki Manager, Enterprise Software Development HotWax Media Pvt. Ltd. Direct: +91-9893287847 http://www.hotwaxmedia.com On Fri, Sep 14, 2012 at 12:43 PM, Reelsen, Alexander < [email protected]> wrote: > Hi > > 2012/9/12 David E Jones <[email protected]> > > > > > The price calculation starts with the list price, so you'd have to change > > that too. > > > What do you mean by "starts with"? > A price rule which changes the price of a product because of the party and > the product id, is not in need of any list price - not seen from the source > code, but rather from a logic point of view I do not see why there is a > list price needed (except that it is implemented this way currently). You > could use the default price for this as well, or? > > > --Alexander >
