d
Topic
vittiegrocer Member
Posts:
7
February 09, 2017

Populating Fields for the Google Shopping App

I'm having a great deal of difficulty populating the Google Shopping App fields.  And I'm having more difficulty figuring out why it is so difficult to accomplish this task in bulk.  I understand I can edit this information one-by-one but I have tens of thousands of products and I'd prefer to have this set up before I die.

So in an attempt to complete this process myself and demystify it for others, I'm going to lay out the data sources for all of the Google Shopping fields and appeal to the Shopify community for help in completing the mapping.  I am using ChannelAdvisor to send my data to Shopify.  ChannelAdvisor allows users to send up to 25 metafields to Shopify.  But the challenge I encountered was what to call the Namespaces and Keys of the those metafields in order for the Google Shopping App to automatically pull them.  Here's what I've discovered.  I'm just down to trying to figure out what namespace and key will send the MPN to the Google Shopping App - any ideas?

Google Product Category

  • Metafield
  • Namespace: google
  • Key: google_product_type

MPN

  • I HAVE NOT DISCOVERED HOW TO POPULATE THIS VALUE.  THE FOLLOWING METAFIELD FAILED
  • Metafield
  • Namespace: google AND global (both failed)
  • Key: mpn

Condition

  • Metafield
  • Namespace: google
  • Key: condition

Age Group

  • Metafield
  • Namespace: google
  • Key: age_group

Gender

  • Metafield
  • Namespace: google
  • Key: gender

Custom Label 0

  • Metafield
  • Namespace: google
  • Key: custom_label_0

Custom Label 1

  • Metafield
  • Namespace: google
  • Key: custom_label_1

Custom Label 2 

  • Metafield
  • Namespace: google
  • Key: custom_label_2

Custom Label 3

  • Metafield
  • Namespace: google
  • Key: custom_label_3

Custom Label 4

  • Metafield
  • Namespace: google
  • Key: custom_label_4
i
Replies
Posts:
8
Last edited February 14, 2017

Their own documentation says it can be done, yet it doesn't work:
https://help.shopify.com/manual/apps/apps-by-shopify/google-shopping/faq

In addition to the MPN not working, brand is not populated either. It doesn't look like you can control it via metafield either, it has to be with the products "vendor"...which is populated...but doesn't make it into the product data on Google Shopping.

So frustrating.

vittiegrocer Member
Posts:
7
February 14, 2017

Justin - thanks so much for your reply.  At least I know I'm not going crazy.  I'm so baffled as to why this is this isn't more straightforward.  I've contacted support and they either just refer me to the link you cited or they provide some contradictory information.  It's nuts.

Posts:
6
Last edited 17 days ago

This post pointed me in the right direction, thanks guys! Now I can also give back to the community by allowing you to access the MPN field (sic, capital letters!)

You can access it using the bulk editor:

https://example.com/admin/bulk?direction=next&edit=metafields.google.google_product_type%3Astring%2Cmetafields.global.MPN%2Cmetafields.google.condition%2Cmetafields.google.gender%2Cmetafields.google.age_group%2Cmetafields.google.custom_label_0%2Cmetafields.google.custom_label_1%2Cmetafields.google.custom_label_2%2Cmetafields.google.custom_label_3%2Cmetafields.google.custom_label_4

please note the capital spelling of the MPN field - apparently it is name sensitive, as metafields.global.mpn will not work, you have to use metafields.global.MPN

As information to anyone trying to debug the names of these fields:

this will give you something like this:

{"metafields":[{"id":(*),"namespace":"global","key":"description_tag","value":"This is a widget. do not buy.","value_type":"string","description":"Description of the product for search engines","owner_id":(*),"created_at":"(*)","updated_at":"(*)","owner_resource":"product"},{"id":(*),"namespace":"global","key":"MPN","value":"ah google shopping mpn 2","value_type":"string","description":"Manufacturer Part Number","owner_id":(*),"created_at":"(*)","updated_at":"(*)","owner_resource":"product"},

and so on.

(*) - edited for security purposes

my suggestion to make this thing more readable is to use Notepad++, and to use search and replace with Extended mode (supporting \n)

  • search and replace , with \n
  • search and replace { with \n\n

this will give you a nice more readable rendition of it, more useful for debugging.

Posts:
6
Last edited 12 days ago

Another input which might be helpful to someone else - this forum post was helpful for that:

https://ecommerce.shopify.com/c/shopify-discussion/t/how-to-edit-variant-meta-data-in-bulk-editor-485291

Editing Variants:

https://<youraccount>.myshopify.com/admin/bulk?direction=prev&edit=metafields.global.MPN:string&resource_name=ProductVariant&show=image,full_title,variants,sku

Thus it is possible to edit individual metafields for the variants.

metafields.global.MPN as a ProductVariant entry will not override the global Product entry.

Also it will not show up in my export to DataFeedWatch, even if I delete the master entry in the Product resource (set metafields.global.MPN to an empty string). I suspect I have to use a different metafield, and route in DataFeedWatch accordingly.

also useful for filtering for certain products:

&query=<name of product>

Like this (product resource version):

https://example.com/admin/bulk?resource_name=Product&show=image,title&ids=&metafield_titles=&metafield_options=&edit=variants.sku,metafields.global.MPN&query=widget

To edit the same in the Variants resource version:

https://example.com/admin/bulk?resource_name=ProductVariant&show=image,full_title,variants,sku&ids=&metafield_titles=&metafield_options=&edit=variants.sku,metafields.global.MPN&query=widget

Bulkedit thumb
Posts:
6
12 days ago