Try our conversational search powered by Generative AI!

TaxCategoryId different for different markets



As I can find in the APIs, I can only set TaxCategoryId on variation and not on price. 

If I'm operating with different markets - and the same product has different tax codes for different markets, how could that be set?


Product A 
MarketID = 1 - TaxCode = 3
MarketID = 2 - TaxCode = 3

MarketID = 1 - TaxCode = 3
MarketID = 2 - TaxCode = 4

In this case it uses a common tax code for Product A - But product B have a special tax in market = 2. 

How can I set that through the API?

/ Thomas

Nov 22, 2017 14:12

The tax categoryid is per SKU, and it's market-independent. So in your case I would suggest to have two SKUs, one for each market. 

Nov 22, 2017 14:33

I really don't think different SKU per market is good enough.

The SKU is usually a unique entity in the ERP system and in analytics, so dealing with a different SKU-code in EPI, connected to the market does not seem like a good idea. :)

A good example here is a book-store (Which can contain hundered thousands of books). In Norway and Sweden we have the same tax-rates on general goods. 

In Norway we have 0% vat on books, while in Sweden, we have 25 VAT.
But books that contains a CD will in Norway also have 25 VAT.

This means that we will duplicate the size of our catalogue if we have two SKUs per book. 

Edited, Nov 22, 2017 14:49

There is no need to dublicate SKU:s.

You need to setup the two tax categories correctly though:

Tax category VAT in Sweden VAT in Norway
Books 25 0
Books with CD 25 25

Have to be done in Commerce Manager, it isn't available in the new UI yet as far as I know:

Commerce Manager->Administration->Catalog System->Tax Categories - for creating the categories
Commerce Manager->Administration->Order System->Tax Configuration - for everything else

Yes it can grow horribly complex with all the different categories to match all possible markets, but that is what support there is.

Nov 22, 2017 17:19

I know that opportunity, Erik. But it, as you say, it can be horribly complex.

When the products are imported the ERP-system, it is much easier to connect it to the price (As it is in most ERP-systems I've been working with) - Then we don't have to make mappings from the ERP-system-codes to custom codes in EpiServer.

So it is supported, but I really think it should be redesigned - since it's not a good solution.

Nov 23, 2017 8:01

Redesign is more of a feature request than a commerce question. wink

To my knowledge there is no way to extend prices with custom fields, the only field you could possibly hijack is the Sale Code one and that only if all your prices are available to all customers so that the field isn't in use.

It would require custom logic for loading the prices thou, episerver library classes assumes you aren't using that field for "all customers".

Although, quite frankly why can't you add a custom CultureSpecific property for the VAT rate on the SKU? Market!=Culture?

I guess you could have an non-translated dictionary with the values in that case.

Nov 23, 2017 12:26
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.