# Product price complement blueprint **URL:** \ **Category:** Ideas\ **Tags:** sales\ **Created:** [December 9, 2022, 7:45am UTC](https://discuss.tryton.org/t/product-price-complement-blueprint/5749 "2022-12-09T07:45:33Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![2cadz](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/2cadz/32/130_2.png) [@2cadz](https://discuss.tryton.org/u/2cadz)\ **Post date:** [December 9, 2022, 7:45am UTC](https://discuss.tryton.org/t/product-price-complement-blueprint/5749/1 "2022-12-09T07:45:34Z")
## Rational It sometimes happens that the selling price including VAT of a product has no direct relationship with the price excluding VAT. Similarly, the selling price of different variants of the same product may be different and result from various combinations. ## Proposal I suggest creating the following fields: - product.template - product.product The base price of a variant before the application of the tariff will be: - if a Tax Included Price List is selected: - if a Tax Excluded Price List is selected : ## Implementation Addition of 2 modules to keep independence and not to impose the presence of fields in the product sheet : - product\_retail\_price - product\_markup\_price For adding and managing the 2 respective fields. ---
**Author:** ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)\ **Post date:** [December 9, 2022, 8:03am UTC](https://discuss.tryton.org/t/product-price-complement-blueprint/5749/2 "2022-12-09T08:03:11Z")
> [@2cadz](#): > > retail\_price : on the model of the list\_price field, this price will be a price including tax and will serve as the base price during a sale with a price list including tax. Gross price already exists in `sale_point` module. > [@2cadz](#): > > markup\_price : supplement that will be added to the template price (list\_price or retail\_price depending on the selected price list) of the item to give the base price of the variant. For me it is not the only way to modify a price per variant, it could be done with a percentage for example. So for me there are too much possibilities that I prefer to stay as customization. ---
**Author:** ![2cadz](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/2cadz/32/130_2.png) [@2cadz](https://discuss.tryton.org/u/2cadz)\ **Post date:** [December 9, 2022, 10:20am UTC](https://discuss.tryton.org/t/product-price-complement-blueprint/5749/3 "2022-12-09T10:20:13Z")
> [@ced](#): > > Gross price already exists in `sale_point` module. Does not work with classic sales and with tariff. Maybe detach it from the point of sale to make it a separate module. > [@ced](#): > > For me it is not the only way to modify a price per variant, it could be done with a percentage for example. So for me there are too much possibilities that I prefer to stay as customization. Yes there are a lot of possibilities. Many are supported by price lists, in particular all those that have a “calculable” relationship with an existing price, there are still cases without this type of relationship. ---
**Author:** ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)\ **Post date:** [December 9, 2022, 12:31pm UTC](https://discuss.tryton.org/t/product-price-complement-blueprint/5749/4 "2022-12-09T12:31:28Z")
> [@2cadz](#): > > Does not work with classic sales and with tariff. Maybe detach it from the point of sale to make it a separate module. I do not see a use case where selling tax-included which is not a B2C sales which is the goal of the POS. ---
**Author:** ![2cadz](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/2cadz/32/130_2.png) [@2cadz](https://discuss.tryton.org/u/2cadz)\ **Post date:** [December 9, 2022, 1:44pm UTC](https://discuss.tryton.org/t/product-price-complement-blueprint/5749/5 "2022-12-09T13:44:04Z")
> [@ced](#): > > I do not see a use case where selling tax-included which is not a B2C sales which is the goal of the POS. For me the POS meets a specific need: the products, the seller and the customer are gathered in the same place at a given moment. There remain all the other cases where it is necessary to manage a sale as in B2B but with B2C prices. ---
**Author:** ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)\ **Post date:** [December 9, 2022, 10:40pm UTC](https://discuss.tryton.org/t/product-price-complement-blueprint/5749/6 "2022-12-09T22:40:58Z")
This is already manageable with price list including taxes. ---
**Author:** ![2cadz](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/2cadz/32/130_2.png) [@2cadz](https://discuss.tryton.org/u/2cadz)\ **Post date:** [December 12, 2022, 3:29pm UTC](https://discuss.tryton.org/t/product-price-complement-blueprint/5749/7 "2022-12-12T15:29:54Z")
Ok, so I haven’t found how to set a quantity discount on the gross\_price in a price list. ---
**Author:** ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)\ **Post date:** [December 12, 2022, 3:37pm UTC](https://discuss.tryton.org/t/product-price-complement-blueprint/5749/8 "2022-12-12T15:37:43Z")
Indeed sale point does not extend the price list module to add the gross price in the evaluation context. This is quiet logical as sale point is not designed to work with price list (future improvement should make sale point working with promotion). But again I think your requirement is specific because we can not implement all the possible way to compute a price. ---
**Author:** ![2cadz](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/2cadz/32/130_2.png) [@2cadz](https://discuss.tryton.org/u/2cadz)\ **Post date:** [December 12, 2022, 4:20pm UTC](https://discuss.tryton.org/t/product-price-complement-blueprint/5749/9 "2022-12-12T16:20:27Z")
> [@ced](#): > > because we can not implement all the possible way to compute a price Yes like now, completeness was not the goal, just allow a few more possibilities … But I understood, it will be customization.