X-Cart forums

[johngwms]

I have just encountered an issue with the Google Product Feed Module and would be interested to know if anyone else has experienced it.

I am getting about 6% of my products rejected for submission to the Google Merchant Center because the XC module Google Product Feed module, by default, sets the field "identifier_exists" in the feed to false. This implies that Google is already aware of the EAN reference for these products

I have the EAN defined as a custom field in X, which I use when submitting to Amazon, but there doesn't seem to be a mechanism of getting XC to include this in the Google Product Feed.

Any thoughts?

[cflsystems]

Use this https://market.x-cart.com/addons/system-fields.html to populate the field then you can set it up in the Feeds module settings (maybe / maybe not, not sure what you can set as fields there). Otherwise if you keep the EAN as product custom field you will have to code custom module to tell the Feeds where the value for that field is.

[johngwms]

Yep, tried that Steve, but it will only populate UPS and ISBN, not EAN.

I could try the MPN field though.

Also, this module does not seem to add the fields as Global Attributes, so I am unable to import them through a csv file. With over 4,000 products, I'm not doing it manually.

[cflsystems]

The module adds 2 new fields to products and variants. What you call them it doesn't matter. You can call the UPC field UPC or EAN or whatever other label suits you. It's just a text field to hold some value.
Same for the Vendor/Mnfr field.


The point is to use it as it is ready module.


And yes you can most certainly import these values using csv file. These are not attributes, they are product fields. So you simply use the product import.


You can assign the UPC and the Vendor # to whatever field you want for the feed.

[johngwms]

OK, that's encouraging.

For me, the use of EAN, UPS etc is important, at least it's important to other organisations such as Amazon because they need to know what system is being used to validate the entries.

If you saying that Google doesn't care, then that's fine for now.

I appreciate your take on this.

[johngwms]

Steve

The product field names that are used are upcsbn and mnfVendor, and indeed I am able to export and import them.

I have discovered, whilst importing that the field mcfVendor is a text field that can contain any value.

The upcsbn field is also a text field but it must contain unique values.

Whilst importing I discovered that many of my EAN numbers are not unique, something I would otherwise have not discovered.

[cflsystems]

Well it is not that Google doesn't care. If the Google feed expects certain field to hold certain value it will complain if it doesn't. However UPC and EAN in general represent unique article identifier. They are used in different parts of the World and sometimes interchangeable. I think. So Google asks you to have 2 out of 3 identifiers and whether you supply UPC or EAN code won't matter.


And yes this product identifying code must be unique. You cannot have 2+ products with same identifier.


https://support.google.com/merchants/answer/7052112?hl=en - search for "gtin"