ATG Recommendations Catalog Format Guide

Catalog Delivery

XML catalogs should be submitted via FTP at ftp.cleverset.com using the same username and password you use on our Retailer Site (http://recmanager.estara.com).

Catalog Formatting

ATG Recommendations presently accepts the Google Base Bulk Upload Format in XML (RSS 2.0) format.

To be well-formed XML, a catalog must extend the RSS 2.0 standard. It must also group all product information within <rss> and <channel> blocks.

Your file must look like this:
<?xml version="1.0"?>
<rss version="2.0" xmlns:g="http://base.google.com/ns/1.0" xmlns:c="http://base.google.com/cns/1.0">
  <channel>

    Your Product Information Goes Here

  </channel>
</rss>

Individual products may then be inserted inside <item> tags. All data inside an <item> block must be within appropriate definition tags. There are tags within all three defined namespaces which you may wish to utilize.

A list of fields that ATG Recommendations expects and their corresponding XML tag follows.
The format is <tag>ATG attribute</tag>.

Required:
  • <title>title</title>
  • <description>description</description>
  • <link>link</link>
  • <g:id>id</g:id>
  • <g:image_link>image_link</g:image_link>
  • <g:price>price</g:price>

Recommended:
  • <g:category>category</g:category>
  • <g:brand>brand</g:brand>
  • <g:instock>instock</g:instock>
  • <g:quantity>quantity</g:quantity>
  • <c:recommend type="string">recommend</c:recommend>
  • <c:sku type="string">sku</c:sku>
  • <c:tags type="string">tags</c:tags>
  • <c:related type="string">related</c:related>
  • <c:recommended type="string">recommended</c:recommended>

So an example file with only one product and only the required information would look like:
<?xml version="1.0"?>
<rss version="2.0" xmlns:g="http://base.google.com/ns/1.0" xmlns:c="http://base.google.com/cns/1.0">
  <channel>

    <item>
      <title>Blue Jeans</title>
      <description>A rugged pair of pants</description>
      <link>http://mystore.com/clothes/mens/pants/bluejeans.html</link>
      <g:id>43920</g:id>
      <g:image_link>http://mystore.com/images/bluejeans.jpg</g:image_link>
      <g:price>$50.00</g:price>
    </item>

  </channel>
</rss>

Required Fields

There are six attributes that must be included for every product in the catalog feed.

  • title – The product’s name or title as it appears on the product page.
  • description – The product’s description as it appears on the product page.
  • link – The full URL of the product page (including ‘http://’).
  • id – A unique identifier, preferably a number. e.g. The product’s SKU
  • image_link – The full URL of the product image (including ‘http://’).
  • price – The product’s price. This must match the price listed on your site.

Optional Fields

Ideally, retailers should also pass as many as seven additional attributes.

  • category – The product’s category structure on your site. Use a ‘>’ to separate category levels. e.g. Clothes>Mens>Pants
  • brand – The brand of the product.
  • instock – Whether or not this product is in stock (‘Y’ or ‘N’).
  • quantity – The number of products available.
  • recommend – Whether or not to recommend this product (‘Y’ or ‘N’).
  • sku – The SKU of the product. A SKU is a custom identifier used by some retailers.
  • tags – A comma-separated list of tags, or keywords, associated with the product. For example, a T-Shirt might have the tags ‘short sleeve,blue,men’s,outdoor’
  • related – A comma-separated list of product Ids (taken from the same catalog) closely related to this product.
  • recommended – A comma-separated list of product Ids (taken from the same catalog) that have been hand-selected to be recommended with this product.

Getting the Most Out of Your Catalog

Additional product information makes recommendations smarter! ATG Recommendations uses this data to make stronger targeted Recommendations and provide additional Recommendations functionality. The more data you supply, the better Recommendations work, and the easier we can provide you with features like:
  • brand exclusivity rules
  • same-category recommendations
  • category filtering
  • cross-selling
  • and more!

Documentation
Quick Start Guide
Catalog Format
Renderers
Flavors
Optimizing Revenue
Handling non-Product Pages
Multiple Recommendations
Fail Over
License & OSS Attributions
Demo Site

Tools
ATG Recommendations Helper Plugin

Have questions?