Hi @darczello83,
I can offer two solutions:
1. Use our EAN when creating the XML file. The exact steps will depend on the plugin you are using for creating the XML, but generally, there should be something called “Custom fields” or similar, where you should be able to select our EAN field. Sometimes these plugins will ask for the field key – it’s _alg_ean
in our case. If you could tell me which plugin you are using, I could tell you the exact steps then.
2. You can use WooCommerce export/import tools as a workaround. I.e. you export all products to a CSV file (via “Products > Export”) and select “ID” and “EAN” fields there (in the “Which columns should be exported?”). Now after that, open the CSV file, and replace the column name (it’s in the first row) from EAN
to meta:_gtin
(you may need to replace the _gtin
with your actual GTIN key). Then import the same file (via “Products > Import”) and check the “Update existing products” box there. Hope you get the idea.
I would recommend solution nr. 1 though – this way you won’t have to perform any additional actions when you’ll generate EANs for your new products in the future.
Please let me know if you have any questions, or if both solutions are not good enough, and I’ll come up with something else.