Google Merchant Centre/Froogle/Google Shopping/Base Changes, Problems and SolutionsOct 11, 2011 · 2 minute read
This is post is now quite old and the the information it contains may be out of date or innacurate.
The current push from Google is enforcing some things that are very difficult for small companies to conform with :-
* EAN Numbers - This is the BIG one, Google are making EAN Numbers required - for some retailers, they just don’t exist, and for a lot of older or cheaper shopping cart systems, they don’t have anywhere to enter them. * Google Category - This is a fairly obvious one, they are attempting to enable shoppers to browse products and find a motherboard for instance with a 1156 socket rather than a CPU that fits an 1156 socket. The answer is to add an extra field to a site’s category system to map site categories to Google categories, or to restructure your products into google’s categorisations. * Product Images - Google are making this mandatory as well, which most people are getting round by using stock or illustration-only images. * Availability - This one actually helps retailers, putting orderable products that are out of stock in front of customers, and is a small change to most scripts exporting to Google
The above changes are being phased in now but should your feed suddenly stop working, how big is the impact on your business? Whilst some of the changes are little tweaks, such as the availability flag, others require fairly substantial changes in the back-end of many cart systems. We are getting many aggrieved businesses contacting us asking for fast turnaround on their Google products feed as they are loosing money all the time that Google are rejecting their products.
What normally (given past changes) has been little tweaks for feeds to be compatible has lately become hours and hours of work both on developers and store-owners. Are you ready to jump through the latest burning hoop Google is holding out for you?