On 29 Dec 16:52, Cédric Krier wrote: > Hi, > > I'm trying to solve a problem for price with tax included. > Generally, when companies work this way they store the price with tax > included on the product for example (could be the list price field). > So the problem is how to make it works on the current sale design. > > Here is my idea, we could create a new module > sale_price_list_tax_included (name to be reworked) which will add a flag > on the price list to announce it will return a unit price that should be > considered as tax included. > On the sale, when such price list is used, we reverse compute the unit > price without tax using the tax on the line (for which the tax rule has > been applied). > Normally, if we have enough decimal on the unit price, it should always > be possible to find such unit price. The number of decimal needed will > depend on the rate of the taxes of course and the quantity sold. > So if we change tryton's module to use a configuration parameter for the > digits (instead of the hard coded 4), a good value could be defined for > each company according to their use case. > > So what do you think about such module?
Instead of creating new module for this option, I modify the existing one because I think such behaviour of price list has a too big impact on any module that will rely on price list. So here is the issue with reviews: https://bugs.tryton.org/issue4446 -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
