Both prices show without tax

-- HikaShop version -- : 6.4.1
-- Joomla version -- : 3.10.12
-- Browser(s) name and version -- : Chrome 155.0

Hi!

The product prices display different prices depending if you are logged in or not.
But it makes no sense cause as you will see in the screenshots, i have added tax rate in the "Default tax category", added that tax category in the product, the product's price is the same in both fields "with or without tax", no access level in the prices and yet in the frondend you will see different prices when you are or not logged in.
I cannot find the issue for this!

Thank you

Hi,

The difference comes from the zone HikaShop uses to calculate taxes. When a customer is logged in, taxes are calculated with the country of their address (Greece, so your 24% rate applies and 19,35484 € becomes 24,00 €). When the visitor is not logged in, there is no address yet, so HikaShop uses the "Main tax zone" setting of the configuration instead. On your site that zone has no tax rule, so guests get the price without VAT.

Your backend screenshot confirms it: in the price edit form, "Price" and "Price with tax" both show 19.35484. The backend calculates the "with tax" value with that same Main tax zone, so when the two are equal it means no tax rate is found for it.

To fix it, go to Components > HikaShop > System > Configuration > Main tab, set "Main tax zone" to Greece (the country of your shop, the same zone as the one used in your tax rule under System > Taxes) and save. After that the backend will show 24 for "Price with tax" and guests will see 24,00 € like logged-in customers.

Also check that your tax rule under System > Taxes is published and that its zone is Greece (or a zone that contains Greece).

The tax zone of a guest is remembered in their session, so test the result in a private browser window (or after clearing your cookies) rather than in a window you already used on the site.

Okay i added a Main Tax Category, and i can see the tax now but there are different taxes depending the customer's location.
So now a product price has 24% tax but can the tax change based on the location at the checkout page?

Hi,

Yes. The "Main tax zone" is only used until HikaShop knows where the customer is: for guests on the product pages, and before an address is entered at checkout. As soon as the customer is logged in with an address, or enters / selects an address on the checkout, HikaShop recalculates the taxes with the zone of that address, so the cart and order totals use the tax rule of the customer's country.

For this to work, you need one tax rule per rate under System > Taxes (Taxation rules listing: www.hikashop.com/support/documentation/3...axation-listing.html ), each one with the tax category of your products, the zone it applies to (for example Greece with 24%, another country or a zone grouping countries with its own rate) and published. A customer whose country has no rule will pay no tax.

In Components > HikaShop > System > Configuration > Main tab, the option "Type of address used for tax" lets you choose whether it is the billing or the shipping address of the customer which decides the tax zone ( see www.hikashop.com/support/documentation/54-hikashop-config.html ). Your accountant can tell you which one applies to you.

Note that by default, the prices you enter in your products are prices without tax, so the price with tax changes with the rate: a 19,35 € product shows 24,00 € with the Greek rate and another amount for a customer from a country with another rate. If you prefer every customer to see and pay the same price with tax, whatever their country, activate the "Floating tax prices" option on the same tab: the prices you enter are then considered as prices with tax, and HikaShop calculates the tax amount and the price without tax out of them with the rate of the customer's zone. When you switch that option, the prices of your products are not changed, so you would then need to enter them with tax (24 instead of 19,35484 in your example), which can be done for all products at once with a mass action as explained on the configuration documentation page above.