Community mailing list archives
Re: Prices incl VAT in ecommerce and POSby
2014-12-12 15:38 GMT+01:00 Ric <email@example.com>:You can handle channel with price list.I think the real question is how prices are being formed.Either you want to focus on the psycological aspect of the price and you want to start by the Public price and you expect the VAT to be includedOr you want to focus on your margin so you start by the Cost Price and you add your margin and VAT on top but without actually caring about theUsing Public Price or Cost Price seem to me quite OK.Only trouble with v8- it is not posible to declare a fiscal position AND pricelist by default for each POS.Actually, There is a PR in OCA / POS project to manage Pricelist and fiscal position in POS V8 : https://github.com/OCA/pos/pull/6- it is not possible to set the pricelist on each invoices (it is only possible on sale orders)Af.Hello,My 2 cents:1. Introduce the concept of channel (B2B National / B2B Export / eCommerce,...) that you can enter in the sales orders.2. Public prices are defined by product+channel3. Taxes are defined by product+channelFiscal positions should be used for concepts such as Tax exemptions by the customer. Do not need to be changed at all. Just make sure that all possible source taxes for every channel the partner is involved in are mapped.Regards,Jordi.>>: > > Anyone has a better idea? > > Well, Fabien, not sure, but the problem is, as you said, the mix, so > remove the two way approach and always use one method (net approach > most obvious) and make it possible to choose how the price will be > displayed in any other context by using always the same way of > computation to achieve this. > > I guess this has already been talked of, but I do not know why this > can not be achieved and who will be cut off by doing this that it > was not done a long time ago?! > > My five cents. > > Wolfgang > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59 > Post to: mailto:firstname.lastname@example.org <mailto:email@example.com> > Unsubscribe: https://www.odoo.com/groups?unsubscribe > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59 > Post to: mailto:firstname.lastname@example.org > Unsubscribe: https://www.odoo.com/groups?unsubscribe > -- Fabien Pinckaers Odoo Founder Phone: +126.96.36.199.00 Web: https://www.odoo.com Twitter: @fpodoo Instant Demo: https://odoo.com/startSebastien, That's exactly what the standard modules do. We do that for a lot of customers and it does not require a specific module. But the problem I'd like to fix is that it's complex for end users. Using fiscal positions, you can select taxes with price include/exclude so that you have a different way of working in both SO and eCommerce. That's what we do for our SaaS customers but it's not a good usability. On 12/12/2014 10:52 AM, Sebastien Beau wrote: > Hi all, > We already have a working solution for managing inc and exc tax in Sale > order (can be extended for the POS) > > We will document it really soon. But very quickly in 3 lines > - you can define if a price type is in taxe inc or not > - you can define on a fiscal position if the price should be in taxe inc > or not. > - than depending on the position fiscal selected on the sale order Odoo > will convert the unit price and use the right tax > > Exemple > > French Case : I manage my price in taxe include (price type tax include) > > Case 1 : french customer price tax include => position fiscal in tax include > - no conversion is done the unit price is the unit price of the product > (I do not map the tax) > > Case 2 : french profesionnal => position fiscal in tax exclude > - conversion of the unit price (tax inc => tax exc) > - mapping of the taxe in order to use the tax-exc > > Case 3 : belgium professional customer => position fiscal in tax exclude > - conversion of the unit price (tax inc => tax exc) > - mapping of the taxe in order to use the 0% tax (as it's an export) > > An OCA module (here https://github.com/OCA/sale-workflow/pull/63) is > waiting to be the merged but for now is blocked as we need to refactor a > little the Odoo core, a merge have been done and is in the pending state > : https://github.com/odoo/odoo/pull/3717. > > Sorry (I am very busy today). But I will be back when some documentation > will be done > > > Note : this module may not fit with every country (at least it should > work in all europe) contribution and review are welcome ;) > > > 2014-12-12 10:15 GMT+01:00 Wolfgang Taferner <email@example.com > <mailto:firstname.lastname@example.org--
Jordi Ballester Alomar
Tel: (+34) 629530707
Twitter: @jbeficent_erp | Skype: jordi.ballester
Este email contiene información confidencial. El contenido de la misma se encuentra protegido por Ley. Cualquier persona distinta a su destinatario tiene prohibida su reproducción, uso, divulgación o impresión total o parcial. Si ha recibido este mensaje por error, notifíquelo de inmediato al remitente y borre el mensaje original junto con los ficheros anexos.
This message contains confidential information and it is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete it from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.