Magento 1

Simple Google Shopping

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 thanks to Simple Google Shopping, an extension built by a Google partner.

marketplace approved
best seller
95,00€excl. VAT

4.9/5 rated 543 reviews

  • Lifetime license
  • 12 months support & upgrade
  • 60 days money-back guarantee
  • Extensible source code
  • Unlimited test domains
  • Free composer access
Demo Store

Easily export your products data to Google Shopping thanks to the powerful Simple Google Shopping extension

  • Create an XML data feed including all your catalog of products in one go using Simple Google Shopping.

Efficiently export your products catalog to Google Shopping

  • Product types — Include all product types to your data feeds: simple, configurable, downloadable...
  • Multi-stores — Create multi-stores, multi-currencies, multi-VAT-rates data feeds

Create a data feed in compliance with Google requirements

  • Template — Use the sample XML pattern included in the extension
  • Library — Find any attribute in the attributes library
  • Reports — Check the errors and warnings reports
  • Preview — Preview data feeds and use the syntactic helper to avoid misprints

Completely customize your data feed according to your products catalog

  • XML pattern — Add any Magento 1 / OpenMage attribute to your XML pattern
  • PHP API — Add PHP scripts into your XML patterns
  • Category filter — Filter your products according to the Product and/or Parent categories
  • Filters — Create attribute set and category filters
  • Advanced Filters — Define more personalized filters using advanced filters
  • AND/OR statements — Use OR/AND statements in your filters

Automatically and regularly send your updated data feed to Google

  • Cron tasks — Use the scheduled tasks to periodically generate your data feed
  • Generation details — Check your data feed generation (number of items, time, and resource)
  • Generation status — Make sure your data feed is correctly generated thanks to the generation status

Easily find the Google categories that correspond to yours

  • Category Mapping — Map your categories to Google ones in one go
  • Search As You Type — Facilitate your category mapping with the Search As You Type option

Content

    What are Google Merchant and Google Shopping?

    What is Google Shopping and Google Merchant?

    Google Shopping is a free Google service allowing customers to find and compare products they want to buy online. If you are an online merchant, you can submit all your products to Google Shopping and attract potential customers by allowing them to view your products more easily.

    Google Merchant Center is a tool that helps you upload your store and product data to Google and make it available for Shopping ads and other Google services. Learn more about getting starting with Merchant Center

    How to create my Google Merchant Account?

    In order to submit your products to Google Shopping, you need to create a Google Merchant Account. Click on the following link for further information on creating an account: https://www.google.com/support/merchants/bin/answer.py?hl=en&answer=188924

    This account gives access to the Google Merchant interface. There you can manage all your product data feeds and plan any daily, weekly or monthly updating tasks.

    What is a products data feed?

    A data feed is a file made up of a unique group of attributes that define each one of your products. This allows customers to search and find your items more easily. This file is similar to an RSS data feed but includes some specific XML tags used by Google Merchant Center or any other shopping engine.

    To know more about the product data feeds, have a look to the Google Merchant Center support site: https://support.google.com/merchants/answer/188478?hl=en

    How to create a products data feed?

    Simple Google Shopping and Data Feed Manager are two Magento extensions that allow you to quickly configure, generate and automate several product data feeds.

    How to use Simple Google Shopping?

    STEP 1: Configure Simple Google Shopping in a general way

    Before being able to configure your data feeds, you should configure the extension in a general way. To do so, go to

    System › Configuration › Wyomind › Simple Google Shopping

    Cron job reporting
    In the Cron job reporting tab, you can activate the cron job reporting and fill in an email address to receive the reports. You can also rename the reports as you want. Finally, you have the possibility to enable the debug mode.  
    Core Settings

    In the Core Settings tab, you'll need to configure a certain number of fields.

    • Items in preview
      By default there are 10 items in preview, if you want you can reduce or increase that number. 
    • Items in buffer
      By default, products are inserted into the file on the server every 10 items but you can reduce or increase that number.
    • Items in SQL request
      By default, there are 1500 items in each MySql query.
    • Number of advanced filters
      By default, you have 10 advanced filters. If you need more, you can at any time increase that value.
    • Use of OR/AND statements in advanced filters
      And/or statements can be used in the advanced filters simply by enabling that option.  
    • Include not in menu categories
      You can also include the categories of products that are not in the menu.  
    • Memory limit size (M)
      The default memory limit is 1024.
    • Use canonical urls

      You'll be able to choose which type of URL to use in your data feed. You can choose between 3 options:
      Product url, Shortest category url or Longest category url.

        For example, if you have a "T-shirt" in 2 categories: "New arrivals" and "Shirts", the URLs may be:
        Product Url = http://mywebsite.com/t-shirt.html
        Shortest category url = http://www.mywebsite.com/men/shirts/t-shirt.html
        Longest category url = http://mywebsite.com/men/new-arrivals/t-shirt.html

      STEP 2: Configure your data feeds with Simple Google Shopping

      To create/configure your own data feed, you need to go to:
      Catalog › Simple Google Shopping

      There, click on Create a new data feed.

      You now have to configure your data feed as you want.

      The Tool Box or so-called "Black Box"


      When creating a data feed, you should see a blackbox on the right of your screen. The Simple Google Shopping extension includes that tool to help you create your feed and see what is wrong.

      The blackbox is inevitably a very useful tool. This will help you to configure your data feed more quickly.

      Below are the different options of the blackbox.

      Syntax validation

      This button allows you to check if your syntax is correct. It helps you to see if you have forgotten a bracket or a comma by underlining in yellow the part of text that contains a mistake.

      Attributes library

      If you click on that button, a library of your store attributes will be displayed. This makes it easier to find very quickly which attribute you need to add into your template.

      Data preview

      When clicking on Data preview, you'll see a preview of your data feed. It's very useful to see if the values of your attributes are correctly retrieved or if your filters are working. 

      Error report

      When clicking on that button, it will display a report on the errors and warnings of your data feed. 

      Configuration


      In that first tab is the main configuration of the data feed. You'll find several fields to fill in that will allow you to customize your feed.

      • File name
        Enter a name for the file.
      • Path
        Define the path where you want the data feed to be generated. For example /feeds/. 
      • Store View
        Define which store view must be used.
      • Website url
        Add your website url.
      • Title
        Add a title to your feed.
      • Description
        Add a description to your data feed.
      • XML template
        This is probably the most important field as this is where you will configure your template
        For a good understanding check how to manage your data feed templates 
         

      Categories filters


      In the Categories tab, you will find 2 sections that will allow you to manage your categories. The first section allows filtering products by categories.

      You can filter products depending on the categories according to two different ways:

      • Exclude all products from the selected categories.
      • Include all products from the selected categories.
      If you don't select any category, all products will be exported.

      For example, if you wish to include only products of the Apparel category, you can configure your filter in two different ways.

      First of all by ticking the Include option that will allow you to include all categories that you have selected.

      Or via the Exclude option that will exclude all categories you have selected.

      You'll be able to include or exclude your categories depending on:

      • Product categories only
      • Product and parent categories
      • Parent categories only

      Imagine you have a configurable product with simple variants associated. The configurable has a category assigned but not the variants. In that case, you'll need to select Parent categories only.

      On the contrary, if you have categories assigned to simple variants but not to the configurable product, you'll need to select Product categories only.

      In the case where you have both situations, you can select Product and parent categories.

      Category mapping


      In that section, you can map your categories to Google ones. This step is very important so that Google can make a link between their product categories and yours.

      What is a category mapping?
      Categories names you are using in your Magento aren't always the same than the 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.

      For example, if you're selling furniture like coffee tables, you'll have a Coffee table category in your Magento admin. But Google Merchant doesn't handle this kind of category. The closest Google product category could be Kitchen & Dining Room Table.

      How to map your categories with Simple Google Shopping?
      Simple Google Shopping  provides you an easy way to input Google product categories matching yours. 

      In your data feed configuration, go in the Categories tab. Then, in Category selection and mapping section, you'll find a treeview of all your categories.

      First select the Google Taxonomy source on which the category mapping is based.

      Taxonomy files for the main countries are directly included to allow you to map your categories more easily. You can also have a look to our faq to know how to add a new taxonomy file.


      For each category, you have a little arrow followed by mapped as . There, you'll be able to start typing a keyword in order to display a list of all categories including that keyword. You simply need to select the one you need.

      If your press the End key of your keyboard after typing a category mapping, the value will apply to all sub-categories.

      Once all your categories are mapped, you can click on Save.

      Here are a few guide lines for choosing the most appropriate category:

      • Use the category that best describes your item. To do this, first determine the primary function of the products you are submitting. For specific items like MP3 Players, select the MP3 Players category. While some MP3 players can also serve different functions, like those that contain a clock, they are primarily MP3 Players.
      • Use only one category. For some products, more than one category might be relevant. For example, an adapter to allow an MP3 player to be used in a car could be in both categories Motor Vehicles > Audio & Video and Electronics > Audio > Audio Accessories > MP3 Player Accessories. In such cases, choose the category that seems the most appropriate to you, but don't include more than one.
      • Use the most specific category possible. Being specific will help to improve your data quality and so ensure that offers are presented in the right category. When viewing the taxonomy, try to navigate to the most specific category that still covers all the products that are being submitted. For instance, if you are submitting MP3 player chargers use the MP3 Player Chargers category. Conversely, if you are submitting multiple types of chargers use the Chargers category.


      www.youtube.com/embed/QNXtwEm7FPo?rel=0

      How to include the Google category to the XML template?

      Finally, so that the Google category is retrieved in your data feed, you must add the following attribute to the XML template:

      {G:GOOGLE_PRODUCT_CATEGORY}

      or

      <g:google_product_category>{category_mapping,[0]}</g:google_product_category>
      Please note that this attribute is different from Product Type. 

      <g:product_type> is for the categories that you have defined independently in your Magento back-office.You can easily fill this XML section using  {G:PRODUCT_TYPE} . This will then retrieve for each one of your products, the category you have assigned to it.

      Read also: https://support.google.com/merchants/answer/6324406?hl=en

      How to add a new taxonomy file?

      The Google product taxonomy is a tree of categories that will help you generate values for the 'Google product category' attribute. It lists all possible values for the 'Google product category' attribute.

      In that page, choose the language you want to use for your taxonomy at the bottom right. Then, in the Downloadable taxonomy, open the Plain Text link that contains full category names.

      Save that file and paste it in:
      Magento Root Directory › Lib › Wyomind › google

      Don't forget to apply the permissions 755 to the file.

      You'll then be able to choose that specific taxonomy from your data feed configuration.

      Filters

      Simple Google Shopping also allows you to filter your products on several levels according to their attribute sets or their visibility for example.

      Product Type
      First of all, you can choose to include products to your feed according to their type. For example, only include simple, virtual and downloadable products.
      Attribute Set
      You have the choice to include several attribute sets. In our case, we've decided to include only attribute sets that are linked to the Apparel category.
      Product Visibility
      Then, choose the products that will be included to the feed between the products that are not visible individually, products from the Catalog, the Search results, or both.
      Advanced Filters

      In the Advanced filters, you can go further by setting more personalized filters.
      For example, we wanted to include only products which price is higher than 0, and which SKU and name are not null.

      Here again, you have the possibility to configure your advanced filters according to several options.

      • LIKE / NOT LIKE

        name like %shirt: will include all products which name ends with 'shirt
        name like Apple%: will include all products which name starts with 'Apple' 
        name like %women%: will include all products which name contains the 'women' character string
        name not like %shirt: won't include any product which name ends with 'shirt'
        name not like Apple%: won't include any product which name starts with 'Apple' 
        name not like %women%: won't include any product which name contains the 'women' character string.

      • IS NULL / IS NOT NULL

        Special price is null: will include all products that don't have special prices
        SKU is not null
        : will include all products which SKU is not null

      • IN / NOT IN

        Brand in Acer, Apple, Sony: will include only products from these 3 brands
        Brand not in Dell, Toshiba: will include all products which brand is not Dell or Toshiba.

      • EQUAL TO / NOT EQUAL TO / LOWER THAN ( OR EQUAL TO ) / HIGHER THAN (OR EQUAL TO)

        Brand is equal to Acer: will include only products which brand is Acer
        SKU is not ABC123: will include all products which sku is not equal to ABC123
        Price is higher than or equal to 1.00: will include all products which price is higher than or equal to 1.00

      Advanced filters can be grouped into sub-division by using AND/OR clauses.

      (SKU LIKE ABC% AND Brand = Acer) OR  (Brand IN Dell, Toshiba AND Price >= 99.99)



      The option must be enabled in 
      System › ConfigURATION › Wyomind › Simple Google Shopping

      Scheduled tasks

      Simple Google Shopping provides you a fully configurable schedule in the Scheduled task tab of your template configuration for each data feed. You just have to tick the days and hours when you want your feed to be generated.

      See also Generate the data feeds automatically through the cron tasks

      STEP 3: Generate/Download the data feeds

      Generate the data feeds manually

      There are two different ways you can use to generate your data feeds: 

      • You can generate your data feeds manually in the grid from the action dropdown.
      • Or you can do it from the configuration panel by clicking on "generate"

      Generate the data feeds automatically through the cron tasks


      You can generate your data feeds automatically using the cron tasks. 

      First, check that the main cron task is enabled on your server.

      If it is disabled, a warning message will appear in Simple Google Shopping.

      You have to select the days and time frames for the data feeds you want to update, in the Scheduled Tasks tab.

      Check our Faq about cron taks for more information about how to configure the cron tasks from your server CPanel.

      Simple Google Shopping also provides you a cron job reporting, so you can get email reports on each data feed you will generate.

      Generate the data feeds from the command lines


      Simple Google Shopping
      allows generating data feed via the command lines:

       php -f shell/wyomind_simplegoogleshopping.php -- [options]

      The following options are available:

      • --generate
        Generate all data feeds
      • --generate id1,id2,...,idN
        Generate data feeds from the given list
      • --list
        List all data feeds

      Download the generated data feed


      When a data feed is ready to be downloaded, the link is displayed in both, the data feed grid and the data feed page at the top of the page. You can download the data feed directly by right-clicking + save as or from your ftp client if the directory where the data feed is stored is not publicly accessible.

      Note that the random parameter at the end of the url avoids caching issue when you download the data feed from your Magento admin.

      Step 4: Check the data feed status and report

      Data feed status


      Go to:
      Catalog › Simple Google Shopping

      Your data feed will be listed according to IDs.You will find the name of the file, its path as well as the link to the data feed file. You should also get a message that sums up the number of products exported, the time it took and the number of errors and warnings in your data feed.

      The status of your data feed will vary according to the situation:

      • Pending
        The data feed has never been generated or the scheduled hour is passed (waiting for the execution of the cron task)
      • Success
        Successful generation of the data feed, manually or automatically (the generation corresponds with a schedule)
      • Hold
        Generation in progress (latency, undetermined status)
      • Processing
        The data feed is processing
      • Error
        The generation is stopped

      You should find the date and the hour of the last generation of the data feed as well as the Store view taken into account for the data feed.

      Errors and warnings reports


      Those reports do not replace the error reports from Google and are by no means a guarantee that your data feed will be approved by the Google team. This will help you to save time by quickly identifying the main problems of your data feed and by making the necessary changes.

      The reports are available:

      • from the action dropdown in:
        Catalog › Simple Google Shopping
      • from the blackbox when editing a data feed
      • In orange will be displayed the warnings
      • In red will be displayed the error that you must correct to be able to submit your data feed 

      Next to these errors or warnings, you should see the number of items that are concerned.

      By default, the reports will give the 10 first examples ( sku ) that are concerned with each error and warning. You can change that by editing the Items in preview in:
      System › ConfigURATION › Wyomind › Simple Google Shopping › Core Settings

      Manage your data feed templates

      10 Things to know when creating an XML data feed

      1.  An XML data feed is made of XML tags using an opening and closing tag that includes a value.
        <g:id>123456</g:id>
        <price>45.99 USD</price>​
      2. A data feed template is made of several tags including a dynamic or a fixed values
        <g:id>{sku}</g:id>
        <price>{price}</price>
        <g:brand>Fixed Brand</g:brand>
      3. Dynamic values are called variables and use the attribute codes of your Magento website. Attribute codes must be surrounded by brackets
        <g:id>{sku}</g:id>
        <title>{name}</title>
        <g:color>{color}</g:color>

      4. Between every opening and closing tags, you can also include some fixed values. Fixed values are simply text.
        <g:brand>YOUR BRAND</g:brand>
      5. You have also the possibility to add several variables and fixed values in a same tag.
        <title>{name},available in {color}-{size} for only ${price}</title>
      6. You're allowed to use PHP code if you want to customize the pattern. You just have to write your PHP code in one single line, and it will work perfectly (check how to add PHP scripts into your templates).
        <g:gender><? if (stristr($product->getName(),"dress")) return "Female"; else "Male"; ?></g:gender>


      7. The syntactic coloration in Simple Google Shopping will help you to avoid any error in your template. First, the errors will be underlined in yellow. You need to correct each error before checking syntax once again. Finally, you'll be able to check data.

      8. Some Magic variables will act as shortcuts to create complete portions of XML in your data feed including the appropriate variables.
        {G:PRODUCT_TYPE}
      9. You can use one or more fallback variables in case of the previous is empty or null.
        {color | colour | custom_color}

        If attributeA exists then the value will be attributeA, otherwise, the value will be attributeB, etc...


      10. CDATA are recommended. CDATA stands for Character Data. It means that the data in between these tags include data that could be interpreted as XML markup, but should not be. (Wikipedia article)
        <description><![CDATA[<p>Fantastic <b>Watch</b>, that not only tells you what time it is,
        but also gives the weather trends</p>]]></description>​

      Attribute specifications

      PARENT ATTRIBUTES


      Most of the time simple products are related to parent products like configurable, grouped and bundle products. That is why you might need to retrieve Parent attribute values instead of simple product attribute values such as url, image, description...

      {attribute_code parent}

      Retrieves the first parent attribute value.

      The parent value is retrieved only if the simple (item) product is associated with a parent product, if not, its own attribute value is retrieved.

      The parent product may be a configurable, a grouped or a bundle product. The first parent product that matches the simple product is used to get the attribute value.

      Eg:

      {G:PRODUCT_TYPE parent}
      <g:product_type>{categories parent,[last]}</g:product_type>
      {attribute_code configurable}

      Retrieves the first configurable parent attribute value.

      The configurable product value is retrieved only if the simple product is associated to a configurable product, if not, its own attribute value is retrieved.

      Eg:

      {G:IMAGE_LINK configurable}
      <g:image_link>{image configurable}</g:image_link>
      {attribute_code grouped}

      Retrieves the first grouped parent attribute value.

      The grouped product value is retrieved only if the simple product is associated to a grouped product, if not, its own attribute value is retrieved.

      Eg :

      {G:GOOGLE_PRODUCT_CATEGORY grouped}
      <link>{url grouped}</link>
      {attribute_code bundle}

      Retrieves the first bundle parent attribute value.

      The bundle product value is retrieved only if the simple product is associated to a bundle product, if not, its own attribute value is retrieved.

      Eg:

      {G:SALE_PRICE bundle}
      <g:price>{price bundle}</g:price>

      PRODUCT IDENTIFIERS

      {id}

      Retrieves the product id.

      For example:

      <g:id>{id}</g:id>
      {G:ID}

      Is the shortcut for:

      <g:id>{sku}</g:id>

      You can retrieve the id instead of the sku by adding an option:

      {G:ID,[id]}
      {G:ITEM_GROUP_ID}

      Is the shortcut for:

      <g:item_group_id>{sku configurable}</g:item_group_id>
      {sku}

      Retrieves the product SKU

      For example:

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

      Retrieves the brand of the product.

      For example:

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

      Retrieves the brand of the product.

      For example:

      <g:manufacturer>{manufacturer}</g:manufacturer>

      BASIC INFORMATION

      {name}

      Retrieve the product name

      For example:

      <g:title>{name}</g:title>
      {G:TITLE}

      Is the shortcut for:

      <title>{name}</title>
      {description}

      Retrieves the description of the product.

      For example:

      <g:description>{description}</g:description>
      {G:DESCRIPTION}

      Is the shortcut for:

      <description>{description}</description>

      You can retrieve the short description instead by adding a parameter:

      {G:DESCRIPTION,[short]}
      {short_description}

      Retrieves the short description of the product.

      For example:

      <g:description>{short_description}</g:description>
      {condition}

      Retrieves the condition of the product.

      For example:

      <g:condition>{condition}</g:condition>
      {weight}

      Retrieves the weight of the product.

      For example:

      <g:weight>{weight}</g:weight>

      PRICES AND PROMOTIONS

      {price}

      Retrieves the normal price or the special price if it exists.

      For example:

      <g:price>{price}</g:price>


      You also have the possibility to use 2 parameters with this attribute:

      • currency must be an ISO3 code. This option automatically converts the original product price to a specified currency.By default, your local currency is used.
      • vat_rate can be a float number that represents the VAT percentage or a ISO2 country code, then the VAT rate will be automatically applied depending on the country and the tax class. VAT can also be substracted by using the minus (-) prefix.
      <g:price>{price,[currency],[vat_rate]}</g:price>

      Here are a few examples:

      To convert the prices to EUR and apply a 20% VAT rate:

      <g:price>{price,[EUR],[20.0]}</g:price>

      To convert the prices to EUR excluding tax:

      <g:price>{price,[EUR],[0]}</g:price>

      To convert the prices to EUR and apply the VAT rate that applies for France:

      <g:price>{price,[EUR],[FR]}</g:price>

      To convert the prices to USD and apply the VAT rate that applies in United States / New York:

      <g:price>{price,[USD],[US/NY]}</g:price>

      To convert the prices to USD and remove the VAT that applies in United States / New York::

      <g:price>{price,[USD],[-US/NY]}</g:price>
      If your prices are including VAT, then var_rate parameter must be omitted.
      <g:price>{price,[currency]}</g:price>


      Here are some examples:

      To convert the prices to EUR

      <g:price>{price,[EUR]}</g:price>

      To convert the prices to USD

      <g:price>{price,[USD]}</g:price>
      {G:PRICE}

      Is the shortcut for:

      <g:price>{price}</g:price>

      The same parameters as {price} may apply.
      {normal_price}

      Retrieves the price and ignores any existing special price value.

      For example:
      <g:price>{normal_price}</g:price>

      The same parameters as {price} may apply.
      {special_price}

      Retrieves the promotional price (special price) if exists.

      If this price doesn't exist the value is null.

      For example:
      <g:price>{special_price}</g:price>

      The same parameters as {price} may apply.
      {price_rules}

      Retrieves either the price or the special price or the price including the catalog price rules if indicated.

      For example:

      <g:price>{price_rules}</g:price>

      You also have the possibility to use some parameters with this attribute:

      • currency is for currency conversion. This option automatically converts the original product price to a specified currency. It uses an exchange rate already stored by you in your admin panel. By default, your local currency is used.
      • vat_rate is a floating value between 0.00 and 100.00 that represents an arbitrary VAT rate to apply. This option rewrites the VAT rule for the product except if the product doesn't have any tax class.
      • customer_group_id allows you to determine which price rules must apply for a given custom group id (by default the "NOT LOGGED IN" customer group applies)
      <g:price>{price_rules,[currency],[vat_rate],[customer_group_id]}</g:price>
      {G:SALE_PRICE}
      Is the shortcut for:
      <g:sale_price>{special_price}</g:sale_price>
      <g:sale_price_effective_date>{special_from_date}/{special_to_date}</g:sale_price_effective_date>
      Must be used in combination with {normal_price}:
      <g:price>{normal_price}</g:price>
      {G:SALE_PRICE}

      The same parameters as {price} may apply.
      {is_special_price}
      Retrieves either 1 if a special price exists or 0 if it doesn't.
      {is_special_price?[value_if_yes]:[value_if_no]}
      • value_if_yes value to retrieve if a special price exists. By default 1.
      • value_if_no value to retrieve if no special price exists. By default 0.


      For example:

      <g:is_special_price>{is_special_price?[yes]:[no]}<g:is_special_price>
      {min_price}

      Retrieves the minimum price.

      For example:
      <g:price>{min_price,[EUR],[20.0]}</g:price>
      {min_price} must be used for Configurable, Bundle and Grouped products.
      The same parameters as {price} may apply.
      {max_price}

      Retrieves the maximum price.

      For example:
      <g:price>{max_price,[EUR],[20.0]}</g:price>
      {max_price} must be used for Configurable, Bundle and Grouped products.
      The same parameters as {price} may apply.
      {G:PROMOTION_ID}

      Retrieves the product promotion id if exists.

      To know more about the use of this attribute, check out our doc on Google Merchant Promotions extension.

      {url}
      Retrieves the product's absolute url.
      For example:
      <link>{url}</link>


      The url attribute can receive the currency code as an url parameter to display the landing page with a specific currency, for example:

      <link>{url}?currency=USD</link>


      With children of configurable products {url} can be used with 2 additional parameters as follows:

      {url,[variant],[force]}

      • variant (optional) generates the url of the configurable product including  additional parameters that may help to display the price of the variant and to pre-select the configurable attribute
      • force (optional when using variant) forces to reload the product model (useful if the configurable attributes are not included in the template)
      <link>{url,[variant]}</link>​
      // return for example: https://www.website.com/product-page.html?c=583&391=768#391=768

      Is the shortcut for:

      <link>{url}</link>
      {image}
      Retrieves the product's main image.

      {image,[index]}
      • index is the index of any additional images to retrieve. By default 0 (the main image).

      For example:

      <g:image_link>{image,[0]}</g:image_link>
      Is the shortcut for:
      <g:image_link>{image}</g:image_link>
      <g:additional_image_link>{image,[1]}</g:additional_image_link>
      <g:additional_image_link>{image,[2]}</g:additional_image_link>
      ...
      {host}

      Retrieves the host url, for example https://www.website.com.


      An example with attribute {small_image}:

      <g:image_link>{host}/media/catalog/{small_image}</g:image_link>
      {url_key}
      Retrieves the product canonical relative url. For example:
      <g:url>https://www.mywebsite.com/mystore_code/{url_key}</g:url>

      CATEGORIES

      {categories}

      Retrieves a list of category paths separated by "," in which the product may be found

      {categories,[number_of_category_path],[from_category_level],[number_of_categories_in_each_path]}

      • number_of _category_path, by default infinity
      • from_category_level, by default 1 (root catalog)
      • number_of_categories_in_each_path, by default infinity


      Example:

      <g:categories>{categories,[INF],[1],[INF]}<g:categories>

      2 arguments can be used to specify the path separator and the category separator:

      {categories,[path_separator],[category_separator]}

      • path_separator, by default "comma" (,).
      • category_separator, by default "higher than" (>)


      Example:

      <g:categories>{categories,[,],[>]}<g:categories>

      Only one argument can be used to get the first or the last (deepest) category path:


      Example:

      <g:categories>{categories,[last]}<g:categories>
      <g:categories>{categories,[first]}<g:categories>

      A complete list of all categories per product can be retrieved with the following method:

      <? $product->getCategoriesArray(); ?>
      {G:PRODUCT_TYPE}
      Has no equivalent, this attribute 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>
      This attribute generates a tag for each category in which the product is classified.
      Options: see {categories}
      {category_mapping}

      Retrieves any new category that you have assigned (in the Categories filter) to the item's own product category. If no mapping is assigned to the first category found, the second category will be used etc.

      {category_mapping,[index]}

      • index: index of the category mapping

      For example:

      <category>{category_mapping,[0]}</category>
      <category>{category_mapping,[1]}</category>
      <category>{category_mapping,[2]}</category>
      <category>{category_mapping,[3]}</category>
      <category>{category_mapping,[4]}</category>

      Will retrieve a maximum of 5 category mappings in 5 separate tags.

      {G:GOOGLE_PRODUCT_CATEGORY}

      Is the shortcut for:

      <g:google_product_category>{category_mapping,[0]}</g:google_product_category>

      This magic attribute retrieves the Google category that you assigned (in filter section/category filter) of the first category found to which the product is linked. If no Google category is assigned to the first category found, the second category will be used, if no Google category is assigned to the second, the third will be used etc.

      To find the Google categories that match with your categories:
      https://www.google.com/support/merchants/bin/answer.py?answer=160081 

      Options: see {category_mapping}

      AVAILABILITY

      {stock_status}

      Retrieves the stock status "in stock" or "out of stock".

      For example:

      <g:availability>{stock_status,[instock],[outofstock]}</g:availability>
      {G:AVAILABILITY}

      is the shortcut for:

      <g:availability>{is_in_stock?[in stock]:[out of stock]:[available for order]}</g:availability>

      Options: see {is_in_stock}

      {is_in_stock}
      Retrieves either "in stock" if the product is in stock, "out of stock" if the product is out of stock or "available for order" if the product is backordered. {is_in_stock?[value_if_in_stock]:[value_if_out_of_stock]:[value_if_preorder]}  
      • value_if_in_stock value to retrieve if the product is in stock
      • value_if_out_of_stock value to retrieve if the product is out of stock
      • value_if_preorder value to retrieve if the product is backorderable

      For example:

      <g:availability>{is_in_stock?[in stock]:[out of stock]:[preorder]}</g:availability>
      {qty}

      Retrieves the available quantity.

      The quantity retrieved for the configurable products is based on the sum of simple products.

      For example:

      <g:availability>{qty}</g:availability>

      PRODUCT VARIANTS

      {gender}

      Retrieves the gender of the product.

      For example:

      <g:gender>{gender}</g:gender>
      {age_group}

      Retrieves the age group of the product.

      For example:

      <g:age_group>{age_group}</g:age_group>
      {color}

      Retrieves the color of the product.

      For example:

      <g:color>{color}</g:color>
      {size}

      Retrieves the size of the product.

      For example:

      <g:size>{size}</g:size>
      {material}

      Retrieves the material of the product.

      For example:

      <g:material>{material}</g:material>
      {pattern}

      Retrieves the pattern of the product.

      For example:

      <g:pattern>{pattern}</g:pattern>

      FUNCTIONS

      You can apply one or more functions to all attributes by using the following syntax:

      {attribute_code,[option1],[option2],[option3],[...]}

      All options are executed in the written order eg:

      <title>{name}</title>
      <title>{name,[htmlentities],[strtolower]}</title>
      <title>{name,[htmlentities],[strtolower],[ucwords]}</title>

      will produce:

      <title>NOKIA© 2610 Phone</title>
      <title>nokia&copy; 2610 phone</title>
      <title>Nokia&copy; 2610 Phone</title>
      {attribute_code,[strip_tags]}

      Removes all html tags.

      For example:

      <description>{description,[strip_tags]}</description>
      {attribute_code,[cleaner]}

      Removes all characters that don't belong to the utf8 charset.

      For example:

      <title>{name,[cleaner]}</title>
      {attribute_code,[substr],[max_length],[end_string]}
      Truncates the value.
      • max_length: maximum length of the value
      • end_string: string that will be added at the end of the string. By default: [...]

      For example:

      <description>{description,[substr],[50],[...]}</description>
      {attribute_code,[strtoupper]}

      Transforms the value to upper case.

      For example:

      <title>{name,[strtoupper]}</title>
      {attribute_code,[strtolower]}

      Transforms the value to lower case.

      For example:

      <title>{name,[strtolower]}</title>
      {attribute_code,[inline]}

      Removes all EOL characters from the value.

      For example:

      <description>{description,[inline]}</description>
      {attribute_code,[html_entity_decode]}

      Converts all HTML entities to their applicable characters.

      For example:

      <description>{description,[html_entity_decode]}</description>
      {attribute_code,[htmlentities]}

      Converts all applicable characters to HTML entities.

      For example:

      <description>{description,[htmlentities]}</description>
      {attribute_code,[implode],[separating_string]}

      Joins all array elements in a string.

      • separating_string: string used between each value. By default it is a comma (,).

      May be useful for multi-select attributes like color.

      For example:

      <g:color>{color,[implode],[,]}</g:color>

      will give: black, blue, red, green.

      {attribute_code,[float],[decimals]}

      Converts a numeric value to a floating number.

      • decimals: number of floating number. By default [0].
      For example:
      <g:shipping_weight>{weight,[float],[2]}kg</g:shipping_weight>

      STOCK IN THE CHANNEL USERS


      The Stocks in The Channel users can use the following attributes in order to build their data feeds :

      {SC:URL} or {sc:url}

      Retrieves the canonical url of the product :

      <link>https://www.example.com/product.html</link>
      {SC:EAN} or {sc:ean}

      Retrieves an unique ean value of the product:

      <g:ean>1234567891234</g:ean>
      {SC:IMAGES} or {sc:images}

      Retrieves the associated image of each product :

      <g:image_link>https://www.example.com/media/catalog/image.jpg</g:image_link>
      {SC:DESCRIPTION} or {sc:description}

      Retrieves the description for the product:

      <g:description>...product description ...</g:description>

      A default value is retrieved when the description is empty.

      PHP API for Simple Google Shopping

      With Simple Google Shopping you can use PHP scripts in different ways to fully customize and control the data feed output.

      Inline PHP scripts directly in the data feed template surrounded by PHP short tags (<? ... ?>).

      For example, to resize your images:

      <? /* {images} */ return Mage::helper('catalog/image')->init($product, 'image')->resize(265,265); ?>

      API coding standards


      The Simple Google Shopping PHP API uses the exact same syntax and standards than any PHP coding.

      Attribute calls

      For performance reasons, Simple Google Shopping only loads in the collection of products the attributes that are explicitly required in the data feed template.

      This means that only the attributes that are called using the template placeholders, {attribute_code}, will be added to the collection of products.

      As a consequence, when you try to access the value of an attribute from the $product object, you must be sure that the attribute has been added to the collection.

      Most of the time when the returned value is null for a given attribute, it means the attribute is not loaded in the collection of products.

      The best way to be sure that all the attributes you need are well loaded in the collection, is to add at the beginning of your template a simple script that lists all the attributes required.

      <?
      /* list of required attributes
      * {attribute_1} {attribute_2} {attribute_3} {attribute_4}...
      */
      ?>

      Then you should be able to get the values of these attributes in your PHP script:

      <? return $product->getAttribute1();?>
      <? return $product->getAttribute2();?>
      <? return $product->getAttribute3();?>
      ....
      PHP functions in attribute calls

      You can use any PHP function to apply in the attribute calls even if the function requires one or more additional arguments, for instance:

      {name,[str_replace("Apple","Banana",$self)]}

      You can use several consecutive functions:

      {ean,[str_pad($self,10,"0",STR_PAD_LEFT)],[str_replace("X","0",$self)]}
      Conditional values

      To output values based on different conditions, use PHP conditional statements:

      • if/else
        <?
        /* attribute {sku} required */
        if ($product->getSku()=="abc"){
        return "Alphabetic";
        }
        elseif($product->getSku()=="123"){
        return "Numeric";
        }
        else{
        return "Mixed";
        }
        ?>
      • switch/case
        <?
        /* attribute {sku} required */
        ($product->getSku()){
        case "abc":
        return "Alphabetic";
        break;
        case "123":
        return "Numeric";
        break;
        default:
        return "Mixed";
        }
        ?>
      Opening and closing tags

      When using the PHP API inline directly in your data feed template, you must use the opening and closing short PHP tags (<? ... ?>)

      <?
      if($product->getData('size')=="X-Large") {
      return "XL";
      }
      ?>
      Outputting a value
      • Return
        Any value that you want to output in your data feed, must be returned with the return instruction.
      <? return "Don't miss! ".$product->getTitle(); ?>
      /* This script adds for each product in data feed  a new ouput line
      *  Don't miss! Iphone 5
      *  Don't miss! Galaxy note 7
      *  ...
      */
      • echo, var_dump, print_r
        Any value printed in the data feed through these functions will be rendered at the top of the data feed and will not be added to the final file.
        Such functions must be used for debugging purposes.
      <? var_dump($product->getTitle()); ?>
      /* This script adds for each product in data feed  a new debugging trace
      *  String(8) "Iphone 5"
      *  String(13) "Galaxy note 7"
      *  ...
      */
      Variables scope

      All variables available in PHP scripts have a local scope, this means they can't be shared between several scripts.

      If you wish to share a variable with different scripts all along the data feed generation process, then the variable must be set as a global variable.

      <?
      global $increment;
      $increment++;
      return $increment;
      /* This script will output a incremental $variable
      * 1
      * 2
      * 3
      * ...
      */
      ?>

      API Objects, Variables and Methods

      Object $product

      $product is an instance of Mage_Catalog_Model_Product. It contains all methods available by default and some other specific to Simple Google Shopping.

      The list below is not exhaustive but lists the most useful methods.

      • $product->getCategoriesArray()
        Retrieves an array of arrays that describes the categories to which belongs the products
      • $product->getCategoryIds()
        Lists all category ids in which the product may be found
      • $product->getVisibility()
        Returns the visibility of the product (1 = not visible individually, 2 = catalog, 3 = search, 4 = catalog and search)
      • $product->getStatus()
        Returns the status of the product (1 = enabled, 2 = disabled)
      • $product->getData($attributeCode)
        Returns the value of the given attribute code
      • $product->getAttributeText($attributeCode)
        Returns the textual value of the given attribute code
      Object $this

      $this is an instance of Wyomind_simplegoogleshopping_Model_Feed. It provides a few useful methods.

      • $this->hasParent($product, $type="parent")
        Returns a Boolean value whether a product has a parent from the given type (parent, configurable, grouped, bundle) or not
      • $this->getParent($product, $type="parent", $strict=false)
        Returns a product object of the given parent type (parent, configurable, grouped, bundle) if available or the product object passed as 1st parameter when $strict parameter is set on false.
      • $this->skip()
        Skips the current product, useful to filter out some products based on specific condition

      Manage your Google Shopping data feeds in your Google Merchant Account

      Each store is different, this is why you must pay particular attention to how is configured your data feed to be sure that it matches your own needs. We highly encourage you to check how to use Simple Google Shopping before starting using our extension and before submitting your data to Google Merchant.

      Be careful, a wrong configuration or an invalid data feed may result in the suspension of your Google Merchant Center account.

      Create a data feed in Google Merchant

      To create a data feed, click on the PLUS icon from your Google Merchant Center account in:
      Products Feeds

      Basic information

      Start with filling in the basic information:

      • Type
        The "Products" feed type is to submit your Google Shopping product information.
      • Country of Sale
        Choose the country where the products included in your data feed are sold and will be shipped. Note that these items must meet the requirements for the country of sale you submit to, including the feed specifications and policies.
      • Language
        It is the language of the content in your feed. Each country of sale has accepted content languages.
      • Destinations
        Select which Google products can display the items in your data feed.

        Shopping ads

      Once it's filled in, click on Continue.

      Name and input method

      You can continue with the name and the input method of your data feed.

      • Primary feed name 
        This is the name of the data feed as it will appear in your merchant account and help you understand the content of the feed.
        Note that the feed name does not need to match the name of the actual file you’re submitting.

      Now choose how to connect your data to Merchant Center. You have several options:

      • Google sheets
        If you're updating your product data via a Google Sheet.
        Note that the changes will automatically be applied to your account.
      • Scheduled Fetch
        If you're hosting a file on your website that contains data and scheduling a regular time for Google to fetch updates.
        Note that updates are only applied to your account when the fetch occurs.
      • Upload
        If you prefer keeping a file on your computer that contains data and regularly uploading it to your account through SFTP, FTP, Google Cloud Storage, or manually.
      • Content API
        If you're using the Content API for Shopping to automatically upload product listings.

      Click on Continue.

      Using the Simple Google Shopping extension, we advise choosing the Scheduled Fetch or the Upload method.
      Setup for Scheduled Fetch

      If you have selected the Scheduled Fetch to connect your data to Merchant Center, fill in the below info:

      • File name
        This is the exact file name that you can find in the File name column from:
        Catalog › Simple Google Shopping
         

        Googleshopping_full.xml

      • Fetch Frequency
        Choose to update your data daily, weekly or monthly.

      Note that Fetch frequency must be synchronized with your catalog updates. A daily fetch frequency requires to monitor your data feeds daily.

      • Fetch Weekday/Date
        Choose the day of the week/month when to update your data feed.
      • Fetch Time
        Choose the time when Google must fetch the data feed.
      • Time zone
        Select your locale time zone
      • File URL
        Add the URL that appears in the File link column when the data feed is generated from:
        Catalog › Simple Google Shopping
      • Login and Password
        Add your login and password in the case where the data feed is protected with http authentication.

      Click on Continue.

      Be careful to synchronize the fetching time with the data feed generation time. For example, when the data feed is generated at 01:00 AM, Google should fetch the data feed at 02:00 AM.

      Setup for Upload

      If you've selected the Upload method, fill in:

      • File name
        This is the exact file name that you can find in the File name column from:
        Catalog › Simple Google Shopping
         

        Googleshopping_full.xml

      • Upload a file now
        You can now directly upload or drop your file.

      Click on Continue.

      Fetch data

      The data feed should then be displayed in the data feed list from:
      ProductsFeeds

      Open the new data feed and click on  Fetch Now.

      Fix the errors and warnings of the data feed

      Once the data has been fetched a report is generated including errors and warnings that must be fixed.

      You can have a clear overview of your products status from the Diagnostics tab. Check how many products are: 

      • Active
      • Expiring
      • Pending
      • Disapproved

      Errors

      Here is a few examples of the common errors in Google Merchant Center. 

      Note that the errors will appear with a red exclamation mark.

      Invalid URL

      All the errors linked to the URL are due to the fact that you didn't specify the URL of your website in your Google Merchant Center account or it is not claimed, so go to:
      Google Merchant Center › Business Information › About Your Business › Website

      Missing shipping information

      If you get this error, it is because you didn't configure a shipping rule in your Google Merchant Center account or if you did, you didn't do it for the target country.

      For that, go to:
      Shipping › Services

      Here you can add a new rule just by clicking on the  + button.

      Then, fill in the different settings and click on Save.

      Insufficient product identifiers: Missing brand attribute

      That error occurs when products don't have a brand. For example, clothing items need a "brand" value.

      You can first check that you're using the right attribute in your data feed template. For example, you may be using:

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

      instead of:

      <g:brand>{brand}</g:brand>

      Otherwise, you can add an attribute from your Magento back-office and define a brand for each one of those products from your admin:
      Magento › Manage products

      In the case where all your products have the same brand, you can also define in your data feed configuration that all products will get the brand XXX by writing:

      <g:brand>XXX</g:brand>

      In the case where your products don't have enough identifiers, you can define that there is no identifier existing by replacing:

       <g:identifier_exists>true</g:identifier_exists>

       by:

      <g:identifier_exists>false</g:identifier_exists>
      Missing required attribute: age group

      That error is due to the age group. In the case where you sell items for only one age group (adult), you could edit the data feed template with:

      <g:age_group>adult</g:age_group>

      In the case where you're selling products for adults and for children, you will need to add an attribute from your Magento back-office (for example age_group) and specify the age group for each one of your products in your Magento admin:
      Magento › Manage products

       and keep in your data feed template:

      <g:age_group>{age_group}</g:age_group>
      Missing required attribute: color

      Concerning that error, it means that there is no "color" value found for some products.

      You can first check that you're using the right attribute in your data feed template. For example:

      <g:color>{colour}</g:color>

      instead of:

      <g:color>{color}</g:color>

      Also, you may not have defined a color value for a particular product in your Magento admin:
      Magento › Manage products

      Currency is not supported in the given country in attribute: price

      When currency is not supported in the given country, it means the currency defined in the data feed template in not the same as the currency of your products.

      For example, the currency defined in the template is in EUR whereas your products prices are in USD. In that case, every EUR must be changed into USD in your data feed template.

      Missing required attribute: size

      When size attribute is missing, you can first check that your products have an attribute for size.

      For example, for the shoes category, the attribute for size may differ. You can have a look in the black box, in your data feed template configuration, to see if there is already an existing size attribute for shoes by clicking on   Attributes Library.

      As you can see, the size attribute for shoes exists under the name of {shoe_size}. Then you can add it to your data feed template as below: 

      <g:size>{size}{shoe_size}</g:size>

      Warnings

      With Google Merchant Center, you can also have an overview of the warnings. Warnings are not penalizing because your products are inserted to Google Shopping however it is better no to have some.  

      Note that the warnings will appear with an orange warning sign.

      That warning means that some of the products don't have image link.

      You can have a look at some products involved. The problem may be that the products are variants of configurable ones.

      The solution would be to modify the template  in order to get the image links of the parent products and to replace:

      {G:IMAGE_LINK}

       by:

      {G:IMAGE_LINK parent}

      When a description is missing, you can simply edit the product directly from your Magento back-office:
      Magento › Manage products 

      When Google product category is missing, it means that you didn't map your categories with Google ones.

      For that, go in the Categories tab of your data feed template, from:
      Catalog › Simple Google Shopping

      FAQ

      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 migration to Magento 2

      We offer our customers who want to migrate their Magento 1 license to a Magento 2 license, the transfer at a reduced price. 

      You have the possibility to migrate your license directly from your Wyomind account in:
      My account › Licenses & Downloads

      Click on migrate to magento 2  in front of the extension and the domain you want to transfer. 

      Confirm you want to migrate your license to a Magento 2 license by clicking on Confirm and checkout .

      An invoice will be automatically added to your account from: 
      My account › Invoices

      The price of the transfer is equivalent to a 30% reduction compared to the price of the regular Magento 2 license.

      You can proceed to the payment by clicking on PP .

      Once the payment is done, you can go back to: 
      My account › Licenses & Downloads

      There you will be able to download and install your license for Magento 2. 

      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 one.

      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 period does. By purchasing an extension, you’ll be granted a 6-month support period for free. Passed this period, you will have to renew your Support plan (see FAQ: How to extend my support period?).
      Domains pre-registration

      You can pre-register your live domain to your license 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: 

      1. Go to:
        mY account › Licenses & DOwnloads
      2. Click on  next to the extension you want your domain to pre-register on.
      3. Click on the link at the bottom of the page saying:
        Do you want to pre-register your domain in order to be ready to go live?
      4. Finally, enter your domain name and click on pre-register now .
      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 2 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 want to transfer your license to another live domain.
        In that case, the support period for your license must still be active.


      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 in:
        syStem › CONFIGuration › WYOMING › YOUR EXTENSION 
      5. Save your configuration.


      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 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.

      Modules versioning and download

      Extensions download

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

        1. Go to:
          my account › Licenses & downloads 
        2. Click on the  icon 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  .

      Your download can start.

      Extensions upgrade

      When purchasing an extension from wyomind.com, you benefit from a lifetime upgrade. You can at any time download the latest version of the extension directly from your account. 

      To upgrade Simple Google Shopping, follow the steps below:

      1. Go to:
        my account › Licenses & 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. Install the new version of Simple Google Shopping to update your Magento admin. 

      Modules Installation/Uninstallation

      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 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:
        system › select cache type › actions › refresh › submit


      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

      Modules activation

      Extensions activation

      Once Simple Google Shopping is installed, 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:
        SysteM › Configuration › 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 license server will be automatic. 
        - By choosing No, you will have to log on to Wyomind license server yourself.

      4. Save the configuration.
      5. Clear your caches. 
      6. A message appears at the top of your admin panel: Activate it now!  Click on that link.
      7. Copy and paste the license code in the License code field from your admin or simply click on  Activate now! 
      8. 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 extension, using the corresponding activation keys (each module has its own activation key).

      Magento and Google accounts access

      Google Merchant account access

      So that our team can proceed with the configuration of your data feed, we need you to share the access to your Google Merchant account with us. 

      As Google Partner, we offer many possibilities to manage your products on Google. Feel free to check our Google Shopping services for more information about the data feed configuration.  

      To share your access, go to your Google Merchant account. 

      1. Click on Users from the parameters on the top of your account. 
      2. Click on the +  icon to add a user and fill in our email address (contact us to see what email address you should use). 
      3. You can choose Standard as the user access.  
      Google Ads account access

      So that our team can proceed with the configuration of your data feed, we need you to share the access to your Google Ads account with us.

      As Google Partner, we offer many possibilities to manage your products on Google. Feel free to check our Google Shopping services for more information about the data feed configuration.  

      To share your access, go to your Google Ads account.

      1. First send us your account ID that you can find on top of your account next to your company name. We'll then be able to send you a request.  
      2. When it's done, you should have received an email. You can also check in the Managers section of your Google Ads account.
        There, you should see a request from Wyomind in your Link requests. Click on Accept from the Actions column. 
      3. A confirmation popup is displayed, click on Grant Access.
      4. Once you've granted access, you should see Wyomind among your Managers. 

      Data feed configuration

      Configurable products retrieve invalid price

      In Magento, configurable products are in fact containers for the simple variant products. Then, their price will depend on the options that the customer has selected.

      Unfortunately, as it's not possible to know in advance the choice of the customers, it is recommended to use the minimum or the maximum price in your data feeds. You can use one of the below attributes:

      {{product.min_price}}
      {{product.max_price}}
      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 (optional), 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.

      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

      Examples

      http://www.website.com/men/new-arrivals/linen-blazer.html?currency=EUR

      http://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

      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: 
        System › Tools › Compilation
        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.
      White page using the extension

      If you're getting a white page using the extension, you should enable the error reporting in order to display the error. You can do that from index.php.

      404 error in the configuration page
      Most of the time log-out/log-in may solve this issue.
      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:
      system › configuration › Wyomind › Simple Google Shopping

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

      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 simplegoogleshopping_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.
      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  lib › Google or lib › Wyomind 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 (with Display › Encoding type › utf8 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.

      User's reviews

      UKD

      Merchant · United Kingdom · User for 9 years

      ★★★★★

      Great Simple And Essential Module

      Great simple and essential module for your Magento 2 store. Easy installation, good guidance and integrates with all our other modules. Support was required a few times for various issues we had and that was first class too. Allows easy and fast creation of google merchant centre feeds. Highly recommended.

      Sergio Doglioli

      Merchant · Italy

      ★★★★★

      Just simple and power

      Excellent module: I needed to perform several exports to synchronize my platform. Nothing is simpler, faster, or more powerful than Wyomind. I had tried other modules in the past, but they all had limitations that prevented their use: with Wyomind, I finally found the ultimate solution, even for those without technical expertise.Very powerful for those familiar with the software, simple to use for beginners or those without specific database and language skills. Perfect. Thanks.

      Fern

      Merchant · United Kingdom · User for 1 year

      ★★★★★

      Good, simple extension that does the job

      all good

      October 9, 2025Magento 2

      Mr Smith

      Merchant · United Kingdom · User for 13 years

      ★★★★★

      Excellent extension, does exactly what we need

      We needed an extension to generate xml sheets for google shopping with the ability to filter out certain product types and also to filter by attributes. This extension does exactly what we need, as well as offering many more customisable options and filter settings that may be useful for others. It has been in use for several years now, generating updated xml sheets every 24 hrs which our merchant centre then pulls across keeping every products details up to date. The few times we have needed to contact support with a query, they have been quick to respond and help resolve our query quickly and without fuss. Highly recommend for any magento website which uses google shopping, this is pretty much essential.

      talc

      Merchant · United Kingdom · User for 6 years

      ★★★★★

      Google Shopping extension for Magento is fantastic

      Wyomind’s Simple Google Shopping extension for Magento is fantastic! Easy to set up, highly customizable, and saves so much time. Great support team too. A must-have for seamless feed management!

      Jose

      Developer · Spain · User for 12 years

      ★★★★★

      Easy to use, intuitive and very good documentation.

      Every day they improve the extension a lot more, besides having it always with a very extensive documentation and the support is super fast.

      September 18, 2024Magento 1 / OpenmageMagento 2

      Mark

      Merchant · United Kingdom

      ★★★★★

      A Game-Changer - Highly Recommend!

      We've been using this Magento extension for several years now, and it has truly transformed how we manage our data feeds. What sets this extension apart is its simplicity combined with incredible flexibility. Setting up product feeds was straightforward, even for team members without extensive coding knowledge. The XML customization options allowed us to tailor our feeds exactly to our needs, ensuring everything is perfectly aligned with Google's requirements.

      The extension isn’t just limited to Google Shopping. We've also successfully used it to create feeds for other marketplaces, which has expanded our reach with minimal additional effort. The ability to schedule feeds and automate updates has saved us countless hours, keeping our product data current without the need for manual intervention. We've often used it in unconventional ways on our care home website.

      Another standout feature is the exceptional support team. Whenever we've encountered a question or needed assistance, their response has been quick and helpful, ensuring that any issues are resolved promptly. The documentation provided is thorough, making it easy to navigate even the more advanced features of the extension.

      In conclusion, this extension is a must-have for any Magento-based website looking to optimize product feeds efficiently. It’s reliable, easy to use, and supported by a team that clearly knows their stuff. We highly recommend it to any business aiming to streamline their data feeds and enhance their online presence.

      ANYBRAND

      Merchant · Germany · User for 10 years

      ★★★★★

      Easy to use and efficient

      We use this module for our promotional gifts products since years now. It is easy to use and efficient. The support from Wyomind is always fast and friendly. We highly recommend this extension.

      HS

      Merchant · United Kingdom · User for 3 years

      ★★★★★

      Makes life simple

      So, I have used Google Shopping feed Extension by Wyomind for our business to generate product feeds , Much satisfied with the extension and support service they offered. Also the extension generates the precised product feeds and much according as per the requirement.Easy to install extension. The configuration backend is very clear and intuitive and also customizable. Configurable products are supported. I installed it without any problem, modules are constantly updating and the upgrade is easy.

      Don D.

      Merchant · United States · User for 8 years

      ★★★★★

      This module is really simple and work well

      We have used this module for at least 10 years now. Yes, we had to pay for extended support a few times to update the compatibility with Magento and PHP versions, but the flexibility of the XML variables and codes itself always worked.

      We have never had to change the XML file, the file created by cron, and submitted the updated version of our inventory to Google every evening and never failed.
      Although they don't advertise it, you can use this same module to create different versions of inventory files to update to different marketplaces like Facebook Shopping...

      Great module, good work you guys!

      Gonzalo

      Developer · Spain · User for 12 years

      ★★★★★

      Very good extension and comfortable to use

      It is a very easy to use extension with a little knowledge and even if you do not have the documentation is very well explained and ready to work with it.

      Also the support is very good

      December 20, 2023Magento 1 / OpenmageMagento 2bluenty.com

      Samuel K

      Merchant · France · User for 14 years

      ★★★★★

      Un outil particulièrement puissant avec une flexibilité hors pair

      Une rapidité de mise en oeuvre, une pureté des données générées et un service client réactif toujours à l'écoute pour nous accompagner dans l'optimisation des mécaniques de création des données dynamiques.

      La puissance de l'intégration de la structure XML modifiable à souhait avec la puissance du PHP, c'est la perfection à l'état pur ! Nous avons rarement été autant surpris par un outil aussi puissant et aussi facile à exploiter, chapeau bas à l'équipe de Wyomind !

      Vicki

      Merchant · United Kingdom · User for 11 years

      ★★★★★

      This module is great for uploading your products to Google

      This module is great to upload your products en mass to the google shopping centre; it is super easy to use without coding knowledge requirement.
      Everytime we have required the support, the team have provided responses within minutes and the resolution to all of our issues.
      We have used this module for over 11 years now on different versions of Magento and it has never let us down.
      A* would thoroughly recommend

      July 5, 2023Magento 1 / OpenmageMagento 2

      JoshFBC

      Merchant · United Kingdom · User for 11 years

      ★★★★★

      Solid data exporter

      We have had this module installed ever since we moved to magento two, around 3 years ago. Since then with have comprehensively used this extension to generate a Google Merchant Feed that has been ingested directly into Google with great results. We now use the plugin to send the data to a Google Comparison Shopping Service (or CSS) with great success. We have also had similar success with exporting feeds to the Meta platform via an equivalent CSS and furthermore to Pinterest too. Each of these feeds had different requirements, all of which were handled with no issue but the extension. However, we have struggled to create stable feeds for other marketplaces that do not first feed into a data aggregator. This is almost certainly due to the fact that this kind of functionality is not the scope of this extension, and the Data Feed extension that wyomind is probably a far better option. I would definitely recommend this extension for businesses who have a simple requirements to send product data to the key Marketplaces, however with caution that they may not always work as expected, especially if not further feeding the data into some form of middleware/ data aggregation software. Overall I would give this module 5 stars, as it achieves more than what we ever expected it to.

      sbakker

      Merchant · Netherlands · User for 13 years

      ★★★★★

      Excelent module! Using it for more then 10 years

      As an online retailer, I understand the importance of having a strong presence on Google Shopping to maximize product visibility and drive sales.The pleasure of using Simple Google Shopping by Wyomind, and I must say, it has been a game-changer for my business. This review aims to shed light on the exceptional features and benefits of this remarkable tool. Simple Google Shopping Wyomind is a game-changer for online retailers. Its user-friendly interface, feed optimization, synchronization, and advanced filtering make it a must-have tool. Highly recommended!

      Areeb

      Merchant · United States · User for 4 years

      ★★★★★

      The Extension is great to generate product feeds

      So, I have used Google Shopping feed Extension by Wyomind for our business to generate product feeds , Much satisfied with the extension and support service they offered. Also the extension generates the precised product feeds and much according as per the requirement. I would recommend this extension to all the bushiness merchants to use it for their business and generate the google shopping feeds so that you all can grow your businesses.

      December 18, 2022Magento 2

      Schmucker_schmuck

      Merchant · Germany · User for 4 years

      ★★★★★

      The extension simple google shopping works fine

      Hi, with simple google shopping you can create data feeds for Google shopping with templates which allow the use of PHP in it. This makes it really easy to adapt the attributes of our magento 2 shop to the guidelines of Google Shopping, it helps a lot! One minor point of criticism is that the templates from the Magento 1 extension of Wyomind which we used as well had to be quite a bit adapted to make them work in the magento2 extension simple google shopping. But overall the migration from M1 to M2 was quite an adaption, so the guys at Wyomind had to do some adaption work themselves I reckon!

      R & W Media Magento Agency

      Ecommerce Agency · United Kingdom · User for 10 years

      ★★★★★

      Best Google Shopping feed extension

      The best Google Shopping feed extension on the market place. We use this for so many of our clients' stores. Easy to set up and use, highly recommended

      November 11, 2022Magento 1 / OpenmageMagento 2

      Manuel Moreno

      Marketing Agency · Spain · User for 7 years

      ★★★★★

      Indispensable for our store

      We were using the Simple Google Shopping plugin in Magento 1, and it worked flawlessly every time. When we migrated our store to Magento 2, we opted for the same solution. The plugin is good overall and performs the functions it was created for. The support team helps with the implementation thanks to the free support period and gives you the option to increase that support time by up to 2 more months. The wyomind team is made up of great Magento certified professionals, which is what we were interested in from the beginning.

      BettyJ2

      Developer · United Kingdom · User for 8 years

      ★★★★★

      Excellent - does exactly what it says it does!

      This is a module we have been using since 2018 and in this time we have had no issues or complaints. We have also been very impressed with the level of upgrades that are available after a Magento 2 update. No complaints here!

      September 8, 2022Magento 2

      Magento 1 / OpenMage Compatibility

      Supported by our master extension versions

      • 1.14.4
      • 1.14.3
      • 1.14.2
      • 1.14.1
      • 1.14.0
      • 1.9.4
      • 1.9.3
      • 1.9.2
      • 1.9.1
      • 1.9.0

      Supported by our legacy extension versions

      • 1.13.1
      • 1.13.0
      • 1.12.0
      • 1.11.2
      • 1.11.1
      • 1.11.0
      • 1.10.1
      • 1.10.0
      • 1.8.1
      • 1.8.0
      • 1.7.0
      • 1.6.2
      • 1.6.1
      • 1.6.0
      • 1.5.1
      • 1.5.0
      • 1.4.2
      • 1.4.1
      • 1.4.0
      • 1.3.3
      • 1.3.2
      • 1.3.1
      • 1.3.0
      • 1.2.1
      • 1.2.0
      • 1.1.8
      • 1.1.7
      • 1.1.6
      • 1.1.5
      • 1.1.4
      • 1.1.3

      Changelog

      11.0.5

      11.0.4

      11.0.3

      11.0.2

      Bug fix

      • Correct an error that could prevent the feed list display

      11.0.1

      Deployment fix for the master version

      10.0.1 legacy

      Deployment fix for the legacy version

      9.6.13

      Compatibility

      • Compatibility with OpenMage

      9.6.12

      • Fix when installing the module

      9.6.11

      • Data base modification to allow managing more attribute sets

      9.6.10

      • Fix for the category mapping (copy/paste)

      9.6.9

      • Fix when updating the category mapping

      9.6.8

      • Fix for category filters

      9.6.7

      • Fix for the number of products exported

      9.6.6

      • Fix for the categories exclusion

      9.6.5

      • Fix for the category filter

      9.6.4

      • Fix for the excluding category filters

      9.6.3

      Improvement

      • Dynamic list of product types for the filters
      • Enhancement of the blackbox library
      • Link to documentation when "No cron task found" message

      Bug fix

      • Fix on review attribute
      • Fix on spelling and typos

      Patch v9.6.3.5

      • Fix when retrieving price rules

      Patch v9.6.3.4

      • Fix on the dates retrieved by {G:SALE_PRICE} 

      Patch v9.6.3.3

      • Fix on g:promotion

      Patch v9.6.3.2

      • Fix for g:image_link

      Patch v9.6.3.1

      • Fix for the {G:PROMOTION_ID} tag

      9.6.2

      Improvement

      • Price retrieves the min_price when there's no price

      Bug fix

      • Fix to avoid catching external errors when the Cron is executed

      Patch v9.6.2.4

      • Fix on the dates retrieved by {G:SALE_PRICE} 

      Patch v9.6.2.3

      • Fix for the {G:PROMOTION_ID} tag

      Patch v9.6.2.2

      • Minor fix for the attribute filters

      Patch v9.6.2.1

      • Fix on warnings for undefined variables
      • Minor fix on the temp file

      9.6.1

      Improvement

      • Better management of the status and the progress bar

      Patch v9.6.1.13

      • Fix on the dates retrieved by {G:SALE_PRICE} 

      Patch v9.6.1.12

      • Fix for the {G:PROMOTION_ID} tag

      Patch v9.6.1.11

      • Compatibility with PHP 7

      Patch v9.6.1.10

      • Fix when retrieving promo_id

      Patch v9.6.1.9

      • Fix for the urls including the category path

      Patch v9.6.1.8

      • Fix for the cron log

      Patch v9.6.1.7

      • Feeds directory is automatically added

      Patch v9.6.1.6

      • Fix for the advanced filters check-boxes

      Patch v9.6.1.5

      • Fix for PHP7 and higher

      Patch v9.6.1.4

      • Remove the useless outputs when the data feed is generated through CLI

      Patch v9.6.1.3

      • Fix for the data feed generation (no product was added to the data feed)

      Patch v9.6.1.2

      • Fix for the data feed status while the data feed is generated by Cron task

      Patch v9.6.1.1

      • Default value for the url type defined in config.xml

      9.6.0

      Improvement

      • new option for the {url} attribute: [variant] and [force]
        see {url} definition for more details

      Patch v9.6.0.8

      • Fix on the dates retrieved by {G:SALE_PRICE} 

      Patch v9.6.0.7

      • Fix for the {G:PROMOTION_ID} tag

      Patch v9.6.0.6

      • Fix for the cron log (the log wasn't disabled despite the settings)

      Patch v9.6.0.5

      • Remove the useless outputs when the data feed is generated through CLI

      Patch v9.6.0.4

      • Default value for the url type preference set to "short product urls"

      Patch v9.6.0.3

      • Fix for the category tree (the "on blur" event triggers the categories updates)

      Patch v9.6.0.2

      • Fix for the category mapping

      Patch v9.6.0.1

      • Fix for PHP version < v7.x

      9.5.0

      Improvement

      • Better tree view management for the category mapping
      • Better CLI management
      • Log can be now disabled or enabled
      • Minor code improvements

      Patch v9.5.0.11

      • Fix on the dates retrieved by {G:SALE_PRICE} 

      Patch v9.5.0.10

      • Fix for the {G:PROMOTION_ID} tag

      Patch v9.5.0.9

      • Fix on cron logs

      Patch v9.5.0.8

      • Default value for the url type preference set to "short product urls"

      Patch v9.5.0.7

      • Fix for the category tree (the "on blur" event triggers the categories updates)

      Patch v9.5.0.6

      • Fix for the category mapping

      Patch v9.5.0.5

      • Fix for the 404 error in the Google taxonomy 

      Patch v9.5.0.4

      • fix for PHP 7

      Patch v9.5.0.3

      • fix for PHP 7

      Patch v9.5.0.2

      • auto-complete for category mapping is fixed

      Patch v9.5.0.1

      • Fix for the price rules rounding

      9.4.2

      Improvement

      • Better handling of children/parent relation

      Patch v9.4.2.8

      • Fix on the dates retrieved by {G:SALE_PRICE} 

      Patch v9.4.2.7

      • Fix for the {G:PROMOTION_ID} tag

      Patch v9.4.2.6

      • Default value for the url type preference set to "short product urls"

      Patch v9.4.2.5

      • Fix for the price rules rounding

      Patch v9.4.2.4

      • automatic creation for var/tmp 

      Patch v9.4.2.3

      • Products url for EE fixed

      Patch v9.4.2.2

      • Qty and Is in Stock filters fixed
      • Useless Javascript content removed on preview box

      Patch v9.4.2.1

      • Qty and Is in Stock filters fixed

      9.4.1

      Bug fix

      • Rounding issue fixed

      Improvement

      • Better report for errors and warnings including parse errors

      Patch v9.4.1.8

      • Fix on the dates retrieved by {G:SALE_PRICE} 

      Patch v9.4.1.7

      • Fix for the {G:PROMOTION_ID} tag

      Patch v9.4.1.6

      • Default value for the url type preference set to "short product urls"

      Patch v9.4.1.5

      • Fix for the price rules rounding

      Patch v9.4.1.4

      • automatic creation for var/tmp 

      Patch v9.4.1.3

      • Products url for EE fixed

      Patch v9.4.1.2

      • Qty and Is in Stock filters fixed
      • Useless Javascript content removed on preview box

      Patch v9.4.1.1

      • Qty and Is in Stock filters fixed

      9.4.0

      Improvement

      • New PHP API + better documentation for developers

      Patch v9.4.0.8

      • Fix on the dates retrieved by {G:SALE_PRICE} 

      Patch v9.4.0.7

      • Fix for the {G:PROMOTION_ID} tag

      Patch v9.4.0.6

      • Default value for the url type preference set to "short product urls"

      Patch v9.4.0.5

      • Fix for the price rules rounding

      Patch v9.4.0.4

      • automatic creation for var/tmp 

      Patch v9.4.0.3

      • Products url for EE fixed

      Patch v9.4.0.2

      • Qty and Is in Stock filters fixed
      • Useless Javascript content removed on preview box

      Patch v9.4.0.1

      • Qty and Is in Stock filters fixed

      9.3.2

      Bug fix:

      • Minor fix on Special Price To Date

      Patch v9.3.2.2

      • Default value for the url type preference set to "short product urls"

      Patch v9.3.2.1

      • automatic creation for var/tmp 

      9.3.1

      Minor fix:

      • End dates for the special prices defined as one minute before midnight : yyyy-mm-ddT23:59+/-hh:mm
         

      Patch v9.3.1.2

      • Default value for the url type preference set to "short product urls"

      Patch v9.3.1.1

      • automatic creation for var/tmp 

      9.3.0

      New feature

      • The url attribute can receive the currency code as a url's parameter to display the page with a specific currency, by example :
        <link>{url}?currency=your_currency_code</link>

      Patch v9.3.0.2

      • Default value for the url type preference set to "short product urls"

      Patch v9.3.0.1

      • automatic creation for var/tmp 

      9.1.1

      Bug fix

      • Correction of the error report display

      Patch v9.1.1.2

      • Default value for the url type preference set to "short product urls"

      Patch v9.1.1.1

      • automatic creation for var/tmp 

      9.1.0

      Improvement

      • New management of licenses

      9.0.2

      Patch:

      • Compatibility fix for Magento Security Patch SUPEE 6788

      9.0.1

      Bug fix

      • Fix on Magic attributes

      Patch:

      • Compatibility fix for Magento Security Patch SUPEE-6285

      9.0.0

      New feature

      • Reports on the data feed errors and warnings
      • Cron tasks generation reports
      • New XML templates
      • New Magic attributes
      • New filters according to the parent and/or to the child categories

      Improvement

      • Code refactoring
      • Multiple selection of filters 
      • Cron tasks notification in the admin
      • Real time generation progress
      • Optimized management of custom options

      Bug fix

      • Fix on JS code
      • Fix on the Type As You Search option

      8.1.0

      Improvement

      • New Magic attribute for Google Merchant Promotions V1.0.0
      • New observer in the configuration tab
      • Filters list enhanced

      Bug fix

      • Misprint fix

      8.0.0

      New feature

      • Google Product categories auto completion
      • New filters (Attribute sets, IDs)
      • File creation report (time, memory usage and item number)
      • Use of the category path in urls
      • New options for the {categories} attribute
      • Full support of all php options
      • Attributes library
      • Check on the errors directly from the console

      Improvement

      • Optimized interface
      • New management of scheduled tasks
      • Fully support of custom options
      • Invalid characters automatically deleted
      • Multiple selection with the IN filter
      • Combination of several attributes

      Bug fix

      • Check on the quantity of children products for {is_in_stock}
      • Fix on the VAT calculation for prices including more than 2 decimals

      7.3.0

      Improvement

      • Compatibility with Magento 1.8.0

      7.2.0

      Improvement

      • Template updated with the latest Google's requirements
      • New support for the {is_in_stock} attribute: additional 3rd option for backorderable products
      • Performance improvement

      Bug fix

      • Fix on MySQL url rewrites

      7.1.0

      Improvement

      • Code refactoring

      7.0.2

      Improvement

      • Compatibility support enhancement

      7.0.1

      New feature

      • New configuration options (memory limit, error reporting...)
      • Option to include the categories that are not visible in the menu

      Bug fix

      • Fix on JS code

      7.0.0

      New feature

      • Data feed real-time preview
      • Syntactic debugger

      6.1.1

      Bug fix

      • Fix on the category filter process
      • Fix on the advanced attributes filter

      6.1.0

      New feature

      • Include or exclude categories from the data feed
      • New advanced filters
      • New special attribute for catalog price rules: {price_rules}

      Improvement

      • Possibility to increase the number of advanced filters
      • New categories tab formatting

      6.0.0

      New feature

      • New scheduled tasks
      • New advanced settings

      Bug fix

      • Fix on JS code

      5.7.4

      Bug fix

      • Minor fix

      5.7.3

      New feature

      • New filter for Google product types

      5.7.2

      Bug fix

      • Minor fix on attributes
      • Fix on urls requests

      5.7.1

      Improvement

      • Improved management of is_in_stock
      • Default value retrieved if sc:description is null
      • Update of sales_effective_date

      Bug fix

      • Minor fix on JS code

      5.7.0

      New feature

      • New option to remove all non-UTF8 characters
      • Duplication and auto-completion of the category mapping (END and INSERT)

      5.6.0

      Bug fix

      • Fix on the Stock In The Channel description

      5.5.2

      Bug fix

      • Fix on SQL request
      • Minor fix on attributes

      5.5.1

      Bug fix

      • Minor fix on SQL request

      5.5.0

      New feature

      • Cron job reporting by email
      • Error reporting improved in the controller
      • New attributes: url, uri, host

      Improvement

      • Categories levels enchanced

      5.4.3

      Improvement

      • Compatibility with Magento >=1.4 for price_index

      5.4.2

      New feature

      • New attributes: min_price, max_price, tier_price

      Bug fix

      • Minor fix on the {G:PRODUCT_REVIEW} attribute

      5.4.1

      Bug fix

      • Fix on the special_price attribute
      • Minor fix on JS code

      5.4.0

      New feature

      • Adjustment of the qty attribute for configurable products
      • Stock calculation for configurable products from simple variants

      Bug fix

      • Fix on the attribute labels management (when no value)

      5.3.0

      Improvement

      • Improved tree view in the Filters tab
      • Enhancement of the select attributes according to the store view

      5.2.0

      New features:

      • Category tree view
      • New cron task tab for each data feed

      Bug fix

      • Minor fix on the new VAT calculation
      • Fix on JS code

      5.1.0

      New feature

      • New VAT calculation with ISO codes

      Improvement

      • Improvement of the [strip_tags] option

      Bug fix

      • Fix on JS code

      5.0.0

      New feature

      • New mapping option for Google categories

      4.8.1

      New feature

      • New syntactic coloration
      • New parent attributes to retrieve config, bundle and grouped products info
      • Available filter on grouped products

      Improvement

      • Syntactic coloration on Magic attributes and on options

      4.7.2

      Improvement

      • Enhancement of the products categorizations

      4.7.1

      New feature

      • Possibility to split the SQL for large files
      • Version of the extension included in the final license

      Improvement

      • The [parent] option retrieves the parent url only if it exists for {url} and {uri}

      4.6.1

      New feature

      • New attribute: {G:ITEM_GROUP_ID}
      • New option for {url} and {url}: [parent] retrieves the information of the parent product

      4.5.1

      New feature

      • New option for {G:PRODUCT_TYPE} and {categories}
      • New attribute: final_price

      Improvement

      • All price attributes are added by default

      Bug fix

      • Fix on bundle prices calculation

      4.3.2

      Improvement

      • Code refactoring

      Feature request

      Specific needs or any ideas of enhancements and new features to add to the extension? Tell us more, we'll get back to you shortly!

      Thank you

      That’s a wrap.

      We will get back to you as soon as possible.

      You may also like