Tax inclusive catalogue, tax exclusive checkout

[justinhill]

I'm trying to figure out if the system can support tax-inclusive prices showing in the catalog but the checkout showing as per tax-exclusive pricing.

I've switched to tax-inclusive in the catalog (partly because of Actinic's weird rounding) but I'm seeing some US buyers bouncing away from the checkout and I suspect it's because the total shown has the inclusive figure for the product one page one, until the they enter a country and state and go to page two.

Before I went to tax-inclusive, checkout page one showed the exclusive price, then the VAT, then the total. Now it shows the inclusive price, then the total, then the VAT. The invoice is printed with tax-exclusive figures for the the product; can checkout do the same?

Justin

[leehack]

The weird rounding disappeared in v9 AFAIK, what are you experiencing as weird?

[Mike Hughes]

If you're entering prices inclusive of tax then as standard Actinic will display prices inclusive of tax in the cart and checkout.

You might be able to change this by changing the variable the cart and checkout is calling.

Alternatively, if you want to show tax exclusive prices then entering prices exclusive of tax might work better for you.

You can select from a wide range of rounding options per product so that alone needn't be a reason for changing how you operate.

Mike

[justinhill]

The weird rounding disappeared in v9 AFAIK, what are you experiencing as weird?

'Weird' might be a bit unfair. I do my pricing in a giant Excel model and the macros always target an "£x.99" or "£x.49" inclusive price. My accounts system and Excel can agree about what the exclusive version of this price should be, but if I feed it to Actinic it often won't agree.

For example, £30.83 x 1.2 = 36.996 i.e. the VAT is £6.166 and the rules say we can round or truncate away from the VAT man's favour, making the VAT £6.16 and the inclusive price £36.99. Actinic won't do this - it will do a strict round, making the inclusive price £37.00. Trying to cheat it by knocking a penny off doesn't work because £30.82 x 1.2 is £36.984 which Actinic rounds down to £36.98. In other words, there is no exclusive price you could enter in Actinic that would produce an inclusive price of £36.99, because 36.99 / 1.2 comes to exactly half way between 30.82 and 30.83.

As well as not having my targetted price showing, it meant that the Google products feed I do (which also comes from Excel, not Actinic) didn't always have the same price as Actinic and I worried Google might eventually disallow those products. I could do the Google feed from Actinic but as my feed is already September 22 compliant including optional fields so I'd rather keep doing it the way I am.

It's entirely possible that this could have been fixed by a change in Actinic and I didn't know how, but because of it I decided to import tax-inclusive prices into Actinic and display them that way and for UK/EU buyers it's probably better anyway. I don't use the Actinic invoice; it's done in the accounts. Apart from my original thread starter, the only problem with this seems to be that Google checkout uses an tax-exclusive price generated by Actinic and so there's often a penny difference when people use Google checkout - which I just accept.

Justin

[justinhill]

If you're entering prices inclusive of tax then as standard Actinic will display prices inclusive of tax in the cart and checkout.

You might be able to change this by changing the variable the cart and checkout is calling.

Alternatively, if you want to show tax exclusive prices then entering prices exclusive of tax might work better for you.

You can select from a wide range of rounding options per product so that alone needn't be a reason for changing how you operate.

Mike

I was probably not experienced enough with Actinic to discover the way to do it but my conclusion at the time was that using tax-inclusive prices was the easiest way forward. The majority of my buyers are retail so not interested in tax-exclusive prices.

Your comment about 'changing the variable' is very interesting. This is what I'm hoping to discover.