Release: Amazon E-Commerce Service on 2007-02-22

Release Notes>Product Advertising API>Release: Amazon E Commerce Service on 2007 02 22
This release introduces expanded functionality, including the support for batch requests when the ItemId is an EAN (European Article Number), and, in the JP locale, the return of loyalty points information through the Offers response group. Some functionality has been deprecated with this release, including support for the Restaurant index and spell checking in certain locales and search indices.

Details

Submitted By: Craig@AWS
Created On: February 23, 2007 10:39 PM GMT
Last Updated: February 24, 2007 2:13 AM GMT

These release notes provide a summary of all New Features, Resolved Issues, Other Issues, and Known Issues in the latest version of Amazon's E-Commerce Service (ECS). For changes made in previous ECS versions, go to http://aws.amazon.com/resources.

Release Date: 2007-02-22
Latest WSDL/API Version: 2007-02-22

New Features

The following table describes the new features found in this release.

Applies
To

Feature
Description
US X

ECS now supports batch requests when the ItemId is an EAN (European Article Number), ISBN (International Standard Book Number), or ASIN (Amazon Standard Item Number ).

In the past, ECS supported batch requests only when the ItemId was an ASIN. ECS now supports batch requests when the ItemId is an EAN (European Article Number), ISBN (International Standard Book Number), or ASIN (Amazon Standard Item Number ). The batch size is limited to ten items.
CA X
DE X
FR X
JP X
UK X
US  

In the JP locale, loyality points are now returned by the Offers response group.

In the JP locale, loyality points are being used to generate sales. To support this effort, the Offers response group now returns loyality points.
CA  
DE  
FR  
JP X
UK  
US X

Amazon no longer supports the Restaurant search index.

In the past, the US locale supported the Restaurant search index, which returned restaurant information in select cities. This search index is no longer supported by Amazon. Consequently, ECS can no longer support this search index. There is no alternate way to obtain this information using ECS.

The ItemSearch parameters cuisine, city, and neighborhood, which were used in conjunction with the Restaurant search index will be deprecated over time. Currently, there is no use for these parameters.

CA  
DE  
FR  
JP  
UK  

Resolved Issues

The following table describes the issues resolved in the latest release of ECS.

Applies
To

Issue
Resolution
US X

Documentation clarification: Customer and seller location information is returned only when customers and sellers have entered this information.

In the previous release, the release notes stated that CustomerContentLookup and SellerLookup responses contained customer and seller location information. This is true only in the US locale and only when customers and sellers have entered this information. Often, customers and sellers do not enter this information. In those cases, this information cannot be returned by CustomerContentLookup and SellerLookup.

CA  
DE  
FR  
JP  
UK  

Other Issues

Applies
To

Change
Description
US X

Adding items to a cart using ASINs is being deprecated.

Currently, you are able to add items to a cart by specifying their ASINs or OfferListingIds. Using ASINs to add items to carts is being deprecated. As of July 30, 2007, you will no longer be able to use ASINs to add items to carts. Instead, you should use an OfferListingId to add an item to a cart.
CA X
DE X
FR X
JP X
UK X
US X

Response limit of 400 pages (4000 items) will be enforced in all locales.

Some ECS operations return less than 400 pages of results. For example, an ItemSearch request that uses a SearchIndex value of "All" will only return 5 items.

Many ECS operations, however, such as ItemSearch, return up to 400 pages of items. On each page there can be up to 10 items. Starting with this release the 400 page limit that has been in place for the US locale will now be enforced in all other locales.

CA X
DE X
FR X
JP X
UK X
US X

Amazon no longer supports in-store pickup (ISPU) of items.

In the past, you could use the DeliveryMethod parameter in several ECS operations to specify how the customer would receive their item. The values were "Ship," the default, and "ISPU." Amazon no longer supports ISPU. Consequently, ECS does not as well. If you set DeliveryMethod to "ISPU," ECS will not return an error but it will not return data.

Response elements , such as ISPUStoreAddress, ISPUStoreHours, and ISPUPostalCode, which supported in-store pickup of items will not be returned anymore.

CA  
DE  
FR  
JP  
UK  
US X

ItemSearch no longer supports spelling correction in some search indices.

If a Keyword value in an ItemSearch request does not yield results, ItemSearch proposes different spellings of the Keyword value. This functionality no longer works for some search indices in specific locales. The following list shows which search indices per locale no longer support spelling correction.

DE

Electronics, HealthPersonalCare , HomeGarden, Kitchen, OutdoorLiving, PCHardware, Photo, Software, SoftwareVideoGames, SportingGoods, Tools, Toys, VideoGames

FR

Electronics, Software, SoftwareVideoGames, VideoGames

JP

Electronics, HealthPersonalCare, Kitchen, Software, SportingGoods, Toys, VideoGames

UK

Electronics, HealthPersonalCare, HomeGarden, Kitchen, OutdoorLiving, Software, SoftwareVideoGames, Tools, Toys, VideoGames

CA X
DE X
FR X
JP X
UK X

Known Issues

The following issues describe irregular behavior seen in ECS 4.0 functionality:

IssueDescriptionImpact
The EAN field does not support ISBN-13 in the JP locale. ISBN numbers have increased to 13 digits. This is larger than it was before. The existing EAN field can hold 13 digits. ItemSearch requests using the EAN field this way, however, return inaccurate results. JP locale ItemSearch requests that use the EAN field for the ISBN number. The workaround is to use the ISBN IdType parameter in an ItemLookup request where the ItemId is an ISBN number of a book. The ISBN value works only with the books search index.
ItemSearch using BrowseNodes when the search index is PetSupplies does not work correctly. A search index is required with every ItemSearch request. Results are inaccurate when the BrowseNodes parameter is also used in such a request. PetSupplies is a subset of the Kitchen search index, which does return accurate results. The work around is to use the Kitchen search index instead of PetSupplies.
The BrowseNodeLookup operation often returns inaccurate results for top sellers when the browse node in the request is the root node of a category. BrowseNode lookup is often used to find the top seller in the browse node category. When the browsenode is at the top of the category, the top sellers list is inaccurate. When trying to find top sellers in a root browse node. The workaround is to use one of the child browse nodes with the TopSellers response group.
Some of the browse node IDs listed in the ECS Developer Guide are out of date. Browse nodes are dynamic and can change during the course of a book's publication. For this reason, you should always validate a browsenode number before using it. When trying to use browse node IDs for various reasons.
The ListFull and ListInfo response groups sometimes return an incorrect value for TotalItems. The discrepancy arises when the response sometimes includes invalid ASINs as part of the total. Applications trying to use TotalItems programmatically can run into problems.
Items returned by ItemSearch may have prices that fall outside of the range specified by MaximumPrice and MinimumPrice. The ItemSearch parameters, MaximumPrice and MinimumPrice, should limit the items returned according to the specified price range. Sometimes, items are returned whose prices fall outside of the specified range. ItemSearch requests that use both MaximumPrice and MinimumPrice.
ItemSearch requests based on Actor or Director return the same results. The source data in the database does not distinguish between actors and directors. ItemSearch requests based on Actor or Director.
Salesrank values in the CA and EU locales do not match the values returned by the retail web site in those locales. Salesrank values given by ECS and Amazon's retail web site differ from those given, at times, in the CA and EU locales. ItemSearch requests that are sorted by Salesrank.
Not all parent browse nodes are returned by BrowseNodeInfo.

The response group, BrowseNodeInfo, used in BrowseNodeLookup requests returns the child and parent browse nodes of the browse node specified in the request. When a browse node has multiple parents, however, only one of the parent browse nodes is returned in the response. That is why there might be a difference between the ECS response and the result displayed on Amazon’s retail web site. BrowseNodeInfo returns the entire lineage of both child and parent browse nodes. For example, in the following response snippet, the parentage of the browse node in the request, Social Sciences, is traced all the way up the browse node tree to the root browse node, Books. Also, all of the children of the node, Social Sciences, are returned. For the sake of brevity, the following response snippet shows only some of the returned child browse nodes.

<Item>
<ASIN>0131856340</ASIN>
-<BrowseNodes>
  -<BrowseNode>
   <BrowseNodeId>11232</BrowseNodeId>
   <Name> Social Sciences</Name>
     -<Ancestors>
      -<BrowseNode>
      <BrowseNodeId>53</BrowseNodeId>
      <Name>Nonfiction</Name>
      -<Ancestors>
       -<BrowseNode>
       <BrowseNodeId>1000</BrowseNodeId>
       <Name>Subjects</Name>
      -<Ancestors>
        -<BrowseNode>
        <BrowseNodeId>283155</BrowseNodeId>
        <Name>Books</Name>
      </BrowseNode>
    </BrowseNode>
  </BrowseNode>
- <Children>
  - <BrowseNode>
      <BrowseNodeId>11233</BrowseNodeId>
      <Name>Anthropology</Name>
    </BrowseNode>
  - <BrowseNode>
      <BrowseNodeId>11242</BrowseNodeId>
      <Name>Archaeology</Name>
    </BrowseNode>
  - <BrowseNode>
      <BrowseNodeId>3048861</BrowseNodeId>
      <Name>Children's Studies</Name>
    </BrowseNode>
  </Children>
</BrowseNodes>

Notice that all of the nodes in the response show only one parent node, for example, the parent node of Social Sciences is Nonfiction. Only a single parent node would be returned even if a node had multiple parents.

BrowsenodeLookups that attempt to work "up" the browsenode hierarchy.
Items sorted by salesrank are returned out of order. In an ItemSearch request where Sort=salesrank, you would expect the items to be returned in order of their sales rank from best (1) to worst (large number). The sales rank values for items change frequently. The ECS sales rank updates lag behind the sales rank updates on the retail web site. So, in an ItemSearch request, although the sales rank numbers are out of order in the ECS response, the items are, in fact, ordered according to the sales rank computed on the retail web site. In this way, the sales rank order of items returned by ECS and Amazon’s retail web site. match. One alternative in the US locale is to use the TopSellers response group to get the top 10 bestsellers. Those items are returned in order. ItemSearch requests that are sorted by Salesrank.
ItemSearch power searches sometimes return different results when the sort parameter is specified versus when it is not specified. Submitting the same request twice, once with and once without the sort parameter, potentially returns different sets of results. ItemSearch power searches.
The parameter, pubdate, which is used in ItemSearch Power searches is not working correctly. This parameter sometimes does not return results for the specified pubdate value when it should. ItemSearch power searches that use pubdate.
Changing access to lists often requires up to twenty-four hours to take effect. Only lists made public by a customer are returned by ListSearch. A customer can change access restrictions on their lists. There is a lag time between that change and the time when others can or cannot (depending on the change in permissions) access that list. Doing ListSearch requests within 24 hours of a change in access permissions.
Relevancy rank does not work with blended searches. Relevancy rank generally corresponds with sales rank. Currently, the relevancy rank using ItemSearch blended searches yields inaccurate results. ItemSearch requests where the SearchIndex is "Blended" and the sort parameter is relevancy.
Updating the availability status of some items takes exceptionally long. There is a lag time incurred for the availability status of an item to be updated. For a few items in each Search Index, however, those lag times are exceptionally long.  These lag times account for inaccurate availability information, even when the ItemSearch parameter, Availability, is set to "Available." To check the true availability of an item, use the Offers Response Group. If an offer is returned for an item, it is truly available. Requests that list the availability of items in the response.
GZIP functionality not working. XML responses are not GZIP'ed, even if the proper Accept-Encoding header is sent with the request. Requests that stipulate a GZIP'ed response.
The total number of pages returned from a search request decreases as you page through the results. To optimize search results, grouping of similar items is not done until the items are viewed. When the items are viewed and the grouping occurs, the page count shrinks. Applications or web sites that make use of the TotalPages element.
Relevancy score values are sometimes unexpected. Relevancy scores are, in part, determined by the number of occurrences of a word. This algorithm can sometimes lead to unexpected results. For example, while you might expect "laptop" to be most relevant to Computers category, the relevancy score is higher in "Sporting Goods" because the word "laptop" occurs there more often, for example, in phrases such as "laptop bag." ItemSearch requests sorted by relevancy.
In cart operations, validation is not performed on ListItemId. Validation is not performed in some cart operations. It is possible, for example, for the ListItemId not to correspond to the ASIN. Adding items to cart from a list using a ListItemId.
MerchantId does not always filter search results. MerchantId is not used in books, music, classical, video, wireless, DVD, communities, wish lists, Target, and all international stores. MerchantId cannot be used as a filter for any of these groups. Doing so might lead to unexpected results, such as items being sold by some merchant other than the one specified by the MerchantId. ItemSearch requests that use MerchantId.
SellerLookup sometimes does not return the Seller Name or correct location. Results from the SellerLookup operation may not return the SellerName element or return the correct Location values. Applications or web sites that use the SellerName or Location values.
ItemLookup does not return some editorial reviews. ItemLookup only returns the editorial reviews written by Amazon.com. Editorial reviews recorded by another web site cannot be included in the reviews returned by ItemLookup.
Items returned using the PCHardware search index may not be hardware. Using the PCHardware search index with the ItemSearch operation returns non-hardware items.  
ItemSearch Power requests do not return accurate results for specific dates. ItemSearch responses may be incorrect when the request specifies a specific day. Using date ranges returns expected results. ItemSearch Power requests that specify specific dates.
WishList is returned even when ListType=WeddingRegistry. In ListLookup, when you set ListType to “WeddingRegistry,” the operation returns both a WeddingRegistry and, unexpectedly, a WishList. Both lists are based on the same ListId. When you set ListType to “WishList,” ListLookup only returns a WishList, which is correct. ListLookup requests that set ListType to "WeddingRegistry."
ReleaseDate not returned for some items. Some items, such as DVDs, do not have release dates. Sorting by release date, then, sometimes generates spurious results. Applications or web sites that use the ReleaseDate element.

Phrases in quotes used as values for the Keywords parameter in ItemSearch requests do not perform as expected.

Quoted phrases in the Keywords field for ItemSearch are not accepted as a whole phrase. Instead, they are broken up into individual terms and results are returned for subsets of the phrase. For example, the parameter Keywords="the last time" should only return results for "the last time", rather than "the", "last" or "time". ItemSearch requests that use phrases for Keyword values. Instead, use the TextStream parameter.
Default input content encoding is not UTF-8. JP is the only locale that correctly takes UTF8 input. All other locales use LATIN1. Applications dependent on UTF8.
ItemSearch using TextStream may not work for all search indices.

Some search indices, such as, Tools, Software, and Jewelry, do not work in ItemSearch requests using the TextStream parameter.

Applications or web sites that use the TextStream parameter.

To receive notification of future releases automatically, go to http://developer.amazonwebservices.com/connect/ann.jspa?annID=64.

Related Documents

©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.