google shopping data feed updates

[Red Flare]

Have you guys looked at the new specks for google shopping?
There are some major changes.
http://www.google.com/support/mercha...?answer=188494

[wcw]

Re: google shopping data feed updates

I'm surprised others have not commented on this. The new Google requirements will mean a massive amount of data entry work for stores to be able to keep their data in Google's Product Search.

[alphabet]

Re: google shopping data feed updates

I don't like the sharing of brand and MPC codes. It allows users to shop solely on price. Not all products are a commodity and customers don't always understand what goes on in product fulfillment.

Some manufacturers have archaic MPC codes that defy logical information architecture. Some products are available from multiple manufacture's with different MPC codes, for example, STOP signs. I can have that product drop shipped from 20 different locations around the US based on inventory levels and shipping costs. How does Google expect me to provide that information timely and accurately.

This is not going to be an easy task. How will the datafeed handle product variants and multiple vendors?

[wcw]

Re: google shopping data feed updates

The data feed needs to output a separate line (with in stock status/inventory status) for each attribute variant. Thousands of stores are going to be forced to implement attribute inventory variants in order to comply with Google or simply not put their products in Google's Product Search. That also means stores will have to be PR7 or newer.

[wcw]

Re: google shopping data feed updates

Consider this REQUIREMENT:
If you're selling multiple variations of a product (such as a t-shirt in multiple colors), you must give an image of the correct variation (except for variations of sizes). If you do not have the correct image for the variation of the product, you may not submit the item.

Google says the image used with a variant has to be for that variant and not the main product image. So it implies you need an option image for small blue v-neck and a different image for large red crew neck if they are in the same product code but different options. I had originally thought of using the attr/option image that exists now. However, some people may just have a blue square for the selection of blue color and nothing for image for size or neck style. Then again, they could have an option image for neck style. There just is not an image that combines color and style. Having to create 30 images or more to have all the different variant options would be totally insane. Then you would have to upload it to the inactive variant products instead of the main product. Google has lost their way.

Does nobody else see this as a problem? Are stores just going to stop submitting to Google Product Search?

[Mark Hood]

Re: google shopping data feed updates

Just checking in with this thread so that I can keep up.

[alphabet]

Re: google shopping data feed updates

I plan to continue to send Google Product feeds. I use Adwords and I can use product extensions to increase CTR. You can also run promotions that appear on search through your Google merchant account to increase CTR.

I've watched product feeds appear on search results and my products are not listed because I do not provide MPC. My competitors are listed there at about the same price I charge so maybe I should be including MPC. Google also uses transaction history to add in actual shipping costs. Users can get real comparison costs which is great customer experience but drives down price for merchants.

Has Google lost their way? Probably not if they are providing a better user experience.

A few years ago marketplaces were the buzzword (Amazon, Walmart, Sears, theFind) but I've read that a lot of merchants are running away from them because they are not profitable.

I use Shipping and Checkout Supermodules to filter shipping costs at the product level during Miva checkout. If a customer goes offsite and uses Google Checkout then the shipping costs are not filtered and the user gets all shipping methods to choose from. So hopefully the Google product feed will help Google Checkout calculate shippping costs.

[janusdesign]

Re: google shopping data feed updates

i got the email about these changes from google as well and cringed while i read through some of the new requirements. i can understand the majority of them, as i do think they would improve the shopper's experience by providing more thorough product information. but wow - i know a number of stores that these changes will IMMEDIATELY affect and hurt as soon as they take effect. the product variation requirements sound like a nightmare. it's going to be a ton of work for merchants if they want to keep up.

[Datagg]

Re: google shopping data feed updates

I was going to post the letter the other day, yet didn't have the time... Both my companies got an exclusion thank god on allot of this stuff as we fall into the retail arena and custom made products... Yet not all of it, we had to add some stuff to custom fields & Bill's template setup for the non custom stuff and for now all seems good... of course im waiting for the ball to drop on there letters of exclusion we got a couple of months ago, as Google is taking this to a level of insanity.

[Datagg]

Re: google shopping data feed updates

^^^^ Reading more on it, it looks like the Ball apparently has dropped already. So much for my exclusion that lasted 2 months... What a nightmare!!!

[wcw]

Re: google shopping data feed updates

I'm still pondering how to handle the unique image based on the variant issue. While the individual options could have an image (as they do now), that image does not suffice for a combination of the selected options, e.g. shirt w/tie vs shirt wo/tie. Hence, I'm thinking the combined options image has to be stored in the variant record.
shirt_blue_tie
shirt_blue_notie
shirt_red_tie
shirt_red_notie
Each of these inactive variant records would have a different thumb and full size image.

What are your thoughts? Once I code the solution that folks think is best, that is what all stores will need to adopt if they want their variant products (apparel) included in Google Product Search. Google says if there is no correct variant image it cannot be listed. If you list it and it does not comply, your whole feed will be rejected. The importance of getting the right solution the first time cannot be overestimated. Suggestions folks?????

[alphabet]

Re: google shopping data feed updates

I use inventory variants. How will I access variant records through admin? I think I can only access the variant record fields through an export/import.

Can user add a new image type through additional images tab for for each variant?

[wcw]

Re: google shopping data feed updates

Click Products. At the top click the button that says All. That will display both active and inactive products. Locate the variants (probably near the end of the list). Using additional images would not be a good idea since the image type could be named something different from one store to another. So there would be no standard way of retrieving the url and exporting it to Google. Instead, the thumbnail or full size image inputs are the logical choice. They are still there. The only time they would be used would be for the Google export. Thoughts?

[alphabet]

Re: google shopping data feed updates

I was able to view product variants after removing the active filter.

The product variants image fields would be an absolute choice.

I was considering that it would be easier to use the additional images tab for bulk uploads and possibly quicker to use the GD library to resize the variant thumbnail. But you are right, it would be messy if the user does not name the image type correctly. You know how thoroughly we read your module instructions.

[Mark Hood]

Re: google shopping data feed updates

I would think people already using the attribute machine to handle images have this info available in the custom field. No different than any other custom field if I'm correct?

The difficult part is that with a mix of products you need to pick one or the other unless there is an if/else that could work? So if something in image_type / else use the thumbnail.

The other option I can think of would be to export products and copy the custom_image type path to the actual thumbnail field.

The more complicated part to me is the P.I.A. of the actual color / size field because the inactive variants do not really have the attribute name in them. Colors can have an uncounted number of names. It would be nice if the attribute name could actually be put into some kind of field seperately instead of just the code shirt_red_blue which will not really do any good especially when the color code is not what you want the customer to see.

It would be nice if when hitting the auto generate function another field could get activated marking it as a variant instead of just an inactive product.