Umbraco Commerce V17 - Product Variants vary by culture

Hi All,

Not sure If I’ve missed something or it’s not possible but can product variants be varied by culture? We have a product item which has the vary by culture on it and so does the variant field that sits on it. When I try to save in an individual language variants the backoffice throws:

“One or more property values specify a culture for an invariant property, or are missing a culture for a culture-variant property. This can happen when a property is inherited from a variant composition on an invariant content type, which downgrades it to invariant.”

Just want to know what the proper setup for language based variants would be if it is at all possible!

Thanks :slight_smile:

Hi @tommypippard

Apart from the Umbraco Commerce specific properties for price, SKU, etc, the product should just be a normal content node, so I would like to think variants are supported as an e-commerce site could be multi-lingual.

Are you referring to child node variants or complex variants?

Justin

Hi @justin-nevitech

I believe they would be complex variants, We have a preset for pattern & type. When the preset was created it would be fine in say English (United Kingdom) but when switching to German any changes made in German would apply to English. Then when I went in and allowed vary by culture on the variant field and parent product and tried again to make changes in different languages it errored.

Hi @tommypippard

Is this something that used to work, or is this a new build on v17?

Justin

New build on v17

Hi @tommypippard

I suspect that field does not support language variants as it is an Umbraco Commerce property editor and the variants are used internally in Umbraco Commerce and not stored as a normal content property.

I can’t find anything definitive to say either way, so it may be worth you raising it on their issue tracker so they can either confirm or look into it if it’s a bug.

All I can find is this reference:

Justin

Thanks for your help Justin. I’ll have a look maybe @mattbrailsford could confirm if this ever was added in v15?