Hi @galbaras
We have tested the scenario on our end by creating a Google Local Inventory Feed using the TXT format and found that the formatting appears correctly according to the field names recommended by Google Merchant Center. Please refer to this screenshot: https://snipboard.io/3umcYj.jpg
This suggests that the issue may be caused by a conflict with another plugin or a custom code snippet modifying the output data. We recommend performing a conflict test by:
- Deactivating all plugins except WooCommerce and Product Feed PRO.
- Switching your theme to Storefront.
- Refreshing the feed from the Manage Feeds section in the WordPress admin panel.
- Reviewing the feed output again.
If the issue continues, please let us know, and we will be happy to help you in any way.
Thanks!
As a workaround, I replaced the plugin’s default fields for these 2 fields with custom fields named according to Google’s guidelines, and my feed was then accepted.
I then created a new feed, just to test what happens, and it was created correctly.
Importantly, the old feed only shows fields like “Price” and “Store code”, while the new one has “g:price” and “g:store_code”.
I’d say that existing feeds were not updated by the plugin with changes to the feed type template. There should be a function to do this and the plugin should check if this needs doing and offer the migration to the site admin.
In fact, the new feed was greated with 4 “g:” fields, and when I try to add new fields, no other “g:” fields are available for selection. And having “g:” fields is strange for a local feed TXT template.
-
This reply was modified 11 months ago by
Gal Baras.
Hi @galbaras
Thank you for the detailed update. We’re glad to hear that replacing the plugin fields and creating a new feed helped resolve the feed formatting issue, especially with Google-compliant field names like g:price and g:store_code.
Regarding the old feed still showing outdated field formats such as “Price” and “Store code,” please ensure that the feed has been refreshed from the Managed Feeds section. In most cases, refreshing the feed triggers an update that aligns it with the latest feed template and field mappings.
Thanks!
I’m not sure what “refreshed” means. The feed is recreated daily, and I’ve recreated it manually (using the dashicons-update icon) many times without any changes to the headings. Did you mean something else?
The new feed was created with 4 “g:” fields, but when I edit it, those fields are not included in the field selection. There are also no other “g:” fields available for selection.
And having “g:” fields is strange for a local feed TXT template, because they are only relevant for XML.
Hi @galbaras
If you are creating the Google Local Inventory Feed using the TXT format, the feed will not include any “g:” fields. As proof, I’ve already shared a screenshot and am sharing it again for your reference: https://snipboard.io/3umcYj.jpg
If your TXT feed is showing “g:” fields, it’s likely due to a conflict on your website or because you’re using an outdated version of the Product Feed PRO plugin.
Please follow the instructions I previously shared to perform a conflict test on your website.
Thanks!
I checked again, and you’re right. Not sure what happened last time. I think we’re good.