My client supports two currencies USD and AUD.
Purchasers based in Australia will be charged in AUD , and have tax added.
The rest of the world get the USD price - no taxes.
I have implemented this using geolocation and only enabling the pricing appropriate to the user’s presumed location. Everyone can see both sets of prices, but any one purchaser will only have one set enabled. (No snipcart button at all on the disabled set of prices)
Snipcart will see, for an AUD purchase,
data-item-taxable="true"
data-item-tax-rate="0.1"
data-item-taxes="GST"
data-item-has-taxes-included="true"
data-item-price="{"aud":"1650.0"}
and for a USD purchase of the same item
data-item-taxable="false"
data-item-has-taxes-included="false"
data-item-price="{"usd":"1500.0"}
On his first test of the live system, my client has had his purchase rejected with “An attempt to create an order with invalid products has been made.”.
I am concerned that this is a by-product of having two pricing systems. Any thoughts?
I loaded the products via the URL today, and they have loaded with their USD prices, so presumably the snipcart process ran with a non-australian ip.
If a user successfully purchases the product from Australia what will happen in the products table? Two copies of each product? Merged data showing both prices (fantastic).?
thanks,
Anita Graham
(I am waiting for him to confirm one or two other questions I have.)