Logo Wyomind Magento workshop

Add-ons for Magento®

The Simple Google Shopping extension allows you to export quickly and safely a valid and well-structured data feed of your complete catalog of products from your Magento website to your Google Merchant Account.

397 Reviews

Simple Google Shopping
is available for Magento® 2

Pre-sales informations
  • Magento® versions supported by Simple Google Shopping

    This extension works with Magento Community Edition and also Magento Enterprise Edition. To know if Simple Google Shopping is compatible with your Magento version, please check the Compatibility tab. 

  • Simple Google Shopping Vs Data Feed Manager

    Data Feed Manager includes all the features of Simple Google Shopping but allows you to create more kinds of data feeds (csv, txt, xml) and with special features like extra-header for any shopping engine, market place or search engine such as BingShopping, Shopping.com, Shopzilla, Amazon...

  • Supported countries with Simple Google Shopping

    All countries are supported (tax rates and currencies). You just need to edit the feed for the target country. You also may have to use the appropriate currency when using prices attributes.

  • Supported currencies with Simple Google Shopping

    Each currency can be managed in your data feed. You can use different values in all price attributes in order to convert currencies.

  • Compatibility with the Google Shopping requirements

    The Simple Google Shopping and Data Feed Manager extensions are fully compliant with the latest Google Merchant requirements.
    We are always looking for ways to improve our extensions so as to offer you the best features and user-experience.

  • Simple Google Shopping and Google Content API

    Simple Google Shopping doesn't use the Google Content API since it generates data feeds. On the other hand, it won't cause any conflict if you're using the API, you just need to disable it when installing the Simple Google Shopping extension following that FAQ.

    Note that the Google Content API migration from version 1 to version 2 won't affect the use of Wyomind Simple Google Shopping. 

  • Syncing with a Google Merchant account

    The data feed is not automatically sent to Google Shopping. Google Merchant will automatically and periodically retrieve your data feed.

    You must first create a Google Merchant Account and then you have to upload the generated file for the first time manually.

    Once your file has been validated (it can take days for the first submission due to a manual validation from Google team), you can create a cron job (a scheduled task) in your Google Merchant Account in order to automatically download the feed from your website.

    You can manage download periodicity directly in your Google Merchant Account.

  • Simple Google Shopping limitations

    Simple Google Shopping has been tested successfully on a file containing more than 70,000 products.

    Remember that the generation and export time for any quantity of products will depend on your server capacity. Generally, exporting a data feed with 10,000 products shouldn't take more than 2-3 minutes on a standard shared server.

License and domains
  • License validity

    A license is valid for an unlimited period of time on one single Magento installation.

    If you use more than one Magento installation, you will have to buy a separate license for each.

    if you run several domains on the same Magento installation, you will need only one license for all of them.

    Although your license doesn’t have a limited period of validity, your support and upgrade period does. By purchasing an extension, you’ll be granted a 6-month support and upgrade period for free.
    Passed this period, you will have to pay for a new one (see FAQ: Extension upgrade).
  • License and pre-registred environments

    You can pre-register your live domain to your license and activate it in advance.

    Thanks to this option, you'll be able to get the extension ready to use on your domain before it goes live.

    To pre-register your production domain, go to:

    my account downloads

    And click on   next to the extension you want your domain to pre-register on.

    At the bottom of the page, below the list, click on the orange link saying: 
    Do you want to pre-register your domain in order to be ready to go live?    

    Finally, enter your domain name and click on pre-register now .

  • License and testing environments

    One license is valid for an unlimited period of time on one Magento installation only.  

    It is possible, however, to extend or transfer your license in three cases: 

    • If you'd like to add your testing environments to your license.
      In this case, it is possible to extend your license to an unlimited number of domains for free.
      For example mywebsite-staging.com or mywebsite-dev.com
    • If you redirected definitively one domain to another one (301 permanent redirection).
      In this case, you can request a license transfer for free.
    • If you'd like to shift your license from one Magento installation to another.
      In this case, you can request a license transfer which you'll have to pay for.


    To be able to use Simple Google Shopping on both your production and testing environments, follow the instructions below:

    1. Download Simple Google Shopping.
      (see FAQ: Extensions download)
      .
    2. Install Simple Google Shopping on your production environment.
      (see FAQ: Extensions installation)
    3. Activate the license.
      (see FAQ: Extensions activation).
    4. From your Magento admin panel, enter your current Activation Key from:
      syStem CONFIGuration WYOMING YOUR EXTENSION 
    5. Save config


    Now that you can use Simple Google Shopping on your production environment, repeat the same steps as above on your testing environments.

    The only difference this time: a notification will appear in your Magento admin. 

    You will be given a choice in between:

    1. buy a new license now
    2. add this domain to my license


    Click on Add this domain to my license.

    A transfer request will then be sent to our team within an hour.

    Once the request is taken care of, you will receive a confirmation email.

    If your transfer request is accepted, you can use Simple Google Shopping on both environments at the same time.

    The order in which you activate your license on your domains does not matter.
    You can start with your staging/dev/local environment or with your live domain, the process will be the same.
Extension Installation/Uninstallation and Activation
  • Extensions installation

    Before installing Simple Google Shopping, you’ll have to:

    • Backup your Magento installation in:
      system  tools   backups
    • Disable the compiler in your Magento admin panel if it’s not already disabled:
      system  tools   COMPILATIONS
    • Refresh your cache in:
      systemselect cache typeactionsrefreshsubmit


    Now you can install Simple Google Shopping:

    1. Download Simple Google Shopping (zip file) from:
      my account my downloads
      Refer to FAQ here: Extensions download
    2. Once Simple Google Shopping is downloaded, open the folder and unzip it.
    3. Copy the content of the unzip folder and paste all files and directories in your Magento root directory (the folder content can vary according to the extension but it generally includes app, lib and skin folders).

    4. Once your installation is complete, don't forget to enable the compiler back (if it was already enabled before the installation) and run compilation process.
    5. Refresh your cache, logout from your admin panel and log back in right after.

    Next step is to activate your license, to do so, click here: Extension activation

  • Extensions uninstallation

    To uninstall Simple Google Shopping, go on its zip folder and open it.

    You will find a shell file (such as: yourextension-uninstall.sh) that you must execute on both your server and Magento root directory.

    Once the uninstallation is over, refresh your cache and enable the compiler back again (if you use it).

  • Extensions activation

    Once Simple Google Shopping is downloaded, you have to activate the license: 

    1. Go to your Magento admin panel. A message pops up at the top of the page.

      If the message doesn't appear then you must check that:

      Wyomind's License Manager has not been removed from your installation.
      Wyomind's License Manager is enabled in: app/etc/modules/Wyomind_Licensemanager.xml
      The HTML output for Wyomind_Licensemanager and/or Adminhtml_Notification are not disabled in your system under:

      system   configuration  advanced advanced
    2. Copy your activation key.

      You can find your activation key in 2 different places:

      - In the confirmation email that you received after purchasing Simple Google Shopping
      - In your Wyomind account:MY ACcount My downloads, select Simple Google Shopping and click on  . A new page opens where you'll find your activation key (see below).

    3. In your Magento admin go to:
      SystemConfiguration Wyomind Your extension

      Paste the activation key in the Activation Key field and choose between the automatic (yes) or the manual (no) activation method:
      - By choosing Yes, the connection to Wyomind's license server will be automatic. 
      - By choosing No, you will have to log on to Wyomind's license server yourself.


    4. Save config.
    5. A message appears at the top of your admin panel: Activate it now!  Click on that link.

    6. Copy and paste the license code in the License code field from your admin or simply click on Activate now!
    7. Finally, refresh your cache, log out and log back in straight after, to complete the installation.

    To activate the license of an extension that includes other modules, you’ll have to repeat the steps described above for each, using the corresponding activation keys (each module has its own activation key).

Extension versioning and download
  • Extensions download

    In order to download Simple Google Shopping, log into your Wyomind account:

      1. Go to:
        my account  my downloads 

      2. Click on   next to Simple Google Shopping.


        A new window opens.

      3. Choose the version of Simple Google Shopping.
        You will be able to choose the most recent version of Simple Google Shopping (for both Magento 1 and Magento 2).


      4. Click on download .

    Your download can start.

  • Extensions upgrade

    With each purchased extension comes a free 6-month upgrade period, during which you can download and install the new version of your extension. Passing this period, you will have to purchase an additional upgrade (price depends on how long the period is)

    To upgrade Simple Google Shopping, follow the steps below:

    1. Go to:
      my account  my downloads 
    2. Click on   next to Simple Google Shopping.
    3. Choose the latest version of Simple Google Shopping (for Magento 1 and Magento 2).
    4. Click on  download .
    5. Enter your current activation key and click on  .
    6. Select the domain name.
    7. Choose from 1 to 12 months of Support and Upgrade period.
    8. Choose a professional installation or not.
    9. Click on  BUY NOW .

    To finish, don't forget to reinstall Simple Google Shopping to update your Magento admin.

    If you can't find your download after upgrading your domain, please contact us:
    https://www.wyomind.com/fr/contact.html

Data feed configuration
  • Shipping and tax in Google Shopping Data feeds

    You have 2 ways to manage shipping and tax with Google Merchant:

    1. Managing your shipping and tax settings in your Google Merchant Account:
      Settings Shipping and tax
    2. Adding shipping and tax informations directly in your data feed template.

    You can refer to Google Merchant specifications for further informations about tax and shipping:
    https://support.google.com/merchants/bin/answer.py?hl=en&answer=160162&topic=2473824&ctx=topic

    How to setup tax (US Only)

    Please note that tax setting should only be used for merchants submitting feeds to the US. For all other countries, it is required to submit prices which are tax inclusive.

    Either you can manage tax in your Google Merchant account by choosing between these 3 options:

    • Opt to not charge tax.
    • Set a tax rate based on the state an item ships to.
    • Use an estimate based on the destination ZIP code. Note: To estimate the tax rate, we use data from Tax Data Systems based on the destination ZIP code.

    Either you can also use the tax attribute in your data feed.

    You have 4 different attributes about tax:

    • Country (optional), using ISO 3166 country code
    • region (optional), using two-letter state abbreviation, ZIP code or ZIP code range using * wildcard
    • rate (required), the tax rate as a percent of the item price.
    • tax ship (optional), boolean value for whether you chage tax on shipping (y or n). n is default value.

    Here is an example of tax attribute group:

    <g:tax>
       <g:country>US</g:country>
       <g:region>CA</g:region>
       <g:rate>8.25</g:rate>
       <g:tax_ship>y</g:tax_ship>
    </g:tax>

    How to setup shipping?

    Either you can manage shipping in your Google Merchant account by choosing between these 3 options:
    • Specify a flat shipping rate (or free shipping).
    • Define custom tables if the shipping rate you charge varies by price, weight, or number of items.
    • (US only) Apply a carrier-calculated rate if the shipping rate you charge is based on rates from UPS, FedEx, or USPS. Note: We use daily rates for UPS, and standard (non-retail counter) rates for FedEx.

    Either you can also use the shipping attribute in your data feed.

    The shipping attribute is an item-level override for merchant-level shipping settings as defined in your Google Merchant Center account.

    You have 4 different attributes about shipping:

    • country (required), using ISO 3166 country code.
    • region (optional), using two-letter state abbreviation, ZIP code or ZIP code range using * wildcard
    • service (optional), the service class or delivery speed (by example : Ground)
    • price (required), fixed shipping price (including VAT) with currency code.

    Here is an example of shipping attribute group:

    <g:shipping>
    	<g:country>US</g:country>
    	<g:region>MA</g:region>
    	<g:service>Ground</g:service>
    	<g:price>5.95 USD</g:price>
    </g:shipping>
  • Configurable products in Google Shopping data feeds

    As you probably know configurable products are only containers filled with not visible individually products, that Google call "variants".

    That's why the configurable products should not be sent to Google Merchant because there are missing required attributes (price, color, size or any variant attribute). Instead, you should submit the simple products that have all the required information.

    In your data feed template, you need to check that:

    • You use the Configurable or Parent option to retrieve the information from the configurable product.
      Most of the time the attributes that must be retrieved from the configurable products are url and description.

      Example
      <link>{url parent}</link>
      <description>{description parent}</description>

    • All the simple products that are not visible individually and that belong to the same configurable product are grouped under the same item_group_id. This can be done easily by adding the below "Magic Attribute" in the data feed template.
      {G:ITEM_GROUP_ID}​
    • Your filters are not too restrictive. For example, if your variants are not visible individually, make sure to have ticked that option in your data feed filters.

    • the categories you've selected are assigned to the simple variant. For example, if only the parent product has a category assigned, you'll be able to include product into your data feed based on the Product and parent categories.

  • Grouped and bundled products in Google Shopping Data feed

    As you know bundle products and grouped products are made of a combination of simple products (visible or not visible individually). Creating a specific data feed for the bundle products and/or for the grouped products in most of the time is a good idea.

    Bundle and grouped products require to use:

    {stock_status}

    instead of:

    {is_in_stock}

    Is_in_stock is based on the stock status (in stock / out of stock) and the available quantity, but bundle/grouped products have no quantity associated so using stock_status is a better choice

    Bundle products require a specific attribute in data feeds:

    <g:is_bundle>TRUE</g:is_bundle>

  • Adwords labels for Google Shopping Ads

    In Google Shopping, you can use custom labels to subdivide the products in your campaigns using the values of your choice to indicate for example that products are seasonal, best sellers... After that, you can use these values to monitor, report and bid in your Shopping campaign.

    For each item in your data feed, you can create up to 5 custom labels (0 to 4). You should only submit one value per item for each custom label attribute.

    If you want to use custom labels in your data feed, you need to create and add a new attribute in your attribute sets.

    Below is how to proceed.

    1. Go to:
      Catalog Attributes  Manage attributes
    2. Add a new attribute.
    3. Enter custom_label_0 (for example) in the Attribute Code field and choose the dropdown input type.

    4. In the Manage Label / Options tab, enter Custom Label 0 (for example) in the Admin field.
    5. Add options, such as Summer, Winter...
    6. Click on Save Attribute and assign the attribute to an attribute set.
    7. Choose a value for all your products.
    8. Add the attribute in your XML template using this syntax:
     
    <g:custom_label_0>{custom_label_0}</g:custom_label_0>
    <g:custom_label_1>{custom_label_1}</g:custom_label_1>
    <g:custom_label_2>{custom_label_2}</g:custom_label_2>
    <g:custom_label_3>{custom_label_3}</g:custom_label_3>
    <g:custom_label_4>{custom_label_4}</g:custom_label_4>

    Then you should get the value for each product.

  • Google Shopping Ads and performance tracking

    Google Analytics provides many details about incoming traffic from Google Shopping Ads Campaigns.

    However, you may want to track incoming traffic from your Shopping Ads in Google Analytics by your owns. To do so, you can use the UTM parameters with dynamic variables and/or fixed values as follows:

    <link>{url}?utm_source=My Website&utm_medium={medium}&utm_campaign={campaign}&utm_term={term}&utm_content={content}</link>
Frequent errors in Google Merchant
  • Errors and warnings in your Google Merchant account

    After having uploaded your feed, you may get some errors and warnings in your Google Merchant account.

    1. Go to the Data Feeds tab and open your data feed by clicking on its name.

    2. There you'll be able to see the list of the different errors and warnings of your data feed. Click on the message you want to get more details about the issue.

    3. The drop-down notification displays details about the error or warning and also contains a non-exhaustive list of products that are concerned about the issue.

    4. Click on Show Item to see what's wrong for that product in particular.

    For example, the item below has no image link. It certainely means that this product has no image and that you'll have to add one from your Magento admin.

    Once corrections are made for each error and warning, don't forget to regenerate your feed from your Magento admin and reupload it manually from your Google Merchant account.

    You can find information on how to make the corrections for each error and warning in the following FAQs.
  • Critical Errors: inaccurate prices

    This issue may happen if you didn't update the price configuration in the data feed template according to your website settings.

    By default the Google Shopping template is pre-configured for the US market, USD currency and prices excluding tax.

    {normal_price,[USD],[0]} 
    {G:SALE_PRICE,[USD],[0]}
    

    If your data feed doesn't target the US market these settings must be updated, for instance :

    • Great-Britain :
      {normal_price,[GBP],[GB]} 
      {G:SALE_PRICE,[GBP],[GB]}
      
    • France :
      {normal_price,[EUR],[FR]} 
      {G:SALE_PRICE,[EUR],[FR]}
      
    • Germany :
      {normal_price,[EUR],[DE]} 
      {G:SALE_PRICE,[EUR],[DE]}
    • ... 

    In the case where the prices of your catalog already include the VAT rate, you'll only need to use:

    {normal_price,[USD]} 
    {G:SALE_PRICE,[USD]}

    For more details about the price configurations you can refer to this price documentation.

  • Critical Errors: Images cannot be crawled because of robots.txt restriction

    It seems that Google Merchant sometimes returns some inconsistent errors message concerning the robot.txt.

    Try to add the following lines into the robot.txt file, what should explicitly allow Google Merchant to crawl your images:

    User-agent: Googlebot
    Disallow:

    User-agent: Googlebot-image
    Disallow:

  • Missing required attribute: unique product identifier

    Google requires some Unique Product Identifiers.

    These informations may be a brand, a MPN (manufacturer part number), an EAN, an ISBN or any other global identifier and must be added like this:

    <g:ean>{ean}</g:ean>


    If you do not have any "strong identifier" to provide to Google, you can use an association of brand and MPN.
    This means that you must add in your data feed configuration this code snippet :

    <g:brand>{manufacturer}</g:brand>  
    <g:mpn>{sku}</g:mpn>

    "Manufacturer" is your own attribute for manufacturer or for brand and your "sku" attribute is used as a manufacturer part number. If you do not have a manufacturer attribute, you can also hard code this value like this :

    <g:brand>your own brand</g:brand>

    It's also possible to specify that your products don't have any identifier at all :

    <g:identifier_exists>FALSE</g:identifier_exists>
  • Missing required attribute: gender

    You didn't specify gender.
    Gender is required for all apparel items in feeds that target the US, UK, DE, FR, and JP.
    3 values accepted:

    • male
    • female
    • unisex

    Read our documentation about required attributes with Google Shopping.

  • Missing required attribute: age group

    You didn't specify age group.
    Age group is required for all apparel items in feeds that target the US, UK, DE, FR, and JP.
    2 values accepted:

    • adult
    • kids

    Read our documentation about required attributes with Google Shopping.

  • Missing required attribute: color

    You didn't specify the dominant color(s) of the item.
    Color is required for all apparel items in feeds that target the US, UK, DE, FR, and JP.
    Read our documentation about required attributes with Google Shopping.

  • Missing required attribute: size

    You didn't specify the size.
    Size is required for all apparel items in the 'clothing' and 'shoes' product categories in feeds that target the US, UK, DE, FR, and JP.
    Read our documentation about required attributes with Google Shopping.

  • Missing recommended attribute: google product category

    You didn't specify any category mapping for listed categories.
    Categories names you are using in your Magento aren't always the same that ones used by Google Merchant to reference your products.
    This means you have to find out which Google Merchant categories have the best matching with yours, according to the Google product taxonomy.
    Read our FAQ about category mapping

  • Missing recommended attribute: product_type

    Reminder : product_type is an attribute which indicates the category of the product being submitted, but you can provide your own classification. Unlike the 'Google product category', you can include more than one 'product type' attribute value if products apply to more than one category.

    In Simple Google Shopping, you have a magic attribute realizing this for you :

    {G:PRODUCT_TYPE}

    It creates a list of all the categories where the product may be found :

    <g:product_type>
    	category A > sub-category B
    </g:product_type>
    
    <g:product_type>
    	category A > sub-category B > sub-category C
    </g:product_type>

    It happens Google Merchant reports you warnings about missing product_type. The issue usually comes from simple products that are associated to the configurable ones. You could try to use this code which will retrieves the parent "product type" for each product :

    {G:PRODUCT_TYPE parent,[10]}
  • Missing recommended attribute: image link

    Image missing means that some of your product don't have any image attached.

    First of all, check if the concerned products have at least one image assigned.

    Then, check if the concerned products are not linked to a parent. If they are, you just need to use the following code that will display the parent product's images instead:

    {G:IMAGE_LINK parent}

    If you still have some missing images in your data feed, this may mean that some of your product doesn't have images at all. In a such case you must use the attribute filters in order to remove these products from the feed :

  • Missing recommended attribute: description

    Description missing means that your products don't have any description available. Google needs the description for each items.

    First of all, check if the concerned products use the short_description. The short descriptions are filled for your products but not the long descriptions, so you must use in your data feed template:

    <description>{short_description}</description>

    rather than:

    <description>{description}</description>

    or both:

    <description>{short_description} {description}</description>

    Then, check if the concerned products are not linked to a parent that have the description, the descriptions are attached to the parent items (when using configurable / simple products), so you must use in your data feed template:

    <description>{description parent}</description>

    rather than:

    <description>{description}</description>
  • Encoding problem in attribute: description

    This error means that your descriptions contain some invalid characters : either wrongly encoded characters or  unsupported characters (not supported by the utf8 character set).


    Most of time the cleaner option should help to remove all wrongly encoded characters :

    {desciption,[cleaner]}



    This option can be applied in addition to any other option, for instance :

    {description,[html_entity_decode],[substr],[1000],[...],[cleaner]}



    If you still have issue with encoding, you could convert all characters to html entities :

    {description,[cleaner],[htmlentities]}
  • Some of my products have issues with microdata

    Microdata are some kind of HTML snippets that must be added on the product pages in order to allow Google to fetch your data more regularly.

    Simple Google Shopping doesn't handle the microdata, however, you can use our Google Rich Snippets extension that will allow you adding the required microdata for Google Shopping.

Developer Resources
  • Add the currency in the URL and preselect the currency in the landing page

    You have the correct currency specified in your data feed. However, when a customer clicks on the link from Google Shopping, it shows the default currency instead of the correct currency.

    For this reason Google may not approve your data feed and may suspend your account.

    That issue has nothing to do with the extension, but you can easily fix it copying the file:
    app/code/Core/Mage/Core/Model/Url.php

    to:
    app/code/local/Mage/Core/Model/Url.php

    Then, locate the method setRoutesParams() and add the below code at the beginning of the function:

    if (!is_null($this->getRequest()->getParam('currency'))) {
        if ($this->getRequest()->getParam('currency') != Mage::app()->getStore()->getCurrentCurrencyCode()) { 
            Mage::app()->getStore()->setCurrentCurrencyCode($this->getRequest()->getParam('currency'));
        } 
    }
    


    The beginning of the function should now look like :

    // [...] 
    public function setRouteParams(array $data, $unsetOldParams = true) {
    
        // the changes begin here
        if (!is_null($this->getRequest()->getParam('currency'))) {
            if ($this->getRequest()->getParam('currency') != Mage::app()->getStore()->getCurrentCurrencyCode()) {
                Mage::app()->getStore()->setCurrentCurrencyCode($this->getRequest()->getParam('currency'));
            }
        }
        // the changes end here
        
        if (isset($data['_type'])) {
            $this->setType($data['_type']);
            unset($data['_type']);
        }
    
    //[...]

    You can now use the below code at the end of your products urls so that the monnaie will be loaded automatically when displaying the page:

    ?currency=currency_code

    Exampleshttp://www.website.com/men/new-arrivals/linen-blazer.html?currency=EURhttp://www.website.com/men/new-arrivals/linen-blazer.html?currency=USD

  • Get a list of all the categories

    This can be easily achieved with a few lines of php code in the product pattern or even in the header pattern. For example:

    <categories>
    	<?
    	if(!isset($this->done)){
    	$xml=null;
    	$categories= Mage::getModel("catalog/category")->getCollection()
    	->addAttributeToFilter('level',array('gt'=>1))
    	->addAttributeToSelect('name');
    	foreach($categories as $category){
    	$xml.="<category>
    	<name>".$category->getName()."</name>
    	<url>".$category->getUrl()."</url>
    	</category>\n";
    	}
    	$this->done=true;
    	return $xml;
    	}
    	?>
    </categories>

    This code will produce:

    <categories>
    	<category>
    		<name><![CDATA[Women]]></name>
    		<url><![CDATA[http://www.wyomind.com/women.html]]></url>
    	</category>
    	<category>
    		<name><![CDATA[Men]]></name>
    		<url><![CDATA[http://www.wyomind.com/men.html]]></url>
    	</category>
    ...
    </categories>
  • Exclude products from a data feed based on the category ID

    You need to complete your data feed template with some php script:

    <? if(in_array(CATEGORY_ID,explode(',',$product->getCategoriesIds())) $this->skip(); ?>
  • Exclude specific products from a data feed

    You have the possibility to exclude some products from the feed using advanced filters from the Filters section.

    For example, you would like to filter out 3 products: SKU1, SKU2 and SKU3. Then you only have to create a NOT IN advanced filter as below:

    Sometimes, advanced filters aren't enough to generate your data feed in the way you want it to be.

    For example, let's say you want to extract all your catalog products, except the ones whose category mapping is Shoes. If you tick all categories except the Shoes one in the Categories section, you'll miss all uncategorized products.

    In that case, you can use a code snippet in your template which will exclude the Shoes category. This will only work if you untick all categories in the Categories section:

    <? 
    // if category is Shoes then skip the product)
    if("{category_mapping}"=="Shoes") $this->skip();
    ?>
    
    

    In a general notation:

    <? if("{attribute_code}"=="value") $this->skip();?>
  • Manage Adwords campaigns by price ranges

    To group your Adwords campaigns by price ranges, you can simply use PHP code into your XML template.

    For example:

    <g:custom_label_0>
    <?
    if({price}<10) return "0-10";
    elseif ({price}<25) return "10.001-25";
    elseif ({price}<50) return "25.001-50";
    elseif ({price}<75) return "50.001-75";
    elseif ({price}>75) return "75.001-100000";
    ?>
    </g:custom_label_0>
Troubleshooting
  • Base table or view not found

    This issue may be due to a problem during the installation process.

    You can fix it by following these steps:

    • Access your database via your control panel (Phpmyadmin for example).
    • Delete the entry extension_setup from the core_resource table.
      Be careful, that entry depends on your extension. For example, if you have the extension called Simple Google Shopping, you should delete simplegoogleshopping_setup.
    • Logout from your Magento admin.
    • Log into your Magento admin.
  • Fatal error: Mage_Core_Model_Resource_Setup.php

    If your site crashes and gives this error message after uploading all files to the correct folders:

    Fatal error: Class 'Wyomind_Notificationmanager_Model_Resource_Setup' not found in includes/src/Mage_Core_Model_Resource_Setup.php on line 234

    It probably comes from installing an extension while the compiler is still enabled.

    Important note:

    • If the compilation is enabled on your website, disable it first before installing any extension from: 
      SystemToolsCompilation
      After installation re-run the compilation process and re-enable the compiler.
    • Before installing any extension, it's advisable to backup your Magento installation.

    Here is how to disable the Magento compiler:

    1. Edit the following file: includes/config.php and add a # before the 2 following lines:
      define('COMPILER_INCLUDE_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'src');define('COMPILER_COLLECT_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'stat');​

      to get:

      #define('COMPILER_INCLUDE_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'src');#define('COMPILER_COLLECT_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'stat');
    2. Then go back to your website admin and re-run the compilation process.
  • Scheduled tasks don't work

    How do cron tasks work:

    • cron.php is launched regularly from your server side (every 5 minutes most of the time).
    • The cron task for Simple Google Shopping is targeted and evaluates if a data feed or a profile needs to be refreshed (depending on the timestamp stored in the database and on the schedule table for this specific profile).
    • If the above condition matches, then the data feed and the profile is re-generated.

    Be sure that you have correctly configured a scheduled task from the server side (cpanel) targeting the cron.php file in your Magento installation.

    The extension includes reporting and debug tools for the scheduled tasks in:
    systemconfigurationWyomindSimple Google Shopping

    We also strongly advice to install the AOE Scheduler that will help you to monitor the Magento cron tasks.

  • 404 error in the configuration page

    Most of the time log-out/log-in may solve this issue.
  • 403 forbidden error

    If when saving your data feed configuration, you get:

    Forbidden, You don't have permission to access /.../ on this server.

    This is probably something regarding the hosting company that doesn't allow to post XML in the form.

    The mod_security (security module) includes rules that stop all post/get requests including code.

    In order to fix that issue, you should get in touch with your hosting company so that they can add some exceptions to the security rules.

  • 404 error instead of the Google Taxonomy

    You must apply the permissions 644 to libGoogle or libWyomind directory and all sub folders and files via FTP.

  • 404 error instead of the extension page in the admin panel

    Try to run the below request in phpmyadmin or in any database manager.

    For Simple Google Shopping : 

    UPDATE simplegoogleshopping SET store_id=(SELECT store_id FROM core_store WHERE store_id>0 LIMIT 1);

    For Data Feed Manager

    UPDATE datafeedmanager_configurations SET store_id=(SELECT store_id FROM core_store WHERE store_id>0 LIMIT 1);
  • 404 error page after deleting a storeview

    If after deleting a storeview, you get a 404 error page, you must look in your database (with PhpMyAdmin) which store_id (i.e. storeview ID) has been deleted.

    Then to fix the issue, you have to update each element from the table simplegoogleshopping or datafeedmanager (depending on your extension) with another valid store_id.

  • Unable to list current working directory

    You should check that the var/tmp folder exists in the Magento root directory. If not, create it with the writing permissions.

  • Please make sure that '/feeds/' is writable by the server

    The directory in which your data feed is stored must be writable (permissions 755). You should try to use another directory such as /media/ if /feeds/ is not properly set by changing the content of Path field.

  • Please create the specified folder before saving the data feed configuration

    You need to access your server with FTP client software (like Filezilla).

    Then in your Magento root directory, you need to create the feeds folder and apply the 755 permissions.

  • String could not be parsed as XML. Please check the template syntax

    The XML error probably comes from some product descriptions that must include invalid tags such as a missing closing tag.

    In your product pattern, replace {G:DESCRIPTION} with:

    <g:description>{description,[cleaner],[inline],[strip_tags]}</g:description>
  • Empty feed when opened from the browser

    You may have an incorrect character in your data feed description, for example the & character.

    In that case you should replace the & character with and or enclose your data between CDATA as in the example below.

  • Characters from the data feed aren't displayed properly

    First, be sure to use special attributes which will clean your content:

    {attribute,[strip_tags],[html_entity_decode],[inline],[cleaner]}

    If your data feed still doesn't display properly, maybe it's because you try to read it as an ISO file while Simple Google Shopping creates UTF-8 encoded files.

    We recommend you to read it with dedicated programs like Notepad++ or even Firefox (withDisplayEncoding typeutf8 selected).

  • Unable to list current working directory

    The Simple Google Shopping module uses a temporary directory to store data. You must make sure that var/tmp exists under your Magento root directory, if not, you should create it.