Funny enough I was just testing products with variation when I saw your message comming in.
I have tested with global attributes (e.g. the ones defined under Products->Attributes with respective translations of the attribute, and translation of all possible values the attribute can have) and custom attributes.
I can’t reproduce your problems. ??
My test scenarios:
1.) Global attribute named “Color” (EN) translated to “Farbe” (DE – 2nd language).
Values are “Blue” and “Green” (EN), respectively translated to “Blau” and “Grün” (DE).
2.) Custom attribute named “Size”. It can’t be translated.
Side Note: This is not a recommended configuration because of that, unless you use it for something international like EAN that doesn’t need translation.
Values are “XS|S|M|L|XL”.
Side Note: They don’t need translation, but you can add also the translations and then just select the ones in the product language to create the variations. Something like “Water|Wine|Wasser|Wein”.
When I create the translation, it works fine. On scenario 2.) all date is copied to the translation but you need to manually assign the Variation name because Polylang doesn’t know the relation between the words. So – works as designed!
Creating order does decrease stock of the variation in the default language and the translation.
I thinking you are configuring wrongly the variations or your setup may have some corrupted data.
I have talked to other developers and users using the plugin and it works for then as well.
If you can, try a fresh setup of WP + WC + Polylang + Woo-Poly and see if the problem still persists.
Or (may start with this one) disable all plugins except WC, Polylang and Woo-Poly, to test if some other plugin may be causing the issue.
