Hello, This may or may not be what you are looking for. My store applies GST and QST for orders shipping to Quebec and only GST to orders shipped to Canada. Right now I calculate the total tax on the order but I think I can also get tax data for each item ordered.
I am using a modified version of this app: http://bitbucket.org/benoitcsirois/satchmo-canadian-tax If you want to see my adapted version, it is here: http://github.com/davecap/satchmo-canada-tax In my order details template I show the taxes: ... {# no tax #} {% if order.tax == 0 %} <tr> <td> </td> <td align="right">{% trans "Tax" %} (Not incl. VAT)</td> <td>{{order.tax|currency}}</td> </tr> {% else %} {# Canadian tax #} <tr> <td> </td> <td align="right">{% trans "Tax" %} ({% for tax in order.taxes.all %} {{ tax.description }}{% if not forloop.last %} &{% endif %} {% endfor %}):</td> <td>{{order.tax|currency}}</td> </tr> {% endif %} ... It will show a line like this: Tax (GST & QST): $... or Tax (GST): $... but you can probably figure out how to put each tax on its own line. - David On Jul 20, 2:32 pm, pmetras <[email protected]> wrote: > Hi, > > The OrderTaxDetail model gives the taxes applying to an order. The > OrderItem keeps the amount of taxes for an order item. > > In Canada, we need to display the detail of all taxes to the customer. > So an order with 2 items would look like the following (we don't need > to display the taxes for each items on the invoice, only for the taxes > total, but it helps to show what the item model must store): > > Item1 Price Tax1 Tax2 Total for item1 > Item2 Price Tax1 Tax2 Total for item2 > ----------------------------------------------------------- > Total: Amount$ Tax1 Tax2 Total to be paid > > The OrderItem gives the amount (Tax1+Tax2) for each item of the order. > Our problem is that we need to create an OrderItemTaxDetail to keep > the amount calculated for each tax for an item. This generalization > would have impacts on the Order model, the TaxProcessor and all > existing tax models would have to be adapted, create a new tax model > or adapt the area one, change tags for displaying the invoice, and > probably touch other parts of Satchmo I don't know. This change would > have a big impact on existing stores, because it needs to upgrade the > database tables. > > On the other hand, we could just add a Tax2 field to the Order model, > and create a new tax processor aware of this new field. The changes in > Satchmo would be to the same places but somewhat limited. The database > upgrade would be a simple column addition. But I feel this is just a > hack. What would we do if some country needs a 3 levels tax process, > for instance federal, state and county? > > From my point of view, it seems the first solution is better in the > long term. But it requires us to change the core of Satchmo, and we > want to be able to follow the version upgrades to keep our store as > vanilla as possible. So it means that our changes would have to get > into the core code. But as I said, the upgrade path would be more > difficult for existing stores. > > What do you think? > -- > Pierre Métras -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
