Hi,

I posted a module in the contribution directory that add tax to product price when you display them.

Basically, you create your product managing prices excluding taxes and you select for which roles you have on your website which can see price including taxes and which can see price excluding taxes.

It was wrote on the begining of ubercart, maybe it is outdated now, I don't have time to upgrade my ubercart installation. It works on beta 5 for me, don't know for newer version.

I will post here the only solution I've found, which is rather laborious, but which may be of use to others who find themselves in the same situation.

After looking through *many* postings and suggestions, I found that there is a "COMPUTED FIELD" type for CCK. This allows us to create a field which can use php code to automatically compute a value to be displayed in a node. It can use for source any value that your php code can access in Drupal, including other fields in the node.

After downloading, installing and enabling the Computed Field module:

1) go into your Content Types list, and click on "Product", to edit the Product Type, then on "Add Field"
2) add a new field, of type "Computed" - name it anything you wish (I named mine "price_inc_tax"). Click Submit to create the field.
3) You will now be in the field configuration page. In the "Computed Code" field, add:

4) in the "Display Format" field, add:

5) if you want this field to be available to your Views, select "Store using database settings below" - the calculation results have to be stored in the database for Views to be able to see them. I saved it as data type "float", and data length "8,2" (just in case my customer wants to sell things worth hundreds of thousands of dollars...)

That's it, it should work.

The calculation is only performed when you click SUBMIT on a product's Edit page, so in order to see the results in your existing products, you will have to re-submit them, one by one... or perhaps someone has a better suggestion?

Last of all, the new field does not sit nicely with the fields being displayed by Übercart's default product template, so you may have to override the template with your own - instructions for doing that can already be found elsewhere!

I hope this info will be of use to others.

It seems I was too quick to think that using a Computed Field would solve this problem...

While the computed field displays the inc. tax price without any problems on the product page, in order for the rest of Übercart to use it, changes would have to be made throughout the entire shop - ie., on the cart display pages and block, product listing pages, etc. Far too many changes.

Perhaps I am approaching this problem from the wrong angle?

It has now occurred to me, that it might be easier indeed to just list the inc. tax price as the product "sell price" - this would make the product pricing correct throughout the entire store, for our purposes in Australia. Then, the only thing missing would be a LINE in the final order, that would list the tax component (= tax total) being paid.

In order to get this functionality, we would need a module *exactly* the same as the current "Tax" core module, with the only difference being, that it would NOT ADD the tax to the final order.

I believe this would provide a solution to all of us in countries where catalog prices have to be inc. tax - ie., Australia, Europe, and many other parts of the world outside the US.

This is probably a trivial solution, which someone with a bit of knowledge of the Übercart framework could implement by making few and minor changes to the existing "Tax" module.

Would anyone be willing to tackle this project? zmove?

Al, thanks for pointing out some possible problems.

The current "Taxes" module *can* be configured (via its connection with workflow-ng) to take into consideration the order's billing or shipping address when applying the tax. It is possible to configure it, for instance, that if the billing address is outside Australia, then no tax is to be applied - so it already caters for the case when a customer wants to sell outside Australia.

I do not want to switch off the tax system. It would be great if it could work just as it does right now, with the sole exception being, that I don't want it to ADD the tax to the order at the end. I still want it to calculate it, and display it to the user during checkout, and on invoices and receipts, but I don't want the tax amount to be ADDED to the order final amount.

Ideally, at this stage, if we could just have a checkbox in the tax rule for a tax, that would let us specify "add this tax to order total" (or not!), then that would solve my immediate problem.

This would not be an ideal solution, however. The main problem I can see at the moment with the way Übercart handles tax is the fact that tax seems to be order-based, rather than product-based. In many countries around the world, different products attract different tax amounts, and these have to be calculated and shown individually to the customer. Even in Australia, where there is only 1 tax (GST) with one simple tax rate (10%), we do have businesses who are partially tax-exempt - like health professionals. In these businesses, people often have to charge GST on some products/services, but not on others. Übercart, at this stage, would not be a good solution for these customers. I suspect that in most of Europe this would be a big problem, too, as generally in most countries there are more than 1 tax rate that can apply to specific products.

It seems to me, however, that this would require a change to a few modules in the core - ie., it would require a change in the way products and orders are handled, and in the entire tax calculation system. I do think that this *is* necessary, for Übercart to fully support countries outside the US, and I hope that there are already plans for such changes to occur in the near future.

For my *immediate* needs, however, the simple change described for the "Taxes" module would already be enough to let me continue!

Hi teksestro
I've been digging around in the code, and I think I have found all the places that would need to be changed to make prices tax-inclusive. These are just the functional changes, assuming you wanted to HARD CODE all prices to be tax-included, which is something I'm considering doing for a site I'm working on now. There would be cosmetic changes needed too which I haven't included here: some of the text in the panes and paypal screens would need to change.

Functional areas that would need to be changed:
In uc_taxes.module, the uc_taxes_action_apply_tax() computes the actual tax amount. Since prices are tax-inclusive for you, you'd need to change the code to calculate tax in this way instead:
Tax = Gross - ( Gross / (1+Rate) )

In uc_taxes.js, the getTax() function calls the set_line_item to store the tax details. One of the parameters is 'summed' - if this is set to 0 then the tax amount isn't included in the total.

In uc_taxes.module, the uc_taxes_line_item function would need to add the following at the end of the line item array that is returned:
'calculated' => TRUE,
'display_only' => FALSE,

In uc_taxes.module, the uc_line_item_tax function would need to create the call to set_line_item with 0 (zero) as the second to last parameter (to indicate the tax shouldn't be summed).